Linked by Thom Holwerda on Mon 30th Nov 2009 23:45 UTC
Oracle and SUN Yesterday (today if you're in the US), Sun released the latest version of its virtualisation solution, VirtualBox 3.1. Among speed improvements and other smaller features, the biggest news is that Virtualox 3.1 introduces something called teleportation: you can move running VMs between machines - servers or clients, different architectures, different host operating systems, it doesn't matter to VirtualBox. Coincidentally, this reminded me of an idea I once had about moving running applications between machines.
Thread beginning with comment 397398
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by talaf
by grat on Tue 1st Dec 2009 23:58 UTC in reply to "Comment by talaf"
grat
Member since:
2006-02-02

It's fun seeing it "in the real world"!


Yes-- It's very nice right-clicking a node in my ESX cluster, selecting "Enter Maintenance Mode", and watching all my running VM's move to other nodes. Watching them move around in response to load is also nice.

Xen has also had this functionality for awhile, so I'm glad to see VirtualBox catching up.

I'm curious to see how "cross platform" it is-- Under VMWare ESX, it's annoying enough to move between two similar CPU's with slightly different feature sets. If the running VM can't tell that it's 64-bit CPU just changed to a 32-bit CPU, then I would think that the VM isn't capable of exploiting very much of the higher-end CPU's.

Reply Parent Score: 2

RE[2]: Comment by talaf
by phoenix on Thu 3rd Dec 2009 17:34 in reply to "RE: Comment by talaf"
phoenix Member since:
2005-07-11

"It's fun seeing it "in the real world"!


Yes-- It's very nice right-clicking a node in my ESX cluster, selecting "Enter Maintenance Mode", and watching all my running VM's move to other nodes. Watching them move around in response to load is also nice.

Xen has also had this functionality for awhile, so I'm glad to see VirtualBox catching up.

I'm curious to see how "cross platform" it is-- Under VMWare ESX, it's annoying enough to move between two similar CPU's with slightly different feature sets. If the running VM can't tell that it's 64-bit CPU just changed to a 32-bit CPU, then I would think that the VM isn't capable of exploiting very much of the higher-end CPU's.
"

This is where the "virtual CPU" comes into play. Not sure how it works in Xen/VMWare, but with KVM, you can select which type of CPU to expose to the guest.

For best compatibility, you can use a "qemu" CPU type, which is a lowest-common featureset CPU (everything that Intel and AMD support). Or you can be more specific on the CPU features to expose. Or you can just pass through the full CPU set of the host.

Thus, if you have all AMD CPUs in the VM farm, you can pass through the host CPU.

If you have AMD and Intel CPUs, you can use the qemu CPU for VM portability.

Moving a 32-bit guest from a 32-bit host to a 64-bit host would work. But going in reverse (64-bit guest to a 32-bit host) wouldn't.

Reply Parent Score: 2