Quoting Dyson Simmons (dysonsimm...@gmail.com): > Hi Serge, > > eth0 and eth1 both plug into a Cisco switch. They are on separate vlans. > eth0 is an internal ip range (10.10.x.x) and eth1 is used for a pool of > public IP addresses we have (203.0.141.x). > > I don't want the VM host to have a public IP as all administration of > the host will happen on eth0 on the private vlan. I do however require > guests to have a public IP address (such as a web server) and so eth1 > and br1 are set to manual. The guest can still set a public IP address > and the host doesn't have a public IP of it's own. > > Does that make sense?
Actually no, that doesn't make sense to me. If you have vnet0 and eth1 enslaved to br1, but eth1 and br1 don't have an address, then I'm not sure you can expect to reliably be able to ssh to vnet0's ip address. Could you try setting br1 to some reasonable address (203.0.141.1), leaving eth1 unconfigured (to leave br1 out of the wider world), and seeing if that helps? status: incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1172091 Title: KVM guests with bridged network drops out intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1172091/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
