Move Windows OS from one platform to another
-
@scottalanmiller said in Move Windows OS from one platform to another:
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
I think you almost certainly have a false assumption driving you to go down a rabbit hole.
While I did mention the storage as a possible issue, I wasn't limiting myself solely to that as the problem, but I wasn't really sure where else to look - hence this post.
But now I do have some new things to search for, namely how, if possible, to change the HAL.
CPU architecture is possible, but unlikely.
Right - I've rarely (actually never) had an issue going from multi to multi before as long as I was going from Intel to Intel or AMD to AMD. Which is why I pretty much dismissed the HAL problem - but it could be more than that - it could be an instruction set issue - something about the chipset drivers looking for something the old Xeon had that the new i5 doesn't.
-
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
I think you almost certainly have a false assumption driving you to go down a rabbit hole.
While I did mention the storage as a possible issue, I wasn't limiting myself solely to that as the problem, but I wasn't really sure where else to look - hence this post.
But now I do have some new things to search for, namely how, if possible, to change the HAL.
CPU architecture is possible, but unlikely.
Right - I've rarely (actually never) had an issue going from multi to multi before as long as I was going from Intel to Intel or AMD to AMD. Which is why I pretty much dismissed the HAL problem - but it could be more than that - it could be an instruction set issue - something about the chipset drivers looking for something the old Xeon had that the new i5 doesn't.
Right, the Xeon to i5 might do it. Or maybe it is failed detection of some sort.
-
I took a backup using Windows backup utility and restored that into a XS 7 server. I'm getting the exact same BSOD 0x0000007b
When the system then boots into the system recover console I look at the diskpart information for
and it's different from the original machine.
Here is the original machine
The VM does not System listed under Info, everything else is identical.
Any thoughts on this?
They are both Active, I even marked it inactive, then back to active, but that didn't fix anything.
-
This is an interesting post - seems to imply the system just trying to load a driver is causing a problem.
http://www.azmer.my/p2v-windows-server-2008-blue-screen-0x0000007b/How to perform the step:-
- Boot-up your VMs with Windows Server 2008 CD.
- Choose Repair Your System
- Choose Command Prompt
- type : $regedit
- Select HKEY_LOCAL_MACHINE
- Click on File –> Load Hive
- Choose your regedit location : (c:\windows\system32\config\SYSTEM ) (make sure correct location)
- Name it as “p2v”
- Then Expand your “p2v”
- Expand ControlSet001 –> Services –> LSI_SAS
- Change LSI_SAS (Start) Property to (0)
- Change LSI_SAS2 (Start) Property to (0)
p/s: It’s could be LSI_SAS, LSI_FC, atiide, megasas, vmscsi, mptsas but depend on the drivers load.
-
Sadly this didn't fix my situation.
-
Found this https://support.citrix.com/article/CTX124961
The following workaround is required to repair a virtual machine that meets this scenario:
After importing the virtual appliance attach a WinPE x64 boot disk ISO to the VM (or use the Server 2003 installation media and drop to a command prompt). Boot the VM. At the WinPE console type the following command: chkdsk c: /f When chkdsk is finished shut down the VM. Eject the WinPE ISO. Attach the xenserver-linuxfixup-disk.iso to the VM. Start the VM. The VM shuts down when the fixup process is complete and the ISO can be ejected. -
I'm trying this now, even though I've done these things separately already in the past.
-
Nope didn't work - I found that If I shrink the partitions I can just barely squeeze it into my ESXi host. trying that now.
-
OK I think I've licked it - it was a storage related issue.
I originally found this page http://www.justandrew.net/2009/10/stop-0x0000007b-on-p2vd-windows-7.html
Which lead to this currently none working thread, but using the wayback machine I was able to see the page and the referenced post.
I booted into recovery mode, launched regedit, I loaded the hive off the
drive, made the following changeshklm\loaded hive\SYSTEM\ControlSet001\services\Intelide\Start = 0
hklm\loaded hive\SYSTEM\ControlSet001\services\pciide\Start = 3
Now in my case I had previously disabled the HP RAID services in hopes of solving this, so you might have to do that as well.
-
@Dashrender Nice find, did the VM boot properly?
-
Nice to know a little thing like that can bring down a system.
It's like the 50 cent washer than keep disabling my $600 snowblower...
-
@BRRABill said in Move Windows OS from one platform to another:
Nice to know a little thing like that can bring down a system.
It's like the 50 cent washer than keep disabling my $600 snowblower...
LOL I have a 50 cent thing killing my snowblower too - the breakaway in in the tines - I just replace it once a month or so with a new 5 cent bolt and nut.
-
@BRRABill said in Move Windows OS from one platform to another:
Nice to know a little thing like that can bring down a system.
It's like the 50 cent washer than keep disabling my $600 snowblower...
Though the storage controller isn't what I would call a little thing.
This issue is probably a fairly uncommon one, not sure how many P2V's are going on much anymore.
-
Someone looking at this thread had a hard time figuring out how to open the registry editor after booting to CLI mode from the 2008 R2 media. from the command line, type regedit and hit enter, it will load.
