[opensuse] Virtualbox+bridged network+Network manager
Hi, I'm having all kind of issues with VMware Server on Opensuse 11.0 and decided to use VirtualBox, the only issue is that it doesn't handle bridged networks automagically and NetworkManager has to be disabled. Having seen the xen bridge schema on sles|opensuse, is it possible to adapt it to work with VirtualBox?, that way the physical interface will be renamed as peth0 and the bridged interface will take the eth0 name, that way NetworkManager should see it and work as a usual. Any thoughts? Regards, Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ciro Iriarte wrote:
Hi, Hi, I'm having all kind of issues with VMware Server on Opensuse 11.0 and decided to use VirtualBox, the only issue is that it doesn't handle bridged networks automagically and NetworkManager has to be disabled.
Having seen the xen bridge schema on sles|opensuse, is it possible to adapt it to work with VirtualBox?, that way the physical interface will be renamed as peth0 and the bridged interface will take the eth0 name, that way NetworkManager should see it and work as a usual.
Any thoughts?
Well, I do not use NetworkManager on my VirtualBox Machine. But my system is setting up all network needs automatically. If you have hit any kind of problem I may be able to help you by providing all steps and configuration files. Just say what your problem is.
Regards,
Regards,
Ciro
Rui -- Rui Santos http://www.ruisantos.com/ Veni, vidi, Linux! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/11/4 Rui Santos <rsantos@ruisantos.com>:
Ciro Iriarte wrote:
Hi, Hi, I'm having all kind of issues with VMware Server on Opensuse 11.0 and decided to use VirtualBox, the only issue is that it doesn't handle bridged networks automagically and NetworkManager has to be disabled.
Having seen the xen bridge schema on sles|opensuse, is it possible to adapt it to work with VirtualBox?, that way the physical interface will be renamed as peth0 and the bridged interface will take the eth0 name, that way NetworkManager should see it and work as a usual.
Any thoughts?
Well, I do not use NetworkManager on my VirtualBox Machine. But my system is setting up all network needs automatically. If you have hit any kind of problem I may be able to help you by providing all steps and configuration files. Just say what your problem is.
Regards,
Regards,
Ciro
Rui
Hi, the issue is not within the VM. I would like to setup bridged network for the VMs and still be able to use NetworkManager on the physical host. Regards, Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ciro Iriarte wrote:
2008/11/4 Rui Santos <rsantos@ruisantos.com>:
Ciro Iriarte wrote:
Hi,
Hi,
I'm having all kind of issues with VMware Server on Opensuse 11.0 and decided to use VirtualBox, the only issue is that it doesn't handle bridged networks automagically and NetworkManager has to be disabled.
Having seen the xen bridge schema on sles|opensuse, is it possible to adapt it to work with VirtualBox?, that way the physical interface will be renamed as peth0 and the bridged interface will take the eth0 name, that way NetworkManager should see it and work as a usual.
Any thoughts?
Well, I do not use NetworkManager on my VirtualBox Machine. But my system is setting up all network needs automatically. If you have hit any kind of problem I may be able to help you by providing all steps and configuration files. Just say what your problem is.
Regards,
Regards,
Ciro
Rui
Hi, the issue is not within the VM. I would like to setup bridged network for the VMs and still be able to use NetworkManager on the physical host.
That was what I asked. If NetworkManager is a must have for you... then I cannot help you. Sorry.
Regards, Ciro
-- Rui Santos http://www.ruisantos.com/ Veni, vidi, Linux! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/11/4 Rui Santos <rsantos@ruisantos.com>:
Ciro Iriarte wrote:
2008/11/4 Rui Santos <rsantos@ruisantos.com>:
Ciro Iriarte wrote:
Hi,
Hi,
I'm having all kind of issues with VMware Server on Opensuse 11.0 and decided to use VirtualBox, the only issue is that it doesn't handle bridged networks automagically and NetworkManager has to be disabled.
Having seen the xen bridge schema on sles|opensuse, is it possible to adapt it to work with VirtualBox?, that way the physical interface will be renamed as peth0 and the bridged interface will take the eth0 name, that way NetworkManager should see it and work as a usual.
Any thoughts?
Well, I do not use NetworkManager on my VirtualBox Machine. But my system is setting up all network needs automatically. If you have hit any kind of problem I may be able to help you by providing all steps and configuration files. Just say what your problem is.
Regards,
Regards,
Ciro
Rui
Hi, the issue is not within the VM. I would like to setup bridged network for the VMs and still be able to use NetworkManager on the physical host.
That was what I asked. If NetworkManager is a must have for you... then I cannot help you.
Sorry.
Regards, Ciro
-- Rui Santos http://www.ruisantos.com/
Veni, vidi, Linux!
--
Never mind, can you specify hoy do you handle tap devices creation automatically?, custom scripts?. Regards, Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/11/4 Ciro Iriarte <cyruspy@gmail.com>:
Never mind, can you specify hoy do you handle tap devices creation automatically?, custom scripts?.
Regards, Ciro
Oops $s/hoy/how/g Regards, Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Never mind, can you specify hoy do you handle tap devices creation automatically?, custom scripts?.
1) Defined my eth0 to ip 0.0.0.0 ( on YaST ). You can also comment your IP/NETMASK on /etc/sysconfig/network/ifcfg-eth0 2) On /etc/sysconfig/network/ifcfg-eth0 make sure you have LINK_OPTIONS='promisc on' 3) created a bridge device br0 ( on YaST ) and added eth0 as br0 member. br0 is now my "master" NIC. 4) added to tap's for my 2 virtual machines: "/usr/bin/VBoxAddIF tap0 username br0" ( you can also you -g groupname to add to all users ). Also added tap1 5) Added my username to vboxusers group 6) Now the only thing I did not find a easy way to do was that all tap devices need to be set to promiscue mode. SuSE let's you do this but, when vboxnet starts, it reconfigures the tap devices al leave them on a non promiscue state. Here is how I did it: 6.1) At /etc/ini.d/vboxnet search for: ifconfig "$interface" up 2> /dev/null 6.2) and replace it with ifconfig "$interface" up promisc 2> /dev/null Then just issue: ~# rcnetwork restart ~# rcvboxnet restart Also get additional hints at: http://en.opensuse.org/VirtualBox
Regards, Ciro
Rui -- Rui Santos http://www.ruisantos.com/ Veni, vidi, Linux! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/11/4 Rui Santos <rsantos@ruisantos.com>:
Never mind, can you specify hoy do you handle tap devices creation automatically?, custom scripts?.
1) Defined my eth0 to ip 0.0.0.0 ( on YaST ). You can also comment your IP/NETMASK on /etc/sysconfig/network/ifcfg-eth0 2) On /etc/sysconfig/network/ifcfg-eth0 make sure you have LINK_OPTIONS='promisc on' 3) created a bridge device br0 ( on YaST ) and added eth0 as br0 member. br0 is now my "master" NIC. 4) added to tap's for my 2 virtual machines: "/usr/bin/VBoxAddIF tap0 username br0" ( you can also you -g groupname to add to all users ). Also added tap1 5) Added my username to vboxusers group 6) Now the only thing I did not find a easy way to do was that all tap devices need to be set to promiscue mode. SuSE let's you do this but, when vboxnet starts, it reconfigures the tap devices al leave them on a non promiscue state. Here is how I did it: 6.1) At /etc/ini.d/vboxnet search for: ifconfig "$interface" up 2> /dev/null 6.2) and replace it with ifconfig "$interface" up promisc 2> /dev/null
Then just issue: ~# rcnetwork restart ~# rcvboxnet restart
Also get additional hints at: http://en.opensuse.org/VirtualBox
Regards, Ciro
Rui
Hi, thanks a lot for the info. Meanwhile found a way to use NetworkManager :D According to the documentation of VirtualBox you can specify script for automatic tap creation/deletion. Using that (with kdesu -t -c <command>) and previously running network-bridge from xen-tools (which renames eth# to peth# and the bridge to eth#), I can use bridging with VirtualBox and I am still able to use NM!!. For general use one would run /etc/xen/scripts/network-bridge at some point of the boot process, but as I sometimes use xen (which already runs this) I prefer to run it manually (once) before launching VirtualBox. Regards, Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El Martes 04 Noviembre 2008 Rui Santos escribió:
Ciro Iriarte wrote:
Hi, Hi, I'm having all kind of issues with VMware Server on Opensuse 11.0 and decided to use VirtualBox, the only issue is that it doesn't handle bridged networks automagically and NetworkManager has to be disabled.
Having seen the xen bridge schema on sles|opensuse, is it possible to adapt it to work with VirtualBox?, that way the physical interface will be renamed as peth0 and the bridged interface will take the eth0 name, that way NetworkManager should see it and work as a usual.
Any thoughts?
Well, I do not use NetworkManager on my VirtualBox Machine. But my system is setting up all network needs automatically. If you have hit any kind of problem I may be able to help you by providing all steps and configuration files. Just say what your problem is.
Regards,
Regards,
Ciro
Rui
-- Rui Santos http://www.ruisantos.com/
Veni, vidi, Linux!
Hi I use ifup.d hooks for notify vmware wrk on networkmanager changes (just iface up/down events) By the way also managed to notify vmware of suspend/resume events to properly hibernate VMs on lid close (hibernation of my laptop) -- Agua para todo? No, Agua para Todos. ->>----------------------------------------------- Clist UAH a.k.a Angel ---------------------------------[www.uah.es]-<<-- "Ninja, muerto de hambre en Oklahoma que se queda con tu nómina en menos de 15 segundos. Hipotecas Subprime para Dummies." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/11/4 Angel Alvarez <clist@uah.es>:
El Martes 04 Noviembre 2008 Rui Santos escribió:
Ciro Iriarte wrote:
Hi, Hi, I'm having all kind of issues with VMware Server on Opensuse 11.0 and decided to use VirtualBox, the only issue is that it doesn't handle bridged networks automagically and NetworkManager has to be disabled.
Having seen the xen bridge schema on sles|opensuse, is it possible to adapt it to work with VirtualBox?, that way the physical interface will be renamed as peth0 and the bridged interface will take the eth0 name, that way NetworkManager should see it and work as a usual.
Any thoughts?
Well, I do not use NetworkManager on my VirtualBox Machine. But my system is setting up all network needs automatically. If you have hit any kind of problem I may be able to help you by providing all steps and configuration files. Just say what your problem is.
Regards,
Regards,
Ciro
Rui
-- Rui Santos http://www.ruisantos.com/
Veni, vidi, Linux!
Hi
I use ifup.d hooks for notify vmware wrk on networkmanager changes (just iface up/down events)
By the way also managed to notify vmware of suspend/resume events to properly hibernate VMs on lid close (hibernation of my laptop)
-- Agua para todo? No, Agua para Todos. ->>----------------------------------------------- Clist UAH a.k.a Angel ---------------------------------[www.uah.es]-<<-- "Ninja, muerto de hambre en Oklahoma que se queda con tu nómina en menos de 15 segundos. Hipotecas Subprime para Dummies."
Well, I read nothing about ifup.d. About VMware, tried Server 1.0.7 and 2.0.0, after some time the VM didn't start anymore and there was a vmx process eating 100% of CPU. Also there where many crashes of vmware-server-console while stopping the VM. On 10.2 everything worked just fine, this only happens on 11.0. Regards, Ciro
participants (3)
-
Angel Alvarez
-
Ciro Iriarte
-
Rui Santos