Port - Exporting VM from Hyper-V and into XenServer - having issues

scottalanmiller

@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.

Lennertgenbr

@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

Net Runner

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.

Lennertgenbr

@Net-Runner Already tried Starwind V2V. It failed on me. Didn't convert the disk just made an empty one that's 512kb

scottalanmiller

@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!

Dashrender

@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.

Lennertgenbr

@Dashrender sfc /scannow will be no help i guess? Can't remember it ever running from a recovery console

Dashrender

I suppose that a 0x0000007b might be fixed by SFC scan...

I still think you have a registry issue or a missing driver issue.

As wires as this sounds... Try installing the xenserver tools in the old VM before you take the image that you then restore to xenserver... Who knows might get lucky.

momurda

I dont think you can sfc/scannow from the recovery console.
What are the export options for Hyper-V? Is ova not an option?
You are getting the 0x7b error which seems to be common recently on these export/import operations.
If you boot the vm with the 2008r2 dvd mounted as first boot device and boot to it, you will eventually get to the Repair your Computer option. This is the same as Startup repair but from the dvd instead of the hdd recovery console. If you do this, it will scan for existing Windows installations. If it finds one it will then attempt auto repair. 'Attempting repairs... blah blah" and then probably, "Windows was unable to automagically repair your computer". When it does this, click on the details(i think it is actually 'view detailed diagnostic info' or somethign) and scroll through that huge list of things it checked. Most of them will say 0x0 which means no problems. There will be one thing that has a different code; this is where the problem lies. Usually this is a corrupt file or missing file that Windows has marked as required for booting.
Though with the 7b error the above might be moot if the boot process is interrupted before all that.

Dashrender

@momurda said in Port - Exporting VM from Hyper-V and into XenServer - having issues:

Though with the 7b error the above might be moot if the boot process is interrupted before all that.

My 7b error was due to IDE drivers being disabled and one was actually missing (had to install from media) AND HP SCSI drivers being enabled. Upon changing those it worked.

Lennertgenbr

I still have to look into this. Didn't get around to it because of my birthday

BRRABill

@Lennertgenbr said in Port - Exporting VM from Hyper-V and into XenServer - having issues:

I still have to look into this. Didn't get around to it because of my birthday

Excuses...

Net Runner

@Lennertgenbr Looks like either read rights are failing or drive surface/filesystem issues.

Lennertgenbr

Allright I got the machine live!
So what I did was really plain and simple...

Create a backup and recovery media with Veeam endpoint backup.
Restore the backup onto my xen server (with driver injection).
Boot the machine in safe mode.
Disable hyper-v services (even though they are disabled in hyper-v...)
Reboot
Done

I still can't believe it took me so long to figure this one out. I was deleting/editing registry entries related to drivers that I didn't need etc...