Virtualization Setup problem with bridge installation

Just did a fresh install of 42.1, minimal installation with XFCE & Xen for a Host machine.

After installing Hypervisor & Tools with Yast, the network was broken! It appears that there is a bug in the code that installs the bridge, as the bridge setup was:

$ sudo cat ifcfg-br0
BOOTPROTO=‘static’
BRIDGE=‘yes’
BRIDGE_FORWARDDELAY=‘0’
BRIDGE_PORTS=’’
BRIDGE_STP=‘off’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IPADDR=’<valid IP address>/24’
MTU=’’
NETWORK=’’
PREFIXLEN=‘24’
REMOTE_IPADDR=’’
STARTMODE=‘auto’
USERCONTROL=‘no’
NAME=’’

I verified the settings at least three times in Yast, … everything looked OK; tried booting the base kernel, no change.

After comparing to a 13.1 machine I saw the problem, but it needs to be fixed upstream.

Posting here so there is a solution for others.

So, which part of the config do you think is “faulty/broken?”
If there is a verified issue, you need to submit a bug at https://bugzilla.opensuse.org

But, I’d first question whether something is actually broken, things may just be different (but might be improvable).

TSU

You forgot to post the solution.

There is one fatal error in this configuration, … one minor, non-fatal.

Hint: The fatal error is a ‘’.

Recommend you don’t play games about what you feel is actually broken.
Be aware that what you perceive as “broken” might be specific to your network setup which might not be considered “typical.”

Most people who read your post would be reluctant to install Xen just to <maybe> see what you are being coy about.
If people already have a working Xen, then they’ll dismiss your post without a second’s further thought.
If people don’t already have a working Xen, they’d be reluctant to try to replicate your issue without details.

TSU

Line 4 - no interface specified. Adding the proper interface reference permits the network to work; this config was generated by the Yast Virtualization installer, and br0 DOES show bound to eth0 in Yast.

I was hoping that someone would a) spot the problem (see previous post), or b) add information that Yast DOES build the bridge correctly under some circumstances so we can figure out why it did not in this case.

Bridge without underlying interfaces is valid configuration. Without knowing what exactly you did it is impossible to say anything. Post step by step description (may be with screenshots as appropriate) if you want others to help to find out whether this is indeed openSUSE problem or simply missing steps from your side.

  • Base 42.1 install
  • Install VIrtualization and Tools via Yast
  • Network broken
  • Realize xen kernel had not booted
  • Rebooted with xen kernel, no change
  • Attempt to verify many times via Yast, no change
  • Add interface identifier in bridge configuration
  • Stop/state network via service command
  • Working

You did not even configure anything yet, how can something be broken?

If the Host networking was found non-functional, that situation was just described in another thread within the past couple weeks and I provided an answer.

https://forums.opensuse.org/showthread.php/511325-Virtual-machine-is-not-running?highlight=bridge+default+gateway

TSU

Ahh, … because a working machine is required to run Yast and install 'Virtualization and Tools??