VMWare Converter - Windows XP P2V - Blue Screen - 7B - 0xBA4CB524

[jkinneberg]

Converted a Windows XP Physical System and recieved a blue screen on it.  Have been extensively through all of the VMWare Knowledge base and none of the articles directly address or provide a resolution to the problem.  There is a great deal of discuss although no clear answers.  Note system converted 100% properly.

1)     The hard drive is an IDE Hard Drive.  Why do we get blue screens on IDE drives?  Does VMware by default inject the proper driver when it is converted?  Does it check to see if the proper driver exists on the system?  Or does it just blankly convert with no error checking to see if the final result will actually work?

2)     All of the articles talk about mutliple methods of resolving issues although they are directed toward SCSI drives.  What steps do we talk to ensure that the drive is functioning in VMware workstation 8 as a IDE drive.  Multiple articles have talked about editing the VMDK but its a 60GB+ file with no attribute lines to edit.  Other articles have talked about editing content in the VMX file although all of them the content they mentioned in the VMX files did not exist in the files.

3)     There are VMware articles that say you need to inject drivers with a floppy.  Then there are are articles that say you do not need to inject drivers since VMware does not PATA or did they mean SATA aka AHCI?

4)     Please help.  I wish the vendor would provide a solution to this.  Make a download package with the right drivers and registry files.  Put them in a ISO, you boot from it, it runs a script.  reboot the workstation and it works.  Have automated enough solutions that this should be easy but cannot find a place online where they have a good enough definition of the problem to turn it into a working easy solution.

5)  HOW DO I FIX THIS?

[jkinneberg]

The following is my .VMX File.  Some of the articles try to say that the VMDK description can be found with the text "ddb.adapterType".  Although this text is not in the VMX file.  The articles allude to that this might be in the VMDK file although this is a 60+GB file that is to large to edit?

--------------

.encoding = "windows-1252"

config.version = "8"

virtualHW.version = "8"

memsize = "2928"

MemAllowAutoScaleDown = "FALSE"

displayName = "D2QHY7C1"

guestOS = "winxppro"

numvcpus = "2"

sound.present = "TRUE"

sound.filename = "-1"

sound.autodetect = "TRUE"

usb.present = "TRUE"

ethernet0.present = "TRUE"

ethernet0.addressType = "generated"

ethernet0.connectionType = "bridged"

ethernet0.startConnected = "TRUE"

ide0:0.present = "TRUE"

ide0:0.fileName = "D2QHY7C1.vmdk"

ide0:1.present = "TRUE"

ide0:1.autodetect = "TRUE"

ide0:1.filename = "auto detect"

ide0:1.deviceType = "cdrom-raw"

mks.enable3d = "TRUE"

vmci0.present = "TRUE"

ehci.present = "TRUE"

pciBridge0.present = "TRUE"

tools.upgrade.policy = "useGlobal"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

extendedConfigFile = "D2QHY7C1.vmxf"

virtualHW.productCompatibility = "hosted"

checkpoint.vmState = ""

ide0:1.startConnected = "FALSE"

ethernet0.generatedAddress = "00:0c:29:97:27:fa"

vmci0.id = "-2020136966"

uuid.location = "56 4d 66 d3 f5 9b f8 9a-61 96 2d 00 87 97 27 fa"

uuid.bios = "56 4d 66 d3 f5 9b f8 9a-61 96 2d 00 87 97 27 fa"

cleanShutdown = "TRUE"

replay.supported = "FALSE"

replay.filename = ""

ide0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

usb.pciSlotNumber = "32"

ethernet0.pciSlotNumber = "33"

sound.pciSlotNumber = "34"

ehci.pciSlotNumber = "35"

vmci0.pciSlotNumber = "36"

usb:1.present = "TRUE"

ethernet0.generatedAddressOffset = "0"

vmotion.checkpointFBSize = "134217728"

usb:1.speed = "2"

usb:1.deviceType = "hub"

usb:1.port = "1"

usb:1.parent = "-1"

tools.remindInstall = "TRUE"

usb:0.present = "TRUE"

usb:0.deviceType = "hid"

usb:0.port = "0"

usb:0.parent = "-1"

[jkinneberg]

http://communities.vmware.com/message/2010897#2010897

Quoted From Other Article.

"Ok, now that you mention it that makes perfect sense, so assuming I want to work with a clone of my current machine I should go ahead and clone the machine leaving the disk adapter type at ide, then add a small SCSI disk based on the buslogic controller and make sure drivers are loaded and working for it, then shutdown the guest, make the adapter type and geometry changes to the vmdk file, then in the machine settings just remove the IDE disk and add it back as a Buslogic SCSI disk and restart the machine? I will try all of this first thing tomorrow and report back."

Breaking down this into understandable steps:

1)  Do I Have to reclone my machine.  During the VmWare Converter Process Do I add another hard drive with a buslogic controller?  Is this done near the end the screen before the summary screen in VMWare Standalone Converter?

2)  It says when you do step 1 you have to "make sure drivers are loaded and working".  How do you do this?  Do you need to install drivers are the system before it is cloned?  If so where do I download these drivers from?  Very strange that VMware Converter would not inject the right drivers during the process?

3)  VMDK is to large to edit so these geometry changes cannot be done what are the options here?

4)  This final step says go back into VMWare Workstation and re-add the hard drive VMDK as with a buslogic controller.  This option is not availble I re add it and it automaticly adds it as a IDE drive.

[continuum]

Hi
dont worry - Converter 5 misconfigures the import of a physical XP per default so your bluescreen is expected behaviour.
If you want flawless imports of XP use Converter 3.0.3

I have attached a corrected vmx-file - replace the existing one and then start Converter again - this timew use the "configure machine" option and run it against the already existing VM

I just see your last reply .... ignore that post - just replace the vmx and run Converter again

[jkinneberg]

Thank you for the response.

1)  When you say replace the VMX file I can copy that to the target Virtual Host running VMware workstation 8.

2)  When you say re-run converter do you expect me to deploy Converter v3.0.3 on the new Windows Virtual Host?  Use VMWare converter on the new physical host to target the first converted virtual, and convert it a second time?

3)  As well if I have to use converter version 3 you can no longer download it.

https://www.vmware.com/tryvmware/p/activate.php?p=converter&rct=j&q=&esrc=s&source=web&cd=2&ved=0CEk...

[continuum]

you must already have a VM that boots into a bluescreen
find the directory where it lives in and copy my edited vmx file into it - replacing the existing one.

then start Converter 5 and use the option "configure machine"
and select the VM that bluescreens

by the way - Converter 3.0.3 is still available just finding it on the vmware download site is a major pain

search via google "converter 3.0.3 download" and you will find http://www.brothersoft.com/vmware-converter-158647.html

[jkinneberg]

Thanks I will give it a try.

1) I replaced the VMX and tried to start the VM.  It started but it is incredibily slow.  Thoughts?

[continuum]

my job is done when you no longer get a bluescreen

your job now is to uninstall drivers and software that is no longer required inside a VM - such as Nvidia drivers, hardware monitoring tools and so on

you probably can speed up the VM if you reduce the a\mount of CPUs and RAM

[bryankipp]

Is this solution the same for a Windows 7 machine?

[ealaqqad]

Hi bryankipp,

I would try the VMware Converter configure VM tool for a Windows 7 VM. It has fixed it for me before & I have shared the procedure at:

P2V Windows 7 Dell machine using VMware vCenter Converter

I hope this help,

Eiad Al-Aqqad

Senior Consultant

Blog: Virtualization Team

[Blato]

I am having the same issue with an XP pro P2V, will your edited VMX work, or will I need to edit my vmx to mach your changes.

thanks

attached is my VMX file.

[continuum]

nope - XP has no driver for LSI-SAS
to configure a XP VM with Converter set
scsi0.virtualDev = "buslogic"

[WoodyZ]

nope - XP has no driver for LSI-SAS

It can be downloaded from: LSISAS1068 SAS Controller Support & Downloads