On 2/26/24 08:40, Jürgen Echter via Users wrote: I think the best would be to enable debugging [1] and then inspect logs. There might already be more info though, in /var/log/libvirt/qemu/$VM.log. reason=crashed usually means that the guest panicked, i.e. the problem lies somewhere in QEMU. 1: Here is full info https://libvirt.org/kbase/debuglogs.html But what I have set in /etc/libvirt/libvirtd.conf (assuming this is qemu:///system URI): log_filters="1:qemu 1:libvirt 4:object 4:json 4:event 1:util" log_level = 1 log_outputs="1:file:/var/log/libvirtd.log" If this is qemu:///session then you need to put it in ~/.config/libvirt/libvirtd.conf. Michal