virtualbox.org

Greetings, I recently moved my XP 32 vdi's from my laptop (ASUS G73GW) to my new desk top (i7-3550, 32G ram) and they will only boot in safe mode. Do I need to update drivers in safe mode to get the vdi's to boot up normally?

Thanks

If you only moved the VDIs then that was a mistake. All of the files in the VM folder are important, especially when it comes to ensuring that you don't make any inadvertant changes to the VM recipe, e.g. in the disk controller type.

If you want us to diagnose a specific problem then provide a log file of a session which shows the problem - as a .zip attachment please.

Interesting. I did not have a problem with moving a vmdk though. What if I cloned/converted the vdi to a vmdk?

Regards

Tom

The container format makes no difference. It's what it contains that's important.

Ok, here is a zipped log for a vm that only boots in safe mode. I copied the xml file and a few other files from my laptop to my PC, but to no avail.

Thanks

Tom

dearth vadar wrote:Ok, here is a zipped log for a vm that only boots in safe mode. I copied the xml file and a few other files from my laptop to my PC, but to no avail.

Thanks

Tom

The real question that needs to be answered here (IMHO) is what version was the guest created with and is it the new standard where the guest is stored in a containing folder that has it control file (*.vbox). If so the easiest way to move the guest is to copy the entire folder to the new location and use the device | add feature to add the guest to VirtualBox.

Note: the attempts to install it will need to be backed out before you try the proper way or it will refuse to let you add the guest. Finally the guest should be completely shut down (not saved state) before you move it.

One other thing I see in the logs is hardware virtualization has not been enabled on the host PC. If it was on the original and not on this one that will also cause this issue.

Yes, mention of the "copied the xml" implies that the original was an old (v3 or earlier) VM. You should have mentioned that earlier. v3 VMs are not very portable, and in particular copying the xml will do nothing. You need to use the xml (displayed in a decent text editor, e.g. Notepad++) as a reference as you go through the new VM settings, ensuring that every setting is identical. In particular you should ensure that the storage controller type is the same, ditto IO APIC setting, network card type, MAC address and RAM size.