1

Hello,

This is an inherited setup

Running into an issue trying to move a VM off an older host.

Source Host OS: Windows Server 2012 R2 Standard 64-bit operating sys
VM: Windows Server 2003, Gen 1, Version 5.0

Destination Host: Windows Server 2016 Standard 64-bit operating sys

I started off making a copy of the VM and moved the copy over to the Destination Host. The VM boots into the boot loader of the VM and I can see 2 partitions, I choose the partition in which Windows is installed and after that the VM reboots and it begins all over again. (Never boots into Windows)

image
image819×463 36.2 KB

I have verified that the copy is fine by creating a new VM on the Original host and pointing the VM to the network location of the copied version, confirmed it booted into Windows.

Destination Host:
Event viewer–>Apps and service logs–>Microsoft–>Windows–>Hyper-V-Worker → Admin
This is reporting that “ServerName” was reset by the guest operating system.

Any help would be greatly appreciated.

8 Spice ups
2

Is it possible something about the new host isn’t compatible with the server version? Maybe a driver missing? Can you look at the log files on the new host to see if it points out any issues?

1 Spice up
3

You’ve not inherited well my friend.

Those OSes are almost older than me.

I’d suggest using the advanced start-up as suggested by pressing F8 and seeing if it will start in safe mode first.

If it does, we can perhaps take a look at some logs.

3 Spice ups
4

Have you tried going into the Hyper-V Manager, go to the settings of the VM, expand the processor, highlight compatibility and check off “Migrate to a physical computer with a different processor version?”

2 Spice ups
5

Took a bit, but I was able to get it to boot in Safe Mode. Based on it being able to boot with Safe Mode, there is an issue with one of the drivers.

2 Spice ups
6

Yes I have checked this

2 Spice ups
7

There should be limited drivers needed for a VM, especially one of such an age.

Moving it from 2012 to 2016 isn’t going to give you much time either, not that the current OSes help.

Is there a reason to move it from 2012 to 2016 vs migrating it from 2003 to something newer?

2 Spice ups
8

My guess from above is that 2003 threw a fit with the newer hardware. I too would like to know the reason for the move. Probably should upgrade the VM OS first…

1 Spice up
9

Don’t copy it - export it.
Check the VM settings - on old and new hosts. Is the virtual hardware identical?

2 Spice ups
10

Yes use export, then on the new machine use the import wizard, in addition to processor comparability, you could also be seeing the change in partition format that happened around win8.1.

2 Spice ups
11

Are the host hyper-v servers or server 20xx with hyper-v roles ?
Is this going to be a permanent move ?

1 Spice up