Dedicated to my late brave, beautiful and silly mummy, Debra Ross. I love you mumster.

Skip navigation

VMware Fusion 2.0 Release Candidate 1 available

Screenshot of VMware Fusion 2.0 Release Candidate 1

For those who are also avid VMware Fusion users, you’ll be pleased to know the first Release Candidate for VMware Fusion 2.0 has been released (build number 113392).

For my own selfish needs, I only had three problems with the last beta which I’m hoping this RC has fixed:

Performace Issues with BSD hosts
Linux distributions performed just fine, but X.org in FreeBSD and Xfree86 in NetBSD on my MacBook Pro with 2GiB of RAM took far longer to load and performed worse than my 200MHz Pentium MMX box with 32 megs. This is not an exaggeration!
Folders that don’t disappear
In an attempt to backup my virtual drives as I like to do on a regular basis, I moved a folder from the virtual Windows 2000 machine to my Leopard desktop. Instead of copying over, the folder vanished from the guest, and didn’t appear on the host! One solid week of work down the toilet!
No stretched resolutions
VMware Fusion 1.x did not stretch the guest’s screen resolution when it was lower than the host’s. This meant in full screen there would generally be black bands on the sides, below and above the guest display… which was just fine for me! The Fusion 2.x betas flipped the default configuration so that it stretches the virtual screen which perhaps is useful for gamers but for reading text on an LCD it looks dreadful! As far as I can tell there’s no way to change this in the GUI, and adding lines to my preferences file turning off GuestToHost does nothing.

I might not have much time to look over these issues fully this evening or tomorrow, but I’ll certainly let you know what I find out when I can get back around to it. Stay tuned.

ASIDE: For what it’s worth, I’ve learned my lesson with virtual machine betas: they’re not worth it. Other "beta" products are actually quite usable, but not software like this. In the future I’ll be sticking with the latest stable release, in order to protect my sanity :-)

VMware Fusion 2.0 beta2 with FreeBSD review

UPDATE: An abridged version of this review has been picked up by the fine folks over at BSD News. If you’ve arrived here from there, all my FreeBSD and NetBSD posts can be found in the aptly-named BSD category. Cheers :-)

I’ve loved using virtualisation software ever since I had an early version of Connectix Virtual PC for my iMac DV back in the early 2000s, and later their Windows version before they were bought out by Microsoft. Virtual PC was mostly intended for people to use recent versions of Windows on Mac OS 8, but I preferred using it for resurrecting classic operating systems such as DOS/Windows 3.x which we had on our first home machine, and playing around with Linux distributions without going through tedious partitioning.

My predictably unnecessarily verbose introduction aside, the latest virtualisation software I’m using on a regular basis is VMware Fusion for Mac OS X, and I’ve been very pleased with it. The second beta release for version 2.0 is out now, and I spent my Sunday afternoon trying out build 107508 with a handful of my most used operating systems, plus FreeDOS for fun!

VMware Fusion 2.0 beta 2 Virtual Machine Library
VMware Fusion 2.0 beta 2 Virtual Machine Library

The most noticeable difference initially between this latest beta and version 1 of Fusion is the redesigned Virtual Machine Library. Taking a cue from Virtual PC, the plain text listing of virtual machines has been revised to include screenshots for the suspended machines. While I think this is a extremely useful and welcome addition for quickly recognising machines visually, I think the Mac-like glossy finishes are a bit overdone. Also despite making the interface more Mac-like overall, I can’t help but think the New, Open and Settings would better be served by a regular toolbar at the top of the window.

The New Virtual Machine Assistant has been improved to allow for more boot and drive options. You’re no longer limited to choosing from a physical or virtual optical disc; you can choose to use an existing virtual drive or even none at all: a VERY welcome addition! Before you run the machine the first time you’re asked whether you want to modify settings too, which means you no longer have to start the machine at the end of the assistant and hastily shut it down to fine tune its configuration.

VMware Fusion 2.0 beta 2 New Virtual Machine Assistant
VMware Fusion 2.0 beta 2 New Virtual Machine Assistant

Speaking of configuration, the Virtual Machine Settings window has been drastically redesigned to make it look much more like the Mac System Preferences application, and to make it easier to access all the new options and virtual devices you can configure. Amongst the new goodies are the ability to configure floppy drives, parallel ports, serial ports, and multiple virtual hard drives. When I saw these additions, I literally jumped out of my chair and screamed "HELL YEAH!"

Fusion 2.0 beta 2 also allows you to visually scale and stretch live running virtual machine displays. Even just a little bit of scaling adversely affects the readability of text, but perhaps for other applications such as full screen gaming which needs to be scaled to fit to an unsupported resolution this might be useful.

VMware Fusion 2.0 beta 2 New Virtual Machine Assistant
Demonstration of the live visual scaling in beta 2. Both the NetBSD and Slackware virtual machines are set to 1024×768 but the latter has been scaled down.

Now for the bad news. I’m not sure if this is a temporary setback as a result of it being a beta version (I did disable debugging checks), but graphical performance in BSD operating systems on my original generation MacBook Pro is nothing short of abysmal. VMware provides welcome additions for FreeBSD, but even installing these in FreeBSD 6.3 Release and using them with the compat6x layer in FreeBSD 7.0 Release made no difference to the overall sluggishness. NetBSD 4.0 was just as bad, without any additions.

This slow performance was most pronounced when I started Xorg on FreeBSD or XFree86 on NetBSD. Typically starting an X11 environment in VMware Fusion 1.x takes less than a second followed by several seconds for loading the desktop environment or vanilla window manager. With Fusion 2.0 beta 2, both FreeBSD and NetBSD take over 5 minutes just to start X11, and another few minutes just to load something as lightweight as Fluxbox… if you want to load Xfce or KDE it takes over a whopping 10 minutes.

To check whether this was a problem with BSD, I tried Slackware Linux 12.1 with the same versions of KDE, Xfce and Xorg; and while it still felt a little sluggish it still managed to load all three in a reasonable amount of time.

Given I need to use FreeBSD for my studies I just can’t use this beta release on a production machine, but if you primarily use Windows or Linux you could probably try it out.

Modular Xorg on NetBSD from scratch

NetBSD Xorg Orange
That’s a lot of orange! That reminds me, I need more F&N… Orange

NetBSD is one of the last Unix-like operating systems still shipping by default with the XFree86 X Window Server as opposed to the new de facto Xorg distribution. From what I’ve been able to find out doing a quick Google around is that given the system’s strict requirement for portability it’s going to take a lot of work to get Xorg working on every port. I respect that.

So enter pkgsrc and modular Xorg! Modular Xorg is an exciting new way of distributing Xorg because it allows you to cherry pick only the drivers, applications and other whatnot that you want instead of installing one huge package.

For me, I’m using a fresh install of NetBSD 3.1 in a VMware Fusion virtual machine, so you’ll obviously have to take these steps as a guide for your own system.

During the initial install I chose the Custom Installation option and de-selected the X11 Distribution Set. This means I avoided any mess right from the beginning, just as I did when I changed from Monolithic Xorg to Modular Xorg on FreeBSD.

Once you’ve installed NetBSD, do your usual configuration of /etc/rc.conf to enable your network, and add X11_TYPE=modular to your /etc/mk.conf file. DON’T add a X11BASE line!

Then go grab yourself the latest pkgsrc tree and update it.

Now it’s just a matter of make install clean clean-depends -ing each package we want. If you really wanted to, you could just install all the meta-packages:

… but that really defeats the purpose of going modular! For me, I installed the base server, the entire fonts meta-package, only the drivers I needed, and the minimum required apps:

Obviously when I said minimal I wasn’t kidding! These packages are enough to get an X session started, but that’s about it. If you’re installing a desktop environment such as KDE, Xfce or GNOME you can go right ahead and install their respective packages, but if you’re using a vanilla window manager such as OpenBox you’ll really need to install at the very least a terminal emulator. I like urxvt.

It is defintely more work to install modular Xorg, and in many cases the default XFree86 distribution Is Good Enough™, but I like the added control this gives me, plus then I have the added convenience of using similar software on my other BSD and Linux machines. Right Mai?

Is she pissed off or distracted somehow? I don’t know. Maybe she runs OpenBSD instead. It’s 01:52, maybe I actually need to go to sleep now.

Another look at NetBSD

A fresh NetBSD install

After a year or so of using FreeBSD I decided today to take another look at the operating system I learned UNIX on from the beginning: NetBSD (well actually it was Red Hat Linux 5, but I never left X!). I admit the way I learn things is to be focused on one specific programme, language or OS and hack away for a week rather than trying to be vague and learning many things at once not that well and not in much detail, and therefore not making much more than token advances in understanding. See how I slipped my critique about my university studies there? ;).

Reading back some of my previous posts I’m not entirely sure why I switched completely to FreeBSD back at the beginning of last year. I think part of the decision stemmed from VMware’s official support of FreeBSD and the fact that more people were using it, so I figured it was a better boat to be floating in. I’ve been using a lot of boat analogies lately, I’m becoming a bit washed up. Get it? Aha. RATHOLE!

Having used NetBSD though for a few hours I’ve remembered what I love about it:

  • the layout of the file system is so clean
  • the initial installer is fast and slick
  • pkgsrc simply rocks!
  • the PowerPC port is an equal citizen not a afterthought next the x86 version, so my old Power Macintosh G3 and iMacs can use the same OS as my generic AMD boxes and just as well
  • compared to Linux it really boots up in a flash, like FreeBSD
  • KDE and Qt apps seems more stable on NetBSD (perhaps it’s just me) and Konqueror has the search box by default right from pkgsrc
  • if it’s good enough for Wintellect at BSDNexus, it’s damn well good enough for me!

That said though, I’m not giving up on FreeBSD, I think there’s definitely room for both. The default addition of portsnap and jail abilities (and coloured file listings!) are still very compelling, and the support for it in third party applications and drivers is certainly stronger. I think it will come down to a machine by machine choice for now.

I think it’s safe to say I’m a *BSD enthusiast, I am a happy user of Mac OS X, I have a passing interest in GNU/Linux and Solaris, and I have a healthy distaste for Windows and System 7 ;).

NetBSD

Just bought VMware Fusion

A couple of days ago I finally gave in and purchased a copy of VMware Fusion. Having used the demo versions of Parallels Desktop and Fusion on my MacBook Pro I decided VMware’s product was much more suited to my needs. Parallels seems to be great for running Windows, but my main use is for FreeBSD and other Unix-like development which Fusion has better native support for (official additions for FreeBSD and Solaris anyone?). And with a special offer of $39.00 for first time beta purchases before the final version came out I figured it was the best choice. I should have taken a PR course at university instead.

So now I have the final, official retail release of VMware Fusion running on my MacBook Pro, and I’m loving it. Having a dual core processor with VT support really kicks some serious virtual arse.

Below is a screenshot of fresh virtual machines running OpenBSD 4.1 sitting at the shell, NetBSD 3.1 with a basic OpenBox window manager session, ReactOS and an installation of Windows 2000 Professional humming along:

VMware Fusion

I do admit I do run a purchased, fully licenced copy of Windows 2000 as a virtual machine to run a few apps that don’t work so well on Wine, and for testing of my websites using Internet Explorer 6. Windows XP and Vista just add useless features and require more system resources, so 2000 works just nice. Well, as nice as Windows can.

Below is a screenshot of AutoPatcher running under Windows 2000 using the Unity feature of Fusion which makes it look as though Windows applications are running on the Mac OS X desktop. I much prefer to use AutoPatcher than Windows Update because it means I don’t have to run Internet Explorer to use it, and I don’t call home to Microsoft.

VMware Fusion

And here it is running in it’s own window. I actually think I prefer having it this way:

VMware Fusion

I just love having virtual machines. I can tinker away with really fascinating operating systems and learn so much, without stuffing up anything when I do something wrong. It’s great for sand boxing, and it also allows me to run a scaled down FreeBSD machine with just the bare basics so I can study without distractions. Not to mention compiling applications for different platforms… the possibilities are so exciting!

Or maybe I’m just easily excited ;).