Hello,
After a convert of a physical machine i'm getting a blue screen with the following error "Stop Error 0x0000007b" (see print screen)
I also got an unknown error back in the task list.
Attached you will find the print screen of the error and the vmware convert logs.
What could cause this?
I already did a checkdisk on the virtual disk (attached to other vm), and changed the lsi logic to bus logic, but problems stays the same
thank you in advance.
Real easy / oldschool. Assuming the old disk was IDE ...
1) Download the buslogic scsi driver from vmware.
2) Use a boot disk on the VM.
3) Rename atapi.sys atapi.xxx on the VM.
(this file's usually in %SYSTEMROOT%\system32\drivers)
4) Copy buslogic.sys (from vmware scsi driver) to atapi.sys .. You temporarily will not have a CD-ROM.
5) Reboot. Guest should come up, because it was already configured to load atapi.sys if the system was IDE ....
6) Install the VMware SCSI driver. Do not reboot.
7) Copy atapi.xxx back to atapi.sys
😎 Reboot. Install VMWare tools.
Hello,
Did the physical server have multiple CPU's? If so and the converter kept multiple CPU's try changing it to only one CPU. This corrected a similar problem for me.
Hope this helps.
Hello,
No it only has one P3 cpu.
Each time i had this error it was the hard disk driver that was in problem. Generally when i went from a ide to scsi. But i guess it can happen from scsi to scsi.. In your situation a would try a bartpe p2v tool that has a driver injection... I solved couple of similar issue with this tool.
Just in case you dont have or know the bart pe tools.. .This page will give you a good amount of info on that. I used it alot before vmware finally came with a real converter. Never has problem with this bart and the driver "injection"...
I was already on that site, but thanks
i will test it out and let you know
thank you
Real easy / oldschool. Assuming the old disk was IDE ...
1) Download the buslogic scsi driver from vmware.
2) Use a boot disk on the VM.
3) Rename atapi.sys atapi.xxx on the VM.
(this file's usually in %SYSTEMROOT%\system32\drivers)
4) Copy buslogic.sys (from vmware scsi driver) to atapi.sys .. You temporarily will not have a CD-ROM.
5) Reboot. Guest should come up, because it was already configured to load atapi.sys if the system was IDE ....
6) Install the VMware SCSI driver. Do not reboot.
7) Copy atapi.xxx back to atapi.sys
😎 Reboot. Install VMWare tools.
Hello,
I tried this yesterday and it worked perfectly.
Thank you very much.
D