systemctl start libvirtd (or
libvirtd.service, seems to have the same effect?) crashes the system, without warning, if one of the pools has
I'm trying install a guest OS with the help of passthrough, on Archlinux, with
virt-manager. I'm following this guide. In the Configuring Virtual Machine section, the first step is to add storage, and select the
/dev. Once I do that, the system will reboot instantly, without any warning, after ~1 min. I have checked with
systemctl status libvirtd at regular intervals, and the lowest time I got to see was 55 sec; I never got to see 1 min. The setting is saved in
pool-1.xml, or something like that). I deleted it in the meantime and now there are no more crashes. There are one and two threads on reddit, but none has any workaround.
Is this a known behaviour, or is it a quirk? How do I get around it and finish installing the guest OS?