iSCSI boot UEFI: guest has not initialized the display (yet)

[stefgrifon]

Hello,

I use the proxmox 7.3-6 (almost fresh install)
I have also configured iSCSI. I tried to build an vm windows server 2022 on iSCSI but the time i start the vm give me this message: guest has not initialized the display (yet)

Vm configuration is the same like the post Windows 2022 guest best practices

• Microsoft Windows 11/2022
• Enable the "Qemu Agent"
• virtual hard disk select "SCSI" as bus with "VirtIO SCSI" as controller.
• Set "Write back" and tick "Discard" to optimally use disk space (TRIM).

How can i fix it?

Thank you,
Stefanos

 

[Chris]

Hello,

I use the proxmox 7.3-6 (almost fresh install)
I have also configured iSCSI. I tried to build an vm windows server 2022 on iSCSI but the time i start the vm give me this message: guest has not initialized the display (yet)

Vm configuration is the same like the post Windows 2022 guest best practices

• Microsoft Windows 11/2022
• Enable the "Qemu Agent"
• virtual hard disk select "SCSI" as bus with "VirtIO SCSI" as controller.
• Set "Write back" and tick "Discard" to optimally use disk space (TRIM).

How can i fix it?

Thank you,
Stefanos

Hi, did you select the right disk to boot from? Can you post the VM config, qm config <VMID> for the VM in question. Also, what storage does the VM disk resides on? Please post the output of cat /etc/pve/storage.cfg

 

[stefgrifon]

Hi,

qm config

agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 3
efidisk0: SANiscsi:0.0.0.scsi-SDELL_MD32xxi_35O001E,efitype=4m,pre-enrolled-keys=1,size=463G
ide2: local:iso/Windows_Server_2022_LTSC_21H2_Build_20348.1006.iso,media=cdrom,size=5023476K
machine: pc-q35-7.1
memory: 4096
meta: creation-qemu=7.1.0,ctime=1677053684
name: RPD
net0: virtio=E2:7F:AB:4E:AD:42,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: SANiscsi:0.0.0.scsi-SDELL_MD32xxi_35O001E,cache=writeback,discard=on,size=463G
scsihw: virtio-scsi-pci
smbios1: uuid=140cb052-50d0-4b07-a2be-3349007cc03f
sockets: 1
tpmstate0: SANiscsi:0.0.0.scsi-SDELL_MD32xxi_35O001E,size=463G,version=v2.0
vmgenid: a4bfbe41-8c13-4836-854b-328d4da9909d

cat /etc/pve/storage.cfg

dir: local
        path /var/lib/vz
        content vztmpl,backup,iso

zfspool: local-zfs
        pool rpool/data
        content images,rootdir
        sparse 1

zfspool: OneTeraSSDm
        pool OneTeraSSDm
        content images,rootdir
        mountpoint /OneTeraSSDm
        nodes IBMX3650M3

zfspool: RaidSAS499
        pool RaidSAS499
        content rootdir,images
        mountpoint /RaidSAS499
        nodes IBMX3650M3

zfspool: RaidSSD249
        pool RaidSSD249
        content rootdir,images
        mountpoint /RaidSSD249
        nodes IBMX3650M3

zfspool: RaidSSD499
        pool RaidSSD499
        content rootdir,images
        mountpoint /RaidSSD499
        nodes IBMX3650M3

iscsi: SANiscsi
        portal 178.178.10.11
        target iqn.1984-05.com.dell:powervault.md3200i.690b11c00055f30e00000000527a0c30
        content images

 

[Chris]

Hi,

qm config

agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 3
efidisk0: SANiscsi:0.0.0.scsi-SDELL_MD32xxi_35O001E,efitype=4m,pre-enrolled-keys=1,size=463G
ide2: local:iso/Windows_Server_2022_LTSC_21H2_Build_20348.1006.iso,media=cdrom,size=5023476K
machine: pc-q35-7.1
memory: 4096
meta: creation-qemu=7.1.0,ctime=1677053684
name: RPD
net0: virtio=E2:7F:AB:4E:AD:42,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: SANiscsi:0.0.0.scsi-SDELL_MD32xxi_35O001E,cache=writeback,discard=on,size=463G
scsihw: virtio-scsi-pci
smbios1: uuid=140cb052-50d0-4b07-a2be-3349007cc03f
sockets: 1
tpmstate0: SANiscsi:0.0.0.scsi-SDELL_MD32xxi_35O001E,size=463G,version=v2.0
vmgenid: a4bfbe41-8c13-4836-854b-328d4da9909d

cat /etc/pve/storage.cfg

dir: local
        path /var/lib/vz
        content vztmpl,backup,iso

zfspool: local-zfs
        pool rpool/data
        content images,rootdir
        sparse 1

zfspool: OneTeraSSDm
        pool OneTeraSSDm
        content images,rootdir
        mountpoint /OneTeraSSDm
        nodes IBMX3650M3

zfspool: RaidSAS499
        pool RaidSAS499
        content rootdir,images
        mountpoint /RaidSAS499
        nodes IBMX3650M3

zfspool: RaidSSD249
        pool RaidSSD249
        content rootdir,images
        mountpoint /RaidSSD249
        nodes IBMX3650M3

zfspool: RaidSSD499
        pool RaidSSD499
        content rootdir,images
        mountpoint /RaidSSD499
        nodes IBMX3650M3

iscsi: SANiscsi
        portal 178.178.10.11
        target iqn.1984-05.com.dell:powervault.md3200i.690b11c00055f30e00000000527a0c30
        content images

Can you reach the uefi interface before booting into Windows? Check your settings there (also iscsi initiator).

Also 4GiB of memory seems a bit low to me, maybe try with a bit more. (At least my Windows 11 Desktop VM is rather memory hungry).

 

[fiona]

Hi,

efidisk0: SANiscsi:0.0.0.scsi-SDELL_MD32xxi_35O001E,efitype=4m,pre-enrolled-keys=1,size=463G
scsi0: SANiscsi:0.0.0.scsi-SDELL_MD32xxi_35O001E,cache=writeback,discard=on,size=463G
tpmstate0: SANiscsi:0.0.0.scsi-SDELL_MD32xxi_35O001E,size=463G,version=v2.0

this seems wrong. You can't use the same LUN as different disks, the reads/writes will conflict. If you'd like to create multiple volumes on the same LUN, I suggest you create an LVM storage on top of the LUN and use that. Can be done in Datacenter > Storage > Add > LVM and select the iSCSI storage as the base storage. And to be safe, uncheck the Use LUNs directly for the iSCSI storage.

 

[stefgrifon]

Hi,

this seems wrong. You can't use the same LUN as different disks, the reads/writes will conflict. If you'd like to create multiple volumes on the same LUN, I suggest you create an LVM storage on top of the LUN and use that. Can be done in Datacenter > Storage > Add > LVM and select the iSCSI storage as the base storage. And to be safe, uncheck the Use LUNs directly for the iSCSI storage.

Thank you all
Solved!