P2v and 0x0000007B BSOD

[islr2558]

I did an import of a physical machine (dell optiplex 780) that was a windows 7 32bit. I used all the defualts to import, however during booting of the machine it is getting and 0x0000007B BSOD. What is the proper way to get the mass storage drivers (if that is the issue) into the virtual machine. Or if i did something wrong how should i proceed with future P2V?

Thanks

[continuum]

which SCSI-controller did you select ?

anyway - read this on how to fix it -

Patching - easy variant

This procedure is used when otherwise the VM would boot into a bluescreen type 7B.

This assumes that VMware is the target and you configure the VM with VirtualHardware type 7.

It only applies if the virtual disk is configured like this

scsi0.virtualDev = "lsisas1068"

scsi0:0.fileName = "imported.vmdk"

On the target platform boot the newly created VM into the Windows 7 Recovery CD.

After boot is finished click on the CMD-button and run regedit.

Select HKLM and then Menu > File > Load Hive.

Browse to the Windows-directory on the virtualdisk > system32\config and select the file SYSTEM.

When asked for a name enter p2v.

Then find the key

HKLM\p2v\ControlSet001\services\LSI_SAS

and set the start type to REG_DWORD 0

Then select HKLM\p2v and click Menu > File > Unload Hive.

You can close regedit now and restart.

On next boot you can start into the 2008 R2 system. It should find drivers and probably needs a reboot when done.

grrrr - no wonder this sounds so familiar - you already asked the same a minute ago ... please - thats not necessary




_________________________

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

[islr2558]

I apologize, I thought that my question was going to be lost as it wasn't under the right subject and I had answered my own question under that subject. I appreciate your help and i will try what you suggested.

[islr2558]

OK i do not follow this exactly

It only applies if the virtual disk is configured like this

scsi0.virtualDev = "lsisas1068"

scsi0:0.fileName = "imported.vmdk"

However i did follow the rest of your directions and had the same results. 07B

What is the purpose of loading the hive then changing it and and unloading. Is it actually changing the file that is located at windows\system32\config\ called system?

[a_p_]

Can you please post/attach the VM's vmx file.

André

[continuum]

this are instructions on how to use a LiveCD to configure the driver settings of a Windows 7 so that it boots from a VM with virtualDev LSI-SAS.

To check if that fits to what you have in your vmx-file we need to see it

those snippet is the relevant part of a howto I posted here:

http://sanbarrow.com/p2v2008r2.html




_________________________

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

[islr2558]

Here is my vmx in its entirety. Like i said i used the defualts so that is just how it generated it. I see what you mean about the scsi0.virtualDev = "lsilogic" though not scsi0.virtualDev = "lsisas1068" like in your example.

.encoding = "windows-1252"

config.version = "8"

virtualHW.version = "7"

memsize = "2468"

MemAllowAutoScaleDown = "FALSE"

MemTrimRate = "30"

displayName = "p2v"

guestOS = "winvista"

numvcpus = "2"

usb.present = "TRUE"

ethernet0.present = "TRUE"

ethernet0.addressType = "generated"

ethernet0.connectionType = "bridged"

ethernet0.virtualDev = "e1000"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "p2v.vmdk"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

mks.enable3d = "TRUE"

vmci0.present = "TRUE"

vmci0.unrestricted = "TRUE"

tools.upgrade.policy = "useGlobal"

ehci.present = "TRUE"

ide0:0.present = "TRUE"

ide0:0.autodetect = "TRUE"

ide0:0.filename = "U:\Apps\Windows\Windows 7\Win7_32.ISO"

ide0:0.deviceType = "cdrom-image"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

lsilogic.noDriver = "FALSE"

extendedConfigFile = "p2v.vmxf"

virtualHW.productCompatibility = "hosted"

ethernet0.generatedAddress = "00:0c:29:0d:85:54"

tools.syncTime = "FALSE"

uuid.location = "56 4d 2d 7e 50 11 92 8d-35 14 38 3d 05 0d 85 54"

uuid.bios = "56 4d 2d 7e 50 11 92 8d-35 14 38 3d 05 0d 85 54"

cleanShutdown = "TRUE"

replay.supported = "FALSE"

replay.filename = ""

scsi0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "16"

usb.pciSlotNumber = "32"

ethernet0.pciSlotNumber = "33"

ehci.pciSlotNumber = "34"

vmci0.pciSlotNumber = "35"

vmotion.checkpointFBSize = "134217728"

usb:0.present = "TRUE"

usb:1.present = "TRUE"

ethernet0.generatedAddressOffset = "0"

vmci0.id = "84772180"

usb:1.deviceType = "hub"

usb:0.deviceType = "mouse"

floppy0.startConnected = "FALSE"

tools.remindInstall = "TRUE"

ide0:0.startConnected = "TRUE"

[continuum · Accepted solution]

change

scsi0.virtualDev = "lsilogic"

to

scsi0.virtualDev = "lsisas1068"

and then follow the instructions from above

_________________________

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

[a_p_]

While you are editing the vmx file, you may also want to replace

guestOS = "winvista"

by

guestOS = "windows7"

or - even better - edit the guest OS in the VM's settings.

André

[islr2558]

Ok that worked.

Follow up question, why did i have to do that? Is that not something that the import can figure out? or can i automate the process somehow? What about other machines. will they need something different in the scsi0.virtualDev field?

Thanks for all the new found info

Sorry again for the double post, just wanted the questions under the correct subject line.

[continuum]

why you have to do that ?

The embedded converter is outdated - don't know which version you used ???

Anyway - Converter is a tool that is not very high on the list of VMware developers I guess.

And for windows7 and 2008 doing this is pretty easy - way easier then with earlier versions.

What about other machines. will they need something different in the scsi0.virtualDev field?

I use lsi-sas with win7 and 2008

lsilogic for 2003

buslogic XP and 2000

If I have to import Vista I open the trash bin and put Vista into it 😉




_________________________

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

[a_p_]

For Windows 7 and 2008 you might get better results with the current version of the VMware vCenter Converter Standalone 4.3

André

[naderawad]

God bliss you ! this saved my life!

[AndrewKV]

---

@continuum wrote:

change

scsi0.virtualDev = "lsilogic"

to

scsi0.virtualDev = "lsisas1068"

and then follow the instructions from above

---

This still helps even after 14 years! )))

Had a need to P2V old physical machine with Win7 and spent few hours trying to figure out a solution for 7B BSOD. Changing to [scsi0.virtualDev = "lsisas1068"] finally resolved the issue and Win7 booted fine!

Thanks!