On Mon, Nov 29, 2021 at 09:38:39AM -0700, Jim Fehlig wrote: > I've been investigating what turns out to be some long-standing issues in > the libxl driver. One of them causes libvirtd to deadlock, the other can > lead to a segmentation fault. Both can be triggered by repeatedly rebooting > a collection of VMs. My reproducer continually reboots 8 VMs on a host > where libvirtd runs in a VM (dom0) confined to 4 vcpus. > > Patches 1-4 contain improvements and preparation for the fixes in patches > 5 and 6. Patch 5 fixes the potential deadlock, and patch 6 fixes the > potential crash. Both contain more detail on the respective issues. My > reprocuder has run for 5 days without issue. Before the patches, it would > trigger within 2 days. For all patches Reviewed-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
