Open an-owl opened 3 years ago
You don't have to modprobe -r
any modules in your start script. Check your log for errors (should be in /var/log/libvirt/qemu/[VM name].log
)
I have gone through many iterations trying to solve this issue and modprobe -r
was something i saw in older scripts so i tried it.
the only error in the log is 3 different 2021-05-12T11:01:57.696722Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE]
which I'm not sure is related
i know its a common issue but I'm stumped. as far as i know i have followed every step correctly, the one think of note is that during the troubleshooting steps it says after your start script your screen should be blank, however mine has text with a frozen cursor. although I'm not sure if this is a clue. the only step i skipped was patching the ROM, because wen i dumped it i was a bit miffed to find it looked like it had already been patched. although i did pass the dumped ROM to the VM i have removed it. my start script
I'm using manjaro cpu: r5-2600x gpu: nvidia 2070
stop script
note that
#echo 1 > /sys/class/vtconsole/vtcon1/bind
is commented out because it throws "no such file" but does not during the start scriptlibvirt xml
any help is appreciated thanks in advance