[Bug 218092] New: Can't start HVM guest if Xen bridge is not xenbr0
https://bugzilla.novell.com/show_bug.cgi?id=218092 Summary: Can't start HVM guest if Xen bridge is not xenbr0 Product: openSUSE 10.2 Version: Beta 1 plus Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: ccoffing@novell.com ReportedBy: jdouglas@novell.com QAContact: jdouglas@novell.com CC: lbendixs@novell.com If I attempt to install a FV guest on a machine configured with a xen bridge other than xenbr0, the guest will fail to start unless I specify the bridge in the config file. This needs to be changed so that the "default bridge" is used even if it is not 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=218092 jdouglas@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |hvm -- 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=218092 ccoffing@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #1 from ccoffing@novell.com 2006-11-07 16:15 MST ------- I've been researching this, and so far, it's not clear to me how this ever worked in SLES 10 GMC. In xen-3.0.2, if you didn't specify a bridge, xend would stupidly default to "xenbr0". Qemu didn't have any defaults. So something was always passed to qemu, to be passed to /etc/xen/qemu-ifup. Sure looks like the problem should have happened here too. In xen-3.0.3, xend still behaves the same (defaulting to "xenbr0"). Qemu now also has a default of "xenbr0". So, despite being redundant, the behavior seems like it would be the same. Annoyingly, the selection of the bridge is done differently for paravirtualized. This could be fixed by ripping out the default xenbr0 from xend and qemu, and putting some intelligence in /etc/xen/qemu-ifup. Still researching if that is the best way. -- 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=218092 ccoffing@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #2 from ccoffing@novell.com 2006-11-09 11:01 MST ------- Fixed as described above. Jason - when regressing this, do similar tests for PV guests... -- 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=218092 jdouglas@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #3 from jdouglas@novell.com 2006-11-13 18:26 MST ------- It appears as though the change you made has broken at least one aspect of the process: As it stands now, if I specify a bridge in my FV config file (with type=ioemu), then the SDL window never appears. The qemu log file shows the qemu onscreen help, suggesting that qemu is receiving an invalid parameter. After removing the ",bridge=xenbr0" from the vif line, the VM starts correctly (and the qemu help does not get output to the qemu log file.) One other item of note, the /etc/xen/qemu-ifup script is not being called if the bridge is specified in the config file. It does get called if the bridge is not specified. -- 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=218092 ccoffing@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Comment #4 from ccoffing@novell.com 2006-11-16 13:38 MST ------- oops. Typo. Fixed. -- 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