First, download the VMWare Image Converter from here. Install this on your Windows box and create a VMWare image using the VMWare image converter wizard. The details within the wizard depend on your situation. I believe most settings can be modified later, so your setup is by no means permanent. If you have the ability to clean out your Windows OS before making an image, I would recommend a good cleanup. I had 56GB of files and starting this image later in VWWare server proved to be extremely slow. An image of a clean OS install would be the best scenario.
Next, move the image to your Ubuntu OS. I had a 500GB external hard drive that I used to move the images over. The image converter allows copying over the network too to your target Ubuntu server. All you need is a Samba mount on Ubuntu to move the files over if you choose to move your image over the network.
Now install the VMWare Server on your Ubuntu OS. There are also instructions out there which describe the VMPlayer setup too. Here's a good article on how to do that, and this also describes how to workaround a header issue that some Ubuntu versions (v18.104.22.168) had with VMWare Player/Server installation.
You will also need a C compiler installed on your Ubuntu machine. The VMWare install will compile all of the libraries during install. The installation will give you specifics if you are missing anything.
Fire up VMWare Server/Player now! You might see something like this..
VMware Player unrecoverable error: (vcpu-0)
Failed to allocate page for guest RAM!
A log file is available in "/path/to/VM/vmware.log". A core file is
available in "/path/to/VM/core". Please request support and include
the contents of the log file and core file.
To collect data to submit to VMware support, run "vm-support".
We will respond on the basis of your support entitlement.
Looking at the VMware log file will show the message "Could not mmap
paging file : No such device".
There is a setting in the Virtual Machine's .vmx config file to fix
this. Edit the config file, add
I was finally able to start my VMWare image. The next issue was extremely slow startup time. No biggie, I'll just go grab a cup of coffee.... in the next state! Yah this was slow. I had to tweek some things to get the speed into acceptable condition. These tweeks included...
- Set the VMWare image memory settings closer to the recommended memory. VMWare server will tell you the recommended setting. Mine was 256M, but I doubled that to 512M and I immediately saw an improvement.
- Install VMWare tools. VMWare Server has an option to do this.
NOTE: the tools are installed into the VMWare image, not the player/server. I am presuming that once the tools are installed into my image I could go back and run my image in VMWarePlayer with the same tools installed.
Once the VMWare tools were installed, I noticed improvements in both video resolution and less choppy mouse movements.
- I removed a lot of crud on my image. This included PICASA which does some background processing at the startup of my VMWare image. There was a floppy drive that I removed from the image that will never be used. This is really the part where you can be creative and is also why I earlier recommended creating an image with the smallest footprint possible.