vCenter

Blue screen 0x0000007B boot error with 64-bit Windows 2003 virtual machine converted from physical machine.

I am running VMWare Converter Starter Edition version 3.0.0 build-39557 installed on a Dell PowerEdge 2950 (a couple of months old) running Windows Server 2003 Enterprise x64 R2 (version 5.2.3790, SP1 with all the latest updates). The server has SCSI RAID drives (2 separate arrays for a physical C: and D: drive).

The physical machine is a new clean installation of 64-bit Windows Server 2003 with no other software installed except for VMWare Server and Converter.

I am attempting to create a virtual machine from this machine to run in VMWare Server (version 1.0.1 build-29996) on the same physical machine. The conversion appears to succeed, but when I attempt to start the new virtual machine, it begins to boot, displays the Windows 2003 startup screen briefly, and then fails with a blue screen with the following error:

STOP: 0x0000007B (0xFFFFFADFD520F3C0, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)

I understand the "0x0000007B" means that it can't access the boot device for some reason. I have searched these forums and the knowledge base, but haven't found a solution to this problem.

I have been able to successfully convert and boot a 32-bit Windows Server 2003 physical machine as a virtual machine running in this same VMWare Server. I don't have any other 64-bit machines to test this with.

I am logged in directly to the console of the physical machine with the administrator account. I enabled virtualization in the BIOS. I have tried various combinations when building the virtual machine (customizing or not, fixed or variable disk sizes, importing both C: and D: drives or importing only the C: drive, etc). I have the SYSPREP files from the x64 installation disks locally on the server, and I have run SETUPMGR in this folder to create a SYSPREP.INF file. All of these various attempts have failed with the same boot error.

Is it possible to build a 64-bit virtual machine using VMWare Converter Starter Edition? Any suggestions on how to resolve this issue?

I don't see why it would not work.

What services do you have running on the source server? Are there any non essential services you can disable to troubleshoot?

Are you able to boot up in Windows Safe Mode?

I have the same problem booting a 64-Bit converted Windows 2003 System. Booting in Windows Safe Mode doesn't change anything, it's the same Blue screen with 0x0000007B ...

Hello,

I had about the same problem. I configured in the BIOS that the processor must be virtual enabled. After that my 64bits server was working. Hope is is helpfull to you

The BIOS Settings are correct, new installed Windows 2003 64-Bit machines are working fine, only converted machines do not boot after the migration.

I have the same problem. I think it is because my original 2003 server has an IDE controller but the converted VM has a SCSI controller. Does anyone know how to tell Converter to create IDE drives?

Converter by default creates SCSI virtual disks. It can handle IDE source disks and convert them to SCSI.

What do your disk entries say in your .vmx?

They all say scsi (except the cd/rom) but since the source OS thinks that it is booting from IDE, won't this cause a 7B on booting?

Can you try running Converter -> Configure on that unbootable VM again? It should properly replace the controller inside the Guest to match the .vmx settings it originally created. Converter did create the VM for you, correct?

How do I do that? Converter built a directory with all the files. I did configure before the conversion so that it would use a different ip address, hostname, etc... Where is the Configure option to run on an existing VM?

Ok I found it (right in front of me!). I redid the Configure on the existing unbootable VM, no luck.

I would try attaching the VM's unbootable disk to another Windows VM and looking inside it to verify that the boot.ini is correct.

Hi Pangchen,

could you please let us know if there is solution to this BSOD?

I'll appreciate this a lot!!!

I'm also having the exact same problem, in fact my situation is identical right down to the hardware, software and method. If i run a repair option from the Windows x64 cd the server comes up fine, but i would have thought the converter would have worked fine.

Any updates on what else to try? I have checked the boot.ini and all is normal. Suggestions?

One possible reason is that the VM ended up with BusLogic SCSI controller instead of LSI Logic. Can you please post the contents of your .vmx file to verify that this is the case?

same problem here.. trying to convert a 64bit XP to VM and getting 7b stop code...

Tried changing LSI to Buslogic, but didn't help..

I think theres a major issue with 64bit compatibility with VMware Converter

I have had the same exact issue that has been described above. Used the Converter on a SUN Fire X2100 Server 2003 x64 install and it blue screens when I try to load the VM. Hope this gets figured out soon.

Josh

ANY PROGRESS WITH THIS COMMON ISSUE?

OK, Converter 3.0 is not installing LSI Logic SCSI driver into the target VM. This causes Windows to BSOD with 0x7b aka "inaccessible boot device". Stay tuned for the fix availability. Sorry for the delay.

I guess I better add my case to the list as well. I just tried converting an XP x64 physical machine to a VM, with identical results: BSOD, 0x07b, same values in the four included addresses.

Do you know if there is a fix for this boot error yet?

This issue is fixed in Converter 3.0.1.

When converting 64 bits guest. I use the customization wizard, so that sysprep will run. I don't reset the SID.

This will make sure a mini-setup will be run and the system can boot afterwards.

It's allmost the same a with symantec live state restore, it also does a mini setup after restore.

The migrated VM blue screens with 7B because VMware convereter doesn't add the entry for VM disk to the criticaldevicedatabase in the registry.

Without this the symmpi driver for lsi logic scsi does not load in the beginning. You can manually add the following entry by merging the following

Windows Registry Editor Version 5.00

"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

"Service"="symmpi"

Just so noone else wastes their time with BartPE/Regedit trying to add that key to their system hive, it doesnt work.

-Drew

The regedit solution posted above has worked for me.

Thanks.

Could you post your exact process for implementing it?

All I did was booted the VM using BartPE, opened regedit clicked on hkey_local_machine, clicked on file -> load hive selected c:\windows\system32\config\system (which is the Windows 2003 Enterprise 64bit VM that is giving me the 0x0000007B error) I loaded the hive as SYSTEM2, I expanded SYSTEM2 -> ControlSet001 -> Control -> CrticalDeviceDatabase. I made a new key called pci#ven_1000&dev_0030 I then created a string named ClassGUID with the value data {4D36E97B-E325-11CE-BFC1-08002BE10318} i then created another string called Service with the value data symmpi

I then unloaded the hive

i rebooted the machine and told the VM virtual bios to boot from the HD it then began the infinite reboot loop.

I then went back in to BartPE to make sure the changes I made to the registry were still in there and it appears that they were.

Any suggestions?

thanks,

-Drew

.

You may also need to check if symmpi.sys is present in winnt\system32\drivers and hklm\system\controlset001\services has symmpi key present and start has a value of 0 (start on boot). You may need to import this from another working machine.

I built a small helper VM with win 2003 64, attached the c: drive of migrated/crashing VM as second drive. I was able to load hive and compare registries better.

btw the solution is on the same lines as MS kb314082 - 'more information' section

Woo hoo, it works :smileywink:

-Drew

Very nice ...

Kleiner TIPP:

Nehmt die Ultimate Boot CD (). Dort gibt es unter den Registry Tools "Fix hdr", was eure vmware automatisch "repariert".

Gruß

Fishermans

I have now a similiar problem with Windows Server 2008 (64bit).

I used VMWARE Converter 4.0 Beta. Source was VMWARE Workstation 6.5.

I get BSOD (STOP 7B)

Is there already a fix for Win2k8???

Best regards,

Volker :smileyhappy:

I'm having a simlar problem with Server 2008 64bit.

Used VMware converter and booted up the machine - that all worked fine but I also need to restore the system state to bring over a live AD. Using the WBADMIN command to resotre the system state causes the 07b error.

I have 32 bit 2003 servers that have restore the system states without any problems.

I'll try the DVD and the repair option now but hoping for a better fix than that :smileyhappy:

Ditto with the exact same problem here...is it possible to fix using the win2k3 CD? If possible please post fix procedure...

Thanks

Sabandija

I have the same issue. Working with vmware to resolve. Once they stop blaming the hardware maybe we will get to the bottom of this.

I converted (P2V using Converter) a 32bit Windows 2003 OS to a virtual server.

The virtual server was running BusLogic SCSI drivers and it came up fine.

After the conversion was complete, I upgraded to Windows Server 2003 Enterprise with SP2.

I tried converting my Windows server to an LSI logic SCSI device and it blue screened as noted above.

I went back to BusLogic and it booted normally.

This document from ESX 2 days says there is no noticeable performance improvement using LSI instead of BusLogic.

http://www.vmware.com/pdf/ESX2_Storage_Performance.pdf

Please use the Windows 2003 CD to repair the OS to correct this.

I have seen this behaviour on Windows 2003 64-bit only; 32-bit is not affected.

The LSI logic driver is not getting added to the VM if the source does not already have a copy of the driver shipped with the OS. Running an OS repair will fix this by adding in the drivers from the Windows CD.

Should it be possible to install the driver on the source prior to running Converter? If so, is there a recommended way of doing this?

SOLUTION[/b]

Boot to a Recovery Console. If it wasn't installed on the server you're trying to convert (it isn't by default), you'll have to boot from a 64-bit Windows CD (doesn't necessarily have to be the same flavor/version as the installed OS). Press the "R" option instead of "Enter" at the first prompt screen.

Select your Windows installation and supply the Admin password.

At the prompt, type:

enable symmpi SERVICE_BOOT_START[/i]

Then type "exit" to reboot. The driver files for the virtual SCSI adapter are installed by default, but frequently (as we've seen here) disabled in typical installations. The above command simply re-enables the driver for the boot environment.

I still suspect there is a way to do this on the source machine (while Windows is running) prior to running Converter, but I haven't looked in to that too much yet. More if I find anything.

VMware, PLEASE update Converter to enable this driver automatically as part of the conversion process!

JN

Not tested, but it should be possible to enable the symmpi (LSI SCSI) driver on the source machine (preferably prior to running Converter) by running this from a command prompt:

sc config symmpi start=boot[/i]

JN

This should be fixed in 3.0.1

Minor correction, the command should be:

sc config symmpi start= boot[/i]

Notice the space after the equals sign.

I've done this and the problem still remains...

Dear all,

i've same problem blue screen when try to convent win2003 x64 from physical to virtual, and after complain to our re-seller, they provide us with iso file (converter-x64.iso) that must run after converting process and it's work.

But that iso file cann't work when converting win2003 x64 from virtual to virtual, it always stop with message "..disk incompatible.." (at progress 97%), because vm never up and iso file cann't run.

any one has try it..??

I have also had the exact same fault with windows 2004 64 bit whilst converting a physical machine using ide disks to a VM. I gget the same BSOD 7B error.

I have tried running the commands as specified but the VM still wont boot.

I had a problem with the sc command, when in repair mode it would not let me execute the command and cli behaved as if the command was not present but it was on the server.

Any suggestions! alan.macmillan@bt.com

I'm having the same issue with a converted 64 bit Windows 2003 server.

There is no symmpi driver in my installation, so this is why the following command is not working as instructed in the repair console.

sc config symmpi start= boot

Anyone have any ideas out there, this seems like a simple one... or should at least be addressed as it is so common!

O.K. I've converted a ton of machines, desktops and servers. I ran into the same Blue screen 0x0000007B error on a VM created from a Dell Vostro 420 and have tried everthing in this thread to fix it. After weeks of trying everthing under the sun I installed the latest build of converter and was looking at the settings and found out by default it uses "preserve disk controller type" by default. I changed this to VM SCSI and ran converter one more time and the machine boots up fine.

for 2003 Converter 3.0.3 is recommended - it does not mess up the settings like 4.0.1 usually does




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup

I had exact same problem.

I removed SCSI Controller added IDE Controller and attached its VMDK, No more blue screen :smileyhappy:

Use Vmware Vcenter converter.

Had the same problem after transferring Windows Server 2003 from Hyper-V to ESXi 6.5:

Solved doing the following:

Mount VHD or VMDK as IDE drive in VMWare Workstation 15.X+

It should boot into OS without BSOD

You can now install vmscsi drivers following VMware Knowledge Base

You can take this opportunity to install VMWareTools

Export to OVA/OVF

Deploy OVA/OVF to ESXi host