Port - Exporting VM from Hyper-V and into XenServer - having issues
-
-
@Dashrender disabled them, rebooted but the same BSOD.
I'm going to inform myself about the previous P2V. I'm guessing yes, but I inherited the environment so I can't be sure.Are the megasas and megasr keys something to disable aswel?
-
@Lennertgenbr Discussed with the boss and it is possible that this machine has gone through a P2V previously.
I saw in the config of the hyper-v that my 2nd disk is linked to a SATA controller. Is this a problem for xen?
-
@Lennertgenbr said in Port - Exporting VM from Hyper-V and into XenServer - having issues:
@Lennertgenbr Discussed with the boss and it is possible that this machine has gone through a P2V previously.
I saw in the config of the hyper-v that my 2nd disk is linked to a SATA controller. Is this a problem for xen?
Shouldn't be - when you are booted from the ISO, can you see both disks? If yes, then not a problem for XenServer.
-
@Dashrender In disk part i can see all my disks
-
@Lennertgenbr said in Port - Exporting VM from Hyper-V and into XenServer - having issues:
@Dashrender In disk part i can see all my disks
Are they mounted? do they have drive letters? if yes, you can change to them and look around at your files - if you see them, then XenServer definitely does not have a problem.
-
On your running Hyper-V VM, you need to find which services are running your storage, then find those in the XS VM and disable them. I had some that were conflicting, which was stopping my system from booting.
-
@Dashrender Easily found by looking at the used drivers on my storage disks I presume
-
@Lennertgenbr said in Port - Exporting VM from Hyper-V and into XenServer - having issues:
@Dashrender Easily found by looking at the used drivers on my storage disks I presume
I would tend to agree. Then find the services that start those, then disable on XS VM.
-
@Dashrender I'm on it!
-
Ok so i've found this but the storvsc is already disabled... Should i disable the other drivers? They seem like native windows ones and not really hyper-v specific
-
We're out of my wheel house at this point.
Can you enable boot logging by pressing F8 and choose boot logging, then look at the log for what driver it's specifically crashing on?
-
@Dashrender I'm restoring todays backup first. Gonna start as clean as possible.
Then i'll run the boot with log.Hope I can get this show on the road really soon. Need to free up that hypervisor lol
-
Quick update, Backup is restored. I am running a chkdsk on all my drives to ensure they are ok. Hoping this will finish later today
-
@Lennertgenbr said in Port - Exporting VM from Hyper-V and into XenServer - having issues:
Quick update, Backup is restored. I am running a chkdsk on all my drives to ensure they are ok. Hoping this will finish later today
Great, keep us up to date.
-
@Dashrender Ok, i can't boot into the advanced startup options list..
I keep getting the "launch startup repair" "start windows normally screen" on which i press enter and then bash my F8 key. But to no avail
-
I would recommend you to try StarWind V2V Converter https://www.starwindsoftware.com/converter. It does hardware patching during conversion and can automatically enable PC rescue mode. Saved me a lot of times and time. Of course it supports most of the common virtual machine drive formats.
-
@Net-Runner Already tried Starwind V2V. It failed on me. Didn't convert the disk just made an empty one that's 512kb
-
@Lennertgenbr said in Port - Exporting VM from Hyper-V and into XenServer - having issues:
@Net-Runner Already tried Starwind V2V. It failed on me. Didn't convert the disk just made an empty one that's 512kb
Now that is awesome compression!
-
@Lennertgenbr said in Port - Exporting VM from Hyper-V and into XenServer - having issues:
@Dashrender Ok, i can't boot into the advanced startup options list..
I keep getting the "launch startup repair" "start windows normally screen" on which i press enter and then bash my F8 key. But to no avail
try running chkdsk
/r like 4-6 times, rebooting between each time. you can even try normal booting between each time if you want.
That's what fixed my 2003 server issue.
