[SOLVED] vm has no boot disk

[johnnywoz]

Installed a fresh PVE4.4 on Supermicro x11sae-m motherboard, 32GB DDR4 RAM, 480GB PCIe NVMe M.2 boot drive, other sata drives to be configured/used later.

PVE installs just fine, have done it a dozen times now. I'm able to access PVE web page. I have been trying to create a Debian8 VM, install goes fine (accepted all defaults, GRUB on /dev/sda), but when rebooting the vm after install, I get the Proxmox bios screen then the console says not able to boot CD-ROM, not able to boot hard drive, booting PXE and then just cycles.

Only change on Supermicro bios was to turn off PXE on the nics and set EFI on devices.
PVE install, accepted all defaults
VM install on local.lvm, 32GB iSCSI(1) disk, 1 core cpu, 1GB RAM, virtio nic.
Deb8, accepted all defaults, all files 1 partition, grub installed on /dev/sda

I've tried searching the forum, but must not be using the right key words as I'm not able to find this issue discussed. If it has, please provide a link to it, if not please help me understand this issue. Also let me know what other details are needed from me.

Thanks, JohnW

 

[johnnywoz]

update: I've tried installing other linux ISOs as a KVM VM with the same result, install goes fine but upon restart of the vm, the proxmox bios just cycles in the console screen.

And yes, I've disconnected the virt cd-rom image.

 

[johnnywoz]

solved my issue. Instead of selecting the default SCSI option for the hard drive (during the vm setup), I selected SATA and viola, os now boots upon completion of the install.

I understand that PVE cannot anticipate all possible hardware configuration scenarios, but now it seems default values need to be questioned at all times. I say this because I also had an issue when installing PVE on my hardware and it not detecting which ethernet port had a cable plugged in, which in turn caused me hours of troubleshooting and research just to figure out that PVE had selected the other port with no cable in it. Good Grief. I now feel like a n00b ;(