Articles

Archive for the ‘VMware’ Category

VMware Converter – Beware of OEM versions of Windows

Monday, October 5th, 2009

I recently decided to virtualize my dying Exchange 2003 server to give it new life on new hardware.  I’ve had bad luck running the VMware Converter from within Windows (hot clone) on a domain controller in the past.  I’ve also performed a hot cone with no issues at all so it is really a crapshoot as to whether it will work.  I decided to play it safe this time and I did a cold clone by booting from the VMware Converter CD.

The conversion process went smoothly, although it took 12 hours to complete.  Upon completion, it automatically booted up the new virtual machine.  I woke up the next morning and went to log in and I was prompted for Windows activation.  I tried to activate online and it failed.  I called the number for telephone activation and they told me my product ID was invalid and I would have to call support.  I called support and they said I would have to pay for emergency after hours service (this was a Sunday).  So I was out of luck.

I happen to own a Volume License version of Windows Server 2003 – it just wasn’t installed on this server which came with the Dell OEM version.  I decided to boot from the CD and run a Windows repair with my VL CD.  After 40 minutes, the install was complete and Windows was booting…and booting.  It spent 1 hour on Preparing Network Connections and I finally got a login prompt.  I logged in and waited another hour for my desktop to appear before giving up.  I turned my old server back on.

Moral of the story – make sure you are running a Volume License version of Windows BEFORE you convert it to a virtual machine.

0xc000035a Attempting to load a 64-bit application, however this cpu is not compatible with 64-bit mode.

Thursday, September 24th, 2009

I installed VMware ESXi 4.0 on my new Dell Poweredge R710 server.  I then created a Windows 2008 Server virtual machine and proceed to boot from the installation DVD to install Windows.  I was quickly greeted with this error:

Status: 0xc000035a

Info: Attempting to load a 64-bit application, however this cpu is not compatible with 64-bit mode.

Solution:

I forgot to enable Virtualization Technology in the BIOS.  Dell has this disabled by default.  Reboot and press F2.  It is under the Processor settings.

0xc000035a Attempting to load a 64-bit application, however this cpu is not compatible with 64-bit mode.

0xc000035a Attempting to load a 64-bit application, however this cpu is not compatible with 64-bit mode.

Parallels / VMware Fusion Ctrl-Alt-Del on a MAC

Friday, March 28th, 2008

Problem:

You just set up Windows as a virtual machine on your Mac so that you can do real work.  The screen comes up and asks you to press Control-Alt-Delete to log in.  You don’t have those keys on your Mac keyboard.

Solution:

fn-ctrl-option-delete

Debian Etch VMware Network Card Problem

Monday, July 30th, 2007

Problem

When you make a copy of a VMware Virtual Machine, the network card on the copy doesn’t work.

Solution

When you boot the copy, VMware creates a new MAC address for the NIC.  Debian adds a new line to this file with the new MAC address.

/etc/udev/rules.d/z25_persistent-net.rules

Delete the lines with the old MAC addresses and change the last one to be eth0.

VMware VMEM Files – How to disable .vmem files

Friday, April 7th, 2006

If you are a VMware user, you have undoubtedly tried to backup a virtual server while it is running.  Until recently, you could.  However, the newer versions of VMware use .vmem files which are created when the virtual machines are running.  There is really no documentation as to why they exist but they are locked and can’t be copied while the machine is running.  A tedious search through the message boards yielded this solution.

Create a file called settings.ini

Put this code in it:

# Disable VMEM files
# ——————
mainMem.useNamedFile = FALSE

Save it here:

C:Documents and SettingsAll UsersApplication DataVMwareVMware Serversettings.ini

or if you are running Workstation save it here:

C:Documents and SettingsAll UsersApplication DataVMwareVMware Workstationsettings.ini

Restart your virtual machines.