[opensuse-virtual] adding a xen guest takes down interface of existing guest??
My xen host is openSUSE 13.2. I have one guest running currently. I created a second guest to install 13.2 and ran "xl create". This appears to have brought down the interface (vif10) for the existing guest ?? 9: vif10: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 512 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff -- Per Jessen, Zürich (-0.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Per Jessen wrote:
My xen host is openSUSE 13.2.
I have one guest running currently. I created a second guest to install 13.2 and ran "xl create".
This appears to have brought down the interface (vif10) for the existing guest ??
9: vif10: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 512 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
I'm not certain but this seems to be related to me having chosen "vif10" and "vif11" as the interface names. On a second try, when I omitted the interface name for the new guest, the new interface was named "vif11.0" and did not interfere with vif10. -- Per Jessen, Zürich (-0.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Depends on how you configured your "interface." The following command should display its details brctl show vig10 You should also describe how you created your interface... When you configure virtual networks (for your virtual networking) you should not configure and assign physical interfaces for your Guests. You should instead create Linux Bridge Devices as virtual devices which can be assigned to a physical interface. A variety of tools can be used to create Linux Bridge Devices including YAST, libvirt (vm manager), brctl, virsh, even GUI managers from other virtualization technologies like VMware, VBox, etc because once a LBD has been created in any way, the LBD can be used by any Guest using any virtualization, and any number of Guests. And, if you're using LBD the name is irrelevant. If you're configuring a real, physical interface then like practically any other use of a real, physical device the device most likely can be used by only one OS (Guest, Host, whatever). Tony On Tue, Feb 3, 2015 at 2:41 AM, Per Jessen <per@opensuse.org> wrote:
Per Jessen wrote:
My xen host is openSUSE 13.2.
I have one guest running currently. I created a second guest to install 13.2 and ran "xl create".
This appears to have brought down the interface (vif10) for the existing guest ??
9: vif10: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 512 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
I'm not certain but this seems to be related to me having chosen "vif10" and "vif11" as the interface names. On a second try, when I omitted the interface name for the new guest, the new interface was named "vif11.0" and did not interfere with vif10.
-- Per Jessen, Zürich (-0.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.
-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Tony Su wrote:
Depends on how you configured your "interface." The following command should display its details
brctl show vig10
Well, 'vif10' is created automagically when I run 'xl create'. # brctl show vif10 bridge name bridge id STP enabled interfaces vif10 can't get info Operation not supported The bridge device 'xenbr1': # brctl show xenbr1 bridge name bridge id STP enabled interfaces xenbr1 8000.0018fefc3ff2 no eth1 vif10 vif15.0
You should also describe how you created your interface...
standard openSUSE network config: # cat /etc/sysconfig/network/ifcfg-xenbr1 BOOTPROTO='static' BRIDGE='yes' BRIDGE_FORWARDDELAY='0' BRIDGE_PORTS='eth1' BRIDGE_STP='off' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
My xen host is openSUSE 13.2.
I have one guest running currently. I created a second guest to install 13.2 and ran "xl create".
This appears to have brought down the interface (vif10) for the existing guest ??
9: vif10: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 512 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
I'm not certain but this seems to be related to me having chosen "vif10" and "vif11" as the interface names. On a second try, when I omitted the interface name for the new guest, the new interface was named "vif11.0" and did not interfere with vif10.
I don't see your problem on an updated 13.2 Xen host. I started two PV domains with 'vifname=vif10' and 'vifname=vif11' in their respective 'vif = [...]' config. The vif device of the first domain (vif10) remains up and continues to work when starting the second domain containing vif11. Are your domains PV or HVM? Can you provide the vif config for the domains? Does /var/log/messages contain any hint about who (or what) is bringing down the vif? Regards, Jim -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Jim Fehlig wrote:
Per Jessen wrote:
Per Jessen wrote:
My xen host is openSUSE 13.2.
I have one guest running currently. I created a second guest to install 13.2 and ran "xl create".
This appears to have brought down the interface (vif10) for the existing guest ??
9: vif10: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 512 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
I'm not certain but this seems to be related to me having chosen "vif10" and "vif11" as the interface names. On a second try, when I omitted the interface name for the new guest, the new interface was named "vif11.0" and did not interfere with vif10.
I don't see your problem on an updated 13.2 Xen host. I started two PV domains with 'vifname=vif10' and 'vifname=vif11' in their respective 'vif = [...]' config. The vif device of the first domain (vif10) remains up and continues to work when starting the second domain containing vif11.
Interesting.
Are your domains PV or HVM?
They're PV.
Can you provide the vif config for the domains?
Typically : vif = [ 'vifname=vif10,bridge=xenbr1,mac=00:11:27:00:00:05' ]
Does /var/log/messages contain any hint about who (or what) is bringing down the vif?
Thanks for suggesting that, yes, there's quite a bit of output from /etc/xen/scripts/vif-bridge. I've put the log here: http://files.jessen.ch/airbus-vif10-log.txt I'm not sure, but this is what it looks like: at 11:19:41 I attempt to create a new guest, unfortunately without having changed the vifname in the config. It looks like this leaves vif10 disabled: Feb 3 11:19:43 airbus kernel: xenbr1: port 2(vif10) entered disabled state Feb 3 11:19:41 airbus root: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif10, bridge xenbr1. At 11:20:08 I've corrected my mistake and create the new guest with vifname=vif11. There's a bit of up and down, but vif10 remains down which I discover some time later. It is odd that an existing vif should be taken down just because I tried to create a new guest with the same vifname, but is it worth writing a bugreport for? -- Per Jessen, Zürich (-2.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
participants (4)
-
Jim Fehlig -
Per Jessen -
Per Jessen -
Tony Su