Hi

 

I had setup a win10 VM. I had passed through an 850 EVO as the primary disk and then didn't use it much.

Recently, i tried to fire it up again, and I encountered the following screen:

 

From my understanding, the boot device isn't properly recognised.

However, when i fire up the VM and Press a key for setup when prompted to, then clic through the several windows setup screens and load the virtio drivers, i see my ssd appearing:

This leads me to believe that my ssd and the windows installation on it are fine.

 

I could try to setup again my VM, but I'd prefer not to if it's avoidable.

 

    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S3R0NF0J857389E'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>

 

Any idea of what happenend? And how can I resolve it? I would appreciate any input.

 

Thanks!

 

N

Try this here to change your boot device in the UEFI virtual bios:

 

 

Thanks for your answer!

 

When I type exit in the UEFI shell and choose Boot Manager, i land on the following screen. I tried to select every of these items, but no success in booting my VM.

 

I read a few more threads and tried this, again with no success: http://lime-technology.com/wiki/index.php/UnRAID_OS_version_6_Upgrade_Notes#My_OVMF_VM_doesn.27t_boot_correctly

I also tried creating a second identical VM template but changed the BIOS from OVMF to SeaBIOS, it get stuck on a screen with "Booting from Hard Disk..."

 

Am I missing something?

 

Well, you can't switch from OVMF to Seabios as the VM won't be able to boot off the vdisk.

 

I would try creating an identical (new) VM and let the setup start, then cancel it and force close the VM. Then use your original vdisk image by either copying it to the new VM folder or change the XML to point to the original (old) vdisk.

Thanks GHunter.

 

I tried what you suggested, but without success so I ended up just reinstalling the VM altogether.