Red Hat Bugzilla – Bug 451784
libvirt 0.4.3 doesn't always clean up after itself
Last modified: 2008-07-01 01:30:17 EDT
Description of problem:
As a corollary of BZ 451709, when libvirtd fails to start domains because of the
bug there, it also fails to clean up after itself. In particular, it leaves a
"vnet?" device visible and connected to virbr0, even though there is no domain.
This further causes problems when rebooting the kernel, since you then get
messages "kernel: waiting for netdev vnet0 to become free" infinitely. You also
cannot kill the libvirtd daemon.
Hm. Weird. I can't seem to reproduce the "can't kill libvirtd" problem at the
moment (after a reboot of the host machine). However, the "doesn't cleanup
vnet?" is still a problem.
This one is actually closely related to BZ 451709, which I now have a patch for.
I'm going to close it as a duplicate.
*** This bug has been marked as a duplicate of 451709 ***
libvirt-0.4.4-1.fc9 has been submitted as an update for Fedora 9
libvirt-0.4.4-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.