Short version:
Using
systemctl start libvirtd
(or libvirtd.service
, seems to have the same effect?) crashes the system, without warning, if one of the pools has /dev
allocated.
Long version:
I'm trying install a guest OS with the help of passthrough, on Archlinux, with virt-manager
. I'm following [this guide](https://dividebyzer0.gitlab.io/GPUpassthrough.html) . In the [*Configuring Virtual Machine*](https://dividebyzer0.gitlab.io/GPUpassthrough.html#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 /etc/libvirt/storage/pool*.xml
(pool-1.xml
, or something like that). I deleted it in the meantime and now there are no more crashes. There are [one](https://old.reddit.com/r/archlinux/comments/o8wy6w/libvirt_reboots_system_after_1_minute/) and [two](https://old.reddit.com/r/archlinux/comments/mbdjot/system_automatically_reboots_1_min_after_booting/) 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?
Asked by a concerned citizen
(171 rep)
Dec 13, 2021, 03:05 PM
Last activity: Dec 13, 2021, 10:16 PM
Last activity: Dec 13, 2021, 10:16 PM