[Bug 210993] New: Booting a new XEN VM fails: "Error: Device 1 (vif) could not be connected. Hotplug scripts not working."
https://bugzilla.novell.com/show_bug.cgi?id=210993 Summary: Booting a new XEN VM fails: "Error: Device 1 (vif) could not be connected. Hotplug scripts not working." Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: Ulrich.Windl@rz.uni-regensburg.de QAContact: qa@suse.de When trying to install a new XEN VM from a network (NFS) source (as suggested), the VM cannot be created (YaST does not tell the reason to the user). It turns out that the message reads: Error: Device 1 (vif) could not be connected. Hotplug scripts not working. The line: vif = [ 'mac=00:16:3e:ff:3b:18,bridge=xenbr0', 'mac=00:16:3e:c0:92:08,bridge=xenbr1' ] causes that problem. If replaced with vif = [] the VM can be created, but then it cannot locate the installation source via NFS (naturally). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210993 cgriffin@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|cgriffin@novell.com |kallan@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210993 kallan@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Ulrich.Windl@rz.uni-regensburg.de ------- Comment #1 from kallan@novell.com 2006-10-09 16:34 MST -------
From the description, it appears that you are trying to create a custom VM that uses two network interfaces utilizing xenbr0 and xenbr1. Are both xenbr0 and xenbr1 up and running on domain 0 before trying to install the VM?
From domain 0, please provide the output from 'ifconfig' and 'ip route'. Also attach the config file used to create/install the VM.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210993 Ulrich.Windl@rz.uni-regensburg.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|Ulrich.Windl@rz.uni- | |regensburg.de | ------- Comment #2 from Ulrich.Windl@rz.uni-regensburg.de 2006-10-10 00:50 MST ------- Maybe it was a mis-understanding from my part: I thought the bridges were created as needed, but it seems only "xenbr0" is (and I'll have to do manual configuring and scripting). When pre-creating "xenbr1" as well, the vm did start. Still, the error message is very much confusing, because it's so unspecific. Also at the moment Dom0 only has one phhysical interface configured (peth0 in xenbr0). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210993 ------- Comment #3 from kallan@novell.com 2006-10-11 10:29 MST ------- The /etc/xen/xend-config.sxp file gives instructions on how to change the default behavior of Xen networking. To bring dom0 up with two NICs always configured, the /etc/xen/xend-config.sxp file needs to be modified to call out a different network script other than the default, network-bridge. Change the line (network-script network-bridge) to call out the custom script e.g custom-network-bridge. (network-script custom-network-bridge) The custom-network-bridge script should be placed in the /etc/xen/scripts directory. The contents of the script could look something like the following: #!/bin/sh /etc/xen/scripts/network-bridge start vifnum=0 /etc/xen/scripts/network-bridge start vifnum=1 This will cause the network-bridge script to be called twice; once to start and create xenbr0 and peth0 and a second time to create xenbr1 and peth1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210993 ------- Comment #4 from Ulrich.Windl@rz.uni-regensburg.de 2006-10-12 04:54 MST ------- I agree it's a configuration problem. While it's possible to construct arbitrary complicated scenarios, most users would be happy with a straight-forward automatic solution like this: for i in 0 1 2 ... do network-bridge "$@" vifnum=$i netdev=eth$i bridge=xenbr$i done Preferrably the default script would extract the bridges being used from the VM configuration file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com