copied vdi not working with new machine

iansane · Post by **iansane** » 20. Sep 2008, 15:33

Hi,

I crashed my system a few days ago. I was able to get to my windowsXP.vdi and copy it over to new location on new install of ubutnu. I installed latest version of virtualbox and created a new machine with the same specs as the old one and used the windowsxp.vdi .

When I booted it I got BSOD. Is this caused by windows seeing it is on a different machine? Is it because it was newer version of virtualbox?

I couldn't figure it out so I just made a new machine and installed XP again. I didn't have anything important on it but if I had, I would have lost it.

I now have my vm machines and drives stored on a seperate partition mounted by host at startup so I'm hoping I won't have this problem again if I have to reinstall the host but what is the best method to copy a machine and ensure it will work with another install of virtualbox?

Thanks

iansane · Post by **iansane** » 20. Sep 2008, 17:10

OK I still want to know what is causing it.

But I was able to solve the problem.

Apparently the new format machines are different on a newer version so here's how I fixed it if anyone else has the problem.

1. copying the vdi:
This doesn't work. You have to use virtualbox to clone it.
The help file tells how and it's easy.
unfortunately I can't clone what virtualbox can't see.
It was the machine, in my case win.xml that was the problem.
Once I got the machine working I could just point it to the win.vdi

2. Making a machine work
Apparently the different format was causeing BSOD when it booted.

I made a new machine, (win.xml)
Pointed it to the old win.vdi (won't boot, BSOD)
Then close virtualbox
go to machine directory and rename new machine to backup_win.xml
Then copy paste the old win.xml to the directory
Then open virtualbox.

Got error about UUID of machine in directory not matching one in
home directory/.VirtualBox/VirtualBox.xml

Simple solution?
open VirtualBox.xml
Find line with UUID
copy/paste correct UUID from the error message in VirtualBox
over the one that's in the .xml

Close and reopen VirtualBox.
When prompted, backup old format and reformat to new format

Problem Solved! Turns out I did have one important document on that machine and boy am I glad I got it to work!

Hope this helps others with same problem

iansane · Post by **iansane** » 20. Sep 2008, 18:11

My mistake. It does not tell you how to clone in the help section.
It gives a link to page with another link that links back to the first one.
Either way it's easy. googleing for it will find the commands.

iansane · Post by **iansane** » 20. Sep 2008, 19:19

Was going to say that

Code: Select all

VBoxManage clonevdi source.vdi target.vdi

didn't work but it works great!! That's the syntax and it moved vdi from external drive to "/vm" mounted internal partition flawlessly.

I was just making a stupid syntax error.

Anyway, that's how to clone a vdi. Not copy/paste

Post by **Sasquatch** » 20. Sep 2008, 20:26

I believe your initial problem was the BSOD on the Guest. This can be caused if you upgrade VB and your VM from a version prior to 1.6.0. The default IDE Controller type is PIIX4 now, it was PIIX3. This setting can cause a BSOD when it's not set properly for Windows Guests.

iansane · Post by **iansane** » 21. Sep 2008, 07:00

Thanks sasquatch,

Sounds like a likely suspect. Well now that i learned how to clone and how to use old vdi I need to get this host interface thing working but that's another topic.