I saw that that the related issue was implemented in 5.1.0.
So after I updated my QEMU to version 5.1.0. My VM(s) with a LVM read-
only volume started again.
Thanks for getting this issue solved.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscrib
The domain.xml:
rotest
b4aa0288-8886-42df-abfd-4c8f729e1330
2048000
2048000
2
hvm
/var/lib/libvirt/pink/kernel
root=/dev/sda ro panic=300 systemd.show_status=1
systemd.unit=graphical.target quiet
qemu64
destroy
restart
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virt
Public bug reported:
This issue is introduced in QEMU 4.2.0 (4.1.0 is working fine)
My root disk is a LVM2 volume thin snapshot that is marked as read-only
But when I try to start the domain (using virt-manager) I get the following
error:
Error starting domain: internal error: process exited wh
