VMWare >

Notes on various blues I had with it from back in the day.

I was using PCLinuxOS back then.

Updated in bits and pieces until 2008-09-07.

Table of Contents [hide]

1 Resources
2 Notes
3 PCLinuxOS Installation Notes
4 vmware-config.pl warnings and errors
5 What is the location of the directory …
6 unmatched headers
7 Working with VMware shared folders (/mnt/hgfs)
8 Warning: Unable to start hgfs.
9 Failed to initialize basic X interface for the virtual machine.
10 vmware-config.pl gives: Bridged networking on /dev/vmnet0 [FAILED]
- 10.1 /etc/init.d/vmware restart — virtual ethernet failed
11 Could not open /dev/vmmon: No such file or directory.
- 11.1 /etc/init.d/vmware start — hangs on Bridged networking on /dev/vmnet0
12 promiscuous mode on adapter Ethernet0
13 VMware Workstation unrecoverable error: (vcpu-0) Unexpected signal: 11.
14 Failed to lock the file.

Resources ∞

oclient1 vmware fixes — I didn’t need them for my installation, but others might.

Notes ∞

To remove it, do

rpm -e VMwareWorkstation

PCLinuxOS Installation Notes ∞

www.pclinuxonline.com/wiki/InstallingSoftware — Using VMware
Make sure you’re using the 2.6-2.6.11-oci12 kernel.
Run synaptic and install dhcpcd and kernel-pclos-source-2.6-2.6.11-oci12.mdk

su -
cp /boot/config-2.6.11-oci12.mdk /usr/src/linux/.config
#cp /boot/config-2.6.11-oci12.mdk-i586-up-1GB /usr/src/linux/.config
cd /usr/src/linux
make xconfig

A window will pop up.

Processor type and features > High Memory Support > 4GB

Save and exit

kate /usr/src/linux/Makefile

Find the line that starts with “EXTRAVERSION” and at the end of the line WITHOUT adding any spaces add -vmware to the end of the line so it looks something like this: EXTRAVERSION = -oci12.mdk-vmware Save and exit.

make && make modules && make modules_install && make install

This will build and install your new kernel without interfering with your old one and add a boot menu to lilo for you.

Shut down and reboot your system, selecting the proper kernel, and then install VMware normally.

`vmware-config.pl` warnings and errors ∞

file eggdesktopentries.c failed

In which directory do you want to install the application's icon? 
[/usr/share/pixmaps] 

** (process:14362): CRITICAL **: file eggdesktopentries.c: line 2226 (egg_desktop_entries_add_group): assertion `egg_desktop_entries_lookup_group (entries, group_name) == NULL' failed

ignored, seems to be ok.

Symbol version dump (KERNEL) is missing; modules will have no dependencies and modversions.

What is the location of the directory of C header files that match your running 
kernel? [/lib/modules/2.6.13-oci2.mdk/build/include] 

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.13-oci2.mdk/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.13-oci2.mdk'

  WARNING: Symbol version dump /usr/src/linux-2.6.13-oci2.mdk/Module.symvers
           is missing; modules will have no dependencies and modversions.

Ignoring it seems to be ok, since I am later given “The module loads perfectly in the running kernel.”

Bridged networking on /dev/vmnet0 failed

Do you wish to configure another host-only network? (yes/no) [no] 

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.13-oci2.mdk/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.13-oci2.mdk'

  WARNING: Symbol version dump /usr/src/linux-2.6.13-oci2.mdk/Module.symvers
           is missing; modules will have no dependencies and modversions.

  CC [M]  /root/tmp/vmware-config0/vmnet-only/driver.o
  CC [M]  /root/tmp/vmware-config0/vmnet-only/hub.o
  CC [M]  /root/tmp/vmware-config0/vmnet-only/userif.o
/root/tmp/vmware-config0/vmnet-only/userif.c: In function `VNetUserIfMapUint32Ptr':
/root/tmp/vmware-config0/vmnet-only/userif.c:152: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105)
/root/tmp/vmware-config0/vmnet-only/userif.c:153: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105)
  CC [M]  /root/tmp/vmware-config0/vmnet-only/netif.o
  CC [M]  /root/tmp/vmware-config0/vmnet-only/bridge.o
/root/tmp/vmware-config0/vmnet-only/bridge.c: In function `VNetBridgeUp':
/root/tmp/vmware-config0/vmnet-only/bridge.c:716: warning: passing arg 3 of `sk_alloc' makes pointer from integer without a cast
/root/tmp/vmware-config0/vmnet-only/bridge.c:716: warning: passing arg 4 of `sk_alloc' makes integer from pointer without a cast
  CC [M]  /root/tmp/vmware-config0/vmnet-only/procfs.o
  LD [M]  /root/tmp/vmware-config0/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST
  CC      /root/tmp/vmware-config0/vmnet-only/vmnet.mod.o
  LD [M]  /root/tmp/vmware-config0/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.13-oci2.mdk'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/root/tmp/vmware-config0/vmnet-only'
The module loads perfectly in the running kernel.

Starting VMware services:
   Virtual machine monitor                                      [  OK  ]
   Virtual ethernet                                             [  OK  ]
   Bridged networking on /dev/vmnet0                            [FAILED]
   Host-only networking on /dev/vmnet1 (background)             [  OK  ]
   Host-only networking on /dev/vmnet8 (background)             [  OK  ]
   NAT service on /dev/vmnet8                                   [  OK  ]

The configuration of VMware Workstation 5.0.0 build-13124 for Linux for this 
running kernel completed successfully.

You can now run VMware Workstation by invoking the following command: 
"/usr/bin/vmware".

Enjoy,

--the VMware team

What is the location of the directory … ∞

What is the location of the directory of C header files that match your running 
kernel? [/usr/src/linux/include] 

The kernel defined by this directory of header files does not have the same 
address space size as your running kernel.

What is the location of the directory of C header files that match your running 
kernel? [/usr/src/linux/include] 

The directory of kernel headers (version 2.6.11-oci11.mdk) does not match your 
running kernel (version 2.6.10-oci7).  Even if the module were to compile 
successfully, it would not load into the running kernel.

Solution:

synaptic
- install the matching kernel
mcc
- Lilo settings > specify the new kernel, make it default
reboot
try again

unmatched headers ∞

What is the location of the directory of C header files that match your running 
kernel? [/usr/src/linux/include] /usr/src/linux/include/

The kernel defined by this directory of header files does not have the same 
address space size as your running kernel.

Edit /usr/bin/vmware-config.pl perl script:

Search for

 } elsif ($first =~ /^[89ab]$/) {
    $first = '80000000';

Replace with

 } elsif ($first =~ /^[89a]$/) {
   $first = '80000000';
 } elsif ($first =~ /^[b]$/) {
   $first = 'B0000000';

It looks like my route was the right choice.

Another way to get around the issue would be to use the i686-up-4GB kernel, as it is using highmem, not lowmem. This is what I used for the main vmware pclos install instructions.

ocilent1: … we use one ‘sources’ rpm… . The sources rpm that we have is hacked up to provide the correct headers for all of the kernel builds we provide. This in combination with the kheader service that is started at boot will make sure you get the correct headers for your running kernel.

Working with VMware shared folders (/mnt/hgfs) ∞

was https://www.vmware.com/support/ws4/doc/running_sharefold_ws.html

In Linux, the shared folder should show up in /mnt/hgfs

`Warning: Unable to start hgfs.` ∞

vmware-guestd

Warning: Unable to start hgfs.

vmware-guestd does indeed start, but /mnt/hgfs has not been mounted.

Failed to initialize basic X interface for the virtual machine. ∞

xhost +localhost

xhost +

The first worked for me. The second would also work.

vmware-config.pl gives: Bridged networking on /dev/vmnet0 [FAILED] ∞

When running vmware-config.pl at the end is:

Starting VMware services:
   Virtual machine monitor                                      [  OK  ]
   Virtual ethernet                                             [  OK  ]
   Bridged networking on /dev/vmnet0                            [FAILED]
   Host-only networking on /dev/vmnet1 (background)             [  OK  ]
   Host-only networking on /dev/vmnet8 (background)             [  OK  ]
   NAT service on /dev/vmnet8                                   [  OK  ]

And then /usr/bin/vmware gives:

vmware is installed, but it has not been (correctly) configured
for this system. To (re-)configure it, invoke the following command:
/usr/bin/vmware-config.pl.

Solution:

rm /etc/vmware/not_configured

I can’t reproduce my success.. see the below issues. This problem remains unsolved!

/etc/init.d/vmware restart — virtual ethernet failed ∞

/etc/init.d/vmware restart

Stopping VMware services:
   Virtual machine monitor                                      [  OK  ]
   Bridged networking on /dev/vmnet0                            [  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                                             [FAILED]

Solution:

From an anonymous contributor, and not tested by me yet:

Remove the file “not configure”, and the start up vmware player.

rm /etc/vmware/not_configured
sudo update-rc.d -f vmware-player remove
}}


== the network bridge ... is not running

{{{
The network bridge on device /dev/vmnet0 is not running.  The virtual machine will not be able to communicate with the host or with other machines on your network.
Virtual device Ethernet0 will start disconnected.

Solution:

/etc/init.d/vmware restart

(Reported anonymously. I have not tested this yet)

Could not open /dev/vmmon: No such file or directory. ∞

Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded.

Failed to initialize monitor device.

Unable to change virtual machine power state: Cannot find a valid peer process to connect to.

Failed to reply to the dialog: Pipe: Read failed

Solution:

/etc/init.d/vmware start

“Unable to change virtual machine power state: Cannot find a valid peer process to connect to.” is probably “Virtual machine monitor” failing to load.

/etc/init.d/vmware start — hangs on Bridged networking on /dev/vmnet0 ∞

/etc/init.d/vmware start

Starting VMware services:
   Virtual machine monitor                                      [  OK  ]
   Virtual ethernet                                             [FAILED]
   Bridged networking on /dev/vmnet0

Solution unknown

promiscuous mode on adapter Ethernet0 ∞

The virtual machine's operating system has attempted to enable promiscuous mode on adapter Ethernet0. This is not allowed for security reasons.
Please go to the Web page "http://www.vmware.com/info?id=10" for help enabling promiscuous mode in the virtual machine.

That link is busted, try:

VMware Workstation unrecoverable error: (vcpu-0) Unexpected signal: 11. ∞

VMware Workstation unrecoverable error: (vcpu-0)
Unexpected signal: 11.
A log file is available in "/mnt/public/vmware/fileserver/vmware.log".  Please request support and include the contents of the log file.  
To collect files to submit to VMware support, run vm-support.
We will respond on the basis of your support entitlement.

This happens when running vmware, when its files are mounted inside an EncFS space that is mounted public.

No solution is known.

This also leaves behind .WRITELOCK files, so retries give Failed to lock the file.
Running vmware as root doesn’t solve this.

In the case where the vmdx is located on an NTFS partition being accessed by NTFS-3G, the folks at NTFS-3g offered this solution taken from the ntfs-3g website:

Why does VMware crash during startup?

VMware tries to use shared writable mmap for paging files from version 5.0 but it can’t detect that it’s not yet supported.

Workaround: Set mainMem.useNamedFile=FALSE in the .vmx file. It will disable paging files and VMware will work fine, often with much better performance.

Status: It’s being worked on by kernel and FUSE developers but it will take many months to be production ready. VMware is also working on fixing their virtual machine.

Another Workaround: LC_ALL=C /usr/bin/vmware if you are using any locale other then C.

Failed to lock the file. ∞

Cannot open the disk '<path>/<file>-nnnnnn.vmdk' or one of the snapshot disks it depends on.
Reason: Failed to lock the file.

Delete the .WRITELOCK files in that path.
You might be out of disk space — or out of space that is accessible to that user, since root may still have reserved blocks left.
If you have copied the VMM from a different computer you may need to put it in the same directory: as some file references are absolute not relative. If you do not have the same drive letter then you can always create a mapped drive.
- An anonymous contributor adds: viewing the vmdk file can help to determine the location in which the file needs to be placed. This file cannot be edited unless the replacement path is the same length as the original path.
- Another anonymous contributor adds: In VMware Server (perhaps others), right click on the tab of the VM you wish to open, and select “Revert to Snapshot”.
- Another anonymous contributor adds: Edit the small (1kb) .VMDK file of a similar name, and change the parentFileNameHint value to point to the correct path for the large (>1GB) .VMDK file
- Yet another anonymous contributor adds: Don’t forget to check the directory permissions…
- Another contributor adds: With VMPlayer – Delete folders with .lck in that are in the reported error.

An anonymous contributor adds:

VmWare-server installed on Windows XP as a host, running Linux (e.g. Ubuntu) as a guest, with a FAT32 partition, with all VM files on it…

Problem: The path variables for the virtual disks still have Windows syntax after using under Windows and now trying to open it under Ubuntu:
Solution: Edit the lines in the vmx files according to the correct syntax (mount point, slash for backslash, etc)

spiralofhope

VMware troubleshooting

Resources ∞

Notes ∞

PCLinuxOS Installation Notes ∞

`vmware-config.pl` warnings and errors ∞

What is the location of the directory … ∞

unmatched headers ∞

Working with VMware shared folders (/mnt/hgfs) ∞

`Warning: Unable to start hgfs.` ∞

Failed to initialize basic X interface for the virtual machine. ∞

vmware-config.pl gives: Bridged networking on /dev/vmnet0 [FAILED] ∞

/etc/init.d/vmware restart — virtual ethernet failed ∞

Could not open /dev/vmmon: No such file or directory. ∞

/etc/init.d/vmware start — hangs on Bridged networking on /dev/vmnet0 ∞

promiscuous mode on adapter Ethernet0 ∞

VMware Workstation unrecoverable error: (vcpu-0) Unexpected signal: 11. ∞

Failed to lock the file. ∞

Leave a Reply Cancel reply

Search

VMware troubleshooting

Resources ∞

Notes ∞

PCLinuxOS Installation Notes ∞

vmware-config.pl warnings and errors ∞

What is the location of the directory … ∞

unmatched headers ∞

Working with VMware shared folders (/mnt/hgfs) ∞

Warning: Unable to start hgfs. ∞

Failed to initialize basic X interface for the virtual machine. ∞

vmware-config.pl gives: Bridged networking on /dev/vmnet0 [FAILED] ∞

/etc/init.d/vmware restart — virtual ethernet failed ∞

Could not open /dev/vmmon: No such file or directory. ∞

/etc/init.d/vmware start — hangs on Bridged networking on /dev/vmnet0 ∞

promiscuous mode on adapter Ethernet0 ∞

VMware Workstation unrecoverable error: (vcpu-0) Unexpected signal: 11. ∞

Failed to lock the file. ∞

Leave a Reply Cancel reply

Search

`vmware-config.pl` warnings and errors ∞

`Warning: Unable to start hgfs.` ∞