VMware Communities : Document List - VMware Workstation

openSUSE 11.1 WS 7 won't start a VM

Sat, 21 Nov 2009 00:02:30 GMT

Trying to eval

When I choose "power on vm" it get "Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded. "

What's this? How to fix?

Where should virus checker go?

Sun, 13 Sep 2009 23:18:24 GMT

Using Workstation 6.5 for Windows. I see no tips on where to install the virus checker. On the host OS? On each Virtual Machine that is created? Does anyone have advice on this?

Fix Virtual Network Cards for Windows 7/Windows Server 2008 R2 Host

Fri, 04 Sep 2009 21:15:32 GMT

After installing Workstation 6.5.3 two network cards appear in the network adapter list of the host OS.

The way they are installed has two drawbacks:

The virtual network cards are always taken into consideration when Windows tries to enumerate network adapters. Best to be seen at the system tray where there's always a yellow warning icon displayed at the Network Connection Status icon.
.
There is always the Public profile of the Windows Firewall applied to these virtual cards, potentially inhibiting network traffic between the host and the guest, although for the conversation between host and guest there's never a firewall protection necessary at all.

I've found a very intriguing remedy for the problem, correcting the VMware virtual network NICs' properties in the registry to tag them as internally used end-points. This will keep them from being enumerated for external network traffic and from being blocked by the Firewall.
.

Here's the corresponding hyperlink, including explanation: http://www.nivot.org/2008/09/05/VMWareVMNETAdaptersTriggeringPublicProfileForWindowsFirewall.aspx

How To: PhysicalDisks on Vista and Server 2008 (Windows7)

Mon, 03 Aug 2009 19:40:46 GMT

Because of nt6.x and nt7.x new security mechanisms, it is not possible to write directly to fs sectors on mounted volumes. In turn, it is not possible to use physical disks in virtual machines under vmware on Vista, Server 2008 and Windows7. It appears that several other applications also struggle with the same thing on those newer Windows platforms. This issue only applies to filesystems supported by MS. Relevant link on msdn; http://msdn.microsoft.com/en-us/library/cc835968.aspx

To cut short on this, it is still possible to use that advanced feature in vm's, we just need to make a workaround and trick the OS a little. The solution was actually triggered and inspired by this thread; http://communities.vmware.com/thread/119210?tstart=45 and the fact that there is no tool (at least known to me) that can easily do this, for people unfamiliar with the structure of the mbr. Therefore I made a little tool that can give rawdisk access.

I can verify that it works on Vista and Server 2008. I have not tested on Windows7, but assume the workaround required is still the same.

To use the whole physical disk under Server 2008 and Windows7, the most easy way is to put the disk offline. To do that start diskpart.exe and select your disk, then enter "offline disk", then "attribute disk clear readonly", then "rescan". That's how simple (and safe) it can be!

But, that option is not available on Vista's version of diskpart (and it is also not possible to use other versions on vista either), and so a workaround is required. Basically just erase the disk signature (55AA) in the mbr, then let diskpart rescan the disks, so that it now believes the disk without the signature is not partitioned. Now write back the signature onto disk's mbr and vmware is ready to boot from the physical disk. It is now in perfect shape although vista believes it is not partitioned. Very important to NOT let diskpart now rescan the disks as that will destroy the fun.

Now the more tricky bit of this is when using individual physical partitions. The solution is to temporarily erase the entry for the specific partition ID in the mbr, then let diskpart rescan the disks. Now the OS will think the partition does not exist, and thus has no need to lock it. Then write back the partition ID to the mbr and vmware is ready to boot from it. It is not possible to put individual partitions offline, so this trick must be used on Vista, Server 2008 and Windows7. However, with the offline trick, you can still use individual partitions with vmware. So how does it actually work? The partition table in the mbr starts at decimal offset 448 and ends at offset 511 (including the signature which is the last 2 bytes). Each primary partition entry is 16 bytes and there are 4 primary partitions. The first partition is from offset 448 - 463, the second is from offset 464 - 479, the third is from offset 480 - 497, anf the fourth is from offset 494 - 509. The disk signature is from offset 510 - 511. So when erasing the partition ID, we replace the hex values at decimal offsets 450, 466, 482 and 498 respectively with 00's. This tool utilizes 2 small apps, dsfi.exe and dsfo.exe, that comes from the dsfok package. It only reads and writes blocks of data from the first sector in \\.\PhysicalDriveN. Note that setting partition ID to some other bogus value, like linux or unused, will not work. At least on Server 2008. There is now implemented backup functionality in the app. The mbr of the disk in question, will be backed up to a uniqe name containing computer name, the 4 byte hex disk signature and a timestamp. It will be named something like MBR-Dell-0x7139661B-20090809150610.bak. The patched partition ID's are also backed up inside the mbr itself. The backup offsets are 434 for partition1, 435 for partition2, 444 for partition3, and 445 for partition4. These offsets are very rarely used and is almost always 00. If something was mistakenly overwritten at those offsets, the original ones will be in the mbr backup anyway. This was only implemented to calm the paranoid users. The app is still just modifying the first sector, and does not touch the bootsector at all.

Here is a screenshot from VistaPE, where VMware Workstation is installed; http://i402.photobucket.com/albums/pp106/jokke49/vista_raw_partition_vmware.jpg
The secondary partition on a flashstick has booted MOA, whereas the virtual machine itself is located on the first partition on the same flashstick. Notice the diskmanager inside and outside of the vm.

That is basically what the tool does. It has an extremely simple GUI, just make sure you know what disk you want to add to a virtual machine.

The OS may under certain circumstances offer to format "non-partitioned" partitions, or initialize "fresh raw disks". It is EXTREMELY IMPORTANT to abort ANY such offers by the OS, as it is just an illusion to the OS while the disks are still in perfect shape.

When you don't need this tool:
If you configure to use a physical disk and take a snapshot of it with vmrun.exe prior to starting the virtual machine.

Safety:
Close all open files and programs, and preferably unmount (remove drive letter) all volumes that you plan to prepare.

Limitations of this tool:

Not for 64-bit.
Not for logical partitions (if using individual partitions)
Will not work if you have any security mechanism that prevents writing to the mbr. Alternatively disable it.
Handles max 21 local disks for gui version, and max 100 local disks for cmd version. More can easily be added.
For partitions, currently only 1 primary partition will be prepared, but there is no problem in preparing for instance 2-3 individual primary partitions. Just tweak the extracted batches.
I am sure there is plenty more..

Extra:
To use multipartitioned flashsticks, install the Hitachi microfilter driver. Instructions are here; http://www.boot-land.net/forums/index.php?showtopic=7512&hl=hitachi The screenshot above is from such. It works on Vista and Server 2008, but don't know about Windows7.

Last words:
I take no responsibility for your system. To be on the safe side though, backup the first sector of all your disks and put in a safe place. It has been tested thoroughly, and it works as expected. Try it in a virtual machine first to se how it works. Remember this is highly experimental stuff, that may cause harm to your first sector if the tool is interrupted while reading and writing the mbr. The AutoIt source is included in the download (which will reveal my low level of programming skills). Feedbacks are welcome.

The command line version takes three parameters:

First parameter is the mode. There are three modes; 1, 2 and 3. 1 is the 55AA trick. 2 is the offline trick. 3 is the individual partition ID (00) trick.

Second parameter is the disk number. It can be in between 0-99.

Third parameter is the partition number. It can be in between 1-4.

Obviously mode 1 and 2 only takes disk number as parameter, but some bogus third parameter has to be supplied for it to work. The bogus parameter in the samples are "a". If parameters are supplied incorrectly the application will not execute anything.

Sample command line:

The 55AA trick on disk number 2;
"rawdisk_cmd.exe 1 2 a"

The 55AA trick on disk number 5;
"rawdisk_cmd.exe 1 5 a"

The offline trick on disk number 0;
"rawdisk_cmd.exe 2 0 a"

The offline trick on disk number 7;
"rawdisk_cmd.exe 2 7 a"

The partition ID trick on disk number 1 and partition number 1;
"rawdisk_cmd.exe 3 1 1"

The partition ID trick on disk number 4 and partition number 3;
"rawdisk_cmd.exe 3 4 3"

Joakim Schicht

Network and internet fix for windows 7 Guest in vmware workstation

Tue, 21 Jul 2009 03:28:59 GMT

VMWare Workstation 6.5.2 and Vista 64-Bit Host

Tue, 23 Jun 2009 18:03:34 GMT

After installing VMWare Workstation, in attempt to create a VM, I try to start it and get this message:

"VMware Workstation cannot connect to the virtual machine. Make sure you have
rights to run the program and to access all directories it uses and
rights to access all directories for temporary files."

I tried "run as administrator", and unhiding the Vista admin account and running it under that context, same message. Thank you for your time, and for any assistance you may provide.

Information Gathering for VMware Workstation on Windows

Mon, 15 Jun 2009 06:03:19 GMT

Document Purpose

This document contains step-by-step instructions for common information-gathering tasks. If you have been directed to this document, then it is likely that someone needs information from you in order to help with a problem. Each section of this document will detail how to locate and collect support data for VMware Workstation and VMware Player running on a Microsoft Windows host system.

Disclaimer: This is a personal document and is not official or endorsed by VMware. Feedback and suggestions are welcome. Feel free to extend.

Note If you are asked to provide multiple pieces of information, you can zip them all together rather than doing each one separately.

Locate a virtual machine

Open the virtual machine's Settings dialog.
- VMware Workstation: Open the virtual machine and select its tab. Then select VM > Settings...
- VMware Player: Open the virtual machine and select it in the Library. Then click the "Edit Virtual Machine Settings" link.
In the Virtual Machine Settings dialog, select the Options tab. Then select the General page in the list.
The edit box in the "Working directory" section contains the location of the virtual machine. Copy that address and paste it into the address bar of an Explorer window.

Note: A virtual machine is not the same thing as the VMware application that can open virtual machines (such as VMware Workstation and VMware Player). This is similar to the relationship between .doc files and Microsoft Word.

Find and Edit a .vmx config file

Open the virtual machine's working directory (see the previous section, "Locate a virtual machine").
The configuration file has a .vmx extension (such as "Windows XP.vmx").
To edit this file manually...
1. Make sure that the virtual machine, as well as VMware Workstation and VMware Player, are not running.
2. Right click the file and select "Open With" (by default, configuration files are opened by the installed VMware application). Choose any text editor (such as Notepad or Wordpad) to open the file.
3. Edit the file (see the Notes below), then save and close the file.

Note: There must only be a single value per key in the configuration file. When changing the value of any key in the configuration, make sure to alter an existing entry before adding a new key.
Note: Editing .vmx configuration files is officially unsupported and doing this incorrectly can break a virtual machine. Unless you know what you are doing or have been instructed to do something, it is probably best to leave this file alone.

Collect vmware.log files (aka the "VMX log")

Open the virtual machine's working directory (see the previous section, "Locate a virtual machine").
There are up to four log files: "vmware.log", "vmware-0.log", "vmware-1.log", and "vmware-2.log". The file "vmware.log" corresponds to the most recent execution of the virtual machine. If you are not sure when your virtual machine encountered the problem, it is perfectly fine to submit all of the available logs.

Collect VMware Workstation or VMware Player log files (aka the "UI log")

To locate the log file for a currently running instance of VMware Workstation, select Help > About. Copy the address specified next to "UI log" and paste it into the address bar of an Explorer window.
For VMware Workstation or VMware Player the log files can also be located by entering %TEMP% in the address bar of an Explorer window and opening the folder "vmware-<username>" (where <username> is your Microsoft Windows account name).
The log files are saved in the form "vmware-<username>-####.log" for each instance of the VMware application. To find the most recent log file, sort by "Date Modified" in the Explorer window. If you are not sure which log file to submit, it is perfectly fine to include all of the available logs.

Find the preferences files

The preferences file for a single user

Note: This is the file that is usually needed when diagnosing a problem with VMware Workstation or VMware Player.

Open an Explorer window and enter %USERPROFILE% in the address bar.
Navigate to %USERPROFILE%\Application Data\VMware.
The preferences file is called "preferences.ini".

The "all users" global preferences files

Open an Explorer window and enter %ALLUSERSPROFILE% in the address bar.
Navigate to %ALLUSERSPROFILE%\Application Data\VMware.
Find "config.ini" and "settings.ini" in the "VMware Workstation" or "VMware Player" directories.

Generate a file listing of a virtual machine's working directory

Open the virtual machine's working directory (see the previous section, "Locate a virtual machine").
Open a command prompt to this location.
Enter in the command prompt (without quotes) "dir /A > filelist.txt". This will produce a file that details the contents of the virtual machine's working directory.
Refresh the opened Explorer window, locate the new "filelist.txt" and include it in your support data attachment.

Collect VMware Tools installation logs

For virtual machines with a Windows guest operating system installed

The Tools installation logs are located inside of the guest operating system.
Open an Explorer window (in the Windows VM) and enter %TEMP% in the address bar.
"vmmsi.log" and "vminst.log" are the installation logs for VMware Tools.

Collect VMware Tools logs

For virtual machines with a Windows guest operating system installed

In the Windows guest operating system, locate and open the following file:
- In Windows Vista - C:\Users\All Users\VMware\VMware Tools\tools.conf
- In Windows XP - C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools\tools.conf
- In Windows XP (if not at the above location) - C:\Program Files\VMware\VMware Tools\tools.conf
Edit the configuration file by adding the following...
```
log = "TRUE"
log.file = "<PATHNAME>"
```
Make sure to replace <PATHNAME> with the desire log file output, such as "C:\vmtools.log". Whatever location you pick needs to have full permission for all accounts.
Reboot the Windows guest operating system.
Reproduce the problem and then collect the log files from the location specified.
You will end up with two files - one with the name you specified, and one with a number appended (e.g. C:\vmtools.log.289). The number corresponds to the process ID of vmwareuser.exe.
You probably want to undo the edits afterward so you don't keep generating log files.

Collect VMware Workstation installation logs

Open an Explorer window and enter %TEMP% in the address bar.
The installer log files are saved in the form "vmsetup.####.log" for each instance of the product installer. To find the most recent log file, sort by "Date Modified" in the Explorer window. If you are not sure which log file to submit, it is perfectly fine to include all of the available logs.

Collect Graphics support data

For virtual machines with a Windows guest operating system installed

In the Windows guest operating system, run the DirectX Diagnostic Tool
- In Windows Vista - click the Windows icon and enter dxdiag in the Search box.
- In Windows XP - select Start > Run and enter dxdiag.
Select "Save All Information..." and specify the location to save the "DxDiag" text document.

VMware Workstation 6.5.2 : Host Window XP:Guest Ubuntu:VMware Tools install issue

Fri, 01 May 2009 14:43:33 GMT

ubuntu 8.10 : re-install VMware tools (sudo ./vmware-install.pl) to soloved vmware-config-tools.pl to build some module failed problems.
ubuntu 9.04: vmwar-config-tools.pl to build vmhgfs module failed in page.c.

http://bbs.archlinux.org/viewtopic.p...485477#p485477
Its message are here:
open-vm-tools-2009.01.21-142982.patch :
Code:
diff -aur
open-vm-tools-2009.01.21-142982.pristine/modules/linux/vmhgfs/page.c
open-vm-tools-2009.01.21-142982.new/modules/linux/vmhgfs/page.c
--- open-vm-tools-2009.01.21-142982.pristine/modules/linux/vmhgfs/page.c 2009-01-21 00:03:01.000000000 -0800
+ open-vm-tools-2009.01.21-142982.new/modules/linux/vmhgfs/page.c 2009-01-22 06:51:20.000000000 -0800
@@ -864,7 +864,9 @@
unsigned pageTo = pos + len;
struct page *page;
- page = __grab_cache_page(mapping, index);
+// change this, because of problems with 2.6.28 linux kernel
+// page = __grab_cache_page(mapping, index);
+ page = grab_cache_page_write_begin(mapping, index, flags);
if (page == NULL) {
return -ENOMEM;
}

Manual tweaking of vmware services on Windows

Thu, 19 Mar 2009 22:24:59 GMT

This is a simple GUI, a frontend for vnetlib.exe, that will let you tweak all vmware services that vnetlib is able to interact with.

It is currently only for 32-bit XP, 2003, Vista and 2008, with support for Player, Workstation and Server.

I am not sure if this will be any useful, but it will nevertheless aid in repairing broken installs/services. It will let you install, uninstall, start and stop the services.

I know most people would reinstall using the installer, but there is one major drawback with that. And that is the TIME it takes. This tool does it in seconds.

Documentation can be found at:http://communities.vmware.com/docs/DOC-9571 and http://sanbarrow.com/network/cmdguide2workstation.html

Joakim

Changing the MAC address of vmnet0 - vmnet9 (a new tool)

Mon, 09 Mar 2009 19:35:35 GMT

This is a package with tools to make custom MAC addresses of vmnet(x)'s.

The package contains 3 tools;

vmnetx_rand.exe
vmnetx_spoof.exe
vmnetx_spoof_debug.exe

Supported OS's; XP, Server 2003, Vista and Server 2008.

Introduction

These tools will let you manipulate the MAC address of the virtual network adapters installed with VMware Player/

Server and Workstation. There are 10 nics named vmnet0 to vmnet9. And yes, this is Windows only. These programs are

dependant on vnetlib.exe that must exist in the same diorectory. The drivers for vmnetadapters will let you spoof

the MAC address to anything as long as the first octet is an even number. I don't know the reason for this and it

certainly makes no sense for me, as there doesn't seem to be any logic reason behind it. If an odd number is

supplied as the first octet, then the driver will refuse to update with it, and consequently revert back to the

default hardcoded mAC address. All tools will update new mac address automatically without further actions needed.

vmnetx_rand

This tool is commandline and takes 1 parameter which is the vmnet(X). It will generate a random MAC address for you

that is within the prefixed 00:50:56, that belongs to VMware. That means it will pick a random address out of a

16.777.215 possible addresses, and automatically update the vmnet(X) with the new one. There are a few safety checks

buildt-in, that will abort execution if either no parameters are passed on the line or the name of the nic is

incorrectly supplied.

Example: "vmnetx_rand vmnet5"

vmnetx_spoof

This tool is commandline and takes 2 parameters which is the vmnet(X) and the wanted MAC address. It will

automatically update the nic with the address that is specified. There are also here some checks that evaluate the

parameters and will abort execution if the checks fail. The first parameter is the vmnet(X). The second parameter is

the wanted MAC address specified in the format 1233c5ee094a. Beware of the even number in first octet bug. Both

these programs take parameters on the commandline and can be scripted, which is an advantage.

Example: "vmnetx_spoof vmnet2 22aa33bb44cc"

vmnetx_spoof_debug

This tools is the same tool as vmnetx_spoof, but will give you a message box with information about what went wrong

for each check that failed. This one is not suitable for scripting, but merely an alternative for those that want to

see how it works.

Note 1

In Vista and Server 2008, I am not sure if scripting works as expected, since the tool requires to be run elevated.

Note 2

Spoofing MAC addresses may interfere with an otherwise working NAT configuration. There is a vnetlib command that

will let you accept any MAC addresses from the virtial machines (vnetlib -- set nat vmnet(X) allowanyoui 1). Strange

as it is, the dhcp service in the host also will not accept MAC's starting with an odd number (at least from the AMD

PCNET adapter driver).

Joakim Schicht

BTW, this is the same package uploaded yesterday, that was incorrectly deleted by this forum software, when handling

version numbers of drafts on the document.

VMWare Player and Workstation crash on OpenSuse11.1

Wed, 25 Feb 2009 21:35:29 GMT

If I is start VMWare Workstation 6.5.1 126130 it will crash with a memory access error.
Is there any way to run VMWare on OpenSuse 11.1?
Will there be a fix for this issue?

Logging to /tmp/vmware-elm/setup-1036.log

(vmware-modconfig:1036): Gtk-WARNING **: Im Modulpfad »qtcurve« konnte keine Themen-Engine gefunden werden,
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:72: error: unexpected identifier `colorize_scrollbar', expected character `}'
modinfo: could not find module vmmon
modinfo: could not find module vmnet
filename: /lib/modules/2.6.27.7-9-default/updates/vmblock.ko
version: 1.1.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: 0D03AFB7AE1D9AEFF2A8629
depends: built-in,built-in,built-in,built-in,built-in,built-in
vermagic: 2.6.27.7-9-default SMP mod_unload modversions
parm: root:The directory the file system redirects to. (charp)
filename: /lib/modules/2.6.27.7-9-default/updates/vmci.ko
license: GPL v2
version: 1.0.14.0
description: VMware Virtual Machine Communication Interface
author: VMware, Inc.
srcversion: DB1E47C104F199AD6C9AE06
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends: built-in,built-in,built-in,built-in,built-in,built-in,built-in
vermagic: 2.6.27.7-9-default SMP mod_unload modversions
filename: /lib/modules/2.6.27.7-9-default/updates/vsock.ko
license: GPL v2
version: 1.0.0.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: BFC329214E804B7D8653C2A
depends: built-in,built-in,built-in,built-in,built-in,built-in,built-in
vermagic: 2.6.27.7-9-default SMP mod_unload modversions
modinfo: could not find module vmmon
modinfo: could not find module vmnet
filename: /lib/modules/2.6.27.7-9-default/updates/vmblock.ko
version: 1.1.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: 0D03AFB7AE1D9AEFF2A8629
depends: built-in,built-in,built-in,built-in,built-in,built-in
vermagic: 2.6.27.7-9-default SMP mod_unload modversions
parm: root:The directory the file system redirects to. (charp)
filename: /lib/modules/2.6.27.7-9-default/updates/vmci.ko
license: GPL v2
version: 1.0.14.0
description: VMware Virtual Machine Communication Interface
author: VMware, Inc.
srcversion: DB1E47C104F199AD6C9AE06
alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
depends: built-in,built-in,built-in,built-in,built-in,built-in,built-in
vermagic: 2.6.27.7-9-default SMP mod_unload modversions
filename: /lib/modules/2.6.27.7-9-default/updates/vsock.ko
license: GPL v2
version: 1.0.0.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: BFC329214E804B7D8653C2A
depends: built-in,built-in,built-in,built-in,built-in,built-in,built-in
vermagic: 2.6.27.7-9-default SMP mod_unload modversions
/usr/bin/vmplayer: line 31: 1036 Speicherzugriffsfehler "$BINDIR"/vmware-modconfig --appname="VMware Player" --icon="vmware-player"

Vnetlib - Documenting the command line

Tue, 24 Feb 2009 05:34:18 GMT

I have been working on a utility that will let you attach VMware Workstation 6.5.1 to ANY running windows based livecd/Preinstallation Environment (xp/2003/vista/2008) and run VM's on top of it.
One of the hurdles has been to correctly set up and register all the services. At first crv_ctl was used in combination with registry patches, but that is an ugly way of setting it up.
While playing with this little powerful tool it became evident that it will aid alot in repairing broken installations as well. That is because you can install/uninstall start/stop all these services in different ways with this utility.

Forgive me if this is already documented, at least I didn't find it, but will share my findings nevertheless.

My research was all collected and conducted from 32bit xp sp3 based machines, and is mainly based on common sense, logic reasoning and a little bit of pe analysis.

Although common sense was helpful, it also kind of confused me a little. Se the note in the end about Bug or Feature.

Following a string dump of the exe the first string that caught my attention was:
"vnetlib: this utility is not intended to be run as a standalone application".
But obviously it's possible to use it as such anyway.

Some configuration commands that modify settings seems already kind of documented by Ulli at www.sanbarrow.com. I will not cover those here.

Before we start I need to mention that you need to have the binaries located at a path according to this registry entry:
HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware Workstation
"InstallPath"="Path_to_cat/sys/inf/dll/exe"

Namely 4 services are dependant on this entry: adapter, authd, bridge and vmkbd.

First a list of all the services that vnetlib is able to interact with:
userif - VMware Network Application Interface (vmnetuserif)
dhcp - hcp Service for virtual networks (vmnetdhcp)
nat - Network address translation for virtual networks (vmware nat service)
bridge - VMware Bridge Protocol (vmnetbridge)
vmkbd - VMware Keyboard Driver (vmkbd)
vmx86 - VMware Virtualization Driver (vmx86)
vmci - VMware vmci Driver (vmci)
hcmon - VMware USB Driver (hcmon)
usb - VMware USB Client Driver (vmusb) -- (appears broken, use rundll32.exe to install)
vmmem - VMware Memory Driver (vmmemctl)
vmcpu - VMware CPU Driver (vmdesched-driver)
authd - VMware Authorization Service (vmauthdservice)
serverd - VMware Registration Service (vmserverdwin32)
vmparport - VMware Paralell Port Driver (vmparport)
adapter - VMware Virtual Ethernet Adapter Driver (vmnetadapter)

The first word is the service name used by vnetlib. The last word in parentheses is the windows service name. The windows description is in the middle.

Some of the commandline switches handling the services are:
"vnetlib -- install userif"
"vnetlib -- uninstall userif"
"vnetlib -- reinstall adapters"
"vnetlib -- start userif"
"vnetlib -- stop userif"

The "-- install" will take these parameters:
userif
dhcp
nat
bridge
vmkbd
vmx86
vmci
hcmon
usb (not working in install mode)
vmmem
vmcpu
authd
serverd
vmparport

Additionally there are some special ones for -- install:

devices - (will install 5 services; adapter, bridge, dhcp, nat, userif)
host - (will install 3 services; hcmon, vmparport, vmx86) -- may require to be executed from within the "vmware workstation" directory of your installation -- really not sure.

The "-- uninstall" will take these parameters:
userif
dhcp
nat
bridge
vmkbd (some problems uninstalling this)
vmx86
vmci
hcmon
usb
vmmem
vmcpu
authd
serverd
vmparport

Additionally there are some special ones for -- uninstall:

legacy - (will uninstall 3 services; bridge, dhcp, nat)
all - (will uninstall 4 services; bridge, dhcp, nat, userif)
host - (will uninstall 3 services; hcmon, vmparport, vmx86)
adapter/aggressive - (will uninstall 5 services; adapter, bridge, dhcp, nat, userif)
netDevices - (have not got this one working - supposedly a parameter)

Starting & Stopping Services:
"vnetlib -- start" and "vnetlib -- stop" will take these parameters:
dhcp
nat
userif
bridge
vmx86
vmci
vmmem
vmcpu
authd
serverd
hcmon
vmparport
vmkbd

Reinstalling services:

"vnetlib -- reinstall" will take these parameters:
all
host
network
drivers/adapters

Updating the settings:

"vnetlib -- update" will take these parameters:
dhcp
nat
adapter
all

Configuration of adapters:

"vnetlib -- add adapter vmnet5"
"vnetlib -- set adapter vmnet5 addr 11.11.11.1"
"vnetlib -- set vnet vmnet5 mask 255.255.255.0"
"vnetlib -- update adapter vmnet5"

*Configuration of services (NAT & DHCP*):

vnetlib -- set dhcp vmnet6 addipmac 33.33.33.33 00:50:56:C0:99:99
; quoted in seconds, 3600 = 1 hour, 86400 = 1 day, 432000 = 5 days
vnetlib -- set dhcp vmnet6 leasemaximum 7200
vnetlib -- set dhcp vmnet6 leasedefault 1800
vnetlib -- set dhcp vmnet6 leaseend 0.0.0.0
vnetlib -- set dhcp vmnet6 leasebegin 0.0.0.0

vnetlib -- set nat vmnet5 activeftp 1
vnetlib -- set nat vmnet5 forward tcp 40022 192.168.2.2 22
vnetlib -- set nat vmnet5 noforward tcp 40022 192.168.2.2 22
vnetlib -- set nat vmnet5 forward udp 406001 192.168.100.200 6001
vnetlib -- set nat vmnet5 configport 44080
vnetlib -- set nat vmnet5 privport tcp 60
vnetlib -- set nat vmnet5 unprivport tcp 60
vnetlib -- set nat vmnet5 privport udp 70
vnetlib -- set nat vmnet5 autopriv tcp
vnetlib -- set nat vmnet5 autopriv udp
vnetlib -- set nat vmnet5 noautopriv udp
vnetlib -- set nat vmnet5 allowanyoui 1
vnetlib -- set nat vmnet5 dnsautodetect 1
vnetlib -- set nat vmnet5 externalipaddr 193.231.70.70
vnetlib -- set nat vmnet5 internalipaddr 10.10.10.1 (GatewayIPAddress)
vnetlib -- set nat vmnet5 dnspolicy order (order/rotate/burst)
vnetlib -- set nat vmnet5 dnsretries 3
vnetlib -- set nat vmnet5 dnstimeout 2
vnetlib -- set nat vmnet5 dnsserver1 100.100.100.100
vnetlib -- set nat vmnet5 dnsserver2 200.200.200.200
vnetlib -- set nat vmnet5 dnsserver3 222.222.222.222
vnetlib -- set nat vmnet5 nbnstimeout 3
vnetlib -- set nat vmnet5 nbdstimeout 3
vnetlib -- set nat vmnet5 nbnsretries 2
vnetlib -- set nat vmnet5 udptimeout 3

Some nat commands must be deleted manually (adjust vmnet*);

"reg delete "HKLM\SOFTWARE\VMware, Inc.\VMnetLib\VMnetConfig\vmnet3\NAT" /v ActiveFTP /f"
"reg delete "HKLM\SOFTWARE\VMware, Inc.\VMnetLib\VMnetConfig\vmnet3\NAT" /v AllowAnyOUI /f"
"reg delete "HKLM\SOFTWARE\VMware, Inc.\VMnetLib\VMnetConfig\vmnet3\NAT" /v ConfigPort /f"
"reg delete "HKLM\SOFTWARE\VMware, Inc.\VMnetLib\VMnetConfig\vmnet3\NAT" /v ExternalIP /f" (internalipaddr)
"reg delete "HKLM\SOFTWARE\VMware, Inc.\VMnetLib\VMnetConfig\vmnet3\NAT" /v GatewayIPAddress /f" (externalipaddr)

Notes on some of the services:

vmusb:
Installing with vnetlib.exe seems broken. Actually vnetlib will never throw you any error messages of any kind telling you if something did not go as planned, but for vmusb even the log tells you it went ok.

vminst.log:
inst : 02/21/09 17:29:20 I1:VNL_InstallUSB: installing USB inf: 'C:\Programfiler\VMware\VMware Workstation\vmusb.inf'
inst : 02/21/09 17:29:22 I1:ParseCommand: operation: successful

But no vmusb service installed in registry and no driver files copied either. Workaround is using rundll32.exe.

Executing this will NOT work;
"rundll32 setupapi,InstallHinfSection _Install1.NT 128 "drive\full path\vmusb.inf""

But this WILL WORK;
"rundll32 setupapi,InstallHinfSection _Install1.NT 128 drive\full path\vmusb.inf"

(Important to NOT have any quotation marks around the last parameter, even though spaces are in the path.)

Note:
I see usb is not listed as a service that vnetlib will take as parameter for the -- start switch, so it might not be possible to get it working through vnetlib.exe.
"vnetlib -- uninstall usb" is working though.
I believe the activation of the service is handled internally inside the player and workstation binary (guessing).

vmnetadapter:
"vnetlib -- install adapter" will NOT work and cannot be installed separately as all the other services can be. Instead vmnetadapter must be installed standalone with rundll32.exe.
Installing VMnetAdapter1:
"rundll32 setupapi,InstallHinfSection VMnetAdapter1.Install 128 C:\path\netadapter.inf"
Important to NOT have spaces and NOT have any quotation marks around the last parameter.

Important
Uninstalling adapter or driver and a subsequent install of driver/devices will require a reboot.
It is then necessary to issue a "vnetlib -- update all" to get vmnetadapter visible again after the reboot.

Adding a virtual network adapter:
"vnetlib -- add adapter vmnet1" (vmnet2/vmnet3/vmnet4/vmnet5/vmnet6/vmnet7/vmnet8/vmnet9/vmnet0)

Removing a virtual network adapter:
"vnetlib -- remove adapter vmnet1" (vmnet2/vmnet3/vmnet4/vmnet5/vmnet6/vmnet7/vmnet8/vmnet9/vmnet0)

Disable a virtual network adapter:
"vnetlib -- disable adapter vmnet1" (vmnet2/vmnet3/vmnet4/vmnet5/vmnet6/vmnet7/vmnet8/vmnet9/vmnet0)

Enable a virtual network adapter:
"vnetlib -- enable adapter vmnet1" (vmnet2/vmnet3/vmnet4/vmnet5/vmnet6/vmnet7/vmnet8/vmnet9/vmnet0)

Update a virtual network adapter:
"vnetlib -- update adapter vmnet1" (vmnet2/vmnet3/vmnet4/vmnet5/vmnet6/vmnet7/vmnet8/vmnet9/vmnet0)

vmnetbridge:
"vnetlib -- install bridge" == "vnetlib -- bridge install"
A second way to install bridging is with rundll32:
"rundll32 setupapi,InstallHinfSection VMnetBridge.Install 128 c:\path\netbridge.inf"

Some notes on already documented configuration commands:
"vnetlib -- set vnet vmnet3 addr 10.10.10.10" == "vnetlib -- set adapter vmnet3 addr 10.10.10.10"

vnetlib.dll related findings:

"rundll32 vnetlib.dll,VNL_SetSuppressDriverPrompt" will write this to registry:

HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMnetLib\VMnetConfig
"SuppressPrompts"=dword:00000000

Setting this value to 1 will effectively suppress the warnings for unsigned drivers (emulate a click on "Continue Anyway"), that will be thrown at you if playing with modified inf files.

"rundll32 vnetlib.dll,VNL_RemoveAllNetworkDevices" will be the same as "vnetlib -- remove adapter all"

"rundll32 vnetlib.dll,VNL_StopDHCP" will be the same as "vnetlib -- stop dhcp"
"rundll32 vnetlib.dll,VNL_StartDHCP" will be the same as "vnetlib -- start dhcp"
and the same goes for nat.

Complete list:
VNL_StartBridge
VNL_StartDHCP
VNL_StartHcmon
VNL_StartNAT
VNL_StartUserIf
VNL_StartVMCI
VNL_StartVMX86
VNL_StartVmkbd
VNL_StartVmparport
VNL_StopBridge
VNL_StopDHCP
VNL_StopHcmon
VNL_StopNAT
VNL_StopUserIf
VNL_StopVMCI
VNL_StopVMX86
VNL_StopVmkbd
VNL_StopVmparport

"rundll32 vnetlib.dll,VNL_UninstallDHCP" = "vnetlib -- uninstall dhcp)
"rundll32 vnetlib.dll,VNL_UninstallNAT" = "vnetlib -- uninstall nat)

Note WMI:
For full support for all the commands you must have wmi running on the system. Vnetlib.exe will still work without it, but interacting with "bridge" does not work then. That can still be solved if vmnetbridge is installed with rundll32.exe as described above.

*Bug or Feature*?
There is something wrong in the way vnetlib.exe checks the parameters supplied. For the install/uninstall switches it appears that it will accept a whole lot more than suggested above. In fact it will only do some limited checks to see if the parameter is close enough to the original/intended. This will vary depending on how many parameters have similar looking names. In some cases it will only check for the first letter and in some cases also the total number of characters for that parameter.

Example:
"dhcp" will be accepted as "d" "dh" "de"
"all" will be accepted as "ali" and "-- install all" = "-- install authd"
"serverd" will be accepted as "status"
"adapter" will be accepted as "anabolics", but also "aggressive" and "aggressively"
"devices" will be accepted as "drivers" "default" and "donjuan", but not as "devicess". Still not sure what it is supposed to be for this one.
"nat" will be accepted as "n" "net"
"bridge" will be accepted as "b" "br" "bbb" "brittt"
"legacy" will be accepted as "looser", but not as "loooser"
"userif" will only accept "userif"
and so on...

"vnetlib -- set vnet vmnet3 addr 10.10.10.10" = "vnetlib -- set vnnn vmnet3 addr 10.10.10.10"
"vnetlib -- set adapter vmnet3 addr 10.10.10.10" = "vnetlib -- set analsex vmnet3 addr 10.10.10.10"
"vnetlib -- update anabolics vmnet3" = "vnetlib -- update adapter vmnet3"
"vnetlib -- update vnnn vmnet3" = "vnetlib -- update vnet vmnet3"
"vnetlib -- remove adapter vmnet3" = "vnetlib -- remove a vmnet3" = "vnetlib -- remove aaaaaaa vmnet3",,,,but "vnetlib -- remove v vmnet3" and "vnetlib -- remove aaaaaaaa vmnet3" will not work

If there is a pattern in this that makes sense and is logically justified, then let me know.

Yes it made me VERY confused in the beginning.

Other commands found:
"vnetlib -- set installpath drive\directory" will set this registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMnetlib
"InstallPath"="C:
LODR
ws651"

The actual meaning of this key is unknown to me. Similarly is vnetlib.exe also reading a LogLevel key from the same place, but that one is also not figured out.

Attached is a little kit with scripts that will collect the necessary files to let you play with these services on a testbox. It will not require an installation of Workstation, just a few binaries. Different batches are included as well as registry patches to setup the environment. Some modified inf files included too.

Hopefully others will comment on and add more information to this.

TODO - what is not resolved yet:

Install usb directly with vnetlib.
Figure out usage of possible commands like; team, unteam, bridge, unbridge, garp, ungarp, connect, disconnect...

Joakim

This document was generated from the following thread: Vnetlib - Documenting some more

Can't load guest operating system

Fri, 06 Feb 2009 13:27:04 GMT

I have downloaded the 30 day trial of VMWorkstation. I want to install Windows 98 as a guest operating system. Every time I power on the guest operating system it tries to perform a network install by AMD. I have booted to the BIOS and set my CD drive as the first device in the list but it stil tries to perform the network install. Is there any way to remove the network install from the boot sequence? Is this a default for the 30 day trial version? I am am using VMware 6.5.

no network access in guest - but only with XP guest?

Sun, 11 Jan 2009 10:10:24 GMT

using VMware 6.5.0 build -118166

RUnning on Vista SP1 x64 as host.

Got a WIn XP x86 guest - and I'mcompletely unable to access any network resources. Oddly - with the same install - I 've got a knoppix guest that can access the network just fine.

I made a point of making sure all my AntiVirus and firewall progs (including the built in windows firewall) were completely disabled on both the xp guest and vista host. No change.

DOnt know if this relevant - but the guest reports a gateway IP that does NOT match any of the IPs of the host system

The guest is set up to get dns/ip/etc with DHCP

Got IPconfig info attached....

Really wierd...normally setting up linux networking is a PITA compared to setting up windows networking......for me anyway...bass ackwards in this case

any pointers apreciated....

"The VMware Authorization Service service hung on starting" on Vista 32 bit Business

Thu, 08 Jan 2009 10:12:26 GMT

Dear Community

Setup: Vista 32 bit Business on HP DC7900 (E8500) pc with 4 GB RAM. Vmware Workstation 6.5.1 for Windows, Build: 126130.

Problem: The computer hangs in the boot up sequence (10-30 min.), and the Windows lists a 7022 error:

Log Name: System
Source: Service Control Manager
Date: 07-01-2009 15:57:12
Event ID: 7022
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxx
Description: The VMware Authorization Service service hung on starting.

My guess is that it is a general bug on Vista - none of my clients have the problem on XP x32?

Best Regards,
jni

What is it happened for when I install on FC10 / openSUSE 11.1 64bit?

Fri, 26 Dec 2008 09:44:39 GMT

Dear all:

I'd install the VMware-Workstation-6.5.1-126130.x86_64.rpm on Fedora Core 10 & open SUSE 11.1,

but both of them shows error as below:

..................................................

10. These terms are governed by the
laws of the State of California and the United States of America without regard
to conflict of laws principles. You may not assign any part of this Agreement
without the prior written consent of VMware. Any attempted assignment without
consent shall be void. These terms constitute the entire agreement between you
and VMware with respect to the SDK, and supersede all prior written or oral
communications, understandings and agreements. Any waiver of these terms must
be in writing to be effective. If any provision of these terms is found to be
invalid or unenforceable, the remaining terms will continue to be valid and
enforceable to the fullest extent permitted by law.
Do you agree? ~~yes/no~~: yes

Installing VMware Installer 1.0
Copying files...
Configuring...
Installing VMware Player 2.5.1
Copying files...
Configuring...
Installing VMware VIX API 1.6.3
Copying files...
Configuring...
Installing VMware Player 2.5.1
Copying files...
Configuring...
Installing VMware Player 2.5.1
Copying files...
Configuring...
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe7 in position 0: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 13: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe8 in position 0: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 47: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 47: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 47: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 47: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 47: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 47: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 47: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 47: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 47: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 0: ordinal not in range(128)
Traceback (most recent call last):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
if self.shouldRollover(record):
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
msg = "%s\n" % self.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
return fmt.format(record)
File "/tmp/vmis.ZGt3uN/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe5 in position 47: ordinal not in range(128)
Installing VMware Workstation 6.5.1
Copying files...
Configuring...
Installation was successful

Can anyone tell me what is it happened for?

I don't know how to evaluate the product if I can't install and run it smoothly.

Thank you.

After update software VMware workstation 6.5.1 don't restart

Sun, 07 Dec 2008 14:15:11 GMT

Hello,

the VM on which I work carried out some safety of software updatings. To the restart I do not succeed to make it distribute in some manner.

For me it's very important to succeed to restore the virtual machine. Someone to some idea?

The pc host is a Dell D531 with processor AMD Turion 64 x2 while the I KNOW and Windows Xp. The virtual car is a Windows Xp with service pack2 and all of the updatings until this last that blocked to the macho virtual.

Thanks one thousand.

Installing VMware ESX Server 3i 3.5.0 in a VMware Workstation 6.5.1 VM

jmattson@vmware.com — Wed, 03 Dec 2008 18:00:36 GMT

There is a growing interest in running ESX or ESXi in a Workstation VM, for demo or training purposes. While this configuration is not supported, it does tend to work pretty reliably.

Prerequisites

First, let me detail the hardware requirements. You must have a 64-bit Intel or AMD processor. Intel processors must have VT support, and VT must be enabled in the BIOS. Most Core2 and Core i7 parts have VT support. AMD processors must have AMD-V support, and they must be at least Family 10H (i.e. Phenom). The earliest Athlon64's with AMD-V support will not work. There are now some mobile Turion parts which are Family 11H, and these will work as well.

Preliminaries

I am assuming that you already have Workstation 6.5.1 installed on your host. You should also download the ESX Server 3i 3.5.0 Installable ISO image from the VMware website. (I used build 123629.)

If you are running Workstation on a Linux host, you will need to change the permissions on /dev/vmnet0 to allow the ESXi guest to put its network adapter into promiscuous mode. The easiest way to do this is:

chmod a+rw /dev/vmnet0

If you want tighter control over this, you can change the group of /dev/vmnet0 to a privileged group and add 'rw' permissions only for that group. If you are running Workstation on a Windows host, there is nothing you need to do.

These instructions configure the VM to get an address via DHCP from your local network. You should have a DHCP server running on the network. Alternatively, you can use host-only networking or a variety of other networking configurations.

Creating the VM

Start Workstation 6.5.1 and select 'Create a new virtual machine.'
Select a 'Custom' VIrtual Machine Configuration.
Leave the Virtual Machine Hardware Compatibility set to 'Workstation 6.5.'
Under Guest Operating System Installation, select 'Installer disc image file' and point it to your ESXi 3.5 Installable ISO.
For Guest Operating System, select 'Other', and select Version 'Other 64-bit.' Really.
Name the Virtual Machine whatever you like.
Select either One or Two processors, as you like.
Set the Memory to at least 1024MB.
Under Network Connection, select 'Use bridged networking.'
Leave the I/O Adapter set to 'LSI Logic.'
Select 'Create a new virtual disk.'
Change the Virtual Disk Type to 'SCSI.'
Set the Disk Capacity to at least 2GB and other disk options however you like. If this VM will host nested VMs, bear that in mind when setting the disk capacity.
Name the Disk File whatever you like.
You are ready to create your Virtual machine.

Installing VMware ESX Server 3i 3.5.0

The VM should now boot from the ESXi 3.5 Installable ISO.

Press enter to install.
Accept the license agreement with F11.
Press enter to select the VMware Virtual SCSI disk.
Press enter to confirm your disk selection.
Press F11 to confirm installation.
Press enter to reboot.

Once the VM reboots, you can download the VMware Infrastructure Client from the VM to manage it. Just follow the instructions on the boot screen.

Running Nested VMs

You can run nested VMs under the ESXi VM, but you may only run 32-bit guest operating systems as nested VMs. Before running nested VMs, you should shut down Workstation, edit the configuration file for your ESX VM with a text editor and add the following configuration option:

monitor_control.restrict_backdoor = "TRUE"

VMware Workstation 6.0.5 & 6.5 Unrecoverable error: NOT_REACHED

Thu, 20 Nov 2008 10:18:05 GMT

I have the following problem:

Each time when I start a VM i get this error:

NOT_REACHED d:/build/ob/bora-118166/bora/lib/disklib/sparseChecker.c:1449
Nov 18 10:28:17.609: vmui| http://msg.panic.haveLog A log file is available in "C:\Documents and Settings\Administrator\Local Settings\Temp\vmware-Administrator\vmware-Administrator-1132.log". http://msg.panic.haveCore A core file is available in "C:\Documents and Settings\Administrator\Application Data\VMware\vmware-1132-0.dmp". http://msg.panic.requestSupport.withLogAndCore Please request support and include the contents of the log file and core file. http://msg.panic.requestSupport.vmSupport.windowsOrLinux
vmui| To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.
vmui| http://msg.panic.response We will respond on the basis of your support entitlement.

I have tried to install VM Workstation on an another partition with a new installed Windows XP x64 on my PC.It doesn't help.

I have created a new VM. This machine runs without problems. All the other VM i have made in the past doesn't work anymore.

I hope somebody could help me.

This document was generated from the following thread: VMware Workstation 6.0.5 & 6.5 Unrecoverable error: NOT_REACHED

Attempting to load a 64-bit application, however this cpu is not compatible with 64-bit mode.

Wed, 19 Nov 2008 01:20:48 GMT

Vmware Workstation 6.5 installed on vista ultimate 32bit, attempting to install vista64 as guest and recieve the following error.

File: \windows\system32\boot\winload.exe
Status: 0x000035a
Info: Attempting to load a 64-bit application, however this cpu is not compatible with 64-bit mode.

I have run the http://www.vmware.com/download/server/drivers_tools.html which says my cpu will support 64-bit mode. Also, in the BIOS I have enabled Virtuization and rebooted system, same error

I did successfully install Ubuntu 32-bit, without a hitch.

If anyone has some ideas I would be very grateful
Thx

New VM is blue screening after updating drivers

Thu, 06 Nov 2008 17:00:56 GMT

Hello,

I have an old laptop running Vista Ultimate 32 bit.
I used VMWare converter to image that machine. I used the "custom" option, gave it a prod id etc. I made the VM onto a 1 TB external drive. All went well.

I have a NEW laptop running Vista Ultimate 64-bit edition. I copied the files from my the above steps to the HD of the new computer. I installed VM Workstation.

When I start the above VM on my new laptop using Workstation it starts up just fine... I login... and Vista begins to immediately start installing new drivers. I don't see a way of preventing that. After installing the drivers and rebooting the screen BSODs. If I boot in safe mode I get the same behavior. I can in any case hit f8 and choose last known good configuration and it will boot again. But it just repeats the behavior.

In advice to troubleshoot what is my errant driver and how to prevent vista from loading it on startup.

Thanks for your help in advance.

Seth

Unable to connect to the second booted guest OS

Tue, 04 Nov 2008 04:43:38 GMT

VMware Workstation 6.5.0
Host OS : Fedora8 x86_64 ( kernel : 2.6.26.6 )
Guest OS : Fedora8 x86_64 ( kernel : 2.6.26.6 )

I havea problem on guest about networking.

Every time only first booted guest OS can be connected but any other guest cannot be connected after that.
Even ping does not rearch.
Of course I have licence key and using it now.

I checked that IP address were not duplicating and same license was not being used by any other.
Does somebody know this situation?

ACE - SysprepTools File Location for Workstation 6.x

Mon, 03 Nov 2008 19:05:03 GMT

Covers: The proper storage location for the Windows SysprepTools used by the ACE package creator in VMware Workstation 6.x.

The user manual for Workstation 6.5 still has a carry over issue from 6.0. On page 422 it states:

"Unzip the files into the directory where Workstation is installed. The default installation directory is: 'C:\Program Files\VMware\VMware Workstation' ".

Though this information is correct it is lacking in critical details. The proper default path to extract the Sysprep tools too should be:

For XP 32-bit: C:\Program Files\VMware\VMware Workstation\Resources\SysprepTools\<os sp version>
For XP x64: C:\Program Files (x86)\VMware\VMware Workstation\Resources\SysprepTools\<os sp version>

It is critical that you have the correct Sysprep tool package in the correct the Service Pack folder. So, if the guest OS is XP with SP2, then '<os sp version> = xpsp2'. If it is XP with SP3 then '<os sp version> = xpsp3'.

NOTE: This only applies to Windows 2K, XP, XP x64, and Server 2003. Unsure of the required paths under Vista.

VMWare Workstation unrecoverable error: (vmx)

Sat, 01 Nov 2008 10:14:10 GMT

in the attached document i added the whole error message. After deleting the *.lck files in the vm folder i can start the session, but after logging on in vista the error appears again.

Thks for answers

Issue - VMware v6.0.5,v6.5 both conflict with the Intel RAID driver v8.6.0.1007

Wed, 22 Oct 2008 11:26:52 GMT

1- Detailed issue description
When to run virtual machines in VMware Workstation v6.5 and v6.0.5 after a
while begins continuous recourse to disk arrays. I used RAID 0 on two drives
320GB HITACHI HTD725032VLA360. It is not possible to correctly complete the
work of virtual machines. In the host system, the mouse is working not
correctly, and the keyboard does not work at all. Shutdown of the host system
through the software UPS only. To do this, the power cord of the power supply
UPS is unplugged.

2- Is there physical damage to the board? Please provide detail.
No. I have not noticed damage to hardware.

3- When did the issue first occur?
A few hours after installing the RAID driver v8.6.0.1007.

4- Are you receiving an error message? If so please provide the exact wording of the error message
No, the error message is absent.

5- What system changes occurred, such as BIOS or operating system upgrade, new peripheral devices, etc.?
I had intalled video Intel Graphics Media Accelerator Driver for Windows XP
14.36.3.4990 and the RAID driver v8.6.0.1007.

6- What steps have you tried to correct the issue?
First, I uninstalled VMware Workstation v6.5 and installed VMware Workstation
v6.0.5, but it did not help. Then, means Windows XP rolled back RAID driver
on the previous version of v8.5.0.1032 and the problem disappeared.

SYSTEM INFORMATION:

Desktop Board: Intel DG965WHMKR
Board Altered Assembly Number (AA#): D41692-306
Board Serial Number (SN#): BQWH7120028N
Onboard Options Used (i.e. Video, Audio, LAN): Video, Audio, LAN
Previous BIOS: MQ96510J.86A.1738.2008.0617.0002
Current BIOS: MQ96510J.86A.1751.2008.0811.0002
Chassis Vendor: 3R R800
Power Supply: be quiet! Straight Power BQT E5-450W (BN034, 450W)
Processor: Intel Core 2 Duo E6700
Memory: 4x 1G DDR2-800 Hynix HYMP512U64CP8-S5 PC2-6400 (5-5-5-12)
Operating System: Windows XP Professional RUS
Service Pack: 3

How to install sound in Win95, 98, 98SE

Sat, 04 Oct 2008 20:10:11 GMT

How to install sound in Win95, 98, 98SE in VMware Workstation (Instructions made from a Windows 98 SE)

1. Install Win95, 98, 98SE.

2. Download the sound drivers from http://rapidshare.com/files/150812291/Creative_AudioPCI__ES1371_ES1373___WDM_.zip.html

3. Unzip the files.

4. Open the "System Properties"

5. Choose the "Device Manager" tab

6. Choose the "PCI Multimedia Audio Device" that is not installed and press "Properties"

7 Press "Reinstall Driver" then "Next" and then the first option (Search for a better driver than the one your device is using now. (Recommended)) then press "Next"

8. Browse to the driver directory that you unzipped before then press "Next" then press "Next" again (the device is starting to install) and then press "Finish"

9. Close down the applications and restart windows.

10. Now another setup window appears press "Next" Choose a installation directory and press "Next" then press "OK"

11. Now the should the sound work properly. Good Luck : )

unrecoverable error (vcpu-0) VM workstation 6.5

Tue, 09 Sep 2008 23:34:34 GMT

Well i start up my VMK starts up just fine, i start up my game in it or
if im not doing anything with it an ERROR will pop up something like,
Unrecoverable .. (vcpu-0) any ideas or link i can go to get this issue
fixed, Im running Windows XP pro.. AMD duel cor

Install Problm (compile error)

Wed, 20 Aug 2008 02:54:47 GMT

I am now installing Vmware workstation (VMware-workstation-6.0.4-93057.x86_64.tar.gz). And I got the following error message.

Please tell me to resolve the error.

Building the vmmon module.

Using 2.6.x kernel build system.
make: entering directory `/tmp/vmware-config3/vmmon-only'
make -C /lib/modules/2.6.26.2/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.26.2'
CC [M] /tmp/vmware-config3/vmmon-only/linux/driver.o
/tmp/vmware-config3/vmmon-only/linux/driver.c:197: error: unknown field ‘nopage’ specified in initializer
/tmp/vmware-config3/vmmon-only/linux/driver.c:198: Warning: initialization from incompatible pointer type
make[2]: *** [/tmp/vmware-config3/vmmon-only/linux/driver.o]Error1
make[1]: *** ~~_module_/tmp/vmware-config3/vmmon-only~~ Error 2
make[1]: Leaving `/usr/src/linux-2.6.26.2'
make: *** http://vmmon.ko Error 2
make:Leaving `/tmp/vmware-config3/vmmon-only'
Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

installation zaptel sur fedora 8

Sat, 19 Jul 2008 13:09:47 GMT

svp aider moi, j'arrive pas à installer zaptel sur fedora 8

lorsque j'installe ce module il m'affiche ce message:

make[3]: quittant le répertoire « /usr/src/zaptel-1.4.11/menuselect/mxml »
gcc -o menuselect menuselect.o strcompat.o menuselect_curses.o mxml/libmxml.a mxml/libmxml.a -lncurses
make[2]: quittant le répertoire « /usr/src/zaptel-1.4.11/menuselect »
make[1]: quittant le répertoire « /usr/src/zaptel-1.4.11/menuselect »
Generating input for menuselect ...
make[1]: entrant dans le répertoire « /usr/src/zaptel-1.4.11 »
echo "You do not appear to have the sources for the 2.6.21-2950.fc8xen kernel installed."
You do not appear to have the sources for the 2.6.21-2950.fc8xen kernel installed.
exit 1
make[1]: *** modules Erreur 1
make[1]: quittant le répertoire « /usr/src/zaptel-1.4.11 »
make: *** all Erreur 2

j'ai cherché sur internet pour installer ce type de kernel-devel mais il n'existe pas.

qlq peut m'aider svp?

Top 10 Tips and Tricks for VMware Workstation

Wed, 09 Jul 2008 19:34:37 GMT

Here are top 10 tips and tricks for VMware Workstation.

To run a virtual machine in a separate window, choose File > New > Window
To add the current virtual machine to the Favorites list, choose File > Add to Favorites.
Suspend a virtual machine if you want to stop temporarily and resume at the same point. Take a snapshot if you want to return the virtual machine to the same point repeatedly.
Before switching video resolution on the host computer, shut down the guest operating system and power off the virtual machine.
You can run a different virtual machine on each of your monitors. Choose File > New > Window to open each virtual machine in a different window. Put each window on a different monitor and click the Full Screen button.
Take multiple snapshots and use the Snapshot Manager to manage them.
To copy a virtual machine, choose VM > Clone.
Use the template mode option in VM > Settings > Options > Advanced if you want to guarantee that linked clones will always have access to the parent virtual machine.
To convert a physical machine, ESX virtual machine, or supported third-party image to a VMware virtual machine that can be used in Workstation, choose File > Import.
To ensure that the virtual machine is always reset to a clean state, choose VM > Settings > Options > Snapshots > When powering off > Revert to snapshot.

vmware Unable to change virtual machine power state: Failed to connect to peer process.

Mon, 09 Jun 2008 20:11:37 GMT

hi, evry body,

I've got this message when i launch vmware workstation 6, "vmware Unable to change virtual machine power state: Failed to connect to peer process".

Is some one can help me ?

I'm on fedora 9 kernel 2.6.25.4-30.fc9.x86_69 and trying to run windows xp.

serial number for vmware 6.0 for linux

Mon, 09 Jun 2008 09:51:43 GMT

hi....

i want serial number for vmware workstation 6.0 for linux i downloaded from vmware.com but i lost the serial key

can anybody help me out...

thanks

uday shankar

Cannot open my Linux VM Getting error message.

Thu, 29 May 2008 01:19:11 GMT

When i try and open up my virual machine these two different error messages pop up "Unable to open kernel device "\\.\vmx86": TCannot find a valid peer process to connect to.he operation completed successfully. Did you reboot after installing VMware Workstation?"
"Failed to initialize monitor device". I have the the error message screen attatched look at that if you need help. Thank you for who ever gives me the solution.

How to print to a Linux host CUPS printer using VMWare Workstation 6 from a MS Win XP Pro guest

Wed, 21 May 2008 20:50:32 GMT

kDE CRASH Opensuse 10.3

Wed, 16 Apr 2008 09:25:52 GMT

When I`m starting VMware workstation 6.5 I often get a crash.

The only solution for me is to reboot manually.

Logging to /tmp/vmware-eberhard/setup-5940.log
filename: /lib/modules/2.6.22.17-0.1-default/misc/vmmon.ko
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
srcversion: 8BD9410375ACDA79B0FDE52
depends:
vermagic: 2.6.22.17-0.1-default SMP mod_unload 586
filename: /lib/modules/2.6.22.17-0.1-default/misc/vmnet.ko
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
srcversion: E3E17172903278B8B8D8E3B
depends:
vermagic: 2.6.22.17-0.1-default SMP mod_unload 586
filename: /lib/modules/2.6.22.17-0.1-default/misc/vmblock.ko
version: 1.0.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: EC480BD35752B7F48153251
depends:
vermagic: 2.6.22.17-0.1-default SMP mod_unload 586
parm: root:The directory the file system redirects to. (charp)
filename: /lib/modules/2.6.22.17-0.1-default/misc/vmci.ko
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
srcversion: FD14186FA488E3B3704D7DC
depends:
vermagic: 2.6.22.17-0.1-default SMP mod_unload 586
filename: /lib/modules/2.6.22.17-0.1-default/misc/vsock.ko
alias: net-pf-28
license: Proprietary
version: 1.0.0.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: FD4BB2AF70F061CE88DBE4F
depends:
vermagic: 2.6.22.17-0.1-default SMP mod_unload 586
filename: /lib/modules/2.6.22.17-0.1-default/misc/vmmon.ko
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
srcversion: 8BD9410375ACDA79B0FDE52
depends:
vermagic: 2.6.22.17-0.1-default SMP mod_unload 586
Using log file /tmp/vmware-eberhard/ui-5994.log
PowerOn
Warning Could not load glWeightPointer extension.
Warning Could not load glWeightPointer extension.
VmdbCtxGet: Failed to get /vm/#_VMX/vmx/runtimeState/dev/#/memory/class/otadd/growStepMb/ (Schema path not found)
VmdbCtxGet: Failed to get /vm/#_VMX/vmx/runtimeState/dev/#/memory/class/otadd/maxSizeMb/ (Schema path not found)
SCSI-CDROM0:1: Allowing unknown command REPORT LUNS (0xa0). --ok
VIDE: Truncating 0x46 from 65532 bytes to 4096
VIDE: Truncating 0x46 from 65532 bytes to 4096
VIDE: Truncating 0x5a from 65520 bytes to 4096
SCSI-CDROM0:1: Allowing unknown command UNKNOWN (0xac) (0xac). --ok
SCSI-CDROM0:1: Allowing unknown command UNKNOWN (0xac) (0xac). --ok

This is a logfile

kde crash

Thu, 10 Apr 2008 18:05:53 GMT

I`ve changed my motherboard on my computer and it was necessary to install OpenSUse 10.3 at once.

I'm using Workstation 6.03 hostsystem is Opensuse 10.3, Guestsystem Windows Vista ultimate 32 bit.

If I want to install Windows Vista , kde crashed and nothing runs every more. To restart I must shutdown manually

and reboot.

Eberhard

VM Guest Running from ExpressCard (EC) Memory/Flash

Thu, 03 Apr 2008 02:19:51 GMT

I have seen some discussion on the Internet of using an ExpressCard slot on a laptop to connect a SATA drive through an EC with eSATA interfaces. So I began researching ExpressCards and found that today you can get a 16GB EC for under $200. With the direct memory access and solid state design, I thought this would be ideal to run a VM guest. Unfortunately to my surprise, my VM guest ran MUCH slower from the EC. Has anyone tried this yet or have any ideas to tweak the performance? I really expected this to be much faster than an external drive connected via USB or eSATA. I appreciate any advice. Thanks.

VMWare libraries swapper

Sat, 29 Mar 2008 12:51:47 GMT

vmware-config fails in compile on Ubuntu hardy heron 8.04 (kernel 2.6.24)

Fri, 21 Mar 2008 22:49:17 GMT

Vmware modules fail to compile from workstation-6.0.3-80004 in Ubuntu Hardy Heron 8.04 on a 2.6.24 kernel.

None of the pre-built vmmon modules for VMware Workstation is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? yes
Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.24-12-generic/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmmon-only'
make -C /lib/modules/2.6.24-12-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.24-12-generic'
CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config2/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config2/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config2/vmmon-only/common/cpuid.o
In file included from include/asm/bitops.h:2,
from /tmp/vmware-config2/vmmon-only/./include/vcpuset.h:74,
from /tmp/vmware-config2/vmmon-only/./include/modulecall.h:23,
from /tmp/vmware-config2/vmmon-only/common/vmx86.h:18,
from /tmp/vmware-config2/vmmon-only/common/hostif.h:18,
from /tmp/vmware-config2/vmmon-only/common/cpuid.c:14:
include/asm/bitops_32.h:9:2: error: #error only <linux/bitops.h> can be included directly
make[2]: *** [/tmp/vmware-config2/vmmon-only/common/cpuid.o] Error 1
make[1]: *** ~~_module_/tmp/vmware-config2/vmmon-only~~ Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-12-generic'
make: *** http://vmmon.ko Error 2
make: Leaving directory `/tmp/vmware-config2/vmmon-only'
Unable to build the vmmon module.

vmdk maint

Fri, 07 Mar 2008 16:27:23 GMT

So… using vmware workstation and disk files that grow automagically can do ‘bad things’ to disk fragmentation. Here’s a script that you can schedule that will help some of this.

First it will search for vmdk files in subfolders of the folder you specify, once found it will shrink and then compress them. Finally, it defrags the drive the vmdk’s are stored on.

Copy & paste it to notepad and save it with a .vbs extension. You can then add it as a scheduled task, or execute it from the command line.

It is a bit windows centric, but I can try my hand at perl if there is interest.

EDITED 3/14/2008 - Added checking for snapshots

'maint.vbs
'This script will parse through the directory specified and compress and defragment vmdk files.
'After this, it will defrag the drive the vmdk's rest on.
'
'Please let me know if you have any issues
' Cody Bunch

'On Error Resume Next

sFolder = Wscript.Arguments.Item(0)
vmwaredir = Wscript.Arguments.Item(1)

If sFolder = "" or vmwaredir = "" Then
Wscript.Echo "Usage: cscript maint.vbs ""c:\folder with vmdk files"" ""c:\vmware install folder"" "
Wscript.Quit
End If

' find and compress/defrag the vmdk's

set wshShell = wscript.createobject ("wscript.shell")
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFolder = objFSO.GetFolder(sFolder)
Set colSubfolders = objFolder.Subfolders
For Each objSubfolder in colSubfolders
snapshotPresent = false
Wscript.Echo "Searching in " & objSubfolder.Name & " for vmdk's"
set files = objSubfolder.Files
if snapshotCheck(files) = true then
wscript.echo "Snapshot found, skipping."
else
for each file in files
if right(file.Name,5) = ".vmdk" then
shrink vmwaredir, sFolder, objsubfolder.Name, file.Name
defrag vmwaredir, sFolder, objsubfolder.Name, file.Name
end if
next
end if
Next

' now defrag the disk they're on
set wshShell = wscript.createobject ("wscript.shell")
drive = left(vmwaredir,2)
cmdStr = "defrag -v -f " & drive
wscript.echo "Defragmenting " & drive
wshShell.run cmdStr, 0, True
set wshShell = nothing

Sub shrink (vmwaredir, sFolder, subFolderName, fileName)
' shrink vmdk's
Wscript.echo "Found " & file.Name & " shrinking"
set wshShell = wscript.createobject ("wscript.shell")
cmdStr = """" & vmwaredir & "vmware-vdiskmanager.exe"" -k """ & sFolder & "\" & subFolderName & "\" & fileName & """"
wshShell.run cmdStr, 6, True
set wshShell = nothing
End Sub

Sub defrag (vmwaredir, sFolder, subFolderName, fileName)
' defrag vmdk's
wscript.echo " ... defragging"
set wshShell = wscript.createobject ("wscript.shell")
cmdStr = """" & vmwaredir & "vmware-vdiskmanager.exe"" -d """ & sFolder & "\" & subFolderName & "\" & fileName & """"
wshShell.run cmdStr, 6, True
set wshShell = nothing
End Sub

Function snapshotCheck (files)
'check for snapshots
for each file in files
if right(file.Name,5) = ".vmsn" then
snapshotCheck = true
exit function
end if
next
End Function

This document was generated from the following thread: vmdk maint

Workstation 6 Cloning

Fri, 29 Feb 2008 15:39:40 GMT

Can someone tell me what the correct procedure is for cloning in Workstation V6.0, I have a Win XP Pro machine all built and configured with all patches and i want to make a full clone, not linked. The clone works successfully. The new clone is now on the domain, so i log onto it and change the machine name, do i need to run NEWSID ? Also is there anything else that needs to be done, or is this completley the wrong way to do this. Thanks in advance ?

If the original guest and the clone meets in the domain, you should generate a new SID for the clone (how did you clone it?).
You also should change the MAC address of the clone's vNIC. Therefore VMware should already have asked you if you wnt to generate a new UUID (which is the base for the MAC address). YOu can check it by looking into both .vmx files.
If you use static IP's you should give a new one to the clone, as well.

AWo

Thanks for your response, i built a Win XP Pro machine from scratch, service packed it etc, made all the configuration changes and then added it to the domian. From there i used the Clone option in Workstation 6 and selected full clone. I then had an identical copy of my XP Pro machine but called something else in VM favourites and also all related files in a seperate folder. I then logged into the new machine and renamed it, restarted the machine, then when i tried to log back into it, it said it couldn't find user on the domain etc. I have run NEWSID to change the SID, restarted and the same thing, cannot log in, i haven't made any changes to the NIC config as i wasn't prompted to when i did the clone. What do i need to change in the NIC config, some of my PC's will have DHCP, some will have Static IP's but all will reside on the domain.

Is there an computer account for this new renamed machine in AD?
Can your original system still log on to the domain (hopefully you didn't change the name of the AD computer account by changing the name of the clone while it still had the old SID)?

Are the MAC addresses different in the.vmx files? Check it. The line reads like this:
ethernet0.generatedAddress = "00:0c:29:88:65:95"

You need to know if you guest has DHCP or static, becaus if it is static you must change it.

AWo

There are computer accounts in AD for all 3 of my cloned PC's, original uncloned system can still log in, all 3 PC's are DHCP and the MAC addresses are different in all .VMX files. I guess that if a cloned machine which is using DHCP needs to become static you just add the IP address into the TCP/IP properties. Is this cloning method in Workstation 6 the best way to achieve this, i mean i would only like to build a XP client once and then just makes clones so i have other copies available, that way all the machines would be an identical spec, so i'm only doing 1 clean build. So as i understand the process is as follows in Workstation 6.

1) Install clean copy of Win XP Pro as a VM guest, make sure it's configured to my liking, add to domain etc.

2) Select the VM/Clone option from the menu, name it accordingly and place the files in a different folder.

3) Shutdown the clean orignal VM guest if powered on (as machine name will be the same)

4) Log into the new clone VM, rename it on the domain, the run newsid, reboot, if using DHCP should be OK if MAC address is different and if using static IP enter that into TCP/IP properties.

I just need to be sure this is the correct procedure that i need to follow, or maybe you can recommend an easier way to achieve this, thanks again for your help.

lewisma wrote:
I guess that if a cloned machine which is using DHCP needs to become static you just add the IP address into the TCP/IP properties.

Yes.

Is this cloning method in Workstation 6 the best way to achieve this

It takes some load from you which you otherwise have to do yourself:

It changes the UUID and the MAC address

But you still have to care about the SID and the IP address.

I guess you have to add your clone to the AD loging on locally using an account which is in the local admin group of the clone and then adding it (Computer Properties --> Computername --> Change Domain Membership) by authenticating to the domain with an domain account which is allowed to add computers to the domain. As your clone has a new SID this must be connected to the already existing computer account (identified by the NETBIOS name) in your AD (this is an "empty" account as long as the machine is not added to the domain).

AWo

OK, so it sounds like i can continue to use this method of cloning addintional VM's as it will change the UUID and MAC address assuming it is using DHCP

Static IP addresses i will change manually if required.

I have to run NEWSID once i log into the newly cloned VM's, now i assume i need to change machine name before i run NEWSID.

Also the clone itslef can be quite time consuming if the guest is quite large i.e - has 2 partitions

Mark

lewisma wrote:
OK, so it sounds like i can continue to use this method of cloning addintional VM's as it will change the UUID and MAC address assuming it is using DHCP

Yes

Static IP addresses i will change manually if required.

Yes.

I have to run NEWSID once i log into the newly cloned VM's, now i assume i need to change machine name before i run NEWSID.

Yes. For this and the static IP I would recommend to disable/disconnect the vNIC until this is done to prevent anything from going wrong.

Also the clone itslef can be quite time consuming if the guest is quite large i.e - has 2 partitions

If you want to clone 2 GB you have to wait for 2 GB to be cloned. That's the way the physics work

AWo

OK, fantastic, to disable/disonnect the vNIC i would just go into VM settings file in GUI when the VM is powered off and disable/disonnect there - is that correct ?

Do you recommend disabling/disconnecting the vNIC for all the operations which need to be perfomed, ie - Renaming PC/NEWSID and static IP address change if required ?

Mark

lewisma wrote:
OK, fantastic, to disable/disonnect the vNIC i would just go into VM settings file in GUI when the VM is powered off and disable/disonnect there - is that correct ?

You can disable it in the guests hardware setting dialog, before or after starting it or by right-clicking on the small icons down right.

Do you recommend disabling/disconnecting the vNIC for all the operations which need to be perfomed, ie - Renaming PC/NEWSID and static IP address change if required ?

Yes:

for the IP so you don't interfere with other hosts which might be up (even if a window guest will reject from entering the network if the same IP is detected I would run this as a general procedure).
for the NETBIOS name for the same reason
for the SID to protect the original AD account.

AWo

If you find this information usefull, please award the appropriate points. Thanks. -

Thanks again for your help. How do i get to the Guests hardware dialog, not sure where i need to go if the VM is powered off

Mark

Go to "VM --> Settings...", mark the vNIC and you'll find the check boxes on the right side, reading "Connected" (actual status) and "Connect at power on" (pretty self explaining).

AWo

OK, so you just untick "Connect at power on" as the Connected is greyed out. I guess once i agree the question being answered you get points awarded.

Mark

It's labelled as Ethernet, if the VM is powered on, do you just disable the NIC

"Disabling" is something you can do within a Windows guest, when the machine is already up and running (therefore it might already have produced some issues).
Under VMWare you can "disconnect" it from the guest (the guest still thinks the card is available but it appears as it's having no link) from the startup of the guest or later.

AWo

Sorry,i am a little confused with your last statement, could you explain that again please. Also i just finished cloning another XP machine, i unticked the 'Connect at power on' box, Connected was greyed out, the new clone was powered off at this stage. When i attempted to rename the PC which was already on the domain it failed saying it couldn't find the domain beacuse the NIC wasn't conneted. I had to connect the NIC for the rename to work

Mark

I was confused by your post saying: "It's labelled as Ethernet, if the VM is powered on, do you just disable the NIC".

You did it right by using "Connect at power on".

It must be disconneted while renaming it or you will rename the original machine account (remember, you still have the same name and SID). I don't know what happens if you change the SID first (while diconnected).

What I know what works is that you take the machine out of AD (all with a disconnected link!!), ignore any message regarding logon to AD etc., and put it in a Workgroup. Rename it, change the SID, connect it it to the LAN again and re-add it to the AD with the new SID and NETBIOS name.

AWo

Sorry for the confusion, i forgot to add that last statement to my last post.

I'll give your last comments a try on Monday and let you know the outcome

Many thanks for you help and quick response

Mark

This document was generated from the following thread: Workstation 6 Cloning

DELETE -- Problem with Experimental 3-D support on 9200

Fri, 22 Feb 2008 09:26:07 GMT

From this page,

http://www.vmware.com/support/ws55/doc/ws_vidsound_d3d_enabling_host.html

It says the experimental 3-D supports the ATI display cards later than 8500
but if I start this feature using my Radeon 9200 64MB,
this error occurs

Feb 22 16:14:40.773: mks| http://msg.glBackend.initFailed Failed to construct OpenGL rendering backend. The 3-D features of the display card will be disabled.----------------------------------------

wondered how to solve it
it has no problem on my Radeon 9600, X1600, HD2600, X700

VMware Authorization Service service terminated error 6000004

Fri, 18 Jan 2008 06:15:41 GMT

I installed VMware Workstation 6 on Vista Ultimate and couldn't seem to start any Virtual Machines.

When attempting to start a VM I received errors about the Authorization Service not being started.

I un-installed and reinstalled Workstation 6 thinking maybe I did something wrong. No Good.
Read the forums tried a couple of things suggested. Still no good.

Upon further investigation discovered that I had inadvertently blocked this service with my Firewall.

Once I unblocked it, all good to go.

So just thought I would post this document for others who may come across a similar problem.

Event Viewer Information:

The VMware Authorization Service service terminated with service-specific error 6000004 (0x5B8D84).

Log Name: System
Source: Service Control Manager Eventlog Provider
Logged: 18/01/2008 1:28:45 PM
Event ID: 7024
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Home
OpCode: Info

How do I network files with the host machine

Tue, 20 Nov 2007 20:31:23 GMT

I have two XP Pro VMs with Workstation 6. Both machines appear in the VM Network Neighborhood. Neither VM appears in my host network (Vista), even though their are part of Workgroup (like Vista).

How do I get my VMs accessible to the host machine?

Graphical, not "text," install of Fedora Core 7 under workstation 6.0.1

Fri, 19 Oct 2007 14:31:05 GMT

Ran an install of Fedora Core 7 on workstation 6.0.1 which seemed to install completely, but upon reboot get black/blank screen - do I need to specify diff. vid. card settings instead of letting it "probe?"

I opted not to install GRUB which I assume is not a problem? I don't see anything on the virtual desktop/screen other than the vmware splash screen. FYI, I also ran a kubuntu install and that runs fine?

Actually, that's exactly the problem. GRUB is the boot loader which loads the actual kernel. Without GRUB (or another loader like lilo) it won't boot.

Ah, I wasn't quite sure about that. I assumed that since Fedora would be the only OS running this wasn't necessary. I will run GRUB and hopefully red hat will follow

Update -> that did the trick thanks for the input

Thank you,

This document was generated from the following thread: New graphical install of Fedora Core 7 on workstation 6.0.1

VMware problem ''not valid configuration file"

Fri, 19 Oct 2007 09:49:08 GMT

First of all, hi all.

All right it's probably all small problem and i really need it fixed somehow. I've tried to replace files with a other VMware but this did not work out. I'd like to ask any person to reply to this topic as soon as possible, and i would really appreciate this.

Below i made some screenshots to describe the problem i get while booting my VMware.

I would like to mention again i would really appreciate a fast reply and a good solution.
Bare in mind that i do not know much about this, so giving steps would be awesome

best regards,

xxx james_1

"A needed file was not found" making pocket Ace Package

Mon, 15 Oct 2007 15:09:54 GMT

First off, this is my first post. There is a lot of great information here, thanks in advance for any help you guys/gals might offer.

I have a new workstation vm made, through VMware Workstation Ace edition.

Its been fully patched (windows xp) and is running smoothly. Vmware tools are of course installed.

When I go to create a new pocket ace image to put on my 8 gb thumb drive (yes, there is enough space, i managed that aspect when i created the vm the first time) it gets to the point of creating it, and then says "a needed file was not found"

Its right after the package summary page.

Any help would be much appreciated.

Thanks

Ryan

Frequently asked questions in the VMware Workstation forum

Wed, 10 Oct 2007 08:48:52 GMT

General

Q: Which host OS - Windows or Linux - should I use for the best performance / results / manageability?
A: You should use the host OS you're most familiar with. There is no remarkable performance difference between Windows and Linux hosts.

Q: When I try to start the VM I get an error message, that the VM currently is in use. I'm sure it is not.
A: Remove any lock files (.lck) or lock folders in the VM directory. Also check that any of the guests disks are not mounted within the host OS.

VM configuration

Q: How do I install VMware Tools in my Guest OS?
A: http://pubs.vmware.com/guestnotes

Q: Is there a list of configurable parameters for .VMX files whether supported or unsupported by VMware?
A: http://sanbarrow.com/vmx.html

Q: When I try to start the VM I get an error message, that one of the disks is already in use by another VM. I'm sure it is not.
A: First read this What to do in moments of crisis, then post in the VMware Workstation forum and provide as much information as possible.

Q: When trying to start the VM I get an error message saying something about a changed "parent disk". What shall I do?
A: Most likely the CID chain is broken. Read this What to do in moments of crisis, then post in the VMware Workstation forum and provide as much information as possible.

Q: How do I safely copy or move a VM?
A: To safely move or copy a VM do the following
- copy the files using a binary transfer method
- after copying check that the file permissions are the same
- if the disk(s) are bigger than 2Gb make sure the tools to transfer the files can handle these big files
- if the disk(s) are bigger than 2Gb make sure the destination file system can handle these big files
- if the copy stays on the same host make sure you rename the original VM folder BEFORE starting the copy the first time. If you don't get error messages you can rename the folder back.
- if after copying / moving you get an error message, stating that one of the disks could not be opened you most likely hit the "pathname" bug (see below).

Q: My host has multiple CDROM/DVD devices and I have problems accessing them from the VMs?
A: Disable CDROM auto detection and manually select the appropriate host device.

Q: I manually modified the VMX file but VMware Workstation doesn't reflect the changes. What can I do?
A: When manually modifying a VMX file make sure to close VMware Workstation first.
If this doesn't help remove the VM from the favorites and add it afterwards.

Disks and snaphots

Q: How do I expand the size of the virtual disk? Are there any precautions to take?
A: Precautions to take:
- don't do this when the VM has snapshots
- make a backup first

The actual resizing of the virtual disk is fairly easy using the vmware-vdiskmanager tool (part of the installation).
To expand a disk to the new size of 10Gb execute the following command from the command shell
vmware-vdiskmanager -x 10Gb disk.vmdk
If disk.vmdk is not in the current folder you have to specify the complete path to the disk. Make sure to enclose the path / the disk name in quotes if it contains spaces.
After expanding the virtual disk you have to resize the partitions inside the VM.
Different methods to do this are described at vmware-land.com (thanks to Eric Siebert).

Q: I read about the "pathname" bug. How do I detect if my VMs are affected?
A: If you use disks with external descriptor files you can simply check the descriptors for absolute paths. If you use monolithicSparse disks you either have to use a HEX editor or use a tool like ddtget (available at sanbarrow.com) to extract the descriptor. There are however scenarios (like linked clones) where absolute paths inside the descriptor are totally valid.

Example of a snapshot descriptor with the "pathname" bug

# Disk DescriptorFile
version=1
CID=83b169c0
parentCID=83b169c0
createType="monolithicSparse"
parentFileNameHint="C:\VMs\test.vmdk"

# Extent description
RW 2097152 SPARSE "test-000001.vmdk"


# The Disk Data Base 
#DDB

ddb.toolsVersion = "0"

the correct descriptor should look like this

# Disk DescriptorFile
version=1
CID=83b169c0
parentCID=83b169c0
createType="monolithicSparse"
parentFileNameHint="test.vmdk"

# Extent description
RW 2097152 SPARSE "test-000001.vmdk"

# The Disk Data Base 
#DDB

ddb.toolsVersion = "0"

Q: I want to commit/remove a snapshot, how much free disk space do I need?
A: This depends on the disk type you use. If you use monolithicSparse disks (the default) you need up to as much free space as the disk can grow.
If you use split disks you need 2Gb of free space.

Q: I want to commit/remove a snapshot, but the Snapshot Manager won't let me. Is there a workaround?
A: If you want to get rid of a snapshot WITHOUT committing the data to the base disk do the following:
- close VMware Workstation
- open the VMX file in an editor and modify the disk entry pointing it to the base disk
Example:

ide0:0.fileName = "test-000001.vmdk"

would become

ide0:0.fileName = "test.vmdk"

If you want to commit the data to the base disk you can use vmware-vdiskmanager to convert the disk. Close VMware Workstation first.
Example: suppose we have a disk test.vmdk with a snapshot test-000001.vmdk (this disk is a monolithicFlat disk).
To commit the changes to the disk we first have to convert the disk to another disk format, the following command converts the disk (including the snapshot) to a monolithicFlat disk named newtest.vmdk.

vmware-vdiskmanager -r test-000001.vmdk -t 0 newtest.vmdk

Now you have to modify the VMX file and modify the disk entry to point to newtest.vmdk.
The last step is to remove any snapshot related files (vmem, vmsn and vmsd). For safety reasons move the files to another folder instead of deleting them!
If the VM successfully starts you can remove the original disk, the snapshot.
Make a backup first before using the above approach!

Q: I want to shrink the disk, how much free diskspace do I need?
A: This depends on the disk type you use. If you use monolithicSparse disk (the default) you need up to as much free space as the disk can grow.
If you use split disks you need 2Gb of free space.

Q: I'm running out of disk space, what shall I do?
A: Most people run into this problem when either using sparse disks or when using snapshots.
First make a backup! Then you need to get some more free disk space in the hosts file system. If this is not possible copy the VM to another temporary storage (for example an USB disk) but make sure that the VM is not affected by the "pathname" bug (see above).
If after the clean-up the VM works again - fine. If not read What to do in moments of crisis and post in the VMware Workstation forum and provide as much information as possible.

Q: What are the pros and cons of the different disk types?
A: Here's a table

VMware name	no of files	max file size	external descriptor file	Description
monolithicSparse	1	950Gb	no	This is a growing disk in one piece - the only disk type that uses no external descriptor but an embedded one
monolithicFlat	2	950Gb	yes	This is a pre-allocated disk in one piece
twoGbMaxExtentSparse	1+x	2Gb	yes	this is a growing disk split into 2Gb chunks
twoGbMaxExtentFlat	1+x	2Gb	yes	this is a preallocated disk split into 2Gb chunks

Disks split into 2Gb chunks are a lot easier to handle. Many filesystems and tools have problems with files larger 2Gb!
Another drawback of monolithic disks is their free space requirements during shrink and snapshot operations.
A more detailed comparison of virtual disk types is available at sanbarrow.

Q: Is it a good idea to use monolithicSparse disks?
A: No. Since monolithicSparse disks use an embedded descriptor they are hard to repair. Another drawback is that they need a lot of free disk space during snapshot or shrink operations.

Q: Is there a performance difference between the different disks?
A: No - at least it is not noticeable.

Q: So which disk type should I use?
A: If you are concerned about disk space use twoGbMaxExtentSparse disks else use twoGbMaxExtentFlat disks.

Q: Help! My VM is broken and I need to recover the data.
A: First read this What to do in moments of crisis, then post in the VMware Workstation forum and provide as much information as possible.
Sanbarrow has a page with common problems and suggested procedures.. These are meant for advanced / experienced users!

Q: I've heard about RAW disks. Shall I use them?
A: Since it is easy to completely "mess up" the disk - don't use RAW disks unless you are an experienced user and you know what you are doing!

Networking

Q: Why does my guest operating system report that it is connected at 10Mbps even though I have a 100Mbps or 1000Mbps network adapter in my host computer?
A: http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=856

Q: My guests can't see the host or can't communicate with the network, networking is set to bridged, Host O/S is Windows 2003 SP2
A: If your host is running Windows 2003 SP2, you will want to try disabling TOE and assoicated settings:
See the MS KB article 912222 for commands / registry entries to modify (i.e. EnableTCPChimney etc...)

Q: My host OS is Windows Server 2003. I can't copy big files from guest to the host using the bridged network connection.
A: On the host add the registry entry called "DisableDos" according to the "Method 2" of the Microsoft's KB898468 and reboot the host.

Q: There are different networking options (bridged, host-only and NAT) available. Which one should I use?
A: In short:
- use host-only if your VMs don't need to/should not (for example in an isolated test environment) communicate with other systems (besides the host)
- use NAT if your VMs don't provide services to other machines but need to access the network
- use bridged if your VMs provide services to other machines or if you have other "special" requirements
- use the "guest-only" networks vmnet2 - vmnet7 and vmnet9 to create closed environments. VMs connected to these networks will be able to communicate only with each other.

Q: The host has two (or more) NICs. Are there any precautions to take?
A: In this case you should disable automatic bridging and manually bridge the different host NICs to different vmnets. Otherwise you might get routing problems.

Q: Is it a good idea to modify the default settings of vmnet1 or vmnet8?
A: No.

Q: I've upgraded VMware Workstation and now my network settings are broken. Did I miss something?
A: Unfortunately the installer overwrites the old network settings.
On a Windows host you can save the settings using the following command

vnetlib -- export filename

and import them using

vnetlib -- import filename

On a Linux host the information is spread across a few files / folders
/etc/vmware/config, /etc/vmware/netmap.conf, /etc/vmware/vmnet1 and /etc/vmware/vmnet8

Thanks to Liz, continuum, devzero and saxa for contributing

How to set up Host networking

Tue, 02 Oct 2007 16:59:17 GMT

I am running Workstation 5.0. I have a Windows Server 2003 VM running on top of my host machine. The VM is running s "Server" application and the host is running the client. I have the VM set to host only, but I cannot figure out how I can get me client (running on the host machine) to talk to the Server VM. I have tried pinging the VM from the host machine using the IP address I get when I run an ipconfig on the VM, but it time out. Any help would be greatly appreciated.

Can't start virtual machine

Mon, 01 Oct 2007 13:05:56 GMT

I was installing software and drivers for a Verizon PC5750 card last Friday when my host machine locked up suddenly. When I restarted it and tried to restart my virtual machine, I got the attached error message. I have restarted my host several times, but I still get this error. I cannot find any reference to the error text in the knowlwdgebase.

I use this virtual machine to run Rockwell PLC and HMI programming software, so this problem has left me unable to do my job. I would warmly appreciate any tips anyone could give me on how to regain the ability to start this virtual machine.

I am running Workstation 6.0. I have attached my VMWare Workstation about box. I have downloaded 6.0.1, but I have not installed it yet.

Thanks,

Berend.

Vista (host) network slow with VMWare Desktop 6

Thu, 27 Sep 2007 17:45:34 GMT

I've been having file transfer and networking issues since installing VMWare Desktop 6 on Vista Ultimate. I tried all the typical things:

I disabled ‘Remote Differential Compression' with no success.
- Start>>Control Panel>>Programs and Features. Click on ‘Turn windows features on or off' on the left side of the screen. Unchecked ‘Remote Differential Compression'
Disabled auto tuning with
- netsh int tcp set global autotuninglevel=disable
Firewall services were already disabled and no firewall software installed
3 GB of RAM, so no paging to the page file

The only thing that resolved file transfer speeds, was to uninstall VMWare. Is there something that needs to be tweaked to make sure it works as expected? My specs on the host are: CPU Type Intel Pentium 4 531, 3000 MHz (15 x 200)

Motherboard Name Asus P5GDC Deluxe (3 PCI, 2 PCI-E x1, 1 PCI-E x16, 4 DDR DIMM, 2 DDR2 DIMM, Audio, Gigabit LAN, IEEE-1394)

Motherboard Chipset Intel Grantsdale i915P
System Memory 3200 MB

Network Adapter Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller

Network Adapter Realtek RTL8169/8110 Family PCI Gigabit Ethernet NIC

Video Adapter NVIDIA GeForce 6200 TurboCache(TM)

VMware Workstation 6.0.0.45731

This document was generated from the following thread: Vista (host) network slow with VMWare Desktop 6

Host in VMware 5.5 cannot play sound

Tue, 25 Sep 2007 09:33:22 GMT

Hello

I have installed the last version of VMware 5 on Windows XP SP2. In VMware, i installed Windows 2003 Standard OS and i also installed VMware Tool, but when i log on Windows 2003, only have BEEP sound and not appear Speaker on system tray.

Do i have install driver on Host in Vmware ??? Please tell me the solution.

How to use a VM from Workstation AND ESX

Sun, 23 Sep 2007 19:08:11 GMT

Tested on a Windows-host

1. set up a NFS-server
2. create VM in WS6 - use monolithicFlat disk- install something - don't install tools
3. create ESX-compatible descriptor
4. add NFS-export to ESX-datastore
5. create VM and add existing disk - use edited descriptor
6. run it

of course you can later use the same disk with workstation again.

#Disk DescriptorFile version=1 CID=e3ee6b90 parentCID=ffffffff createType="monolithicFlat" # Extent description RW 16777216 FLAT "flatbase-flat.vmdk" 0 #The Disk Data Base #DDB ddb.virtualHWVersion = "6" ddb.toolsVersion = "0" ddb.geometry.cylinders = "1044" ddb.geometry.heads = "255" ddb.geometry.sectors = "63" ddb.adapterType = "lsilogic"	#Disk DescriptorFile version=1 CID=7341dd22 parentCID=ffffffff createType="vmfs" #Extent description RW 16777216 VMFS "flatbase-flat.vmdk" #The Disk Data Base #DDB ddb.virtualHWVersion = "4" ddb.toolsVersion = "0" ddb.adapterType = "lsilogic" ddb.geometry.sectors = "63" ddb.geometry.heads = "255" ddb.geometry.cylinders = "1044"
Workstation-version	ESX-version

Has anybody else tested this ?

Seems to be a pretty fast way of deploying VMs to ESX

This document was generated from the following thread: How to use a VM from Workstation AND ESX

Read before posting questions

Sun, 23 Sep 2007 18:12:36 GMT

When you encounter a problem and need help, it's important that you give as much information as you can so others can diagnose what's wrong.
Remember that what may be obvious to you, sitting in front of your computer, may not be obvious to someone far across the internet.
However, before you report a problem, please be sure that you've read the release notes, the FAQ, the documentation, searched the forums, and searched the internet.
You might find the answer is readily available - searching first gets you the answer faster and keeps the forums less cluttered, making it easier to find things in the future.

Once you've done some preliminary searching and determined that it's not an easily-available solution, please include the following information with a request for help:

* What exact version of VMware Workstation.
* What is your host OS and include if it is 32-bit or 64-bit OS. If Linux include the exact Linux distribution and kernel version.
* What is the guest OS and include if it is 32-bit or 64-bit OS. If Linux include the exact Linux distribution and kernel version.

* How often you see the problem (e.g. all the time, sometimes, rarely, etc.), and if it had previously worked in the same setup (e.g. same virtual machine, same computer)
* What seems to trigger the problematic behavior
* If there are any conditions where it does work

If troubleshooting a network issue, please include the following additional information.

* Post the output from "ipconfig /all" (Windows) or " ifconfig -a" (Linux) from both the host and the guest OS
* Post the .vmx file from the virtual machine.
* Details of how your host is connected to the network / Internet (Cable Modem, DSL, Router, Switch, Wired, Wireless,...).
* Details on how networking is configured for the guest (NAT, bridged, host-only).

If troubleshooting a disk issue , please include the following additional information.

* Post the .vmx file from the virtual machine.
* Post the vmware.log file located in the VM folder.
* Post a complete directory listing of the VM folder, including file sizes (preferably in bytes).

This is not an exhaustive list of useful information - if you have more details that you think are relevant, be sure to include them.

Etiquette

Sometimes there are multiple causes with the same symptoms, so unless you have the exact same setup as someone else, it's not usually useful to just chime in with "Same for me!" - at the very least, specify any differences (for example, Workstation 6.0 vs. 6.0.2, XP SP1 vs. XP SP2, etc.).

Don't use terminology or abbreviations you're not completely sure of; even then, be aware that context matters. For example, BT might mean "BlueTooth" to you, but to someone else it might mean VMware's "Binary Translation" technique. "VRAM" might make sense to you as "Virtual RAM", but most people would think "Video RAM". Being explicit helps people understand what you're talking about, which is necessary for them to help you.

Don't use ALL CAPS or lots of punctuation!!!!! - this is annoying and makes posts harder to read. Also, since most posts are questions, it's redundant to say "Need Help!" or similar in the subject.

After someone answers your question, it's nice to recognize their contribution with "correct" or "helpful" points. These points affect user rankings, which can be seen as a very rough guide to people who post a lot of answers to questions. Note this is not a perfect guide - some people with low rankings are very useful/knowledgeable and may contribute in ways that don't generate points, or just don't post as often.