virtualbox.org

Hello,

I have read the How To on Moving VM's, and searched various topics, I do't seem to find the answer.?
Everything I have read seems to be about moving VMS, but on the "same" machine.
I currently have 2 VMS working on my current machine, I'm now wanting to move them to a new one.

I have already installed Virtualbox on new Machine, same revision as current machine, not created any VM's yet.
The 2 machines though have different Hardware, CPUs, memory disks etc.

Can I move them.?
Is this the purpose of the export function.?
or is there another method to move them across to a different machine.?

Many Thanks... David

Do you expect the new architecture to be less capable than the old? The procedure for moving VMs is the same, otherwise we would have mentioned the exceptions. You can of course run into problems with even the simplest of moves, but we can jump that bridge you come up with a concrete issue.

mpack wrote:Do you expect the new architecture to be less capable than the old? The procedure for moving VMs is the same, otherwise we would have mentioned the exceptions. You can of course run into problems with even the simplest of moves, but we can jump that bridge you come up with a concrete issue.

Hi mpack,

Thanks...
It's not about the capability, it's about compatibility, and will that create any issues/errors.?
Forewarned is to be prepared, rather than closing the stable door after the horse as bolted.

I will just try and see what happens.

Regards - David

Wirezfree, At work I bounced an SBS2003 guest around from a hyperthreaded single core Xeon to a Core-2Quad, to a Core-I5, back to the Xeon, then up to a Hex-core Xeon, with no problems. At home I had a Celeron host with a XP guest. I upgraded the host CPU to a Pentium 4, then switched the guest to an AMD host, with no difficulties.
In almost all cases only the CPU gets through to the guest (unless, maybe, you have 2D or 3D acceleration turned on? or you're trying PCI pass-through). The rest of the hardware on the host can usually change without trouble. You should move the guest after it has been completely shut down, not save-stated, to set things up for the easiest move. After moving a guest you may have to switch the network card the machine was bound to, but that's about it.

scottgus1 wrote:Wirezfree, At work I bounced an SBS2003 guest around from a hyperthreaded single core Xeon to a Core-2Quad, to a Core-I5, back to the Xeon, then up to a Hex-core Xeon, with no problems. At home I had a Celeron host with a XP guest. I upgraded the host CPU to a Pentium 4, then switched the guest to an AMD host, with no difficulties.
In almost all cases only the CPU gets through to the guest (unless, maybe, you have 2D or 3D acceleration turned on? or you're trying PCI pass-through). The rest of the hardware on the host can usually change without trouble. You should move the guest after it has been completely shut down, not save-stated, to set things up for the easiest move. After moving a guest you may have to switch the network card the machine was bound to, but that's about it.

Hello scottgus1,

Many Thanks...
All noted, especially network..

Thanks