How to export VM?

[tatoosh]

How to export my existing VM and import on another PC?

Thx

[Sasquatch]

You copy the VDI file to the other computer, create a new VM with exactly the same settings (including the MAC address of the NIC) and attach the existing VDI to it. In VB 2.2 there will be an export and import option available for exporting it to OVF format. VB 2.2 is currently in Beta, but it shouldn't be long before the final is released.

[tatoosh]

OK thanks for your answer.
Can i do an update to version 2.2beta and export my VM? will this work?

[Sasquatch]

Yes, this will work. But you MUST read the release notes and known issues first before doing that. I suggest you wait a few days though, unless you really need to have the VM now (transferring it manually might be faster, it takes a while to export).

[tatoosh]

Ok i tried it out with the newest beta and got this error while exporting:



Is that an error occoured by the beat version?

When i do the other step by copy the VID can i copy the snapshots, too ?

[Sasquatch]

The error you got is the same as someone else reported in the Beta forum. It's likely a Windows build error, 'cause I don't have that problem on my Linux Host.

You didn't mention snapshots before. That's a bit of a problem, but it can be done. Copy the entire VB folder to the other Host, so you have the snapshots too. Now, if the Host is the same OS (Windows to Windows, Linux to Linux), it should be no issue whatsoever getting it to work. The VB folder is located in your user profile by default. If you transfer that whole folder to the new Host, importing is already one. But keep in mind that any existing VM on the new Host will most likely get lost because you replace the existing folder with the new one from the old Host.

[kchai007]

What about export a VM to another PC of different processor (say Intel vs. AMD)? Would the VDI file still work on the new PC?

[vbox4me2]

Try it and find out, between intells I haven't seen problems(yet).

[kchai007]

The same VDI file (for WinXP guest) works on both Intel and AMD. Initially it (VDI) failed to boot because of different settings on "General" tab, in particularly, ACPI and IO APIC settings need to match.