Archive for the tag 'workstation'

VMware Workstation 6.04 linux x64 unrecoverable error

Ivan Versluis June 25th, 2008

I am running Ubuntu 8.04 LTS Desktop Edition 64bit edition and after I installed VMWare Workstation 6.04 Linux x64 edition I got the following error when trying to start my virtual machines sitting on a NTFS USB disk volume.

VMware Workstation unrecoverable error: (vcpu-0)
Failed to allocate page for guest RAM!
A log file is available in “/media/USB_DATA/NET-DC-01/vmware.log”.  Please request support and include the contents of the log file.
To collect data to submit to VMware support, select Help > About and click “Collect Support Data”. You can also run the “vm-support” script in the Workstation folder directly.
We will respond on the basis of your support entitlement.

image

Please click OK and locate the vm file. Open the vmx file with nano or another text editor and add the setting below. Save the file and try to start the virtual machine again.

mainMem.useNamedFile = “FALSE”

This setting doesn’t use named-file - use for VMs on USB-disks or other slow disks
Windows: useNamedFile= “FALSE” causes memory to be backed by the host’s swap space.
Linux: useNamedFile= “FALSE” causes a hidden file to be created in a temporary directory, which is immediately deleted when you power off the VM

VMWare Workstation 6.5 beta

Ivan Versluis May 19th, 2008

If you are curios and interested like I am than the latest VMWare Workstation 6.5 beta is definitely something to download and install on your system.

Why Participate in a VMware Beta Program?

Here are a few reasons why you should participate in VMware beta programs.

  • Exposure to the next generation features helps you grow your technical skills and understand the direction of the virtualization industry.
  • Ability to prove that the product will work properly in your environment and report areas where it doesn’t.
  • Prototype your solution during the beta program and be ready for deployment when we reach General Availability.
  • Help shape today’s product and tomorrow’s features.
  • Ability to work with VMware engineers on some programs.
  • Problems encountered have a higher probability of being fixed by GA.

Join the new beta program for Workstation 6.5 here.

image

New Features in VMware Workstation 6.5:

  • Seamless integration of guest and host applications with Unity
  • Enhanced advanced VM Record and Replay
  • Support for Smart Cards & Smart Card Readers
  • Link state propagation networking
  • Enhanced ACE authoring capabilities
  • Easy Install Option’s support for Linux
  • Improved 3D graphics Support
  • Release 91182 supports ESX 3.5 and 3i installations

For me personally I would like to explore Unity and ESX in virtual machine support features. I like to keep my system as clean as possible and right now I can have one virtual machines hosting all my applications which I use occasionally. I don’t want to install Adobe Photoshop, Paintshop,  Visual Studio and many others on my host system; with Unity I can bring all those application to my host system. Definitely  something I will use quite often.

Since the release of ESX 3.5 and 3i I have been waiting to have a working installation of those products into VMWare Workstation. Thanks to Eric from NTPRo.nl who is confirming that ESX is up and running in the latest release of VMWare Workstation 6.5 beta.

Failed to lock the file! VMWare virtual disk (vmdk)

Ivan Versluis March 12th, 2008

I copied one of my Windows XP virtual machine running on a VMWare Server 1.02 host locally to my workstation. After the files were copied I opened the vmx file with VMWare Workstation 6 and received the error below after trying to start the virtual machine. I made one snapshot on the VMWare Server host.

Cannot open the disk ‘C:\VM-machines\Windows XP-001\Windows XP Professional-000001.vmdk’ or one of the snapshot disks it depends on. Reason: Failed to lock the file.

 

clip_image002

Locate the virtual machine in Windows Explorer and delete any .lck folders

clip_image004

Start the virtual machine. If this fails try to Map the virtual hard disk to Z:\

clip_image006

clip_image008

I than disconnect the virtual hard disk and retried. The virtual machine boot without any problem; my snapshot was valid.

BitLocker in a vm machine without TPM or USB howto tutorial?

Ivan Versluis March 11th, 2008

Before I read the Step by Step Guide document and quote below I tried getting the BitLocker drive encryption running in a virtual machine.

Windows BitLocker Drive Encryption Step-by-Step Guide

For a non-TPM scenario, you use a startup key to authenticate yourself. The startup key is located on a USB flash drive inserted into the computer before the computer is turned on. In such a scenario, your computer must have a BIOS that can read USB flash drives in the pre-operating system environment (at startup). Your BIOS can be checked by the hardware test near the end of the BitLocker setup wizard.

Using USB removable storage and VMWare virtual machine is just not going to work. The only way to get BitLocker working in a virtual machine is to change the group policy setting and allow BitLocker to work without a TPM chip and use a floppy disk as storage for the startup key. Floppy disk is available in a virtual machine during the boot process of Vista. I was successfully being able to run the BitLocker preparation tool but after the final check of the C volume encryption the system complained about the removable storage was not available during the boot process of Windows Vista.

BitLocker Drive Encryption from the control panel and steps which I executed before reading the Step by Step Guide.

clip_image001

Click Turn on BitLocker

clip_image002

Now I was required to put the Startup key on a USB device.

clip_image003

My USB flash disk was available in the virtual machine.

clip_image004

I clicked continue and restart now.

clip_image005

After logon the error message.

clip_image006

BitLocker could not be enabled. The system firmware failed to enable clearing of system memory on reboot. No encryption applied, any changed made to C: during BitLocker setup will be removed.

How to get BitLocker working in a virtual machine?

  • Install Windows Vista SP1(Enterprise or Ultimate editions) in a virtual machine
  • Make sure you partitioned or format the volumes in the right way. Use the SHIFT+F10 to perform these steps in Vista Setup.

create partition primary size=1500

assign letter=S

create partition primary

assign letter=c

If you don’t partition and format the hard disk this way use the BitLocker Drive Preparation Tool

  • Change the GPO setting. Gpedit.msc and locate the “Control Panel Setup:Enable advanced startup options” setting  in Computer Configuration/Administrative Templates/Windows Components/Bitlocker Drive Encryption and configure “Control Panel Setup: Enable advanced startup options”; check Allow Bitlocker without compatible TPM chip. Reboot

clip_image007

  • Make sure Floppy drive has been configured for the virtual machine and create new bitlocker.flp file. Format the disk.

clip_image008

  • Open a privileged cmd prompt and run cscript c:\Windows\System32\manage-bde.wsf -on C: -rp -sk A:

clip_image009

  • Reboot and make sure floppy drive is last option in the bios boot oder.

clip_image010

  • Encryption in Progress. Keep in mind that BitLocker will encrypt the complete partition and in my case a SCSI harddisk of 64GB will be expanded. After the process has been finished I will end with 64GB virtual disk; same deal with physical hard disk only 6GB will be left during the encryption process. Anyway good lesson learned for my next virtual machine. Using these steps now I am able to test all different features and options available by BitLocker. If you buy new hardware today than the TPM complaint chip will be on your motherboard so setting up a virtual lab is good preparation for the real physical setup.