VM Status io-error / BdsDxe: failed to load

[MultiLANs]

Hi everyone, I´m experiencing the following problem on my Proxmox, the VM is not initializing, first I had the error "BdsDxe: failed to load ", after backup I tried to solve it as shown in this topic: https://forum.proxmox.com/threads/cant-boot-my-vm-anymore-disk-not-found.125936/ after that the error "BdsDxe: failed to load" no longer appears, it tries to start the VM (Windows Server 2016) but it freezes and the error "VM Status io-error" appears with a yellow triangle on the VM. The disk physically seems to be fine since no read or write errors appear, the VM configuration is as follows:

bios: ovmf
boot: order=sata0;virtio0;net0;sata1
cores: 12
efidisk0: local-lvm:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
machine: pc-q35-7.1
memory: 26624
meta: creation-qemu=7.1.0,ctime=1679594795
name: SRV
net0: e1000=46:56:88:FA:88:D4,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win11
sata0: local:iso/SERVER_EVAL_x64FRE_es-es.iso,media=cdrom,size=4936852K
sata1: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
scsihw: virtio-scsi-single
smbios1: uuid=e641fd97-0984-423a-8ac6-f20e23140dee
sockets: 1
tpmstate0: local-lvm:vm-100-disk-1,size=4M,version=v2.0
virtio0: local-lvm:vm-100-disk-2,iothread=1,size=814G
vmgenid: 116421bf-63a8-4f19-90a1-2d38ad1864b7
root@pve:~#

The command journalctl displays the following:

-- Journal begins at Wed 2023-03-22 21:51:31 -03, ends at Tue 2025-06-24 21:39:32 -03. --
Mar 22 21:51:31 pve kernel: Linux version 5.15.74-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU l>
Mar 22 21:51:31 pve kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.74-1-pve root=/dev/mapper/pve-root ro quiet
Mar 22 21:51:31 pve kernel: KERNEL supported cpus:
Mar 22 21:51:31 pve kernel:   Intel GenuineIntel
Mar 22 21:51:31 pve kernel:   AMD AuthenticAMD
Mar 22 21:51:31 pve kernel:   Hygon HygonGenuine
Mar 22 21:51:31 pve kernel:   Centaur CentaurHauls
Mar 22 21:51:31 pve kernel:   zhaoxin   Shanghai
Mar 22 21:51:31 pve kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on u>
Mar 22 21:51:31 pve kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Mar 22 21:51:31 pve kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Mar 22 21:51:31 pve kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Mar 22 21:51:31 pve kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Mar 22 21:51:31 pve kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Mar 22 21:51:31 pve kernel: x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:    8
Mar 22 21:51:31 pve kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' form>
Mar 22 21:51:31 pve kernel: signal: max sigframe size: 3632
Mar 22 21:51:31 pve kernel: BIOS-provided physical RAM map:
Mar 22 21:51:31 pve kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Mar 22 21:51:31 pve kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Mar 22 21:51:31 pve kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable

Any help will be appreciated.

 

[MultiLANs]

Well, finally the problem was solved, I comment the resolution in case it happens to someone else, regarding the message: "BdsDxe: failed to load" when starting the VM I understand that it has to do with the UEFI configuration of the VM but it does not affect the operation at all, what did crash the VM was the "io-error", this was because it had run out of space on the VM disk since a software was running on it that greatly increased the database and filled the space assigned to the VM, I was able to make a backup, install Proxmox on a larger physical disk and start the VM without problems