Error using VMDK files

[Josh]

Machine will not boot using an existing VMWare .VMDK file created with workstation 6.5

[Klaus Espenlaub]

The bug report so far is pretty meaningless - there are many ways in which an OS install in a VMDK image is tied to virtual hardware which only VMware provides. Could you describe what guest OS this is, what configuration you used in VMware and what exactly happens in VirtualBox?

[Josh]

Latest Log File

[Josh]

I'm using Windows XP Pro to host VirtualBox. I'm attempting to run an Windows XP Pro guest. When using the vmdk file in VirtualBox, I just get a black screen that sits there. I did some additional searching on the forums and found many people suggesting to convert the file to a vdi. I took that advice and switched the Hard Disk on the machine to use the newly created vdi. Now, I get to the windows loading screen and get a BSOD before it immediately reboots. Attempts to boot into safe mode have resulted in the same thing. Attached are the latest log and config xml.

[Klaus Espenlaub]

The black screen hang is usually due to the fact that Windows XP installed with IO-APIC on (VMware default) doesn't boot on a system with IO-APIC off (VirtualBox default). The attached xml file proves that you enabled it in the mean time. This is totally unrelated to converting to VDI or not.

The bluescreen is most likely due to the fact that you're using the wrong disk controller. Windows won't boot if there are even tiny differences. That's why I asked for the VMware configuration - was it using a SCSI controller? VirtualBox supports many options which are compatible to VMware, but it's your task to use those options.

[Josh]

I found the IP-APIC thing on the forum as well and yes, that resolved the black screen. WMWare is set to use the HD as SCSI 0:0. I found the place to add a SCSI controller in VMWare and removed the drive from the IDE controller and added it to the SCSI controller. I've got it assigned to Port 0 and i've tried both sub-types of SCSI controllers in VirtualBox, but I'm still getting a BSOD. I'm sure I'm close to figuring this out as it appears to be a configuration issue somewhere. Updated config xml.

[Josh]

Config File