Sun is continuing to push its virtualization agenda forward. This week, Sun's VirtualBox virtualization software received a platform refresh and a few significant new features with the announcement of Version 3.1. New features include, believe it or not, a live migration feature called Teleportation, vastly improved snapshot capabilities, and 2-D video acceleration for Windows guest environments.
The most interesting new feature announced with Version 3.1 of VirtualBox is a technology dubbed as "teleportation." The feature enables users to move a running virtual machine between two different host machines, and the host machines don't have to be operating with the same host operating system. According to Sun, the host machines can run different operating systems, be different classes of computer (desktop or server), and run different processor types such as Intel or AMD. Virtual machines can be migrated in this way if a host machine needs to be rebooted or taken down for maintenance.
[ Check out InfoWorld's latest guide that explains the ins and outs of server virtualization | Keep up with the latest virtualization news with InfoWorld's virtualization newsletter or visit the InfoWorld Virtualization Topic Center for news, blogs, essentials, and information about InfoWorld virtualization events. ]
Moving virtual machines from an Intel-based machine to an AMD-based machine is a difficult task, but one that many virtualization users would be excited to be able to perform. While the announcement claims migration support for moving from one chip type to another, the user manual states something a bit different. It reads:
The hosts must have fairly similar CPUs. While VirtualBox can simulate some CPU features to a degree, this does not always work. Teleporting between Intel and AMD CPUs will probably fail with an error message.
Still, this live migration feature alone will give VirtualBox and Sun a boost in this competitive market, but teleporting still has a ways to go before it is as mature as some of its competitors' technologies. With Version 3.1, the feature must be invoked from the command line. It also requires the user to manually create identical virtual machine configurations on the host machines where the feature will be used. Disk images must be on a shared storage source that is accessible by both the source and the target machine (nothing new here), and it cannot have any snapshots.
Other interesting features include: