ExportXMLWordPrintable

    • Type: Incident report
    • Resolution: Unresolved
    • Priority: Trivial
    • None
    • Affects Version/s: 8.0.0rc3
    • Component/s: Appliance (L)
    • Environment:
      Zabbix Appliance: 8.0.0rc3 (official VHDX download)
      Host: Windows 10 with Hyper-V
      VM Generation: 2
      Secure Boot: Disabled
      RAM: 4 GB
      CPUs: 2
      Disk attached to SCSI Controller

      Problem:

      The official Zabbix Appliance 8.0.0rc3 VHDX fails to boot on Hyper-V and enters the dracut emergency shell.

      The system cannot find its root filesystem (UUID 33fbc092-6b31-47f4-9843-9b22c127fdac).

      Diagnostics showed:

      • /proc/partitions was empty.
      • /sys/class/scsi_host/ and /sys/block/ were empty.
      • modprobe hv_storvsc failed in the initramfs environment.
      • The hv_storvsc driver was present in the installed system's kernel modules.

      Workaround:

      Booted a CentOS Stream 10 rescue environment, mounted the appliance filesystem, entered it using chroot, and rebuilt the initramfs for kernel 6.12.0-211.69.1.el10_2.x86_64 using:

      dracut --kver 6.12.0-211.69.1.el10_2.x86_64 --add-drivers hv_storvsc --force

      After rebuilding the initramfs, the appliance booted successfully under Hyper-V.

      Expected behavior:

      The official VHDX appliance should boot on Hyper-V without requiring manual initramfs repair.

      Actual behavior:

      The appliance enters dracut emergency mode because the virtual SCSI disk is not detected during early boot.

      Possible cause:

      The Hyper-V storage driver is not included in the initramfs shipped with the VHDX appliance.

      Please check the initramfs generation process for the 8.0.0rc3 Hyper-V appliance.

            Assignee:
            Edgars Melveris
            Reporter:
            Silvio H.
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: