Slashdot Mirror
VirtualBox 2.1 Supports 64-Bit VM In 32-Bit Host
Stephen Birch writes "Following closely behind the mid-November 2.06 release of VirtualBox, Sun Microsystems has released version 2.1. This has a number of new features, but one of the most interesting is the ability to run a 64-bit VM inside a 32-bit host. Another useful feature is integrated host-based networking; no more fiddling around with network bridges. Sun is really giving VMWare a run for their money."
sorry, the hardware has to be 64 bits. The most likely situation where you'd use this is 64-bit Linux or Solaris under 32-bit Windows. Most recent machines have 64-bit hardware, but a lot of people are wary of running 64-bit Windows. So I think this will be a useful configuration, if the performance penalty isn't too high.
I have an Athlon64 but run a 32 bit OS. I tried running a 64 bit virtual machine using VMWare Server 1.0.x a year or so ago and it worked. The performance was not noticeably poor.
So... assuming I haven't missed anything too obvious, my response would be "No, vmware is not getting a run for their money." Not today anyways.
A quick check of the user manual states hosting a 64-bit OS requires 64-bit hardware. So I think you are out of luck.
This update is really just adding support for running 64-bit on systems where the host OS is not taking advantage of 64-bit hardware they already have.
It means that the virtual network adapter can get IP connected without resorting to NAT. This was usually done by bridging a physical interface to a tun device and setting that tun device as VirtualBox's network device. Setting up this bridge requires using a script outside of VirtualBox to get everything set up. Now VirtualBox can do it from the GUI with no scripting required. In short, one can dedicate a physical NIC to VirtualBox by bridging it or allow VBox direct access to the host NIC.
The easy way to do networking with virtuals is to use NAT to pass TCP traffic to the virtual from the host's IP connection. That suffices for web surfing and other apps that don't severely exercise networking but it doesn't work well for things like VPN clients.
If you wanted your VM to have an IP and appear as if it is a real machine on the network many people used to have to follow the 100 odd lines of documentation here: https://help.ubuntu.com/community/VirtualBox#Networking
Now they can just start it and it works out of the box.
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
VirtualBox is free. VMWare Workstation costs money (the free Server products don't support 3D graphics).
The VirtualBox GUI is written with Qt, not GTK.
I'm using VirtualBox to run 32 bit Windows XP on a 64-bit Linux machine. VirtualBox 2.0 runs really well for me. I'm glad I can use an open-source package for this.
DNA is the ultimate spaghetti code.
The difference is VMWare emulates DirectX, using Wine.
What are you talking about? VMWare does no such thing, there is no connection between vmware and wine whatsoever.
I was in the same position as you, only recently found about VirtualBox, and have converted all my VMware images using the instructions here (which are distro-agnostic): http://wiki.archlinux.org/index.php/VirtualBox#Converting_from_VMware_images .
:)
Good luck!