Re: libvirt opens kernel+initrd in read-write mode

On 7/9/20 8:27 PM, Olaf Hering wrote: Am Thu, 9 Jul 2020 19:00:18 +0200 schrieb Michal Privoznik : 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

Re: libvirt opens kernel+initrd in read-write mode

Am Thu, 9 Jul 2020 19:00:18 +0200 schrieb Michal Privoznik : > 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

Re: libvirt opens kernel+initrd in read-write mode

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. hvm /path/to/kernel /path/to/initrd net.ifnames=0

libvirt opens kernel+initrd in read-write mode

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. hvm /path/to/kernel /path/to/initrd net.ifnames=0 console=ttyS0,115200 linemode=1 panic=9 start_shell