VMware Cloud Community
drider201110141
Contributor
Contributor

STOP error 7b subcode c0000034 after p2v with Converter 5.5.3

Hello,
I have a problem with p2v conversion of one machine (Lenovo Thinkpad W530). Virtual machine gets STOP error 7b (inaccessible boot device) with subcode c0000034 (operating system not found).

I run Converter 5.5.3 and ask it to convert "powered on machine -> this machine".

The only hard disk in the computer is connected to embedded Intel ICH7 SATA controller. In BIOS it is configured to run as AHCI. OS is Windows 7 x64 Enterprise with SP1.

That's how disk configuration looks like:

diskpart_physical.png

Since Windows disovers it as ATA, I also choose this type of controller in VMware Converter.

Diskpart on virtual machine:

diskpart_virtual.png

I did everything mentioned in articles:

Windows 7 Guest: STOP 0x0000007B

VMware KB: Virtual machine fails to boot with a blue diagnostic screen stating: 7B Stop Code after u...

and nothing helped.

Of course there is no Bitlocker nor any other encryption on hard disk.

My VMX file is in attachment.

Any ideas how can this be fixed? I'd appreciate any help.

0 Kudos
9 Replies
a_p_
Leadership
Leadership

For Windows 7 select the "LSI Logic SAS" controller in the Converter Wizard.

André

0 Kudos
drider201110141
Contributor
Contributor

Already tried that. LSI_SCSI too. No change.

0 Kudos
a_p_
Leadership
Leadership

Just to confirm, did you select the "LSI Logic SAS" controller?

André

0 Kudos
drider201110141
Contributor
Contributor

Yes I did.

I also made another try and selected SCSI LSI Logic (without SAS) controller and another with choosing SATA. In all cases virtual machine crashed with stop error I mentioned in first post.

I made sure LSI Logic SAS (lsi_sas.sys and lsi_sas2.sys) and SCSI (lsi_scsi.sys) driver exist on source machine and they do.

0 Kudos
POCEH
VMware Employee
VMware Employee

Could you upload log bundle?

0 Kudos
drider201110141
Contributor
Contributor

Sure I can. Here they come.

0 Kudos
POCEH
VMware Employee
VMware Employee

I was unclear, I want to check the converter's log because of drive letter change. Otherwise you should ask in workstation forum why the VM can't run.

0 Kudos
drider201110141
Contributor
Contributor

OK, please find attached log files bundle related to my conversion task. Druve letters are different because first screenshot was done on source (physical) machine, and the second one on virtual machine booted from Windows 7 installation media.

I also don't think it's a matter of Workstation, because I tried running this machine also on Player 6 and ESX 5.5 and nothing changed.

0 Kudos
POCEH
VMware Employee
VMware Employee

Everything looks fine. IMO there is other device that prevent VM to boot, not the disk controller, however I've recommend not change the defaults for disk controllers.

Try to get support from Workstation forum, I've found many threads about 7b/c0000000034 into.

HTH

0 Kudos