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.