FS#56759 - libvirt 3.9.0-2: attempting to start a VM with virsh results in hard freeze

Attached to Project: Arch Linux
Opened by Jimi Bove (Jimi-James) - Sunday, 17 December 2017, 22:10 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 20 December 2017, 15:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Trying to start a virtual machine after I upgraded resulted in a freeze so hard that even trying `systemctl restart libvirtd` resulted in systemctl freezing indefinitely. It and all virsh-related processes could be killed with SIGTERM just fine, but they'd freeze again if I tried to run them again. For some reason, with none of those processes running (after I had killed them), my computer froze trying to shut down and I had to hold the power button down. Downgrading back to 3.8.0-1 seems to be a working workaround.


Additional info:
libvirt 3.9.0-2 -> 3.8.0-1
My VM is a QEMU VM running Windows 10 with OVMF for PCI passthru, and I'm passing through a GPU and a USB card. I haven't yet had the chance to troubleshoot and figure out whether passing that hardware through has anything to do with this issue.


Steps to reproduce:
-Upgrade libvirt to 3.9.0-2
-Try to start a VM, possibly specifically the kind of VM I have (Windows 10, PCI passthru), with `virsh start <domain>`
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 20 December 2017, 15:38 GMT
Reason for closing:  None
Comment by Jimi Bove (Jimi-James) - Sunday, 17 December 2017, 22:10 GMT
Ah, sorry, that "libvirt 3.9.0-2 -> 3.8.0-1" is backwards because I accidentally copied it from the wrong line in my pacman log.
Comment by Jimi Bove (Jimi-James) - Monday, 18 December 2017, 20:36 GMT
OK, nevermind. I was very wrong about 2 things:

-libvirt's version has nothing to do with it (meaning it's most likely a kernel bug, because qemu was not part of the upgrade that started this issue). Downgrading libvirt didn't solve the problem--restarting my computer did. And doesn't always.

-The exact bug isn't that virsh freezes. The exact bug is that libvirtd freezes when it first runs in my system. And a valid workaround so far seems to be having libvirtd.service be not enabled, and instead starting it manually after my computer has finished booting up into a GUI.

I'm going to have to do more troubleshooting and submit a completely different bug, maybe not even to the Arch Linux tracker. This bug is now invalid.

Loading...