VMWare could not start after updaing Centos 6 kernel

Posted by aionman on Jan 10, 2015 in CentOS, Linux, VMWare

When update my Centos 6 to kernel 2.6.32-504 , my VMWare Workstation 10.0.3 doesn’t work, when start the vm appear the error.

could open /dev/vmmon: No such file or directory.


  1. sudo service vmware stop
  2. sudo rm /lib/modules/$(uname -r)/misc/vmmon.ko
  3. sudo vmware-modconfig –console –build-mod vmmon /usr/bin/gcc /lib/modules/$(uname -r)/build/include/
  4. sudo depmod -a
  5. sudo service vmware start


Chose there best essayhttp://customessayhere.com/!


VMware Workstation-10.0.1 fails after RedHat-6 / Centos software update

Posted by aionman on Dec 21, 2013 in CentOS, Linux, VMWare, Windows 7, Windows XP
No problems in XP or Windows 7 VMs anymore.
Summary of what I did:$ sudo service vmware stop$ sudo mv -v /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.orig

$ sudo rm -v /lib/modules/$(uname -r)/misc/v*.ko

$ sudo depmod -a

#I already had gcc, make, and the kernel headers, but if anyone is following this, they should probably make sure

$ sudo yum install make gcc kernel-headers-$(uname -r)

start vmware


Accessing VMWare Server 2 with vSphere Client (the unsupported way)

Posted by aionman on Jun 20, 2013 in VMWare



Accessing VMWare Server 2 with vSphere Client (the unsupported way)

As many of you already discovered there’s no official Linux client for accessing VMWare Server 2.x, the only thing VMWare suggests you to do is to use internal web interface based on a Tomcat webserver.

This web interface is ugly and slow, not so reliable if you plan a clean and fast administration, as alternative you can use the good and efficient Virtual Infrastructure Client (VIC).

Again: VIC is only available for Windows platform and no Linux (or OS-X) client is available now, you can run it on top of WINE libs but it’s still not a linux native client.
VMWare promised a lot of time ago a “planned version” for Linux but nobody have already seen it (planned with no expected date…) so we’re still waiting for it.

Now vSphere architecture is out, new vSphere Client replaces Virtual Infrastructure Client and guess what ? vSphere Client doesn’t support officially VMWare Server, this makes me really upset and after reading different posts even from their community forum (like this) I was really trying to find a different way to access my server installations or move to a totally different product (VirtualBox, KVM, …)

But after some TCPDUMP traces, a lot of different retries and some Google searches  I’ve solved my problem and I’ll hope this article may help someone else as well.

When you try to connect vSphere to VMWare server you need to insert your credentials and the host name/IP, I’ve started with https://ip.address.to.use:8333 (the old way used with VIC), ip.address.to.use, ip.address.to.use:8333 and so on…
Finally I’ve discovered this form: ip.address.to.use:8333 seems to be the right one.

At the first connection you need to install a certificate in your Windows machine, second step is to retrieve from server “a generic installer”, so you can choose to “Save the Installer” or “Run the Installer“;

both options drives you to a generic error like:

"The required client support files cannot be retrieved from the server"
"The login process will now exit"
"Details: The server could not interpret the client's request. (404 not found)"


But what kind of support files do you need, where are there ? Here’s a link with some useful and legal files in it

Now what you should do after downloading these support files ?
Just unrar these files into your vSphere Client installation folder, something like
“Program FilesVMWareInfrastructureVirtual Infrastructure Client” (x86 32bit)
“Program Files (x86)VMwareInfrastructureVirtual Infrastructure Client” (x86 64bit)
you’ll finally have a directory named “2.5” inside this root folder, now run your vSphere Infrastructure Client again, after inserting your credentials you’ll see
the entire login process like in the past with VIC (so “loading inventory form”,
“loading classes”, and so on…) and the new shiny Client interface is now connected
to VMWare Server as in the past.


This is just a trick to have authentication running again and have access to your
legitimate VMWare Server installation, I’ll hope they’re really working on this
promised linux client capable of connecting to VMWare Server.
At the moment I’m quite skeptic because this new client relies on Microsoft Windows .NET 3.x Framework and Windows J# redistributable package, as a programmer these are not my preferred tools if I’m planning to have a cross platform program because I’m totally depending on .NET (or Mono) and MS libs.
If you’re running a big business you don’t really need it, you just purchase vSphere (new ESX) and you’re set, but if you really need “bare metal emulation” and you can’t afford vSphere, VMWare Server is still the best reliable solution for it, yeah I know Virtual Box/KVM/XEN and others are growing fast but on bare metal VMWare is still the best (from my point of view)



I hope this process may help someone else and I’ll look forward for your comments to this post


Recover vmx from log file

Posted by aionman on Feb 15, 2013 in VMWare

 Recover vmx from log file

On the VMware community forums, Eric Tung has devised a little jewel of code that automates recreating a vmx file from a recent vmware.log file.

This is possible as on every boot of a virtual machine, the vmware.log gets a copy from your virtual hardware settings written out into the vmware.log logfile along with some extra information such as the date and time this VM was run. The script extracts the relevant part for you and eliminates the risk of making a typo while doing this by hand. It is written in perl, just a few lines long and shows the true power of what a bit of perl can do for you 🙂

vmxRecover.pl code

use strict;
use warnings;  

if ($#ARGV != 0) {
   print "Recovers .vmx files from .log files. Usage:\n";
   print "$0 logfile > vmxfile\n\n";

while (<>) {
   # Scan until we reach the config section
   if (/: vmx\| DICT --- CONFIGURATION/) { last; }

while (<>) {
   if (/: vmx\| DICT --- \S/) { last; } # Keep going until the next section
   s/^.*: vmx\| DICT\s*//;    # Strip off the leading timestamp and other stuff
   s/\r//;                    # Get rid of any \r's that may have somehow snuck in
   s/([^=]*=) (.*)/$1 "$2"/;  # Quote the value


Say you want to recreate a the virtual hardware configuration for a VMware virtual machine “Windows XP.vmx” then you’d call it like this:

vmxRecover.pl vmware.log > "Windows XP.vmx"

Another way to do it.

Rebuilding the virtual machine’s .vmx file from vmware.log


You may want to rebuild the .vmx file of a virtual machine and recover its contents if the .vmx is missing or has lost its configuration.

This article provides a shell script that rebuilds the .vmx file from the vmware.log file.


To rebuild the virtual machine’s .vmx file using a shell script which parses the information from the vmware.log file:


  • VMware does not guarantee that this script will recover every .vmx file. This is only an option to try if the operation becomes necessary. For example, if the virtual machine configuration is changed after the last power on, then that information is not logged in the vmware.log and the .vmx may not be accurate.
  • Ensure that you run the commands or the script from the virtual machine working directory. To determine the working directory, right-click the virtual machine and click Edit Settings, then click Options > Virtual Machine Working Location.
  1. Create a new file using a text editor. Name it, for example, vmxrebuild.sh.

    Note: For information on using a text editor, see Editing files on an ESX host using vi or nano (1020302).

  2. Copy and paste this script to the file:

    VMXFILENAME=$(sed -n 's/^.*Config file: .*\/\(.\+\)$/\1/p' vmware.log)
    echo -e "#\041/usr/bin/vmware" > ${VMXFILENAME}
    echo '.encoding = "UTF-8"' >> ${VMXFILENAME}
    sed -n '/DICT --- CONFIGURATION/,/DICT ---/ s/^.*DICT \+\(.\+\) = \(.\+\)$/\1 = "\2"/p' vmware.log >> ${VMXFILENAME}

  3. Save the file, ensuring that it has an .sh extension.
  4. Run this command to give execute privileges to the file:

    chmod +x filename

    Where filename is the name of the saved shell script file.

  5. If uuid.location has changed due to operations such as cloning or Storage vMotion, run this command to get the new UUID:

    NEWUUID=$(sed -n "s/^.*UUID: Writing uuid.location value: '\(.\+\)'.*$/\1/p" vmware.log)

    Note: Whenever possible, use the latest vmware.log file.

  6. Run this command to replace the old UUID in the .vmx file with the new one:

    if [ "${NEWUUID}" ] then sed -i "s/uuid.location = .*$/uuid.location = \"${NEWUUID}\"/" ${VMXFILENAME} fi

  7. To run the script:



Starting a virtual machine generates a syntax error

Posted by aionman on Dec 3, 2012 in VMWare

Starting a virtual machine generates a syntax error


  • The virtual machine fails to power on.
  • The .vmx file contains garbled data or is zero bytes long or is corrupted.
  • You see the error:“<VM_Name>.vmx” line <x>: syntax error


This issue occurs if the .vmx file is corrupted. To resolve this issue, either build a new.vmx file or manually repair the existing file.

Creating a new .vmx file

To create a new .vmx file:

  1. Locate the virtual machine files and delete the .VMX file.
  2. Open the VMware product or VMware Infrastructure Client.
  3. Click File > New > Virtual Machine (if listed).
  4. Follow the new virtual machine wizard making sure to select the Custom configuration installation option. When prompted to create a new virtual hard disk file, choose to specify an existing file. Specify the existing .vmdk file.

Note: For related information when using a Fusion virtual machine, see Creating a virtual machine from an existing virtual disk in Fusion (1023555).

Manually rebuilding the .vmx file

It is possible to reconstruct the corrupted .vmx file provided a copy of thevmware.log is available where the virtual machine started correctly.
To manually rebuild the .vmx file:
  1. Locate the virtual machine files. For Fusion, see Locating the virtual machine bundle in VMware Fusion (1007599)
  2. Open the vmware.log file where the virtual machine started successfully with a text editor. In Macs, use Text Edit.
  3. Find the line in the log file that contains: — CONFIGURATIONBeyond this line — until the next line that contains  — are the complete contents of the .vmx file as it was parsed by the vmx process.
  4. Copy the text into a new .vmx file, overwriting the damaged .vmx file.
  5. From the new file, clean the logging output from the text to restore the original configuration.For example, change the line that reads: 

    vmx| DICT svga.vramSize = 134217728


    svga.vramSize = “134217728”


Cloning VMs on Linux Hosts with VMWare Server 2.0

Posted by aionman on Apr 16, 2010 in Ubuntu, VMWare

think it’s a MAJOR pain not having a “clone” feature in VMWare Server without using Virtual Infrastructure, so I made my own Linux shell scripts to do it.

The clone script does a straight clone of a VM. It copies the directory, renames the files and tweaks all the text inside the files by using sed to replace the old name with the new one, then sets all the permissions to what they would be if you created a new VM.

The rename script basically does all but copy it. This is handy for if you tried to rename a directory manually or attempted a manual copy and then found it still shows up under the old name in the web console. Remember this one assumes you have already renamed the directory to the new name and it MUST be the same as what you intend for the new name to be.

Both work the same way… scriptname <old name> <new name>

You can use quotes around the names if there are spaces, I went to great lengths to make sure it would still work with spaces in names (although I personally hate spaces).

Save the scripts to the base directory where your VM’s are, “standard” location is “/var/lib/vmware/Virtual Machines”. Make executable with chmod +x <scriptname>.

Once ran, add the new/renamed VM to the web console and choose “I copied it” or “I moved it” as appropriate.

These scripts are offered free to everyone to use, modify, or do anything else you want with except take credit for the original version. Absolutely no warranty or guarantee of any kind on the part of anyone that they won’t hose your VMs or even your whole system.

If I understand correctly how the split disks work, the 3rd file attached (clone-split-disk.sh) should work for those VM’s. I have not tested it myself and will likely not get a chance anytime soon, so I will rely on feedback from the community for any near-future tweaking. This is really just a change to one line (line 34) in the file – in the original we exclude the binary .vmdk file from parsing to find-and-replace since this is how single-disk-file versions are saved; in this version we exclude -f???.vmdk where “?” is a number between 0-9 (i.e. files like -f001.vmdk, -f002.vmdk, etc) while we parse the .vmdk file since with split disks, the .vmdk is a text file describing the -f???.vmdk binary disk files. IF you use a combination of split disks and single-file disks, probably neither one of these will work – maybe in a future version I will be able to merge the two scripts and add logic to tell the disk types apart.



VMWare – Guest cannot browse Internet

Posted by aionman on Apr 11, 2010 in Linux, VMWare

I think I figured it out. It isn’t related to SLlinux, nor to port 443, nor to VMWare and the FC5 port directly, but a combination of the Fedora port and VMware settings. It is related to the MTU setting consistancy between the virtual machine, FC5 and the site in question. For some reason the FC5 was set to 1492 and not 1500 as set under FC3. For this reason some of the HTTPS sites, I assume, require 1500 mtu. All I did was set Fedora’s eth0’s MTU setting to 1500 (ip link set eth0 mtu 1500) and it works fine. Weird. I could be wrong, but I think that was the problem. At least now it works. I got this hint from the guys at Fidelity. They thought it was unrelated, but apparently it is.

Maximum Transmission Unit(MTU), the largest physical packet size, measured in bytes, that a network can transmit. Any messages larger than the MTU are divided into smaller packets before being sent.By optimizing the MTU setting you can gain substantial network performance increases, especially when using dial-up modem connections.

Default MTU Size for Different Network Topology

Network MTU(Bytes)
16 Mbit/Sec Token Ring 17914
4 Mbits/Sec Token Ring 4464
FDDI 4352
Ethernet 1500
IEEE 802.3/802.2 1492
X.25 576

To change the MTU of an interface on GNU/Linux, you just need to use ifconfig command to do so, like this for example

sudo ifconfig eth0 mtu 1492

To change it permanently on Debian, put it in the /etc/network/interfaces file .where almost all network parameters are found. To do this, just add a line mtu to the definition of your interface and save the file.

sudo gedit /etc/network/interfaces


iface eth0 inet static
mtu 1492

Daiup Users

For dialup users: the Maximum Transmission Unit (MTU) value can be changed within the file

Copyright © 2017 IT Support Blog All rights reserved. Theme by Laptop Geek.