kvm hypervisor host network problem during VM startup/shutdown
(please CC me on replies)
I have been running kvm on this host for almost two years now. Using
bridged networking, rather simple setup, with about 4 VMs and the
There is one bridge, br1 (there is an unused br0 which has no connection
out) which is connected to the physical ethernet, one of the VMs is
providing DHCP to the whole network.
Things work fine, except, when I attempt to create a new host, or
destroy a running host. I am playing with FAI profiles now, and so have
"tested" this many times. Every time, the hypervisor briefly (5-10
seconds or so) stopps responding on the network, though, other systems
which use the same bridge, have no issue.
Script used to start the new VM:
I run this and get:
Creating domain... 0 B
Domain installation still in progress. You can reconnect to
the console to complete the installation process.
Timeout, server not responding.
Then I am back on my local host (I ssh in to the hypervisor). I connect
back in, and I can now use virt-viewer to see the console and watch the
install (already in progress).
The same thing happens when I "destroy" test via virsh (why graceful
shutdown a system being blown away?)
I have found that other systems (like the DHCP VM) still respond to ping
during this time. In fact, one of them is providing the VPN end point
which I am using to get to the hypervisor, and the VPN connection never
In the logs, at the same time, I see only the following, though, looking
around indicates that these are common and probably not indicitive of an
May 10 15:27:38 hyper kernel: [492763.100101] device vnet5 entered
May 10 15:27:38 hyper kernel: [492763.104224] br1: port 6(vnet5)
entering listening state
May 10 15:27:47 hyper kernel: [492772.133560] br1: port 6(vnet5)
entering learning state
May 10 15:27:56 hyper kernel: [492781.146314] br1: topology change
May 10 15:27:56 hyper kernel: [492781.150297] br1: port 6(vnet5)
entering forwarding state
Bridge is setup in /etc/network/interfaces as follows:
iface br1 inet static
Anyone else run into this? Any ideas?
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org