Public bug reported:
Opened by request of Serge Hallyn.
Creating more than one virtual machine (using libvirt) and putting them in a
bridge using a tun interface, only the first one
is able to reach the underlaying network. However, after an unspecified amount
of time, the connection to even this one fails - but may return again at a
later point.
Altough unconfirmed, it seems as I got the 'other' tun interface to work,
however at a cost of the first one.
The bridge itself appears to be working as expected. Both virtual machines can
ping the host, as well as each other.
* 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)
* libvirtd (libvirt) 0.8.3
* Linux alexo 2.6.38 #2 SMP Mon Apr 11 13:57:58 CEST 2011 x86_64 GNU/Linux
(also tried with 2.6.35-27-generic kernel).
I am using virt-manager (version 0.8.4) 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
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.
Some googling have suggested it only appears on 64 bit system.
Any other information I can provide to help shed some light on this? I
am completely stumped.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/759490
Title:
Bridged: virtual machine unable to reach network
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
