Public bug reported:

I've had this bug for some time now. From ever since i started to use
KVM on 10.04 until now 11.10 and all versions in between. Also on
numerous hosts with different hardware. And with both linux and windows
guests.

VM's are working fine, but on reboot they hang. They have to be running for 
some time though. VM's running for 10 days or more have a 90% possibility of it 
happening. But it almost never happens on freshly booted VM's.
Also when a VM hangs in boot, 1 core on the host goes to 100% cpu and 
virt-manager can not connect to the host anymore. 

When already connected to the console of a linux guest with virt-manager (since 
you can't connect anymore when it's hanging), you can see the kernel boot hang 
right before virtio-pci would normally load virtio_net:
[    0.865019] virtio-pci 0000:00:03.0: irq 42 for MSI/MSI-X
[    0.865044] virtio-pci 0000:00:03.0: irq 43 for MSI/MSI-X
[    0.865069] virtio-pci 0000:00:03.0: irq 44 for MSI/MSI-X

00:03.0 is indeed the virtio_net:
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device

Sometimes after a long wait time the VM does boot, although i can't
really confirm that now since it's been a while i actually waited and
not just kill it right away. But we're talking about hours. Fastest i've
ever seen it happen was more then 30 minutes. And i've seen cases where
a (non critical) windows server that got rebooted by windows update hung
for more then 1.5 day before i killed it.

Never ran into the problem when booting VM's that where powered off.

** Affects: libvirt (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/921609

Title:
  virtio_net hangs guest on reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/921609/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to