https://bugzilla.novell.com/show_bug.cgi?id=458967
User jfehlig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=458967#c15
--- Comment #15 from James Fehlig
But the interesting part is that the paravirtualized machines WORK with "bridghe=xenbr0"!!! That's why I didn't knew where to start to debug my problem...
The vif script used for PV guests can access xenstore and read bridge info from there. vif script for HVM guests do not have this luxury and use the device with default route (assuming it is a bridge device) when bridge is not specified. In your case, bridge was specified - but one that does not exist. This used to work because HVM vif script would try ethX when xenbrX was specified but non-existent. The script was changed in openSUSE11.1/SLES11 since we no longer use network-bridge by default.
I want to try to configure in xend-config a bridge name and use it in all domU configuration files...
I would suggest not using network-bridge and use YaST to configure bridge instead. Then set bridge name in all domU config files to the bridge name you used in YaST. network-bridge can be disabled in xend-config.sxp with (network-script ) -- 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.