This is my /etc/network/interfaces
eth0 is connected to the local network, eth3 is reserved for the cluster
(it's a redhat cluster), domain.it is not the real domain...
I have no autostart network in libvirtd, the
/etc/libvirtd/qemu/networks/default.xml is the standard one as installed
by lucid l
It is not a KVM bug, it is a bridge bug, affecting adding and removing
interfaces from the bridge. qemu-ifup and qemu-ifdown do so, and
generates the bug, but it is not Windows or Linux VM related, not either
KVM related...
--
kvm images losing connectivity w/bridged network
https://bugs.launchpa
Yesterday I saw another strange behavior.
I shutdown VM once a day to make a backup and I adjusted my scripts for
the 1-10 min network freeze, but yesterday the network did not unfreeze
at all. I restarted the machine and the network continued to be frozen!
I had to physically power off the machin
It is a bridge problem. I get the same freeze if I delete a tap interface from
the bridge. I was trying to use a "static" tap interface and use it from the
virtual machine, then I executed the command:
# brctl delif br0 tap0
and suddenly the network frozen in the same exact way, so I suppose that
