Moozer,
I'm running into a similar issue, also in the simulation of large
network topologies. I think Libvirt will make more sense for these as well.
That being said, Libvirt also has some real benefits for parallelization
which come into play for larger simulations so me being forced to use it
isn't the end of the world I suppose. I found the vagrant-serial plugin to
be busted in my experimentation with it as well.
-Eric
On Wednesday, August 5, 2015 at 9:11:43 AM UTC-4, Big Moozer wrote:
>
> I am using the libvirt plugin. It works.
> https://github.com/pradels/vagrant-libvirt
>
> And I agree. It is not a feature that will be used much, but maybe someone
> finds the time and need to implement it :-)
>
> regard
> Moozer
>
>
>
> Den mandag den 3. august 2015 kl. 19.45.18 UTC+2 skrev dragon788:
>>
>> Hi Big Mozer,
>> What you are referring to as "missing" is probably a communicator plugin
>> utilizing the serial port as the console. It may be feasible to create a
>> plugin for it, but the demand is probably vanishingly small as most people
>> can easily use the networking options (NAT/Bridged/etc) to manage the VM
>> using a virtual network connection. If Libvirt supports it, I think there
>> is a vagrant plugin to manage libvirt machines, but I wouldn't be surprised
>> if Virtualbox and VMware don't support it, because they have been primarily
>> GUI driven tools, and only been slowly that there have been more "power
>> user" options to manage things via the command line and as headless
>> machines with only networking.
>>
>>
>>
>> On Tuesday, July 21, 2015 at 4:43:03 PM UTC-5, Big Moozer wrote:
>>>
>>> hi,
>>>
>>> Thanks for the suggestion.
>>>
>>> This plug-in maps a serial port on the guest to a tcp/ip port.
>>>
>>> I'm looking for a way not to depend on the actual networking of the
>>> guest.
>>>
>>> The console is used a lot in network equipment, so you are not dependent
>>> on ip addresses, firewall rules and such - so that is what I am aiming for.
>>> E.g. on a linux machine adding some kernel parameter
>>> console=tty0 console=ttyS0,115200n8
>>> allows you to access the console directly from the host's command line
>>> using something like
>>> $ virsh console <domain>
>>>
>>> This is how it works with Libvirt, I suppose Virtualbox has something
>>> similar.
>>>
>>> It just seems so possible with vagrant supporting both "vagrant ssh" and
>>> "vagrant rdp". There "just" seems to missing a file here:
>>> https://github.com/mitchellh/vagrant/tree/master/plugins/communicators
>>> and a "serial" command here
>>> https://github.com/mitchellh/vagrant/tree/master/plugins/commands
>>>
>>> Any way, thanks for taking an interest.
>>> Regards
>>> Moozer
>>>
>>>
>>> Den lørdag den 18. juli 2015 kl. 16.56.20 UTC+2 skrev Artem Yakimenko:
>>>>
>>>> Hi,
>>>>
>>>> It's a bit old, so not sure if it's working or not, but maybe that's
>>>> what you're looking for?:
>>>> https://github.com/7Pikes/vagrant-serial
>>>>
>>>> Cheers,
>>>> A.
>>>>
>>>> On Thursday, July 16, 2015 at 7:12:06 PM UTC+2, Big Moozer wrote:
>>>>>
>>>>> Hi all
>>>>>
>>>>> I want to do "vagrant up" and then access the console of the virtual
>>>>> machine using a serial connection.
>>>>> I am thinking something like doing "vagrant serial" instead of "vagran
>>>>> ssh" or "vagrand rdp".
>>>>>
>>>>> I found a discussion about it from 2011.
>>>>>
>>>>> https://groups.google.com/forum/#!searchin/vagrant-up/serial/vagrant-up/E3a_fY4n0L0/Xll6XCH18QkJ
>>>>>
>>>>> Is there any progress on this?
>>>>> Is it implemented?
>>>>> Are there plugins that can help with this?
>>>>>
>>>>> Any pointers will be appreciated.
>>>>>
>>>>> regards
>>>>> Moozer
>>>>>
>>>>
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/296e0cfc-6e95-4a56-bca6-5faf4cf1a0cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
