Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-68418

VM startup failed with the message "import_mok_state() failed: Volume Full"

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • rhel-9.5.z, rhel-10.0
    • edk2
    • Yes
    • Moderate
    • 2
    • rhel-virt-confidential-firmware
    • ssg_virtualization
    • 2
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Virt Firmware Sprint 1 - Dec24, Virt Firmware Sprint 2 - Jan25
    • None
    • None
    • Known Issue
    • Hide
      .A virtual machine with a large amount of bootable data disks might fail to start

      If you attempt to start a virtual machine (VM) with a large amount of bootable data disks, the VM might fail to boot with this error: `Something has gone seriously wrong: import_mok_state() failed: Volume Full`

      Workaround: Decrease the number of bootable data disks and use one system disk. To ensure the system disk is first in the boot order, add `boot order=1` to the device definition of the system disk in the XML configuration. For example:

      [source,xml,subs="+quotes"]
      ----
      <disk type='file' device='disk'>
        <driver name='qemu' type='qcow2'/>
        <source file='/path/to/disk.qcow2'/>
        <target dev='vda' bus='virtio'/>
        *<boot order='1'/>*
      </disk>
      ----

      Set boot order only for the system disk.
      Show
      .A virtual machine with a large amount of bootable data disks might fail to start If you attempt to start a virtual machine (VM) with a large amount of bootable data disks, the VM might fail to boot with this error: `Something has gone seriously wrong: import_mok_state() failed: Volume Full` Workaround: Decrease the number of bootable data disks and use one system disk. To ensure the system disk is first in the boot order, add `boot order=1` to the device definition of the system disk in the XML configuration. For example: [source,xml,subs="+quotes"] ---- <disk type='file' device='disk'>   <driver name='qemu' type='qcow2'/>   <source file='/path/to/disk.qcow2'/>   <target dev='vda' bus='virtio'/>   *<boot order='1'/>* </disk> ---- Set boot order only for the system disk.
    • Done
    • None

      What were you trying to do that didn't work?

      When testing the edk2 test loop, hit this issue when running to this case "block_boot_multi_disks.with_ovmf".

      in the test case: boot a VM with 1 system image and 99 data images with virtio-blk. When booting the VM, hit this issue. 

      What is the impact of this issue to you?

      Normal: not hit is every time and it works well if I replace the vars file with a copy of the template.

      Please provide the package NVR for which the bug is seen:

      hit this issue on the following three versions.

      edk2-20240524-9.el10

      edk2-20240524-10.el10

      edk2-20240524-11.el10

      How reproducible is this bug?:

      2/5

      Steps to reproduce

      1. boot a VM with 1 system image and 99 data images with virtio-blk. boot_multi_disk.sh

      Expected results

      the VM boots up successfully

      Actual results

      Hit the following message in serial log.

      2024-11-14 05:46:56: BdsDxe: loading Boot0002 "redhat" from HD(1,GPT,37C18397-B1DF-455C-9E61-DC767C20836C,0x800,0x12C000)/\EFI\redhat\shimx64.efi
2024-11-14 05:46:57: BdsDxe: starting Boot0002 "redhat" from HD(1,GPT,37C18397-B1DF-455C-9E61-DC767C20836C,0x800,0x12C000)/\EFI\redhat\shimx64.efi
2024-11-14 05:46:57: Could not create MokListRT: Volume Full
2024-11-14 05:46:57: Could not create MokListXRT: Volume Full
2024-11-14 05:46:57: Could not create SbatLevelRT: Volume Full
2024-11-14 05:46:57: Could not create MokListTrustedRT: Volume Full
2024-11-14 05:46:57: Something has gone seriously wrong: import_mok_state() failed: Volume Full
2024-11-14 06:16:23: Ncat: Broken pipe.

       

        1. rhel100-64-virtio-ovmf_qcow2_filesystem_VARS_volumn-full.raw
          528 kB
        2. edk2-avocado-vt-vm1_volumn_full.log
          2.41 MB
        3. edk2-avocado-vt-vm1_pass.log
          3.05 MB
        4. edk2_log_without_bootindex_volumn_full.log
          1.88 MB
        5. boot_multi_disk.sh
          73 kB

              osteffen@redhat.com Oliver Steffen
              jetwei Xueqiang Wei
              virt-maint virt-maint
              Xueqiang Wei Xueqiang Wei
              Daniel Vozenilek Daniel Vozenilek
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: