VMware Workstation 6.5 Beta 2 released

Latest Version: Beta 2 | 6/23/08 | Build 99530

Can I start a VM in ESX 3.5 on WS 6.5 ? Yes we can
The beta 2 of VMware Workstation contains a permanent fix for this problem......

New Features in VMware Workstation 6.5:

-Seamless integration of guest & host applications with Unity
-Advanced VM Record and Replay with Visual Studio integration
-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
-Virtual Machine Streaming

BRON: NTpro

Sanbarrow's VMware-liveCD

Ulli Hankeln over at Sanbarrow created a new version of the VMware-liveCD this version contains:

-Workstation 6.0.2 ripped
-Converter 3.0.3 cold clone mode
-ViClient for ESX 3.5.0 u1
-RemoteCli
-Virtual Disk Developement Kit
-ViToolkit for Powershell

The complete build is about 450 MB - it requires a box with at least 512 MB RAM to load the dotnet2 apps. Latest MOA 2.3.-011 now allows to run ESX 35i in WS 6.5. beta 91182. In this case the ESX 35i is running from the LiveCD - you can of course mount any local VMFS-volumes and assign them to the ESX 35i. Obviously you need a fat machine to run this LiveCD Of course it still works as a simple Cold Clone CD .

Turn off debug in VMWare 6.5beta (windows)

I’m playing with VMWare workstation 6.5beta(build-91182) and was looking to do some advanced configurations, specifically running ESX 3.5U1 , therefore i was interested in maximum performance to squeak out as much out of my laptop….

A couple things i found out really quick 1) set the Virtualization setting in your systems BIOS if you have one. My core duo did , my centrino did not. This speeded things up considerably, i’d say by a factor of 10.

2) The VMWare workstation process wants to run VM’s with the vmware-vmx-debug binary, and it indicates that you must live with this. Upon closer inspection in the application directory (C:\Program Files\VMware\VMware Workstation) I found vmware-vmx and its about 2MB smaller binary. So what I did was rename vmware-vmx-debug to vmware-vmx-debug-orig and then copy vmware-vmx to vmware-vmx-debug.

Bron: jthomasser.wordpress.com