Archive for the ‘Vmware’ Category

Vmware Server 2 Web Access Connection Loss (vmware-hostd crash) Workarounds

November 16th, 2009 17 comments

Summery of Issue

With upgrading to RHEL 5.4, CentOS 5.4 and Ubuntu 9.10, the latest 2.x.x versions of VMware Server are having serious Web Access GUI connection failures, specifically vmware-hostd crashing repeatedly. This has been found with VMware Server 2.0.0, Vmware Server 2.0.1 and VMware Server 2.0.2. VMware Server 2.x.x was stable in the previous revisions of the mentioned OS’s. Below are two solutions that “appear” to make for a stable vmware-hostd process. You are advised strongly to satisfy your own assuredness of the stability of vmware-hostd using these solutions before deployment to a mission critical environment.

Both solutions do not require you to stop all vmware related processes on the host server. The following steps assume vmware-hostd has crashed and left VMware clients still running.

Verify vmware-host Process has Failed

Note: If you get the below from the ps command you have another issue and this document is not for you.

# ps -ef |grep vmware-hostd

root 10858 1 0 16:47 ? 00:00:02 /usr/lib/vmware/bin/vmware-hostd -a -d -u /etc/vmware/hostd/config.xml

root 11055 11026 0 17:02 pts/3 00:00:00 grep vmware-hostd

Regaining VMware Server 2 Web Access GUI Control

If you want to start the vmware-hostd process to manage your VMware Server 2 guest operating systems again you may do so with the following commands.

# export LD_LIBRARY_PATH=/usr/lib/vmware/vmacore:/usr/lib/vmware/hostd:/usr/lib/vmware/lib/

# /usr/lib/vmware/bin/vmware-hostd -a -d -u /etc/vmware/hostd/config.xml &

[1] 11139

# <hit return/enter>

[1]+ Done /usr/lib/vmware/bin/vmware-hostd -a -d -u /etc/vmware/hostd/config.xml

# ps -ef | grep hostd

root 11140 1 22 17:13 ? 00:00:01 /usr/lib/vmware/bin/vmware-hostd -a -d -u /etc/vmware/hostd/config.xml

root 11155 11026 0 17:13 pts/3 00:00:00 grep hostd&

nohup is not needed in this instance as vmware-hostd runs as a daemon but the ampersand “&” is. Otherwise you’ll get logged output to the screen and when you exit your session vmware-hostd will stop too.

Solving the VMware Server 2 Web Access GUI Connection Failure

I recommend looking at both solutions. I’m currently employing solution #2 but I’ll leave that decision up to you. Both allow you to use the start/stop /etc/init.d/vmware script as you normally would and are permanent unlike the quick fix above to get the vmware-hostd process up and running again. Again with both solutions you need to determine if they, in fact, produce a stable VMware Server 2 environment before deployment to a mission critical environment.

SOLUTION #1 ( reversion – RHEL 5.4 & CentOS 5.4)

Download and copy into place:

# lynx

# rpm -Uvh –root=/tmp/ –nodeps ./glibc-2.5-34.x86_64.rpm

# mkdir /usr/lib/vmware/lib/

# cp /tmp/lib64/ /usr/lib/vmware/lib/

Edit /usr/sbin/vmware-hostd adding the following export command just before the last line in the script as follows:

# tail -3 /usr/sbin/vmware-hostd

export LD_LIBRARY_PATH=/usr/lib/vmware/lib/$LD_LIBRARY_PATH

eval exec “$DEBUG_CMD” “$binary” “$@”

SOLUTION #2 (Circumventing vmware-hostd library wrapping script – RHEL 5.4, CentOS 5.4 & Ubuntu 9.10 )

Here is another method not requiring reverting to an older version of The downside in this solution is it circumvents the dynamic library path building of the /usr/sbin/vmware-hostd script and executes the /usr/lib/vmware/bin/vmware-hostd binary directly. I do not know if this will present problems in the future or not.

Below is the snippet from the modified /etc/init.d/vmware. You can see I added a LD_LIBRARY_PATH statement, commented out the old exec call and added a new one.

# Start host agent

vmware_start_hostd() {

export LD_LIBRARY_PATH=/usr/lib/vmware/vmacore:/usr/lib/vmware/hostd:/usr/lib/vmware/lib/

vmware_bg_exec “`vmware_product_name` Host Agent” \

“$vmdb_answer_LIBDIR/bin/vmware-hostd” -a -d -u “$vmware_etc_dir/hostd/config.xml”

#”$vmdb_answer_SBINDIR/vmware-hostd” -a -d -u “$vmware_etc_dir/hostd/config.xml”


Restart VMware Server 2

If you don’t have critical guest OS’s running you can stop the guests via the VMware Server 2 Web Access GUI and restart VMware:

# /etc/init.d/vmware restart

Stopping VMware autostart virtual machines:
Virtual machines [ OK ]
Stopping VMware management services:
VMware Virtual Infrastructure Web Access
VMware Server Host Agent [ OK ]
Stopping VMware services:
VMware Authentication Daemon [ OK ]
VM communication interface socket family: [ OK ]
Virtual machine communication interface [ OK ]
Virtual machine monitor [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
Host network detection [ OK ]
DHCP server on /dev/vmnet1 [ OK ]
Host-only networking on /dev/vmnet1 [ OK ]
DHCP server on /dev/vmnet8 [ OK ]
NAT service on /dev/vmnet8 [ OK ]
Host-only networking on /dev/vmnet8 [ OK ]
Virtual ethernet [ OK ]
Starting VMware services:
Virtual machine monitor [ OK ]
Virtual machine communication interface [ OK ]
VM communication interface socket family: [ OK ]
Virtual ethernet [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
Host-only networking on /dev/vmnet1 (background) [ OK ]
DHCP server on /dev/vmnet1 [ OK ]
Host-only networking on /dev/vmnet8 (background) [ OK ]
DHCP server on /dev/vmnet8 [ OK ]
NAT service on /dev/vmnet8 [ OK ]
VMware Server Authentication Daemon (background) [ OK ]
Shared Memory Available [ OK ]
Starting VMware management services:
VMware Server Host Agent (background) [ OK ]
VMware Virtual Infrastructure Web Access
Starting VMware autostart virtual machines:
Virtual machines [ OK ]

As more information on this issue becomes available this post will be updated. Please post your findings too.

This information was generated by my experimentation and the helpful posts of the VMware Community, reference:

Categories: Linux, Vmware Tags:

VMware Server 2 Advanced NAT

October 17th, 2009 2 comments


If you decide to use NAT’d networking for your VMware Server 2.x.x. guest OS you will want to create some port mapping to access the guest with the likes of SSH.  This documents the procedure for creating the needed mapping and uses SSH as an example.  In this document it’s assumed you have VMNet8 configured as your NAT network interface.  If you configured NAT during the installation and configuration of VMware Server 2.x.x and chose the default it will be VMNet8.

Adding a NAT Network Interface

If you did not add a NAT network interface during your VMware Server 2.x.x installation and configuration you may do it now by invoking the following command.

# /usr/bin/

Edit nat.conf

Open the file /etc/vmware/vmnet8/nat/nat.conf for editing.  In our example we will add three guest OS’s for SSH access via port mapping.  Most likely there is an example already for SSH under the [incomingtcp] section.  Under this section is where all incoming TCP traffic will be mapped.

Here are the three mappings for SSH access to our three guest OS’s.

8889 =
8890 =
8891 =

Restart VMNet 8

Next you have to restart VMNet 8 for the changes to take affect.

# /usr/lib/vmware/ restart 8

Try Your New Port Mappings

To gain access, if for example your VMware Server 2.x.x’s IP is, you would perform the following for our first guest OS:

# ssh -p 8889 user@

Be sure your VMware Server’s ports are open in the firewall for, as in our example, 8889, 8890 and 8891 and of course port 22 for all the guests.

It’s important to note that if you run the configuration script for any reason your port mapping may get overwritten by the default nat.conf file.  Your port mappings are backed up to a file similar to this: nat.conf.old.0.

This should take care of SSH access to NAT’s VMware Server 2.x.x guest OS’s.  If you have any comments, we would like to hear from you.

Categories: Vmware Tags:

OpenFiler Vmware Guest Raid 1 Array Creation

September 4th, 2009 No comments


This is part 1 in a proof of concept serious involving the creation of a RAID 1 iSCSI Target using OpenFiler 2.13 and Vmware Server 2.  We will purposely fail one of the virtual disks in the array rebuild the array and verify the data.  In part one of the series we will create the Raid 1 array.  In subsequent parts we will create an ISCSI Target, connect Windows Vista using iSCSI Initiator and simulate RAID 1 drive failure and recovery.  The OpenFiler vmware appliance is free to download and use.  The installation of both Vmware Server 2 and OpenFiler 2.13 vmware appliance will not be covered here.

Create VMware virtual disks

From the VMware Server 2 web administration create two 50 MB disks for the OpenFiler VMware guest accepting the VMware defaults.

Create Raid Partitions

As seen in Figure 1, navigate to openfiler > Volumes > Block Devices and select the first of our newly created disks /dev/sdb.

FIGURE 1: opefiler > Volumes > Block Devices

Create a RAID array partition by selecting Partition Type: “RAID array member” for the entire cylinder range (default) and clicking “Create”.  See Figure 2.  The resulting RAID partition should like as seen in Figure 3.  Repeat the previous steps to create a RAID partition for /dev/sdc

FIGURE 2: opefiler > Volumes > Block Devices > /dev/sdb

FIGURE 3: openfiler > Volumes > Block Devices > /dev/sdb

Create New Raid 1 Array

Once the two raid devices have been created navigate to openfiler > Volumes > Software Raid as seen in Figure 4 below. Select RAID-1 from the drop down menu, leave the chunk size at default, select the two raid devices as seen in Figure 4 and click “Add array”.  The resulting raid array information will be displayed as seen in Figure 5.

Figure 4: openfiler > Volumes > Software Raid

Figure 5: openfiler > Volumes > Software Raid

Create New Volume Group

Navigate to openfiler > Volumes > Volume Groups and create the new volume group “volgroupraid001”.  If this is not your preferred volume group naming convention, change it to your liking.  After entering your “Volume group name”, select our newly created Raid 1 volume /dev/md0 and click “Add volume group” as seen in Figure 6.  The resulting Volume Group is displayed as seen in Figure 7.

Figure 6: openfile > Volumes > Volume Groups

Figure 7: openfiler > Volumes > Volume Groups

Create New Volume

Navigate to openfiler > Volume>Add Volume select our “volgroupraid001” volume group, enter the name our new volume “volraid001”, fill in a description, enter the Required Space” (32MB) and be sure to select the proper “Filesystem Type” of iSCSI.  Click “Create” when ready.  See Figure 8 below.  The resulting Volume Group will be as seen in Figure 9.

Figure 8: openfiler > Volume > Add Volume

Figure 9: openfiler > Volumes > Manager Volumes

In our next section we will create the OpenFiler iSCSI Target using our newly created RAID 1 volume.