libvirt opens kernel+initrd in read-write mode

[Olaf Hering]

Am Thu, 9 Jul 2020 19:00:18 +0200
schrieb Michal Privoznik <mprivozn at redhat.com>:

> do you see an actual libvirt error? I think this may come from 
> secdrivers trying to remember the original owner of kernel/initrd files.

Jul 09 16:10:42 libvirtd[5741]: internal error: child reported (status=125): unable to open /path/to/initrd: Read-only file system
Jul 09 16:10:42 libvirtd[5741]: unable to open /path/to/initrd: Read-only file system
Jul 09 16:10:42 libvirtd[5741]: internal error: child reported (status=125): unable to open /path/to/initrd: Read-only file system
Jul 09 16:10:42 libvirtd[5741]: unable to open /path/to/initrd: Read-only file system

> If you set remember_owner=0 in /etc/libvirt/qemu.conf (and restart 
> libvirtd) then does it fix your problem?

Yes, this helps as a workaround.


Olaf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: Digitale Signatur von OpenPGP
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20200709/bcbd74f8/attachment-0001.sig>