I am having the exact same issue as described above, but using the
following:
* Ubuntu 10.10 (upgraded from 10.04, upgraded from 9.10, upgraded from 9.04
which was a fresh install).
* KVM (QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright (c)
2003-2008 Fabrice Bellard)
* Linux alexo 2.6.38 #2 SMP Mon Apr 11 13:57:58 CEST 2011 x86_64 GNU/Linux
I am using virt-manager to manage the virtual machines.
Network settings:
~ % ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 00:1b:21:3a:ed:30 brd ff:ff:ff:ff:ff:ff
inet6 fe80::21b:21ff:fe3a:ed30/64 scope link
valid_lft forever preferred_lft forever
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 00:1c:c0:ab:d4:2c brd ff:ff:ff:ff:ff:ff
inet 10.85.25.1/16 brd 10.85.255.255 scope global eth0
inet 10.85.25.2/16 scope global secondary eth0
inet 10.85.25.3/16 scope global secondary eth0
inet 10.85.25.4/16 scope global secondary eth0
inet6 fe80::21c:c0ff:feab:d42c/64 scope link
valid_lft forever preferred_lft forever
23: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 500
link/ether fe:54:00:e6:85:4d brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fee6:854d/64 scope link
valid_lft forever preferred_lft forever
25: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN
link/ether 00:1b:21:3a:ed:30 brd ff:ff:ff:ff:ff:ff
inet 10.85.25.5/16 brd 10.85.255.255 scope global virbr0
inet6 fe80::21b:21ff:fe3a:ed30/64 scope link
valid_lft forever preferred_lft forever
26: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 500
link/ether fe:54:00:1c:37:4f brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe1c:374f/64 scope link
valid_lft forever preferred_lft forever
~ % brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.001b213aed30 yes eth1
vnet0
vnet1
One of the vnet devices (which is the tap interfaces to the virtual machines)
work at a time. At the moment of writing it's vnet0 - but appears to be random.
I have tried all setups I can think off:
* Setup above.
* Turning eth1 off completely, bridging eth0 instead and using it from both
host and guest.
* Used eth0 for bridge and eth1 from host.
Consequently, only one of my virtual machines work.
Some googling have suggested it only appears on 64 bit system. Is that
true for everyone here?
Any other information I can provide to help shed some light on this? I
am completely stumped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728519
Title:
Bridged Guests losing network connectivity under non-ubuntu Xen after
upgrade from 8.10 to 10.04
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
