, /vmfs/volumes/<datastore_name>/<vm_name>/vmware.log shows below entries:<date><time> In(05) vcpu-0 - NVME-VMK: nvme0:0: FLUSH QUEUE Command failed. Status: 0x80/0x1.<date><time> In(05) vcpu-0 - NVME-VMK: nvme0:0: FLUSH QUEUE Command failed. Status: 0x80/0x1.<date><time> In(05) vcpu-0 - Guest: Status upon boot failure: No Media<date><time> In(05) vcpu-0 - NVME-VMK: nvme0:0: FLUSH QUEUE Command failed. Status: 0x80/0x1.<date><time> In(05) vcpu-0 - NVME-VMK: nvme0:0: FLUSH QUEUE Command failed. Status: 0x80/0x1.<date><time> In(05) vcpu-0 - Msg_Post: Warning<date><time> In(05) vcpu-0 - [msg.Backdoor.OsNotFound] No operating system was found. If you have an operating system installation disc, you can insert the disc into the system's CD-ROM drive and restart the virtual machine.
/var/run/log/vmkernel.log on ESXi host during the same time shows below entries:<date><time> Wa(180) vmkwarning: cpu#:#######)WARNING: VNVMEScsi: 823: NVME Opcode: 0x0 Not Supported, handle ID: 0x#######0<date><time> In(182) vmkernel: cpu#:#######)VNVME: 338: Error status: Not supported converted to: 0x80:0x1<date><time> Wa(180) vmkwarning: cpu#:#######)WARNING: VNVMEScsi: 823: NVME Opcode: 0x0 Not Supported, handle ID: 0x#######0<date><time> In(182) vmkernel: cpu#:#######)VNVME: 338: Error status: Not supported converted to: 0x80:0x1VMware vSphere ESXi 8.x
This issue will be fixed in an upcoming ESXi patch release.
Follow one of the below Workarounds: