On Fri, Oct 19, 2018 at 12:41:32PM +0200, Guido Günther wrote: > Can you reproduce this bug when you disable libvirtd to start at boot > and then start libvirtd later on? Is this maybe tied to a specific VM > being auto started (that gets the GPU passed in or similar)?
Yes, I disabled libvirtd service so I can login and than try to start it manually using: # /usr/sbin/libvirtd -v It does not report any errors but the kernel generates a soft lockup very soon. Also no VMs are configured to start automatically at boot. If I don't start libvirtd everything else seems to work fine. -- Valentin
