A Django site.
November 1, 2008
» VMware Server 1.0.7 on Ubuntu 8.10 “Intrepid” (2.6.27-7-generic)

Based on a request in the Ubuntu Tutorials Forum I spent some time this morning researching VMware Server on the new Ubuntu 8.10 release.  Google was quickly helpful, and I was able to get VMware Server 1.0.7 running on a fresh install of Ubuntu 8.10 “Intrepid”.  Here are the steps I took toward getting this installed and working.

Download the dependencies and components

You’ll need to, of course, download the VMware Server .tar.gz file.  This can be done using this command:

wget -c http://download3.vmware.com/software/vmserver/VMware-server-1.0.7-108231.tar.gz

There is also a patch to get this to compile properly.  VMware has regularly been guilty of not keeping up with the latest kernels.  This patch will help correct this problem:

wget -c http://www.insecure.ws/warehouse/vmware-update-2.6.27-5.5.7-2.tar.gz

And the one last thing we’ll need are the compiler tools, which can be installed using this command (or click the package name to use aptURL):

sudo aptitude install build-essential linux-kernel-headers xinetd

Now that we have all of the dependencies and archives downloaded we can unpack them.  In the same location where you downloaded the .tar.gz files (likely your home folder or Desktop), run the following command:

tar xf vmware-update*.tar.gz
tar xf VMware-server*.tar.gz

Installing VMware Server 1.0.7 + patch

We’ll now start the installation.  First we need to install the core vmware application.  We’ll then patch the configuration script, and configure the system.

cd vmware-server-distrib/
sudo ./vmware-install.pl

On my installation I used the defaults until it asked me if I’d like to run the vmware-config.pl configuration script.  At this point select [no].

Once this has finished and you’ve quit at the configuration option, use these commands to patch the config:

cd ../vmware-update*/
sudo ./runme.pl

This script will patch the configuration and then again ask you to run the vmware-config.pl configuration script.  This time around select [yes].  On my installation I selected the defaults for the remaining questions and my installation works fine.

Good luck.  Any issues, give the Ubuntu Tutorials Forum a try.

Other Points of Interest

September 23, 2008

Jared Ottley
nonic
Jared Ottley
» Recent Alfresco Presentations

Over the past few weeks I have had the chance to do a couple of presentations.  One at UTOSC on Enterprise Document Management and another as part of the Alfresco Developer Series on building VMWare Appliances with Alfresco.

Links to the slide decks are here and here.

A recording of the VMWare Presentation can be found here.

July 27, 2008

Hans Fugal
no nic
The Fugue :
» VMWare Server on Hardy

I had a heck of a time getting VMWare Server running on Ubuntu 8.04 (Hardy Heron). The problem is that the vmmon and vmnet modules fail to build against kernel 2.6.24. A little googling quickly reveals that you want the any-any-update patch, but that didn't work for me either. To be specific, vmware-any-any-update117c.tar.gz did not work. It turns out vmware-any-any-update-116.tgz works great. Maybe 117 is for the 2.6.25 kernel or something.

So, you do the vmware installation except for the vmware-config.pl step. Then you download and extract the above tarball and run runme.pl. Simple enough.

But when you try to run it, you get errors like this:

/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_3.4' not found (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_3.4' not found (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_3.4' not found (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6)

I'm not sure what the right way to fix this is, but this way works for me.

sudo cp /lib/libgcc_s.so.1 /usr/lib/vmware/lib/libgcc_s.so.1/

June 8, 2008
» KVM and Virt-Manager On Ubuntu 8.04

You’ve been seeing a lot of virtualization specific posts recently here at Ubuntu Tutorials.  I’ve been tinkering with a number of virtualization options, namely VMware Server, Virtualbox and now KVM with Virt-Manager.

I’m not going to go into comparing the three in this post, but I will say that KVM is the only solution that will let me run 64bit guests on my 64bit host.  It also cleanly manages networking, whereas VirtualBox still has issues there.  KVM is still fairly new however so the UI features are not as nice as the other two.

Installing The Packages

Assuming your machine will support KVM (generally, core 2 duo and later) lets get the right packages installed.

sudo aptitude install kvm virt-manager libvirt-bin

This will install the Virt-Manager graphical interface for creating and managing your virtual installations.  It’ll also install the kernel module to make use of the KVM instruction set and the libvirt library.

Initial Setup

Once you’ve got the right packages installed you’ll need to give yourself access to the KVM device.  This is done simply enough using:

sudo gpasswd -a username libvirtd

This will require you to logout and login again.  When you get back we’ll get Virt-Manager launched and some virtual machines built.  Go ahead, relogin.  I’ll wait…

Running Virt-Manager

Virt-Manager is a nice kvm/qemu/xen management interface developed by the good folks at RedHat.  This utility makes it really easy to create, manage and delete virtual installations.  You can launch Virt-Manager via the command line, or the Applications menu.

virt-manager

Troubleshooting

If you have VirtualBox installed you may run into conflicts between the kernel modules.  Make sure to remember to remove the conflicting module before you run either of the virtualization solutions.  You can do this by using these commands.

To remove the VirtualBox module:

sudo modprobe -r vboxdrv

To remove the KVM module:

sudo modprobe -r kvm-intel

Enjoy.

Updated: added user to libvirtd group instead of kvm group. Removed launching with sudo.

Related

June 7, 2008
» How To Install VMware Tools on Ubuntu 8.04 Guests

Installing VMware Tools on virtualized guests gives you a much more enjoyable experience within your virtual environment.  Screen resolution, mouse behaviour, etc will be improved for your virtual sessions after installing these additional tools.  Installing these tools within Ubuntu 8.04 virtualized guests is fairly simple, just follow along below.

Installing VMware Tools

The first requirement, of course, is that you have Ubuntu 8.04 installed within VMware Server and that Ubuntu 8.04 is running.

Once you’ve got your Ubuntu 8.04 guest logged in, navigate to the “VM” menu option (File, Edit, View… VM) and select “Install VMware Tools”.  This will notify you once again that your guest must be logged in.  If that is the case, click “Install”.

note: The next step in the process may be simpler if you make sure any other CD images are unmounted before continuing.

This part of the process mounts a virtual CD image with the VMware Tools contained on it.  To find these tools for installation navigate to Places > Computer > CD Drive.  You should find these two files listed there:

VMwareTools-*.rpm
VMwareTools-.tar.gz

For Ubuntu guest installations we’ll want to use the .tar.gz file.  Now we have access to the needed file, the next part of the process is opening the archive and installing the tools.

Below I’ve put together a copy-paste list of commands you should be able to use to unpack and setup VMware Tools on your Ubuntu 8.04 guest.  All of these commands happen within the Ubuntu 8.04 Guest machine:

sudo aptitude install build-essential linux-headers-generic
cp /media/cdrom/VMwareTools-*.tar.gz /tmp/
cd /tmp/
tar xf VMwareTools-*.tar.gz
cd vmware-tools-distrib/
sudo ./vmware-install.pl

You should be able to safely select the defaults for most of the questions.  You might want to pay attention at the step where it asks for your preferred available resolution and set that properly.  For the new VMware Tools to be available once this process is done you’ll need to reboot your Ubuntu 8.04 guest.  Enjoy.

Related

May 3, 2008
» Install VMware Server 1.0.5 on Ubuntu 8.04 “Hardy”

UPDATE: This tutorial has been updated for VMware Server 1.0.6.  See the updated instructions here, at How To Install VMware Server 1.0.6 on Ubuntu 8.04.

Now that most of the modern world has upgraded to Ubuntu 8.04 I’ve begun to see comments regarding VMware Server no longer working.  You may have used my previous article, Installing VMware Server on Ubuntu 7.10, which has worked great.  Now that 8.04 “Hardy” is installed things have become a bit more complicated unfortunately.

The problem is that VMware has not updated their latest versions to make use of the latest kernel, GCC or gnome libraries.  So, we’ve got two options.

  1. Wait for a new VMware release and hope they patch everything.
  2. Follow the rest of this tutorial and get your hands dirty on the terminal.  We can make it work, but we have to hammer it into submission.

So, I’ll assume because you’re still reading that you’ve opted for the hammer into submission option.  Let’s get started.

Downloading the Requirements

The first step, of course, is to download VMware Server 1.0.5.  You’ll have to agree to the EULA (actually twice.  Once before download and once during installation.  Remember, VMware is free-as-in-beer but not free-as-in-speech.)

The second step is to install some development tools that we’ll need to get things running.  Use the following command or click the package names to install the requirements:

sudo aptitude install build-essential linux-kernel-devel linux-headers-generic xinetd

The third step is to download one more tool to help in the manual build process for VMware Server 1.0.5.  What we need is a script which will help in the custom config hosted at Google Code.  Download the vmware-any-any-update-116.tgz.

You will also need to generate a serial number to run VMware Server.  Visit this link to register and generate the number of codes you might want. Remember to print the codes or write them down because in my experience they are not emailed to you.

OK, at this point we should have all of the requirements, now we can get to work…

Installation and Configuration

Let’s unpack the VMware archive that we downloaded and run the VMware installer.  NOTE: After some basic configuration it will ask you to run vmware-config.pl.  DO NOT RUN vmware-config.pl, WE ARE NOT READY YET.

tar xf VMware-server-1.0.5
cd vmware-server-distrib
sudo ./vmware-install.pl

When it asks you to run vmware-config.pl you want to answer “no” and this is where the vmware-any-any-116.tgz patch comes in.

cd ..
tar xf vmware-any-any-update-116.tgz
cd vmware-any-any-update116
sudo ./runme.pl

After this runs it will ask you again if you want to run vmware-config.pl.  At this point select “yes”.

The Last Step

If you attempt to run vmware at this point you might notice that it spits out some nasty errors and complains at you.  There is one more thing we need to setup. (Hey, VMware, if you’re reading this will you please incorporate these fixes into your official download already!)

Basically VMware is missing and complaining about some cairo libraries and gcc.  So, the simple fix for this is to point to them by using a symbolic link:

sudo ln -sf /usr/lib/gcc/i486-linux-gnu/4.2.3/libgcc_s.so /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1
sudo ln -sf /usr/lib/libpng12.so.0 /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0

At this point you should be able to launch vmware and enjoy some virtualization goodness.  Please stay tuned for virtualization updates regarding virtualbox and the new KVM!

sources: I want to throw a big thanks to my buddy Igor for helping figure out these tweaks.  Check out his blog, with these and other instructions, here.

UPDATE: based on some of the comments below I’ve added the “-f” to the symbolik link options.

Related

May 1, 2008

Phil Windley
pjw
Phil Windley's Technometria
» Fusion 1.1.2

VMWare released a new version of Fusion last week: 1.1.2. There are a lot of little fixes that if they were a problem for you you'll be very glad to have fixed. If not, you might not notice much difference. I'd been bit a few times by Fusion refusing to release USB resources when it quit. Bottom line: if you're not having any issues, no rush.

Tags: virtualization vmware fusion

March 24, 2008

Phil Windley
pjw
Phil Windley's Technometria
» Parallels and OS X Instability

VMWare Fusion

Lately, I've had a very rocky relationship with my Mac Book Pro. One of the things that attracted me to OS X was its stability. Over the past several months (before and after Leopard) my MBP has had trouble with sleeping, waking, and weird, inexplicable freezing. Often when the machine woke up, it would the screen would be black and never come back. The machine would freeze at odd times and nothing would unstick it. I couldn't even log in remotely using SSH, so it was pretty stuck.

The final straw was erratic mouse behavior. The mouse seemed sluggish and wouldn't follow the track. Only a reboot would cure it and the it would deteriorate over the next 5-10 hours.

I considered an OS reload, but didn't really expect that would solve the problem since these issues had persisted through reloads before. I suspected, but didn't have much evidence that it has something to do with a kernel extension because the locking up was occurring at a deep level.

The good news is that OS X some new tools for exploring what kernel extensions are loaded. I used the following command to see what (besides Apple extensions) were loaded:

kextfind -loaded -not -bundle-id -substring 'com.apple' -print 

Doing so revealed about five extensions. I started Google each one and discovered that vmmain.kext was suspected in at least one other case of causing erratic mouse behavior. I didn't want to uninstall Parallels to test this, so I just renamed the plist file in StartupItems so it wouldn't load.

mv /Library/StartupItems/Parallels/StartupParameters.plist foo.plist

Now, after a reboot, Parallels doesn't load and looking at the loaded kernel extensions shows that in particular vmmain.kext hasn't loaded.

I did this five days ago and my machine has been remarkably stable. It feels like my old Mac again. I don't know that it's a Parallels problem--at least not exclusively. I suspect that its an interaction with other things. In particular, I run Parallels and Fusion both and there may be some weird interaction going on there.

I like Parallels. I like Coherence better than Unity. I like the snapshot feature in Parallels because it allows multiple snapshots of the same image. But I need Fusion for running Fedora (Parallels didn't work so well for me there). Fusion also wins on the performance front--particularly with multiple cores.

There are ways to load and unload kernel extensions and that may be a better solution, but for now, I'm just using Fusion to see what happens. I'll let you know if my experiment turns up anything else.

Tags: osx parallels virtualization debugging fusion vmware

November 21, 2007

Jared Ottley
nonic
Jared Ottley
» Jeos and Initramfs

When installing Ubuntu Jeos in VMWare, you need to change the disk type in VMWare from SCSI to IDE, otherwise, when it goes to boot, it will appear to hang and then launch in to initramfs, because it is not expecting SCSI disks, even though you may have installed on SCSI disks. This was very frustrating for a couple of hours.

September 12, 2007

Phil Windley
pjw
Phil Windley's Technometria
» Installing Tools in Fusion When They Won't Install

In Fusion (and other virtualization systems) you should install OS tools on the guest OS to make it behave better. This is not something specific to Fusion, this is a general fact of virtualization. Usually, clicking the "Install VMWare Tools" does the trick--especially with Windows. Sometimes, however, it doesn't do anything. On those occasions you need to take over and do it manually. Here's how.

First, mount the right ISO as a CDROM image. You'll find these in

/Library/Application Support/VMWare Fusion/isoimages

Select the right one for your OS. You may need to manually mount the disk. Fedora, for example, should automatically mount the CDROM when you connect it, but sometimes it doesn't. As root, use a command like this one to mount it:

mount /dev/hdc /mnt/media -t iso9660

I say "like this one" because you'll have to figure out which device is the CDROM. Note that if the /mnt/media directory doesn't exist, you may get an error.

The image will contain a tarball. Untar it to a convenient directory and then run the Perl script. It will ask you lots of questions. For Fedora Core , I accepted it's default answers and it worked great. If it can't find the right version of vmmemctl it will try to build it. This worked flawlessly for me. If it doesn't for you, it probably needs include files from packages you didn't load at install. I always load the developer and kernel building packages.

That's it, a reboot or an X restart and you're done.

Tags: virtualization osx vmware fusion