Linux in Government: VMware Workstation 5

A look at the new VMware Workstation release--what it can and cannot do.
Looking Back and Forth at VMware

If you have followed the progress of VMware since it started up, you may have thought of it as a way to use Windows applications on your Linux desktop. I know I did. That seemed like the founders' intentions. But, we cannot really know what vision or roadmap the company had.

VMware workstation ceases to have relevance in terms of a way to deploy Windows applications as Linux begins replacing those applications with native versions that run in GNOME, KDE and other desktop environments. The future for VMware lies in the server area, where it has given Linux a leg up in the data center. One can only wonder how much longer the workstation will continue to have a market.

Regardless, VMware has served an important place in the history and evolution of free Linux. Many people still love it and are glad it's around. Hopefully, the company y will innovate and make using Windows applications simpler for Linux users while they grow their server business.

Tom Adelstein is a Principal of Hiser + Adelstein, a consulting and operating company specializing in free and open-source software solutions and support. Tom is the co-author of the book Exploring the JDS Linux Desktop, author of an upcoming book on Linux system administration and has written prolifically since 1985. Tom's business career began in public accounting where he first learned to program and develop software and later progressed to Wall Street, where he became the designated principal of a NYSE firm. He later returned to technology and has consulted and worked with start-ups as well leaders of the Fortune 500.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

fedora as guest on VMWare

Anonymous's picture

I currently run FC2 through FC4 as guests on VMWare 5

VMware Linux hosts

Anonymous's picture

VMware may not officially support all Linux distro's, but this only means that VMware is shipped with modules matching the default kernel for those Linux versions. What VMware needs to run is vmmon & vmnet modules that match the hosts kernel. Just make sure that there are matching kernel headers and kernel image. Run the ~/ and it will compile the needed modules. Runs on all version of Debian I have used.

SuSE 9.2 as VMware host

Anonymous's picture

I too had this problem. A little searching the SuSE and VMware forums brought me these commands which did the trick:

$ cd /usr/src/linux
$ make cloneconfig
$ make modules_config

Suse 9.2 as VMware host alos works for 9.3

Anonymous's picture

Just F.Y.I

I tried this proceedure on Suse 9.3 and it worked there as well.

Suse 9.3 as VMware host

Shimon's picture


Yes, works well without any problems.


SuSE 9.2 as VMware host

Anonymous's picture

Thanks for the commands. You sure it was just a little searching?

I never found anything like that and used an earlier version to get it to work.

SuSE 9.2 + VMware

DJM.'s picture

> I never found anything like that and used an earlier version
> to get it to work.

The problem is that SuSE's 9.x kernels are full of additional patches that Novell/SuSE put there, so that most packages relying on pre-built modules will fail. Workaround: You have to re-compile the modules.

I have this problem with VMware but also with the Linux-versions of a VPN software I have to use (Nortel VPN client).

As for VMware and SuSE 9.2:

Here is how I solve the problem:

cd /usr/src/linux
make cloneconfig
make prepare

With "make prepare" some files that are usually created during a kernel compilation are created too, but nothing more happens, ie. the actual compilation does not take place.

When you call "" it will then find all the necessary files as if a fresh kernel had been compiled. Voilà, problem solved.

I use SuSE 9.2 as main OS on my Laptop, and VMware to run other virtual installations, e.g. Windows 2000, other Linuxes, and so on.



SuSE 9.2 + VMware

Anonymous's picture


I appreciate your explanation a ton. I was going to sell my SUSE 9.2 on eBay and take a big L-O-S-S.

I followed everyting you wrote and understand it. I wish you would post your work-around on Linux Questions or some of the other support sites.

Search engines don't pick up anything from Linux Journal because of this content management system they use. All this great advice in the comment sections and it's totally useless to the community.

Hey Editors - did you get that?



PK's picture

I too run VMware workstation to use Windows programs. 1GB of RAM with a 1.4mhz Pmobile works pretty well. Mine is running on Ubuntu 5.04 with no difficulties. It is nowhere near as fast as Windows running natively but is acceptable. I have used it on Mandrake (Mandriva), Gentoo, Redhat and Debian without difficulty. It boots somewhat slowly but runs pretty well.

The biggest problem with VMware on a laptop is that the host IP changes with locations. And then the guests cannot find the host to share files without a great deal of effort, every time you change locations. It get's old real quick. I take the laptop home at night and I'm tired of changing guest IP info.

I have never made or intend to make a clone. I don't care about this capability. And I just don't have or intend to get or make the space for two or more VMware instances on my harddrive.

Someday Intuit will release a Linux version of Quicken and possibly Quickbooks and OpenOffice's .doc compatibility will improve to the point that I no longer need Windows and I will delete VMware completely. But until then....

There's a very easy way to sh

Anonymous's picture

There's a very easy way to share files between host and guest in everywhere without modifying anything when changing place.

You just have to add another ethernet interface to the guest. Then you can define that eth0 is for the outside world (using bridge mode, probably dhcp enabled for eth0) and eth1 is using host-only mode. Guest can then have a static ip address or dhcp enabled (usually gets always the same ip address). Host has a static ip address (host-only network adapter Vmnet1), so guest OS always finds the host using that ip address. No more trickies and worries about host and guest, they have created a private LAN. Now you can change the place as much as you like.

VMware and applicable hosts

Anonymous's picture

I run VMware 5 on Fedora Core 3 with no problems.
One has to update the install for each new kernel release but that is quickly done.

The guest OS is Win2K Pro and it runs fine on my
3.2GHz pentium with 1 GB RAM and 640 GB of IDE and SATA disks.
File IO runs as 15 -20 MB/sec as a GuestOS whereas under W2K
directly I get 7 - 10 MB/sec on a good day.

My only concern is the cost as I only use two apps under Win2K.

VMware performance

Anonymous's picture

The virtual hardware of VMware 5 runs better than previous versions. With a single Pentium IV or an equivalent AMD processor and 512MB of RAM, one should be able to run two virtual machines simultaneously. The previous versions would grind to a halt in such a scenario.

I wouldn't recommend running your system that way, however. If you have a need to run more than one virtual machine, you should run dual high-end processors and 3GB of memory. Otherwise, you cannot use your host machine and the two virtual machines with any efficiency.

I don't agree that such a high-end machine is needed to run VMware Workstation. I've run RedHat Linux in VMware on a 600 MHz Pentium III, 512 MB RAM Windows box with almost the same performance as booting directly into RedHat Linux on the same machine.

All you need a machine that is powerful enough to run the applications you want to run in the virtual machine. The overhead of VMware is very less in terms of CPU utilization and moderate in terms of memory.
For example - If you can run applications A, B & C on an OS without VMWare, you can also run A on the original OS, B & C on two virtual machines if you have enough memory.
You can't expect VMware to triple the power of your machine by installing two virtual machines!

How does it differ from QEMU?

mangoo's picture

It would be nice if the article outlined some differences between VMWARE and QEMU (which is free and is packaged in many distributions).

Don't forget that VMWare 5 al

b34r's picture

Don't forget that VMWare 5 also support DirectX acceleration using OpenGL under a Linux host running a guest XP. While the feature is not yet perfect it already runs a lot of recent game titles that do not work either in Cedega or Wine at more than acceptable performances.

OpenGL != DirectX

Matt H's picture

You know that OpenGL and DirectX/Direct3D aren't the same thing, right; they're competing things. You can run DirectX 9c in vmware. you cannot run OpenGL in vmware. Almost all modern windows 3D is directX, things like Compiz on linux etc are OpenGL. important distinction as you can run windows guest games with directX if the host, vmware and guest are turned on, but you cannot run OpenGL in any virtual machine. OpenGL is seen as being at least a decade out of date, although it's making a comeback in the linux world for compositing window managers.

Short version is that QEMU is

Anonymous's picture

Short version is that QEMU is an emulator and VMware is a virtualizer. VMWARE makes an x86 look like lots of x86 systems. Qemu in theory makes and x86 look like a sparc,ppc,etc,etc it can also be used to run multiple copies but will have a higher overhead than a virtualizer. From what I have seen, VMware is way easier to setup.

Re: Short version is that QEMU is

Anonymous's picture

Sorry, but QEmu is a Virtualizer, to my limited experience no great difference with VMWare (I don't do DirctX &c.) in performance, but $200 cheaper, i.e. free.

Wine is an emulator.

W(ine) Is Not an Emulator.

Anonymous's picture

W(ine) Is Not an Emulator. Is a complete replication of M$ libraries on top of Linux. If it is slower is because it is not polished yet, it has a long way to go to replace win2000 totally.

Regards from Spain.

but QEMU isn't hard to setup :)

mangoo's picture

All I did in my Mandrake system was:

1) urpmi qemu qemu-launcher

2) Then I started qemu-launcher

3) checked "Use CDROM" and pressed "Launch Qemu"

And that was it, I was able to run another Linux from a CDROM :)

I think the comparison you ar

Anonymous's picture

I think the comparison you are looking for is between vmware and xen.

I think the comparison you ar

Anonymous's picture

I think the comparison you are looking for is between vmware and UML.

vmware and UML have more in common than either has with xen.

VMware Workstation 5 and slackware

Anonymous's picture

So how do u get this to work on a slackware 10.x system?