libvirt opens kernel+initrd in read-write mode

[Michal Privoznik]

On 7/9/20 8:27 PM, Olaf Hering wrote:
> 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.
> 

Patch proposed here:

https://www.redhat.com/archives/libvir-list/2020-July/msg00530.html

Michal