question

hendriyu-7141 avatar image
0 Votes"
hendriyu-7141 asked 4trax-7021 published

Hyper-V VM is not able to boot up

Dear Microsoft Expert,

Good Day

We would like to migrate all VMs from Vmware ESX to Microsoft Hyper-V. To do this, i am using the tool from Microsoft called "MVMC" to convert the Vmware .VMDX files to Hyper-v virtual machines files with .VHD or .VHDX extension. The file size is 1TB and the conversion is successful without any error message and currently i have the .vhdx file with me.

Not that on Vmware, those VMs are running Microsoft Windows Server 2018 R2.

Now, i am creating a brand new virtual machine in new hypervisor server (running Windows Server 2019) and attach the converted .VHDX file as the HDD. However, when i tried to boot, i am only seeing blank black screen with blinking cursor on the left. Please refer to the attached picture below. I have tried with both First Generation and Second Generation Virtual Machine creation, but it is still the same.

21373-hyper-v.png




Kindly help to advise what is the issue. I am suspecting issue with some boot configuration, however not sure which part is giving problem.

Appreciate Microsoft Expert helps on the issue i faaced.

Many Thanks

Hendri

windows-server-hyper-v
hyper-v.png (30.3 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Satishchaudhary-1504 avatar image
1 Vote"
Satishchaudhary-1504 answered 4trax-7021 published

Create New and select Generation 2, it's worked for me

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

This also solved my problem!

0 Votes 0 ·
Satishchaudhary-1504 avatar image
0 Votes"
Satishchaudhary-1504 answered

Creat new VM and select gneration 2
it's worked for me

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

XiaoweiHe-MSFT avatar image
0 Votes"
XiaoweiHe-MSFT answered hendriyu-7141 commented

Hi,

Please check the bootup method of the VM, in the BIOS, set the first startup order:

21488-image.png

Then start the VM and enter F8, and select "safe mode", in safe mode, select "Repair your computer":

21511-repair.png

Check if it could help repair the system.

If the above method still not work, It's recommended to open a case with MS to analysis the dump for deep troubleshooting:

Below is the link to open a case with MS:

https://support.microsoft.com/en-us/gp/customer-service-phone-numbers


If the reply could be of help, please help to accept it as an answer, thanks for your cooperation!
Thanks for your time!
Best Regards,
Anne



image.png (56.8 KiB)
repair.png (41.4 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Dear Xiao Wei,

I did tried before to:
1. change to IDE = Fail, blank black screen with cursor blinking
2. change to CD = Fail, blank black screen with cursor blinking

For CD, actually i tried to insert Windows 2019 ISO to boot up and check whether there are any options there. But one thing, the converted VM is actually running on Windows Server 2008 R2 and now if i am trying to repair using 2019, will that work?

I am still thinking that the booting file might be corrupted during the conversion from Vmware to Hyper V or perhaps due to UEFI or Legacy BIOS modes? but, how to actually enter BIOS of the VM for changing the boot? it is unlike physical computer or server whereby we could enter BIOS to change this.

Many Thanks


Hendri

0 Votes 0 ·

----For CD, actually i tried to insert Windows 2019 ISO to boot up and check whether there are any options there. But one thing, the converted VM is actually running on Windows Server 2008 R2 and now if i am trying to repair using 2019, will that work?

Sorry for the mislead in my screenshot, if the VM is Server 2008 R2, please use the Server 2008R2 ISO to try to repair.

----I am still thinking that the booting file might be corrupted during the conversion from Vmware to Hyper V or perhaps due to UEFI or Legacy BIOS modes? but, how to actually enter BIOS of the VM for changing the boot? it is unlike physical computer or server whereby we could enter BIOS to change this.

Please provide the screenshot of the VM settings.

The method in my above reply is used to help go into BIOS mode, does it not work when enter F8 when the VM booting?

Best Regards,
Anne

0 Votes 0 ·

Dear Xiaowei,

Good Day

The converted VM is using Windows Server 2008 R2 Enterprise Sp1, hence i am using Windows Server 2008 R2 Enterprise Sp1, but unfortunately i am not able to do repair. Please see below error message:

37370-system-recovery-error.png


You might be right about the booting corrupted issue. Because, i have verified that the converted VM is actually using EFI and GPT disks. Hence, now my question is: Should i create Gen 1 Hyper V or Gen 2? Currently, the converted VM is on .vhdx disk format and it is dynamic disk.

I tried to attach the vhdk disk file to Gen 1 Hyper V, but as mentioned above, it is not able to boot. I only see blinking cursor with black screen.

here is the hyper v settings screenshot:

37473-hyper-v-settings1.png




Please help to advise what will be the next action to try out.

Thanks
H

0 Votes 0 ·