Hyper-V Virtual Machine (gen 1) hangs with "Booting from SAN device 0x80"
-
@sebastian-roth I did this before posting. I even tried every GRUB Exit Type.
-
@sgwk I am absolutely sure you don’t get the same error message for all the different exit style settings. Please try each and every exit style again, take a picture and post here which is causing what error.
-
@sebastian-roth but I listed the “messages” I got on my post “…I get a blinking cursor or “starting cmain()”, “chainloading failed…”, iPXE>, grub>, etc.”
-
Is this “new vm in hyper-v” setup as Generation 2? Is it defined to boot in UEFI mode?
Have you tried rEFInd?
-
Are you changing exit types on the host, or global? If a host has a defined exit type, it will supersede what the global value is (cascading down if that makes sense.)
This still, really, feels like a UEFI based system though. Windows 10 is typically deployed this way and for that I think this is why you “just see the blinking cursor” or “starting cmain()” for grub. It isn’t that grub or the exit types aren’t working, rather this really seems that the exit type isn’t exiting and releasing to the proper mode the device is expecting to boot into.
-
@tom-elliott It is gen 1. I tried Refind_efi and it did not work.
-
@tom-elliott First, I changed the Exit Types globally in the iPXE boot menu. Now, I am changing them on the Host. Thanks,
-
@wayne-workman I’m trying this, now.
-
@sgwk said in Hyper-V Virtual Machine (gen 1) hangs with "Booting from SAN device 0x80":
@tom-elliott It is gen 1. I tried Refind_efi and it did not work.
Sometimes the basics need addressed. So, there’s two exit type options per host. One for legacy/BIOS mode and one for uEFI.
If your changing the bios one only, but the VM is factually uEFI, then no change will appear to happen. Because fog directs uEFI machines to use the uEFI setting.
So please check this too.
-
@wayne-workman I am changing the Exit Type for BIOS and UEFI.
-
@sgwk So do you have success or no joy after you made the change?
-
I did your suggestion “If I had this issue, I’d reinstall the OS on the VM from vanilla ISO, and then see if it can netowork boot via FOG and then sent to the HDD to boot the OS via the fog menu.”
This VM will boot from the FOG menu if the BIOS Exit Type is set to boot grub_first_hdd. It will boot to Windows if the BIOS is set to boot from IDE first.
However, my original VM created from a FOG captured image gives “Launching GRUB… begin pxe scan… Starting cmain()…” when the Exit Types for BIOS and EFI are set to grub_first_hdd. Also, if I set the BIOS to boot from the IDE first, I just get a blinking underscore (cursor).
I’m not sure where this leaves me since the ISO is a trial from Microsoft and the PCs from the vendor do not come with the ISO.
Thanks,
-
@george1421 no joy yet
-
@sgwk So if you remove the nic from the network boot order does it boot correctly?
Since this is a gen 1 VM, what host OS are you using for this VM? Is that up to date? I assume that since it is a gen1 then bios mode is the only option? (sorry I’m a vmware guy).
-
@sgwk said in Hyper-V Virtual Machine (gen 1) hangs with "Booting from SAN device 0x80":
This VM will boot from the FOG menu if the BIOS Exit Type is set to boot grub_first_hdd.
This is much different than what was happening before - so the problem is (was?) with the image. Just build a new image then.
-
Thanks for all the suggestions. I will have to move this to the back burner and concentrate on physical PCs, now.
-
@sgwk Will you have time to tackle this issue with us again or should be just close it?
-
@sebastian-roth Hi, I can take a look if you have another suggestion. Thanks,
-
@sgwk I would like to see if we can confirm the issue. Though I don’t have access to Hyper-V, not yet. Maybe I can spin one up. But first lets see if @Moderators or @Testers have a similar setup at hand. Please try and let us know.
-
@sgwk Sorry, couldn’t find the time and resources to try this out. Anyone having this setup at hand out there?
