Re: ecrypting image file breaks efi/boot of the guest/Ubuntu - ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 14/04/2023 13:57, Peter Krempa wrote:
On Fri, Apr 14, 2023 at 13:39:17 +0200, lejeczek wrote:

On 11/04/2023 09:13, Peter Krempa wrote:
On Sat, Apr 08, 2023 at 11:25:18 +0200, lejeczek wrote:
Hi guys.

I've have a guest and that guest differs from all other guest by:

      <type arch='x86_64' machine='pc-q35-rhel9.0.0'>hvm</type>
      <loader readonly='yes' secure='yes'
      <boot dev='hd'/>
      <bootmenu enable='yes'/>

whereas everything else has:

      <type arch='x86_64' machine='pc-q35-rhel9.0.0'>hvm</type>
      <boot dev='hd'/>
      <boot dev='cdrom'/>
      <bootmenu enable='yes'/>

Now, that different guest fails - as the only one - to start, to boot after
its qcow2 image was luks-encrypted.
Guest starts but says that:

BdsDxe: failed to load Boot0001 "Uefi Misc Device" from PciRoot
(0x0)/Pci(0x2,0x3)/Pci(0x0,0x0): Not found

revert back to original, non-encrypted qcow2 image and all works a ok.
Please attach either the full XML or at least the disk part for *both*
the case where it doesn't work and where it does work.

     <disk type='file' device='disk'>
       <driver name='qemu' type='qcow2' cache='none' discard='unmap'/>
       <source file='/00-VMs/ubusrv1.qcow2'/>
       <target dev='vda' bus='virtio'/>
       <address type='pci' domain='0x0000' bus='0x04' slot='0x00'

When I add encryption to <disk> & use encrypted qcow2 then VM fails as I
I specifically asked for '*both*' XMLs. The working one. And the
non-working one.

The only difference between the two, as far as XML goes - it's in reality the same one guest - is encryption and the lack of thereof, in <disk> section.

[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux