Running VMware ESX 3.0.1 inside a VMware Workstation 6.0

It is now possible to run VMware ESX 3.0.1 servers inside a VMware Workstation6.0 (Build 45731) if you have specific processors in your system. These processors need to have the new x86 virtualization capabilities (Intel VT or the AMD-V).

The guys are xtravirt.com have written a good starter guide. While they only mentionned how to run it with the Intel VT ( monitor_control.vt32 = TRUE ) flag, you can run them on AMD Opteron (AM2 or Socket F 1207pin). You need to use the monitor_control.svm_enable = TRUE. Thanks to the monitor_control.svn_enable switch, the virtual ESX 3.0.1 server will boot and be ready within 90 seconds.

Here is a sample esx-01.vmx file that I’m using on my AMD Opteron workstation (HP xw9400 Workstation). Notice the ethernet device used (e1000), the number of vcpu (2), and the monitor_control switches.

esx-01.vmx

annotation = "esx-02.vi3.local|0A|0AVMware ESX 3.0.1 Build 39823|0A|0AvSwitch0 - Service Console|0AvSwitch1 - VM Network|0AvSwitch2 - VMotion|0A"
<span lang="EN-GB">config.version = “8″
deploymentPlatform = “windows”
displayName = “esx-02 (VMware ESX 3.0.1)”
ethernet0.addressType = “generated”
ethernet0.connectionType = “bridged”
ethernet0.present = “TRUE”
ethernet0.virtualDev = “e1000″
ethernet0.wakeOnPcktRcv = “FALSE”
ethernet1.addressType = “generated”
ethernet1.connectionType = “bridged”
ethernet1.present = “TRUE”
ethernet1.virtualDev = “e1000″
ethernet2.addressType = “generated”
ethernet2.connectionType = “bridged”
ethernet2.present = “TRUE”
ethernet2.virtualDev = “e1000″
floppy0.fileName = “/dev/fd0″
floppy0.startConnected = “FALSE”
guestOS = “other-64″
ide1:0.deviceType = “cdrom-raw”
ide1:0.fileName = “/dev/hdc”
ide1:0.present = “TRUE”
isolation.tools.hgfs.disable = “TRUE”</span>
<span lang="EN-GB">isolation.tools.getPtrLocation.disable = “TRUE”
isolation.tools.setPtrLocation.disable = “TRUE”
MemAllowAutoScaleDown = “FALSE”
memsize = “1024″
monitor_control.enable_svm = TRUE
monitor_control.restrict_backdoor = TRUE
#monitor_control.vt32 = TRUE
numvcpus = “2″
nvram = “esx-02.nvram”
RemoteDisplay.vnc.port = “0″
scsi0:0.fileName = “esx-02.vmdk”
scsi0:0.present = “TRUE”
scsi0.present = “TRUE”
scsi0.virtualDev = “lsilogic”
svga.vramSize = “16708800″
tools.upgrade.policy = “useGlobal”
</span>virtualHW.productCompatibility = “esx”
virtualHW.version = “4″

Two entries in the VMware Community forum cover this topic. “Ability to run ESX as a Workstation guestand “How to install ESX3 on Workstation 6 – Whitepaper!

Zattoo for Linux (x86-64)

zattoo Just got back from a long weekend, and I saw a nice news item waiting for me in my email box, the Zattoo client is now available for Linux. The Zattoo client is a peer-to-peer client that allows the user to select a Live TV channel (out of a growing selection of television channels).

While only released so far for Linux in a x86 (32bit) format for 3 different distributions : Ubuntu 6.10, Fedora Core 6, and OpenSuse 10.2, it can quickly be adapted to other distros. I’ve been able to get it running without much trouble (just had to add 2 libraries) on my Red Hat Enterprise Linux 5 (x86-64). Here are the few steps needed to get it running after having downloaded the binary from the Zattoo download pages.

 

Create two Symbolic Links:

ln -s /lib/libssl.so.0.9.8b /lib/libssl.so.0.9.8
ln -s /lib/libcrypto.so.0.9.8b /lib/libcrypto.so.0.9.8

In addition it requires two additional libraries that where not on my configuration The gtkglext library for i386, which I found already compiled for rhel5-i386 and the libfaad library found in the faad2 package for i386. In addition I also created a ldconfig entry for Zattoo to find it’s libraries. Under RHEL5 I use the ld.so.conf.d directory.

 

Edit /etc/ld.so.conf.d/zattoo.conf :

/usr/lib/zattoo

When I didn’t do this, I was getting the following error code:

 

zattoo_player: symbol lookup error: zattoo_player: undefined symbol: faacDecOpen

Another list of people making comments about Zattoo on Linux is available on this more official blog.

Enabling Virtual Machine Interface (VMI) in VMware Workstation 6.0 & Ubuntu 7.04 (i386)

The Virtual Machine Interface (VMI) that is provided in the VMware Workstation 6.0 work currently only with the Ubuntu Feisty Fawn 7.04 distro. But it requires the i386 version, not the x86-64. To check if you’re kernel has VMI paravirtual kernel support enabled, you can check the kernel compile config.
Code:

# grep VMI /boot/config-2.6.20-15-server

CONFIG_VMI=y

There isn’t much showing inside the virtual machine when it’s running with the paravirtual kernel support. The only quick way I’ve found so far, is to check the APIC timer interrupt. In the Virtual Machine Interface (VMI) enabled machine you have to check the following

Code:

# grep VMI /proc/interrupts

0   74    IO-APIC-Edge            VMI-alarm

The normal APIC timer function has been replaced by a VMI-alarm function.

It goes without saying that you need to activate the VMI paravirtual kernel support in the config of the virtual machine in the Options/Advanced section.

VMware Workstation 6.0 for Linux

VMware LogoVMware has released VMware Workstation 6.0 yesterday. It is the sixth generation of the Workstation virtualization product. This version brings enhancements on the virtual devices and connectivity for the virtual machines (USB 2.0 support, more network cards, multiple-display). Seemlessly run both 32bit environments and 64bit (x86-64) on the same host. Supports running virtual machines in the background with headless operations. Enhanced support for developpers.

Up to this point nothing earthshattering right. Well two new features that VMware Workstation 6.0 brings to virtualization are :

  • Virtual Machine Interface (VMI) support (experimental): VMware Workstation 6.0 is the first virtualization platform to allow execution of paravirtualized guest operating systems that implement the VMI interface. Please note that VMI configuration is only available in i386 kernels for the moment. x86-64 will come.
  • Continuous virtual machine record and replay (experimental): Users can record the execution of a virtual machine, including all inputs, outputs and decisions made along the way. On demand, the user can go “back in time” to the start of the recording and replay execution, guaranteeing that the virtual machine will perform exactly the same operations every time and ensuring bugs can be reproduced and resolved.

Having taken part of the two beta releases and the release candidate of the Workstation 6.0 product, I immediately upgraded my Workstation 5.0 for Linux license to the new version last night. This is an amazing product !!!

Windows Mobile 5.0 AKU 3.3 Improved performance

HTC TytnI’ve purchased last year a Swisscom XPA v1605 (HTC TyTN, HERMES or Qtek 9600) PocketPC Phone. It’s a PocketPC sized phone that supports GSM & UMTS communications. It came with Windows Mobile 5.0 and had a few Service provider installed applications (F-Secure Anti-Virus, TomTom Navigator 5 for Switzerland, SBB Timetable) and the Swisscom Mobile Assistant tools. While the phone looked good, I have not been too happy about the performance of the user interface. Additional programs like the SPB Pocket Plus also gave me lots trouble, and the worse, was the high quanity of missed calls.Swisscom has made available on their support pages an upgrate to Windows Mobile 5.0 AKU 3.3 (Update V2.08.170.1). After having installed the memory card software for the XPA v1605 on a brand new 2GB MicroSD, I upgraded the Swisscom XPA v1605 to the latest firmware version. I added the two excellent versions of SPB Pocket Plus and SPB Diary.

The result is a Windows Mobile 5.0 device that feels a lot more snappy at usage, faster loading, using smaller memory footprint and supports the latest Direct Push Technology from Microsoft.

Warning: A small note for SPB Backup users, the backup created on the previous version of Windows Mobile 5.0 didn’t load up properly under AKU 3.3, I had to retrieve all my original contacts from an old Outlook contact list.

Another Weekend in the Alps

OvronazWell, I just spend another weekend in the alps. We spend three great days in a thermal therapy site in the heart of the Alps, in Ovronaz (Valais). While we where onsite, we enjoy some great thermal therapy, based on massages, hydromassages, warm stone therapy and watsu massage (Water-Shiatsu). The best and most enjoyable moment is always bathing in warm water and having snow drift down from the sky at night.

Level 70

I haven’t been able to play as much as I might have wanted, but I finaly reached the famed Level 70 with my character. Time to start working on my flying mount and starting the faction grind.

World of Warcraft – Burning Crusade

Ouch… nearly 8 Million went to the stores today to get their copy of the World of Warcraft expansion pack : Burning Crusade. Lots of new content (zones, dungeons, new mounts, quests) and 10 new level to raise. On some servers there is such a large population, that Blizzard is now looking to split them in two. It looks like my server will be hit sooner than other servers.

CrossOver Linux 6.0

Today, CodeWeavers have released their latest version of the CrossOver suite. CrossOver Linux 6.0 allows you to install and run natively a select few windows applications on top of a Linux system. The applications are installed inside Windows ‘bottles’. The CrossOver suite is based on the Wine application, but has lots of proprietary extensions. Wine is an Open Source implementation of the API on top of X and Unix.

My interest in the current version of CrossOver Linux 6.0 is it’s capability to run World Of Warcraft on Linux. If I had to run any other kind of Windows applications, I would run them inside a VMware virtual machine, but unfortunately 3D graphics are not accelerated in these VMware machines.