On 7/9/20 4:32 PM, Olaf Hering wrote:
Is there a reason why libvirtd v6.5.0 opens kernel+initrd in mode RW?
'virsh start vm' fails of both are on a read-only filesystem.
Not sure if this ever worked before.
<domain type='kvm'>
<os>
<type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type>
<kernel>/path/to/kernel</kernel>
<initrd>/path/to/initrd</initrd>
<cmdline>net.ifnames=0 console=ttyS0,115200 linemode=1 panic=9 start_shell</cmdline>
<boot dev='hd'/>
</os>
</domain>
....
13111 stat("/path/to/initrd", {st_mode=S_IFREG|0755, st_size=119207064, ...}) = 0
13111 openat(AT_FDCWD, "/path/to/initrd", O_RDWR) = -1 EROFS (Read-only file system)
....
Hey,
do you see an actual libvirt error? I think this may come from
secdrivers trying to remember the original owner of kernel/initrd files.
If you set remember_owner=0 in /etc/libvirt/qemu.conf (and restart
libvirtd) then does it fix your problem?
Michal
