Ticket #897 (closed defect: worksforme)

Opened 10 years ago

Last modified 10 years ago

converted VMWare 6 vmdk with MS Win XP guest to a vmdk for VirtualBox pro current; failed

Reported by: yk Owned by:
Priority: major Component: other
Version: VirtualBox 1.5.2 Keywords: vmdk MS Win XP from VMWare
Cc: ykarant@… Guest type: other
Host type: other


have read

and have done 1. enable IO APIC support in VirtualBox

  1. MergeIDE, 3. done the steps in

and 4. removed VMWare tool from MS Win XP. Additional details: latest stable VMWare 6.x, using a 10 GB extensible vmdk Windows XP Professional-s001.vmdk Windows XP Professional-s002.vmdk Windows XP Professional-s003.vmdk Windows XP Professional-s004.vmdk Windows XP Professional-s005.vmdk Windows XP Professional-s006.vmdk Windows XP Professional-s007.vmdk Windows XP Professional.vmdk

I am using the latest stable VirtualBox pro (with USB support) RHEL5 rpm.

These files and additional ones are in a directory. I made a cp -pr of this directory into another with a different directory name. I used VMWare on the new directory to perform steps 2, 3, and 4 above on a running MS Win XP. I then shutdown MS Win XP, exited VMWare, and started VirtualBox using the same new directory with the modified WinXP image as the file to start -- using only the Windows XP Professional.vmdk file -- not the sub (-s00x) files. As MS Win XP boots, VirtualBox suffers a fatal error; I have the logs VirtualBox automatically generates. What have I done wrong? I do not want to reinstall all my MS Win XP applications from CD-ROM; ghost would not solve this problem because it would make an image of MS Win XP with devices/drivers that VirtualBox cannot use. Once I get the modified MS Win XP running under VirtualBox, I will install the VirtualBox equivalent of VMWare tools into the running MS Win XP so that the screen will resize, etc.

Change History

Changed 10 years ago by yk

Changed 10 years ago by yk

Changed 10 years ago by yk

comment:1 Changed 10 years ago by sandervl73

You've included the wrong logs. The release logs are in ~/your_name/.VirtualBox/Machines/VM_Name/logs.

comment:2 Changed 10 years ago by frank

  • Status changed from new to closed
  • Resolution set to worksforme

No response, closing.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use