Hi, I was checking by starting with a common setup I ususlly use adapting towards your case step by step.
uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily release=xenial arch=s390x label=daily uvt-simplestreams-libvirt query uvt-kvm create --memory 2048 --cpu 4 --password=ubuntu --template template-s390x.xml kvmguest-xenial release=xenial arch=s390x label=daily cat template-s390x.xml <domain type='kvm'> <os> <type>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <devices> <interface type='network'> <source network='default'/> <model type='virtio'/> </interface> <console type='pty' tty='/dev/pts/3'> <source path='/dev/pts/3'/> <target type='sclp' port='0'/> <alias name='console0'/> </console> </devices> </domain> virsh dumpxml kvmguest-xenial [...] <interface type='network'> <mac address='52:54:00:1b:de:4e'/> <source network='default' bridge='virbr0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/> </interface> [...] Ok, so far things are fine - I have a bridge brctl show virbr0 bridge name bridge id STP enabled interfaces virbr0 8000.5254006ec370 yes virbr0-nic vnet0 The guest is connecte to that. The bridge is the default libvirt way of handling default network (nat). The guest gets a dhcp (from host) address on that net 192.168.122.241 in my case. This gets to the Host just nice and works to get to the outside as well via the host. Changing the guest to a static IP in guest e/n/i auto eth0 iface eth0 inet static address 192.168.122.241/24 gateway 192.168.122.1 Still working fine. Changing that to a guest linked to a bride looks like <interface type='bridge'> <source bridge='br0'/> <mac address='52:54:00:fa:ae:a8'/> <model type='virtio'/> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/> </interface> Unfortunately my net setup here is very demaning with vlan only. Could one send me 10 extra OSAs so we can autotagging by the switch :-) ? It is just very complex to get bridge, onto only one Host interface that has vlan required to be set up correctly. So before doing all that I'd like to ask a few questions: But to go on I think it is time to ask you how exactly you 1. defined the bridge and host networking in your case (exact commands to set up your bridge + brctl show on the bridge + host ifconfig -a and route) 2. connected the bridge to your guest (see my xml example above, how does yours look like?) 3. is it a hard requirement that there is only one Host network device? ** Changed in: bridge-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1626826 Title: KVM guest cannot use br0 created by brctl on Ubuntu16.04 Status in Ubuntu on IBM z Systems: New Status in bridge-utils package in Ubuntu: Incomplete Bug description: == Comment: #0 - QI YE - 2016-09-22 06:01:59 == ---Problem Description--- Ubuntu16.04. Created a bridge br0 on enc100 via brctl. enc100 is the only external accessible nic. Defined a ubuntu guest to use br0 and assigned an IP to the guest in the same subnet as br0. After started the guest, couldn't access external servers or internet from the guest. ---uname output--- Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016 s390x s 390x s390x GNU/Linux Machine Type = 2827 (z Systems EC12) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. define br0 on enc100 via brctl command (IP on br0 is 192.168.1.170 for example) 2. update /etc/network/interfaces 3. create a guest on KVM and use br0 for it's nic 4. Start guest via virsh command and assign an IP, e.g. 192.168.1.171. After installation, cannot access external systems via KVM host. == Comment: #2 - QI YE - 2016-09-22 09:53:58 == attached sosreport file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1626826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
