Home

Documentation

VM-Sickbay

MOA

News

About

VMX-file parameters
Welcome - this is the Xth version of the introduction to the vmx-file list. Before you complain: this is incomplete, out-dated, full of errors, completely unsupported, dangerous ... Warning: sometimes this list is in contradiction to the VMwaredocumentation - but I guess that can't be helped

the shorter the better

Most of the times shorter vmx-files are better than long ones ;-) Don't use parameters just because they were listed once in a vmx-file created with vmxbuilder or easyvmx or Workstation. These 3 tools usually write quite good vmx-files - anyway: homegrown is the best ;-)

Basics

Experts Advanced virtual hardware settings:

bios cdrom chipset disklib hard-disk pcisound svga keyboard

Introduction
Starting small - minimal vmx-file Files used by a VM What's new in Workstation 6 ?

Commented parameters for the virtual hardware:

CD-settings Network Floppy-drives IDE Parallel ports RAM SCSI Serial ports Sound USB port

Advanced interaction with the host:

powerTyp priority isolation.tools mks (mouse, keyboard, screen) uuid msg guest.commands

Advanced setup of the host:

host mainMem monitor_control vmx hypervisor

Commented parameters for behaviour of the VM:

Guest operating system Displayname Logging GUI Movies

Server related settings:

remoteDisplay sched

Advanced guides:
Assigning PCI-slots: expect the unexpected Translating Linux - Windows - ESX Undoable mode for current VMserver The 3 different Virtual-Hardware-modes Configure the start date and time for a VM updated 3 man in a boat (more than one VM in one directory)

Snapshot handling:
snapshot checkpoint undopoint

GUI - VMX translation:

GUI > Edit > Preferences NEW Config.ini - used to configure host-wide settings (GUI) Preferences.ini - user-settings and autogenerated VM-list

Dangerous parameters:
Don't-touch-list uncommented list of device parameters

Trouble-shooting:
just starting this lists so they are very short at the moment Netware FreeBSD Windows

Examples:
ESX 3.0.* in a WS 6 VM

Syntax
You can use # for comments. The sequence of line doesn't matter. Parameters with *.present work like a main-switch. If parameter scsi0.present is activated every parameter in the sub-category is used. So if you have scsi0.present = "TRUE" then lines like scsi0.virtualDev = "lsilogic" are used. If you have scsi0.present ="FALSE" all lines starting with scsi0 are ignored. What happens if you use unknown or mis-spelled lines? A line like zoo.number_of_elefants = "387" causes an error-message and VMware-player will not start - this doesn't mean that there are no VMversions that count the number of elefants. Maybe a future version will ignore this line or even use it. So don't count on it. Better go with the rule: Unknown or mis-spelled lines are ignored or give error-messages.

1 of 2

Memory
You can change the amount of RAM that a VM will use like this memsize = "128" If you don't assign a value for memory VMware will use the default-setting which is 32MB memsize = "32" Whenever you assign RAM manually make sure the value is a multiple of 4 - otherwise the VM will not start: memsize = "255" causes this error-message: Memory size 255 not a multiple of 4

Displayname
You can assign a displayname for your virtual machine by adding displayName = "VMX-Test" If you don't assign a nicname VMware will autogenerate one- useing the path and name of the vmx-file displayName = "X:\home\moon\Desktop\vmx.sammler\minimal.vmx"

Movies
You may try to add this to your config.ini to enable sound in the recorded videos: mks.movie.config.high.recordSound = "TRUE"

Note for webmasters

Please don't simply copy any of the vmx-pages. I have invited VMware to cooperate - I offered to skip the dangerous parameters in exchange for information on useful parameters. By the way, the "Don't touch list" is the first result of this "cooperation" - I guess I don't need to mention that I didn't received any information on useful parameters in turn ... As long as the vmx-documentation can be found at one place - I see a small chance that VMware accepts my invitation. If this stuff is scattered all over the net VMware has a good reason to ignore my offer. So if you run a site about virtualisation and are interested in improving the vmx-documentation: link here - don't copy. Thanks Ulli Hankeln

home

vmx

vmdk

about this site

forum

downloads

2 of 2

home

vmx

vmdk

about this site

forum

downloads

What's new in Workstation 6 / VMplayer 2

VMX-file parameters

virtualHW.version = "6" config.version = "8" virtualHW.productCompatibility = "hosted" or "esx"

used for WS 6 and VMplayer 2 If you use "esx" this will disable IDE-disks and USB-devices

pciBridge0.present = "TRUE" pciBridge1.present = "TRUE"

To get more than the 6 PCI-slots you need to enable one or more PCI-bridges. Adding one should be enough in most cases.

*.pciSlotNumber = "17" *.pciSlotNumber = "-1"

inWS 6 you can set the PCI-slot for PCI-cards. Valid slotnumbers are 16-20 and 32-60. The SVGA is hardcoded to use slot 15. The first SCSI-controller should use slot 16. A value of "-1" means: take the next free slot

home

vmx

vmdk

about this site

forum

downloads

1 of 1

home

vmx

vmdk

about this site

forum

downloads

a minimal vmx-file
VMX-file parameters
A very short vmx-file only needs 3 lines - I call them the identity-lines. This minimal vmx is enough to start a VM. It is the equivalent of starting a legacy-real-metal box with nothing more than the main-board with 32MB RAM and one CPU plugged in.

If you forget one of this critical parameters or misconfigure it the VM will not start and give an error-message. guestOS = "dos 397" causes an error-message Guest operating system `dos 397' is not supported Available choices for "guestOS" VMplayer 2.* Workstation 6.5 VMserver 2 ESX 4 VMplayer 2.* Workstation 6.* VMplayer 1.* Workstation 5.* VMserver 1.* ESX 3 Workstation 4.5* ESX 2.5

config.version = "8" virtualHW.version = "7" guestOS = "winxppro" config.version = "8" virtualHW.version = "6" guestOS = "winxppro" config.version = "8" virtualHW.version = "4" guestOS = "winxppro" config.version = "6" virtualHW.version = "3" guestOS = "winxppro" config.version = "6" virtualHW.version = "2" guestOS = "winxppro"

Workstation 3.* GSX 2.5*

advanced settings for the virtual hardware

Handle with care - this will case serious changes. Don't use if you do not understand the consequences this may cause. Please read: Undoable mode for current VMserver The 3 different Virtual-Hardware-modes

config.version = "6" virtualHW.allowVeryOldVersion = "TRUE"

GrandPa-mode - see Undoable mode for current VMserver The 3 different Virtual-Hardware-modes

virtualHW.productCompatibility = "hosted" virtualHW.productCompatibility = "esx"

no need to set this - it will be automatically set

virtualHW.atLeastESX31 virtualHW.atLeastWS20 virtualHW.atLeastWS30 virtualHW.atLeastWS40 virtualHW.atLeastWS50 virtualHW.atLeastWS60 virtualHW.future virtualHW.latest virtualHW.supportPartialWS6 virtualHW.wasVersioned

Workstation 6 only

home

vmx

vmdk

about this site

forum

downloads

1 of 1

home

files used by a VM
Short description of the files that are used by virtual machines (applies to VMplayer, VMserver and Workstation 5.5) needed when VM is moved yes yes yes text binary

File-extension

type

size

content

*.vmx *.vmdk *.vmdk

1-4 kb 1-4 kb can be very large maximum 950Gb can be very large

main configuration file virtual disk descriptorfile virtual disk of type monolithic-sparse this file contains the changes since snapshot X non volatile RAM: contains current settings of the virtual BIOS this file only exists if you use mainMem.useNamedFile = "true" this extension is used for the data chunks of growing-split disks this file contains the changes since snapshot X this extension is used for the data chunks of preallocated-split disks this file contains the changes since snapshot X this extension is used for the data chunk of preallocated monolithic disks this file contains the changes since snapshot X contains current snapshotdata like nvram and a copy of the vmx-file example

*0000000*.vmdk

yes

binary

*.nvram

no

binary

8 kb

*.vmem

no

binary

nominal RAM

*s00*.vmdk

yes

binary

can be very large maximum 2Gb

*0000000*-s00*.vmdk

yes

binary

can be very large maximum 2Gb

*f00*.vmdk

yes

binary

can be very large maximum 2Gb

*0000000*-f00*.vmdk

yes

binary

can be very large maximum 2Gb

*flat.vmdk

yes

binary

can be very large maximum 950Gb

*0000000*-flat.vmdk

yes don't move if present don't move if present don't move if present only appears with running VMs only appears with running VMs

binary

can be very large

*.vmsn

binary

varies

*.vmsd

text

varies

descriptorfile for current snapshot

*.vmss

binary

nominal RAM

contains RAM of a suspended VM

*.REDO_a03180

binary

can be very large

this file is used when a disk is in "independent-nonpersistent" mode

*lck

very small

lockfile - is used to lock files that are currently in use

back to startpage |

about this site |

forum

1 of 1

home

moa

vmx

vmdk

links

about

donate

forum

downloads

CD-rom settings
VMX-file parameters

You got more or less 4 different options to use CDs: iso-file atapi-cdrom - this is the legacy mode offered by the GUI cdrom-raw connected as IDE cdrom-raw connected as SCSI
ide1:0.present = "true" ide1:0.deviceType = "cdrom-image" ide1:0.filename = "myiso.iso" ide1:0.startConnected = "TRUE" This settings allow to boot from the CDrom. The device will be detected as a VMware CDrom. This settings are the ones that work troublefree. Device is detected as:NECVMWar_VMware_IDE_CDR10 This mode will detect a VMware CDrom and use a real CDrom drive of your host. Specify which device to use by giving the driveletter on Windows-hosts. This settings will allow booting from CDrom. Failsafe option when you need to use a physical CDrom Device is detected as:NECVMWar_VMware_IDE_CDR10 This mode will detect a VMware CDrom and use a real CDrom drive of your host. Specify which device to use like /dev/hdc on Linux This settings will allow booting from CDrom. Failsafe option when you need to use a physical CDrom Device is detected as:NECVMWar_VMware_IDE_CDR10 This mode will detect the CDrom like it is detected by your host. You can specify which device to use by giving the driveletter on Windows-hosts. This settings will allow booting from CDrom. This mode will detect the CDrom like it is detected by your host. You can specify which device to use by useing the Linux-device name like /dev/hdc This settings will allow booting from CDrom. This mode will detect the CDrom like it is detected by your host. You can specify which device to use by giving the driveletter on Windows-hosts. This settings will not allow booting from CDrom - but it can be used for CD-writing.

ide1:0.present = "true" ide1:0.deviceType = "atapi-cdrom " ide1:0.filename = "E:" ide1:0.startConnected = "TRUE"

ide1:0.present = "true" ide1:0.deviceType = "atapi-cdrom " ide1:0.filename = "/dev/hdc" ide1:0.startConnected = "TRUE" ide1:0.present = "true" ide1:0.deviceType = "cdrom-raw" ide1:0.filename = "E:" ide1:0.startConnected = "TRUE" ide1:0.present = "true" ide1:0.deviceType = "cdrom-raw" ide1:0.filename = " /dev/hdc" ide1:0.startConnected = "TRUE" scsi0:0.present = "true" scsi0:0.startConnected = "TRUE" scsi0:0.deviceType = "cdrom-raw" scsi0:0.filename = "E:"

Additional settings ide1:0.startConnected = "TRUE" This parameter defines wether you want the device connected at boot-time - for performance reasons set to "false" as soon as possible! ide1:0.exclusive = "TRUE" This parameter defines wether you want to use the device exclusicely by one VM only. It only makes sense if you don't use Isos. Don't use unless there is no way around it. ide1:0.autodetect = "TRUE" You can use autodetect instead of giving the driveletter - but I don't recommend this - it's always cleaner if you assign the device like you want it to be assigned. In case you have problems with detecting daemon-tools or other virtual CD-drives better specify the device you want to use. ide0:0.allowGuestConnectionControl = "TRUE" Use to allow control via the vmware-tools from within a guest. Server only ide1:0.clientDevice = "TRUE" Use this to connect Isos from a remote host. Looks like current VMserver silently implies ide1:0.startConnected = "false" when he uses a client device ??? Warning Don't switch from 'raw-device/cdrom-raw' to any of the other settings without thought , as this may also mean that you need different drivers inside your guest. This may even cause a necessary Reactivation in XP.

1 of 2

Generally speaking try to use Isos whenever possible - as this is the option that uses the smallest amount of host-resources. Disconnect Isos or CDroms whenever you don't need them anymore.
about this site forum

2 of 2

home

vmx

vmdk

about this site

forum

downloads

Network settings
VMX-file parameters
Basically you got 12 different options to set up a virtual network-card: Why 12 ? - well you have 4 different connection types and 3 different "vendors" for your virtual network card. For a first start of a VM you only need one of the twelve blocks listed below. All other parameters are assigned automatically on first start of the VM so you do not need to specify them. Which one do I need ? - first select the connection type and then select an appropriate "Vendor" "bridged" connects to an automatically assigned physical nic "hostonly" connects to the virtal adapter of the host named "hostonly" "nat" connects to the virtal adapter of the host named "nat" - allows to use the internet-connection of the host "custom" - use for non-defaults setups on hosts with more than one nic or when ever you want to connect guests only.

How to use this chart:

For a first configuration pick one of the twelve blocks listed below. All other parameters are autoconfigured at first start. Do not use any other parameters than just this 4 or 5 from the list below unless you really need to. For advanced trouble-shooting see the Advanced network settings

"Bridged" to an automatically assigned physical nic

WARNING: this is unreliable on hosts with more than one physical nic. ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "vlance" ethernet0.connectionType = "bridged" This settings enable an AMD PCnet32 network-card. Most older OS have drivers for this nic.

ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "vmxnet" ethernet0.connectionType = "bridged"

This settings enable an VMXnet network-card. You can only use this nic if you install the VMware-tools inside the guest.

ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "e1000" ethernet0.connectionType = "bridged"

This settings enable an Intel E1000 network-card. Modern OS should have drivers for this nic. NOTE: VMware usually assigns this nic to 64bit-guests - but it also works with 32-bit guests

Connected to the virtal adapter of the host named "hostonly"

You can use the VMware-builtin DHCP-service to auto-configure guests that use this type of connection. WARNING: this is unreliable on hosts that don't use defaults for the vmnet-mapping. NOTE: this is the same as ethernet0.connectionType = "vmnet1" ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "vlance" ethernet0.connectionType = "hostonly" This settings enable an AMD PCnet32 network-card. Most older OS have drivers for this nic.

ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "vmxnet" ethernet0.connectionType = "hostonly"

This settings enable an VMXnet network-card. You can only use this nic if you install the VMware-tools inside the guest.

ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "e1000" ethernet0.connectionType = "hostonly"

This settings enable an Intel E1000 network-card. Modern OS should have drivers for this nic. NOTE: VMware usually assigns this nic to 64bit-guests - but it also works with 32-bit guests

1 of 2

Connected to the virtal adapter of the host named "nat"

You can use the VMware-builtin DHCP-service to auto-configure guests that use this type of connection. Guests configured this way can also use the hosts internet connection via the VMware NAT service. WARNING: this is unreliable on hosts that don't use defaults for the vmnet-mapping. Note: this is the same as ethernet0.connectionType = "vmnet8" ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "vlance" ethernet0.connectionType = "nat" This settings enable an AMD PCnet32 network-card. Most older OS have drivers for this nic.

ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "vmxnet" ethernet0.connectionType = "nat"

This settings enable an VMXnet network-card. You can only use this nic if you install the VMware-tools inside the guest.

ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "e1000" ethernet0.connectionType = "nat"

This settings enable an Intel E1000 network-card. Modern OS should have drivers for this nic. NOTE: VMware usually assigns this nic to 64bit-guests - but it also works with 32-bit guests

Custom configuration
For multihomed hosts specify your physical > vmnet mapping manually and configure your guests with type "custom" All unused vmnets can be used for "guest-only" connections. WARNING: on Linux hosts that use UDEV you may have to create device-nodes manually. ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "vlance" ethernet0.connectionType = "custom" ethernet0.vnet = "vmnet5" ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "vmxnet" ethernet0.connectionType = "custom" ethernet0.vnet = "vmnet5" ethernet0.present= "true" ethernet0.startConnected = "true" ethernet0.virtualDev = "e1000" ethernet0.connectionType = "custom" ethernet0.vnet = "vmnet5" This settings enable an AMD PCnet32 network-card. Most older OS have drivers for this nic.

This settings enable an VMXnet network-card. You can only use this nic if you install the VMware-tools inside the guest.

This settings enable an Intel E1000 network-card. Modern OS should have drivers for this nic. NOTE: VMware usually assigns this nic to 64bit-guests - but it also works with 32-bit guests

about this site

forum

2 of 2

home

vmx

vmdk

about this site

forum

downloads

floppy settings
VMX-file parameters
You got more or less 4 different options to use floppiess: best choice: use a floppy-image not connected at boot-time - this doesn't block resources and leaves all options

floppy0.present = "true" floppy0.fileName = "start.flp" floppy0.fileType = "file" floppy0.startConnected = "true"

If you boot from a floppy this is your best options - only in some rare cases like slackwareboot-floppies that use an unusual size like 1.77MB this will not work. Floppy images can be 1.44MB or 2.88MB - I was able to use 11.52MB images but this may change with different versions. For performance reasons disconnect as soon as possible. Floppy-images boot almost as fast as virtual hard-disks. Forget all your prejudices against slow, loud, old-fashioned real floppy-drives !!!

floppy0.present = "true" floppy0.autodetect = "TRUE" floppy0.startConnected = "true" floppy0.fileType = "device"

This mode will try to auto-detect a physical device. I never use this mode ...

floppy0.present = "true" floppy0.startConnected = "true" floppy0.autodetect = "false" floppy0.fileName = "A:" floppy0.fileType = "device"

This mode will use a physical drive of your host. You can specify which device to use by giving the driveletter on Windows-hosts. This setting allows booting from Floppy. Failsafe option when you need to use a physical Floppy

floppy0.present = "true" floppy0.startConnected = "true" floppy0.autodetect = "false" floppy0.filename = "/dev/fd0" floppy0.fileType = "device"

This mode will use a physical drive of your host. You can specify which device to use by useing the Linux-device name like /dev/fd0 This setting allows booting from Floppy. Failsafe option when you need to use a physical Floppy

floppy0.allowGuestConnectionControl = "true" floppy0.clientDevice = "TRUE" floppy.minVirtualTime

Use to allow control via the vmware-tools from within a guest. use to select an image on a remote-host - (VMserver)

old fix - no longer required - see kb

floppy0.changeTimeout floppy0.trackCache floppy.synchronous floppy.raw.aiomgr floppy.minVirtualTimeReadID floppy.image.aiomgr floppy.force144mb floppy.asyncTimeout floppy.aiomgr

Don't use unless you know what you are doing!

floppy0.present = "TRUE" floppy0.fileName = "newly-created.flp" floppy0.fileType = "file" floppy0.startConnected = "TRUE"

WARNING: don't use a newly created - unformatted floppy-image like this: your VM might hang for a very long time.

home

vmx

vmdk

about this site

forum

downloads

1 of 1

home

vmx

vmdk

about this site

forum

downloads

ide settings
VMX-file parameters

ide0:0.present = "TRUE" ide0:0.deviceType = "disk" ide0:0.filename = "aunt-lindas-favorite-sausage-ide00.vmdk"

This is a nice entry for a disk - relative path - no spaces name describes contents: perfect! If the filename points to a *.vmdk you can skip the device type

ide0:0.present = "TRUE" ide0:0.deviceType = "cdrom-image" ide0:0.filename = "weird-os-install.iso"

This connects an iso-file as a CDrom.

ide0:0.startConnected = "TRUE"

Silent default when *.present is set to true if you don't want that CDs or ISOs are connected at boot-time you have to add this. Don't use with virtual disks

ide0:0.startConnected = "FALSE"

ide0:0.deviceType = "disk" ide0:0.deviceType = "rawDisk" ide0:0.deviceType = "ata-hardDisk" ide0:0.deviceType = "cdrom-image" ide0:0.deviceType = "atapi-cdrom" ide0:0.deviceType = "cdrom-raw"

only set deviceType when you need a CD/ISO. "disk" usually appears when you swapped a CDrom and a vmdk.

ide0:0.autodetect = "TRUE"

Use this for CDroms only - I don't recommend to use this entry at all - as it produces unpredictable results on hosts with more than one CDrom. If you have problems with Virtual CD-drives like Daemon Tools - check this first.

ide0:0.filename = "E:" ide0:0.filename = "dev/hdc" ide0:0.filename = "weird-os-install.iso" ide0:0.filename = "system.vmdk"

Depending on the device type you selected one of this entries is appropriate. instead of using autodetect you can also give the driveletter or device-name

ide0:0.mode = "independent-persistent"

This mode makes a vmdk behave like a good-old-real-metal harddisk. If you accidentaly format it, the only way to restore your files is the use of forensic tools. All changes are written to the vmdk directly and the disk will not be included in snapshots.

ide0:0.mode = "independent-nonpersistent"

This mode writes all changes to a temporary file which will be deleted when you power off the virtual machine. The temporary files are named like this 2k-ide-system.vmdk.REDO_a02144 Obviously this setting makes no sense for a brand new VM. Disks useing this mode are not included in snapshots.

ide0:0.mode = "undoable"

WARNING: for experts only This mode writes all changes to a temporary file. This time the file will not be deleted when you power off the virtual machine. The temporary file are named like this 2k-ide-system.vmdk.REDO_a02144 Current VMserver doesn't offer this mode via GUI - though he can use it. Be very careful with this mode: this is not the mode used for snapshots! Snapshots nowadays are created per VM - the REDOlogs created by the 'undoable mode' are created per disk. Never use this in combination with a snapshot !!! At first sight this mode looks like the one we had in WS 3 and GSX 2.5 - but you can not commit/ discard/ keep these REDOlogs when you power down a VM with current VMserver. To commit or discard these REDOs you need a special hack that should be used by experts only ...

1 of 2

ide0:0.dmaCapable ide0:0.forcelba48 ide0:0.noDMA

I use them in case I want to use very old guests - early Dos for example. Be careful - may have strange and un-expected side-effects.

home

vmx

vmdk

about this site

forum

downloads

2 of 2

Sanbarrow.com

VMX-file parameters - parallel ports

Home MOA Live CD VMX Exotic Guests Links Forum

Introduction Parameters for max 3 parallel ports

parallel ports parallel0.present

value true or false

type switch

usage main switch

parallel0.startConnected parallel0.autodetect parallel0.fileType parallel0.bidirectional

true or false true or false file or device true or false

switch switch switch switch

true connects device at startup use to autodetect host device

enable or disable biderctional mode - doesn't work with files

parallel0.allowGuestConnectionControl

true or false

switch

true allows control via vmware-tools

parallel0.present parallel0.fileType parallel0.fileName parallel0.present parallel0.bidirectional parallel0.fileType parallel0.present parallel0.bidirectional parallel0.fileType parallel0.present parallel0.bidirectional parallel0.fileType parallel0.fileName

true file parport2txt.txt true true device true false device true true device LPT1

switch switch switch file or device switch switch switch switch switch switch switch switch switch switch switch switch file or device this settings use host-device LPT1 the device will start connected this settings use a automatically detected host-device the device will start connected the device does not use bidirectional mode this settings use a automatically detected host-device the device will start connected the device uses bidirectional mode this settings use a textfile "parport2txt.txt" for the output the device will start connected

parallel0.startConnected true

parallel0.startConnected true

parallel0.startConnected true

parallel0.startConnected true

Home
Ulli Hankeln - mail to webmaster at sanbarrow dot com

Top

1 of 1

home

vmx

vmdk

about this site

forum

downloads

scsi settings
VMX-file parameters
scsi-controller device is a virtual disk - example device is a virtual cdrom - examples parameters for virtual disks parameters for CD-roms

scsi-controller
scsi0.present scsi1.present scsi2.present scsi3.present = = = = "true" "true" "true" "true"

"MAIN-SWITCH" for up to 4 virtual SCSI-controllers

scsi0.virtualDev = "buslogic" scsi0.virtualDev = "lsislogic"

Use "buslogic" for old guests - "lsilogic" for modern guests as a rule of thumb. Warning: this parameter depends on the settings for "guestOS" In Workstation 6 you also need to specify the PCI-slot-number. Don't change default slot "16" for the first SCSI-controller. For a first start of a VM "-1" means assign the slot automatically

scsi0..pciSlotNumber = "16" scsi1..pciSlotNumber = "-1" scsi2..pciSlotNumber = "-1" scsi3..pciSlotNumber = "-1"

scsi0.returnBusyOnNoConnectStatus scsi0.sharedBus scsi0.unsafeReordering

advanced ...

top

parameters for virtual disks

scsi0:0.fileName = "system.vmdk" scsi0:0.mode = "persistent" scsi0:0.mode = "undoable" scsi0:0.mode = "nonpersistent" scsi0:0.deviceType scsi0:0.deviceType scsi0:0.deviceType scsi0:0.deviceType scsi0:0.deviceType scsi0:0.deviceType scsi0:0.deviceType scsi0:0.deviceType = = = = = = = = "plainDisk" "PhysicalDrive0" "rawDisk" "scsi-hardDisk" "scsi-passthru" "scsi-nonpassThru-rdm" "scsi-passthru" "scsi-passThru-rdm" path to vmdk - avoid absolute paths

controls how a virtual disk is affected by snapshots WARNING: don't set this parameter unless you know what you are doing

don't set this manually !

device is a virtual disk - example

scsi0:0.present = "TRUE" scsi0:0.fileName = "scsi.vmdk"

required to add a virtual scsi-hard-disk for a new virtual machine

advanced settings for virtual disks

scsi0:0.RESLCK scsi0:0.shared scsi0:0.writeThrough top

1 of 2

parameters for cdroms

scsi0:0.fileName = "install.iso" scsi0:0.filename = "E:" scsi0:0.filename = "/dev/hdc" scsi0:2.fileName = "auto detect" scsi0:0.deviceType = "cdrom-image" scsi0:0.deviceType = "atapi-cdrom" scsi0:0.deviceType = "cdrom-raw" scsi0:0.allowGuestConnectionControl scsi0:0.autodetect = "true" scsi0:0.clientDevice scsi0:0.exclusive = "true" scsi0:0.startConnected = "true"

path to iso-file, driveletter or device-name

Sets the number of the used vmnet. Only use with connection type "custom" also see additional notes allow control of device from with the guest (VMware-tools) autodetect a physical CDrom (unreliable) Server-versions only only this VM may use this physical CDrom (don't use unless you need to) device is connected at bootup of VM

device is a cdrom - examples

scsi0:0.present = "TRUE" scsi0:0.deviceType = "cdrom-image" scsi0:0.fileName = "install.iso"

required to add an ISO as a virtual scsi-CDrom

scsi0:0.present = "true" scsi0:0.startConnected = "TRUE" scsi0:0.deviceType = "cdrom-raw" scsi0:0.filename = "E:"

required to add a real CDrom as a virtual scsi-CDrom. Windows-host: driveletter is E: in this example

scsi0:0.present = "true" scsi0:0.startConnected = "TRUE" scsi0:0.deviceType = "cdrom-raw" scsi0:0.filename = "/dev/hdc"

required to add a real CDrom as a virtual scsi-CDrom. Linux-host: decive used is /dev/hdc in this example

scsi0:2.autodetect = "TRUE" scsi0:2.deviceType = "cdrom-raw" scsi0:2.fileName = "auto detect" scsi0:2.present = "TRUE"

required to add a real CDrom as a virtual scsi-CDrom. Autodetected device: warning - this is unreliable

top

advanced settings for the controller

scsi.buslogic.available scsi.EnableBIOS scsi.lsilogic.available scsi.passthru.aiomgr scsi.passthru.logging scsi.passthru.logmaxdata

top

home

vmx

vmdk

about this site

forum

downloads

2 of 2

home

vmx

vmdk

about this site

forum

downloads

serial ports
VMX-file parameters
uncomplete ... you can use max 4 serial ports

serial0.present = "TRUE" serial0.fileType = "device" serial0.fileName = "/dev/ttyS0 " serial0.tryNoRxLoss = "FALSE" serial0.autodetect = "FALSE" serial0.present = "TRUE" serial0.fileType = "device" serial0.fileName = "COM1" serial0.tryNoRxLoss = "FALSE" serial0.autodetect = "FALSE" serial0.present = "TRUE" serial0.fileType = "device" serial0.tryNoRxLoss = "FALSE" serial0.autodetect = "TRUE" serial0.present = "TRUE" serial0.fileType = "file" serial0.fileName = "serial-port-2-file.txt" serial0.tryNoRxLoss = "FALSE" serial0.present = "TRUE" serial0.fileType = "pipe" serial0.fileName = "\\.\pipe\com_1" serial0.tryNoRxLoss = "TRUE" serial0.pipe.endPoint = "server" serial0.present = "TRUE" serial0.fileType = "pipe" serial0.fileName = "\\.\pipe\com_1" serial0.tryNoRxLoss = "FALSE" serial0.pipe.endPoint = "server" serial0.present = "TRUE" serial0.fileType = "pipe" serial0.fileName = "\\.\pipe\com_1" serial0.tryNoRxLoss = "TRUE" serial0.pipe.endPoint = "client" serial0.present = "TRUE" serial0.fileType = "pipe" serial0.fileName = "\\.\pipe\com_1" serial0.tryNoRxLoss = "FALSE" serial0.pipe.endPoint = "client"

Linux-host useing physical device /dev/ttyS0

Windows-host useing a physical device com1

this settings use an autodetected host-device

this settings use the file "serial-port-2-file.txt"

useing a named pipe this end is the server the other end is an application useing a named pipe this end is the server the other end is a VM useing a named pipe this end is the client the other end is an application useing a named pipe this end is the client the other end is a VM

serial0.present serial0.startConnected serial0.fileName serial0.fileType serial0.tryNoRxLos serial0.autodetect serial0.pipe.endPoint serial0.yieldOnMsrRead serial0.baseAddr serial0.irq serial0.allowGuestConnectionControl serial0.hardwareFlowControl = "TRUE"

main switch true connects device at startup

see examples for usage as they must be combined in a special way

yuild CPU on poll

use true to allow control via vmware-tools

1 of 2

home

vmx

vmdk

about this site

forum

downloads

2 of 2

home

vmx

vmdk

about this site

forum

downloads

sound
VMX-file parameters
I hardly ever use sound in a VM - that's why this section is a little bit neglected ;-) Related: pcisound-parameters Drivers: 2k, XP and 2k3 use Soundblaster PCI 128 which is no longer supported by Creative. Last seen here ... minimal (failsafe) example for a new VM bad example the parameters in details advanced example

drivers for win9x drivers for VISTA

minimal settings for a new VM

sound.autodetect = "TRUE" sound.fileName = "-1" sound.present = "TRUE" only this 3 lines are required to enable sound in a VM. Don't use additional entries unless you have to.

bad example
sound.present = TRUE sound.virtualDev = sb16 sound.filename = -1 sound.autodetect = TRUE sound.deviceNr = -1 sound.device = /dev/dsp Warning: errors in sound related settings often result in hard to track down problems do not use parameters just because they worked for someone else blindly !!! Look at this example - it will very likely crash your VM without indicating an obvious reason in the logs!

the parameters
sound.present = "true" sound.startConnected = "true" sound.allowGuestConnectionControl = "true" sound.virtualDev = "sb16" sound.virtualDev = "es1371" sound.autodetect = "true" sound.fileName sound.fileName sound.fileName sound.fileName sound.fileName sound.fileName sound.fileName = = = = = = = "Creative SB Live! Series" "Creative Sound Blaster PCI" "Crystal WDM Audio" "NVIDIA(R) nForce(TM) Audio" "SB Audigy 2 ZS Audio [A000]" "SoundMAX Digital Audio" "YAMAHA AC-XG WDM Audio" main-switch to enable sound enables sound at VM-start allow control via VMware-tools

all newer VMware-versions use the ES 1371 per default

VMware will detect the appropriate sound device automatically

If VMware finds a sound-device that can be used it sets appropriate value automatically "-1" means assign automatically

sound.fileName = "-1" sound.synth.operational = "true" sound.baseAddr = "0x220" sound.dma16 = "7" sound.dma8 = "1" sound.irq = "5" sound.mpu401baseAddr = "0x330" sound.Opl3BaseAddr = "0x388" sound.maxLength = "value" sound.smallBlockSize = "value" sound.disableMasterVolume sound.highPriority set to "true" to enable OPL3 / Yamaha synthesizer AFAIK this only works with "sb16"

try these settings to enable sound with DOS 6.2.2

use with values like 2 64 128 256 512 1024 see KB 617 for info see KB 853 Linux - see KB 1219

1 of 2

sound.baseAddr = "0x220" sound.dma16 = "7" sound.dma8 = "1" sound.irq = "5" sound.mpu401baseAddr = "0x330" sound.Opl3BaseAddr = "0x388" sound.buffering sound.copyDelayFactor sound.device sound.deviceNr sound.devNr sound.directSound sound.ignoreOverflows sound.logFragmentSize sound.mixer sound.virtualrealcorrection

try these settings to enable sound with DOS 6.2.2

sorry ???

advanced example
sound.virtualdev = "sb16" sound.present = "true" sound.autodetect = "true" sound.buffering = "10000000000.0" sound.copyDelayFactor = "1000000.0" sound.directSound = "false" sound.highPriority = "true" sound.ignoreOverflows = "true" sound.maxLength = "2048" sound.smallBlockSize = "1024" sound.virtualrealcorrection = "10000000000.0" pciSound.priorityBoost = "true" top

advanced example posted by andremachado

home

vmx

vmdk

about this site

forum

downloads

2 of 2

Sanbarrow.com

VMX-file parameters - usb ports

Home MOA Live CD VMX Exotic Guests Links Forum

Introduction Parameters for usb ports. Sorry - mostly unknown ground at the moment - any help is appreciated! First aid when ever USB behaves strange: Use a USB 1.1 hub and plug it between the device you want to run and your hosts USB 2 connector.
(Thanks to kingneutron and dmair.)

to automatically reconnect a USB-device read knowledgebase 1648

usb ports

value true or false

type

gui usage main switch

usb.present

switch x

usb.generic.autoconnect

true or false

switch x switch switch -

use true to automatically connect when guest has focus

usb.generic.resetOnDisconnect true or false usb.generic.allowHID usb.generic.devfsPath usb.generic.devicesFileName

true or false

path_to_usbdevfs path

see .../support/ws55/doc /ws_devices_usb_linux.html

usb.asapTransfer usb.autoConnect.device%d

usb.FrameLen usb.idleFrameLen usb.options usb.stickyConnect usb.ZeroBasedInterface

true or false

switch -

usb.analyzer.enable usb.generic.skipsetconfig

true or false

switch -

use true if you want extra verbose logging to debug USB problems skip the low-level USB "set configuration" command

true or false

switch -

uhci.syncWriteback

true or false

switch -

use for Dell 1450 Wireless USB adapter

uhci.intr.maxUrbs uhci.iso.buffers uhci.iso.maxIsoPackets uhci.newCore uhci.numPorts uhci.scanFrames uhci.simEOF uhci.syncWriteback

Home

Top

1 of 2

 Ulli Hankeln - mail to webmaster at sanbarrow dot com

2 of 2

home

vmx

vmdk

about this site

forum

downloads

guestOS
VMX-file parameters
What happens: Most obvious effect of the choice of a 'guestOs' is the 'VMware-tools-iso' that will be connected if you click the "Install VMware tools..." menu option. If your guest is a Linux you will get the linux.iso, if your guest is a Windows, you will get the windows.iso. When you selected 'other' the "Install VMware tools..." menu option is not available. The 'guestOS' choice also decides which virtual hardware is used: GuestOS = "winnt" sets scsi0.virtualDev = "BUS" GuestOS = "winNetEnterprise" sets scsi0.virtualDev = "LSI" Things like this can have unexpected effects when you try to upgrade a WinNT to Windows 2003! Generally speaking try to use the option that is the best match for the Os you want to install: for example to install OpenBSD or NetBSD use guestOs = "FreeBSD" The guestOS = "other" - option disables all optimizations and should be used when every other option has failed only.

List was created with VMserver P L A Y E R S l E default W W E etherE e S scsi install S S S net R g X virtual uses diskX install virtual V a device amount size 5 3 uses device E c 2 type of 5 2 3 type R y 5 RAM

guest operating system

gui-option comments

darwin dos freebsd freebsd-64 other other-64

Netware guests

x x x x x x x x x

(not available via GUI) IDE IDE LSI IDE IDE vlance vlance e1000 vlance e1000 BUS LSI LSI BUS LSI 16 256 256 256 256 MS-DOS Freebsd FreeBSD 64-bit Other Other 64-bit

netware4 netware5 netware6

Solaris guests

x x x x x

IDE IDE LSI

vlance vlance vlance

BUS LSI LSI

256 256 512

NetWare 4 NetWare 5 NetWare 6

solaris6 solaris7 solaris8 solaris9 solaris10 solaris10-64

Linux guests

x x x x x x x x

(not available via GUI) (not available via GUI) (not available via GUI) IDE IDE LSI vlance vlance e1000 LSI LSI LSI 128 512 512

Solaris 6 Solaris 7 Solaris 8 Solaris 9 (experimental) Solaris 10 (experimental) Solaris 10 64-bit (experimental)

linux mandrake mandriva-64 mandriva nld9 other24xlinux

x x x x x x x x

(not available via GUI) BUS LSI LSI IDE BUS vlance e1000 vlance vlance vlance BUS LSI LSI BUS BUS 256 256 256 256 256

Linux Mandrake Linux Mandriva Linux 64-bit Mandriva Linux Novell Linux Desktop 9 Other Linux 2.4.x kernel

1 of 3

other24xlinux-64 other26xlinux other26xlinux-64 otherlinux-64 otherlinux redhat rhel2 rhel3 rhel3-64 rhel4 rhel4-64 sjds suse suse-64 sles sles-64 turbolinux ubuntu ubuntu-64
Windows guests

x x x x x x x x x x x x x x x x x x x x x x x x x x

LSI LSI LSI LSI BUS BUS BUS LSI LSI LSI LSI LSI LSI LSI LSI LSI BUS LSI LSI

e1000 vlance e1000 e1000 vlance vlance vlance vlance e1000 vlance e1000 vlance vlance e1000 vlance e1000 vlance vlance e1000

LSI LSI LSI LSI BUS BUS BUS LSI LSI LSI LSI LSI LSI LSI LSI LSI BUS LSI LSI

256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256

Other Linux 2.4.x kernel 64-bit Other Linux 2.6.x kernel Other Linux 2.6.x kernel 64-bit Other Linux 64-bit Other Linux Red Hat Linux Red Hat Enterprise Linux 2 Red Hat Enterprise Linux 3 Red Hat Enterprise Linux 3 64-bit Red Hat Enterprise Linux 4 Red Hat Enterprise Linux 4 64-bit Sun Java Desktop System SUSE Linux SUSE Linux 64-bit SUSE Linux Enterprise Server SUSE Linux Enterprise Server 64-bit Turbolinux Ubuntu Ubuntu 64-bit

win2000advserv win2000pro win2000serv win31 win95 win98 winme winnt winnetenterprise winnetenterprise-64 winnetbusiness winnetstandard winnetstandard-64 winnetweb longhorn longhorn-64 winxphome winxppro winxppro-64 winvista winvista-64
OS2

x x x x x x x x x x x x x x x x x x x x x

x x x x x x x x x

BUS BUS BUS IDE IDE IDE IDE BUS LSI LSI

vlance vlance vlance vlance vlance vlance vlance vlance vlance e1000 vlance vlance e1000 vlance vlance e1000 vlance vlance e1000

BUS BUS BUS BUS BUS BUS BUS BUS LSI LSI LSI LSI LSI LSI LSI LSI BUS BUS LSI

384 256 384 16 64 256 256 256 384 384 384 384 384 384 512 512 256 256 256 16 24

Windows 2000 Advanced Server Windows 2000 Professional Windows 2000 Server Windows 3.1 Windows 95 Windows 98 Windows Me Windows NT Windows Server 2003 Enterprise Edition Windows Server 2003 Enterprise x64 Edition Windows Server 2003 Small Business Windows Server 2003 Standard Edition Windows Server 2003 Standard x64 Edition Windows Server 2003 Web Edition Windows Vista (experimental) Windows Vista x64 Edition (experimental) Windows XP Home Edition Windows XP Professional Windows XP Professional x64 Edition

x x

LSI LSI LSI

x x

LSI LSI LSI

x x

IDE IDE LSI

no defaults (not available via GUI) no defaults (not available via GUI)

os2experimental
VMware

no defaults (not available via GUI)

against all rumours: it's possible - see forum for information on drivers and some more tricks that may be useful

vmkernel

no defaults (not available via GUI)

Rumours report that this is used by VMware engineers to run ESX in a VM. Well makes sense - why not? Recently I had the chance to test it - but failed. I guess it needs some more special parameters. Fact is VMserver and WS 5 accept this as guestOS

2 of 3

home

vmx

vmdk

about this site

forum

downloads

3 of 3

Sanbarrow.com

VMX-file parameters - logging

Home MOA Live CD VMX Exotic Guests Links Forum

Introduction Sorry - some time ago I knew some reasonable settings for the throttle-function ...

parameter-name

default

type

usage

logging

true

switch

main-switch

log.fileName log.append log.keepOld log.throttleBytesPerSec log.throttleThreshold log.timeStamp log.vmmstats

logs/vm.log false 3

path switch value value value

path to logfile append to old log ? number of logs to keep

monitor_control.log_vmsample

false

switch

log virtual machine progress periodically GUI-option of newer versions

Home
Ulli Hankeln - mail to webmaster at sanbarrow dot com

Top

1 of 1

home

vmx

vmdk

about this site

forum

downloads

gui settings
VMX-file parameters
uncomplete ... gui.exitAtPowerOff = "true" gui.exitAtPowerOff = "false" GUI checked: "close after powering off or suspending" GUI unchecked: "close after powering off or suspending"

gui.fullScreenAtPowerOn = "true" gui.fullScreenAtPowerOn = "false"

GUI checked: "enter full screen mode after powering on" GUI unchecked: "enter full screen mode after powering on"

gui.powerOnAtStartup = "true" gui.powerOnAtStartup = "false"

GUI checked: "power on after opening this virtual machine" GUI unchecked: "power on after opening this virtual machine"

gui.available gui.controlShiftAlt gui.exitOnCLIHLT gui.managementUI gui.powerOnAtStartup gui.restricted gui.shellMsg gui.silentRebootOnOsCrash home vmx vmdk about this site forum downloads Advanced

1 of 1

home

vmx

vmdk

about this site

forum

downloads

Advanced parameters
VMX-file parameters
only a small selection of this is commented yet - any help is welcome - contact me via forum-PMs or email - thanks Ulli Thanks to Oliver for ESX-related parameters

advanced virtual hardware settings:

bios cdrom chipset devices disklib hard-disk pcisound pcibridge svga keyboard

advanced interaction with the host:

answer powerTyp priority isolation.tools mks (mouse, keyboard, screen) uuid msg guest.commands

advanced setup of the host:

host mainMem monitor_control monitor vmx hypervisor

server related settings:

remoteDisplay sched

snapshot handling:
snapshot checkpoint undopoint

stupid features
autoprotect

answer
answer.msg.serial.file.open = "Replace" answer.msg.serial.file.open = "Append" answer.msg.<question_ID> = <answer>

top automatically answers the question if you want to replace or append an already existing file used as a serial port manually answer the question once - next look up the question_ID in the vmware.log

bios
bios.bootDelay = "5000" bios.forceSetupOnce = "TRUE" bios440.fileName = "name of replacement bios file"

top sets the boot delay in milliseconds WS 6.0.1 / Fusion force the VM to enter BIOS on next boot WS 6.0.1 / Fusion replace theoriginalVMware BIOS with your own one - highly experimental and unsupported of course in WS 7 and Fusion 3 you can set the boot-device ... the example boots from the second nic other values that may be used : ide0:0 = boots from IDE-disk or CDrom

bios.bootOrder = "ethernet2"

1 of 10

scsi0:0 = boots from scsi-disk at controller 0 : 0 the device must be present - otherwise this will be ignored

cdrom
cdrom.minVirtualTime cdrom.aiomgr cdrom.asyncTimeout cdrom.bufferedPassThrough cdrom.defaultCdbLength cdrom.directPassThrough cdrom.iso.aiomgr cdrom.lockCDOnReads cdrom.logging cdrom.logMaxCmd cdrom.logMaxRes cdrom.modeSenseInterval cdrom.raw.aiomgr cdrom.releaseTimeout cdrom.reopenOnMediaChange cdrom.synchronous cdrom.useNonUnified cdrom.useSGIO

top see knowledgebase

hard-disk
hard-disk.useUnbuffered = "true" aiomgr.buffered = "TRUE" hard-disk.asyncTimeout hard-disk.dropio hard-disk.enableIBR hard-disk.minVirtualTime hard-disk.synchronous

top disable buffering of vmdk I/O (this setting was used per default in Fusion Beta 3) see forum

host
host.TSC.noForceSync = "true" host.useFastclock = "false" host.TSC.forcedDelta host.TSC.maxDelta host.cpukHz host.dumpDI host.noTSC ptsc.noTSC

top see kb 928 fix timing issues - see kb 892

Timekeeping and power management kb article 1227 top silently defaults to "true" - set to "false" if you don't want to use mem-file for swapping - see config.ini

mainMem

mainMem.useNamedFile = "true"

this parameters is used on all Windows platforms on Linux it is used for all VMserver version and Workstation 4.5 upto 6.5 Workstation 7 on Linux no longer uses it - the parameter was replaced with mainmem.backing - see below

mainMem.partialLazyRestore mainMem.partialLazySave

available via GUI available via GUI Workstation 7 on Linux only "swap" only works on 64bit host "named" uses mem file in VM-directory "unnamed" uses mem file in /tmp dangerous ! in case a VM denies to start and complains like "... drive is critical low on space ..." this parameter may overriide this use with caution - and remove as soon as you fixed the issue

mainmem.backing = "swap" mainmem.backing = "named" mainmem.backing = "unnamed"

mainMem.freeSpaceCheck = "FALSE"

mainMem.allow8GB mainMem.ioBlockPages mainMem.ioWait mainMem.pageFileSave mainMem.preAllocVACache mainMem.prefetchMB mainMem.sharedMemHashTableSize mainMem.traceSave mainMem.vaAlignSize mainMem.vaCacheSize mainMem.vaTileSize

dangerous - may affect performance

mks
mks.ctlAltDel.ignore mks.disableHotkeys mks.enable3d = "true" mks.noBeep = "true"

top non functional ???

required to enable experimental 3d support disable annoying guest-beeps

2 of 10

mks.movie.config.high.recordSound = "true" mks.movie.config.high.bppDepth mks.movie.config.high.byteBudgetPerFrame mks.movie.config.high.byteThresholdWeight mks.movie.config.high.keyFrameThreshold mks.movie.config.high.pixelThresholdWeight mks.movie.config.high.sampleRate mks.movie.config.high.stereo mks.movie.config.high.useADPCM mks.movie.config.high.usecPerFrame mks.movie.config.high.useVMC2 mks.absoluteMouse mks.alwaysWatermark mks.correctRemoteDesktopDirectInputScale mks.debugChainMgr mks.fullscreen.allowScreenSaver mks.fullScreenMonitor mks.gaffleInjectedModKeys mks.gl.dontLogErrors mks.gl.doubleBuffer mks.gl.fbo mks.gl.magFilter mks.gl.minFilter mks.gl.noTimeInfo mks.gl.useCopyContext mks.gl.useFBTexture mks.glConsole mks.keyboard.swapAlt mks.keyboardFilter mks.maxRefreshRate mks.minFullscreenHeight mks.minFullscreenWidth mks.mouseDebug mks.noEmulateResolution mks.noGL mks.noHostCursor mks.noThinkPadWorkaround mks.scaleMode mks.setMouseParams mks.showCursor mks.stayInFullScreen mks.threadPriority mks.thumb.fileName mks.thumb.scaleFactor mks.thumb.scaleMode mks.thumb.targetHeight mks.thumb.targetWidth mks.thumb.updatePeriodSecs mks.useDirectInput mks.windowed.allowScreenSaver mks.x.screenSaverTimeout

video-capture with sound - workstation only

workstation only

disklib
disk.locking = "false"

top usually VMware use a *lck file to lock vmdks - use "false" to override this sets max amount of data that should be read ahead for clustering use 0 to disable caching at all sets min amount of data that should be read ahead for clustering use 0 to disable caching at all use for clustering

diskLib.dataCacheMaxReadAheadSize = "0" diskLib.dataCacheMinReadAheadSize = "0" diskLib.dataCacheMaxSize = "0" diskLib.dataCachePageSize = "4096" diskLib.maxUnsyncedWrites = "0" diskLib.tmpShrinkDefragExtension

file-extension used for temp. files during shrink - 2.phase

diskLib.defaultEmbeddedDescSize

sets size of embedded descriptor for monolithic-sparse ??? sets size of the split flat 2GB chunk could be used in earlier versions to create custom-size split disks sets size of the split sparse 2GB chunk could be used in earlier versions to create custom-size split disks disables WS6 overeager filesystem check - (prevents using disks via drivers for ext2/3 on Windows or ntfs on Linux ...)

diskLib.twoGBFlatExtentSize = "2147221504"

diskLib.twoGBSparseExtentSize = "2146435072"

diskLib.sparseMaxFileSizeCheck= "false"

diskLib.bufferedMigrate diskLib.createSpaceSafetyMargin diskLib.dataCacheMaxRABusyCnt diskLib.dataCacheMaxSeqRA diskLib.dataCachePageSize diskLib.dataCacheSeqThreshold diskLib.dataCacheUpdateFrequency diskLib.dataCacheUseExtraRA diskLib.defaultGTEsPerGT diskLib.disableSparseChecker diskLib.flatAllocWriteSize diskLib.grainCoalescing

3 of 10

diskLib.gtCacheMode diskLib.gtCacheSize diskLib.ignorePermissions diskLib.legacyCheckerTolerateHoles diskLib.maxNumGrainsCoalesced diskLib.redoGrainSize diskLib.redundantGrainMetadata disklib.sparse.bigJobGTWritePolicy disklib.sparse.bigJobMaxChangesBeforeFlush disklib.sparse.bigJobMaxDirtyGTEs disklib.sparse.bigJobRGTWritePolicy disklib.sparse.gtWritePolicy disklib.sparse.maxChangesBeforeFlush disklib.sparse.rgtWritePolicy diskLib.sparseOpenForceCheck diskLib.sparseRFPWriteSizeThreshold diskLib.sparseSplitStress diskLib.traceLevel diskLib.vmhsDefaultSimpleAioMgr diskLib.vmhsDefaultUnbufAioMgr

priority
priority.grabbed = "high" priority.grabbed = "normal" priority.ungrabbed = "high" priority.ungrabbed = "normal" priority.ungrabbed = "idle"

top available via GUI - sets the priority for the VM in grabbed state

available via GUI - sets the priority for the VM in ungrabbed state

powerType
powerType.powerOff = "default" powerType.powerOn = "default" powerType.reset = "default" powerType.suspend = "default"

top

available via GUI

svga
svga.vramSize svga.maxHeight svga.maxWidth svga.3d.disableStateCaching svga.3d.floatTextures svga.3d.maxLights svga.3d.maxTextureUnits svga.3d.renderTargets svga.alwaysAccelFront svga.autodetect svga.capabilitiesMask svga.debug.fpsFrameCount svga.debug.port svga.debug.showFPS svga.enableOverlay svga.fitHostDimensions svga.forceTraces svga.ignoreSavedState svga.ignoreVGAPalette svga.loghw svga.maxChangeCount svga.maxChangeTick svga.maxFullscreenRefreshTick svga.maxLocalChangeTick svga.maxNoChangeTick svga.mergeRectCmds svga.no3d svga.no8BitEmulation svga.noAlphaCursor svga.noCursorBypass svga.noCursorBypass2 svga.noExtendedFIFO svga.noFIFOAccelFront svga.noFIFOFence svga.noHWCursor svga.noMultimon svga.noOprom svga.noPitchLock svga.noPitchLockFifoReg svga.noPitchLockReg svga.noRectCopy svga.numDisplays svga.PCIAccelSize svga.PCIFBSize svga.syncTimeLimit

top used to enable experimental 3d support - see manual and KB article 1003 - used for custom video modes

4 of 10

svga.yes3d svga.yesAlphaBlend svga.yesGlyphClipping svga.yesGlyphs svga.yesLegacyOffscreen svga.yesOffscreen svga.yesRasterOp svga.yesRectFill

uuid

top generate new uuid this is this the "I copied the VM" answer generates new MAC for ethernet*-devices use for first boot of copied or cloned VMS keep uuid this is this the "I moved the VM" answer keeps existing MAC use when you often move your VM autogenerated values like "56 4d 8e a8 77 69 80 ea-db d7 a2 77 40 fd fd 37" don't change this manually !

uuid.action = "create"

uuid.action = "keep"

uuid.bios uuid.location uuid.getHostUuid uuid.newScheme

RemoteDisplay
RemoteDisplay.vnc.enabled = "true" RemoteDisplay.vnc.port = "<port>" RemoteDisplay.vnc.password = "password" RemoteDisplay.vnc.ip RemoteDisplay.vnc.key RemoteDisplay.vnc.keyMap RemoteDisplay.vnc.keyMapFile RemoteDisplay.vnc.zlibLevel RemoteDisplay.vncWheelStep RemoteDisplay.depth = "24" RemoteDisplay.depth = "16" RemoteDisplay.depth = "8" RemoteDisplay.bpp remoteDisplay.forceDepth RemoteDisplay.maxConnections RemoteDisplay.maxHeight RemoteDisplay.maxWidth RemoteDisplay.no RemoteDisplay.noRingBell RemoteDisplay.noVMWCursorEncodings RemoteDisplay.noVMWEncodings

top

vnc-settings

set color depth for remote display - server only

monitor_control
top dangerous - may affect performance monitor_control.virtual_rdtsc = "false" monitor_control.restrict_backdoor = "true" This should turn off TSC virtualisation if you want to run VMware inside a VM you will need this setting - it may cheat any program that scans for the VMware-backdoor channel like Ken Katos vmchk.exe It is NOT enough to cheat advanced VM-scanning methods like redpill or scoopy required to run ESX inside aWS 6.0. VM - use with AMD CPUs required to run ESX inside a WS 6.0 VM - use with Intel CPUs some older versions of FreeBSD needed this entry to install - no longer necessary very old - used to install OpenStep - no longer necessary force Solaris to install in 32bit-mode - see forum timing issues ? - see forum

monitor_control.enable_extended_svm = "true" monitor_control.vt32 = "true" monitor_control.disable_apic = "true" monitor_control.simmmu = "true" monitor_control.mmu_adaptive = "true" monitor_control.disable_longmode = "1" monitor_control.pseudo_perfctr = "true" monitor_control.log_vmsample = "false" monitor_control.disable_checkcodeexpire = "true" monitor_control.disable_checkcode = "true" monitor_control.disable_directexec = "true" monitor_control.disable_chksimd = "true" monitor_control.disable_ntreloc = "true" monitor_control.disable_selfmod = "true" monitor_control.disable_reloc = "true" monitor_control.disable_btinout = "true" monitor_control.disable_btmemspace = "true" monitor_control.disable_btpriv = "true" monitor_control.disable_btseg = "true" monitor_control.enable_extended_core monitor_control.enable_paravirt

used for MAC OS Tiger

disable VM-detection

5 of 10

monitor_control.enable_vmeopt = "true"

see kb 461

monitor

top

monitor.usecHostedVSMPMaxSkew = 0 monitor.usecHostedVSMPYieldPoint = 0

try this 2 lines to improve performance of SMP-VMs in WS 6.5

isolation.tools
isolation.tools.osNotFound.disable = "false" isolation.tools.copy.disable isolation.tools.copy.enable isolation.tools.paste.disable isolation.tools.paste.enable isolation.tools.dnd.disable isolation.tools.hgfs.disable = "false"

top per default VMware displays the "os not found" message

copy and paste

set to "true" to disable shared folders

isolation.tools.apmFunction.disable

disable APM functions of the guest ???

monitor_control.virtual_rdtsc = "false" monitor_control.restrict_backdoor = "true" isolation.tools.getPtrLocation.disable = "true" isolation.tools.setPtrLocation.disable = "true" isolation.tools.setVersion.disable = "true" isolation.tools.getVersion.disable = "true" monitor_control.disable_directexec = "true" isolation.device.edit.disable isolation.monitor.control.disable isolation.tools.ACPI.disable isolation.tools.autoConnect.disable isolation.tools.diskShrink.disable isolation.tools.diskWiper.disable isolation.tools.getDiskGeo.disable isolation.tools.getGuiOptions.disable isolation.tools.getInfo.disable isolation.tools.getMachineId.disable isolation.tools.getMemSize.disable isolation.tools.getMhz.disable isolation.tools.getOS2IntCursor.disable isolation.tools.getPtrLocation.disable isolation.tools.getScreenSize.disable isolation.tools.getTime.disable isolation.tools.getUUId.disable isolation.tools.getVersion.disable isolation.tools.haltReboot.disable isolation.tools.haltRebootStatus.disable isolation.tools.hostCopy.disable isolation.tools.initScsiIoprom.disable isolation.tools.Int13.disable isolation.tools.log.disable isolation.tools.message.disable isolation.tools.osStateChange.disable isolation.tools.osStateChangeStatus.disable isolation.tools.removeImage.disable isolation.tools.rsvd0.disable isolation.tools.rsvd1.disable isolation.tools.rsvd2.disable isolation.tools.setGUIOptions.disable isolation.tools.setGUIOptions.enable isolation.tools.setInfo.disable isolation.tools.setOption.disable isolation.tools.setPtrLocation.disable isolation.tools.setVersion.disable isolation.tools.stopCatchup.disable isolation.tools.unifiedLoop.disable isolation.tools.updateTools.disable isolation.tools.vmdbpipeSend.disable

this example prevents that the app Sword of the New World detects that it is running in a VM

sched
sorry folks - this is mostly unknown area to me - thanks Oliver for explanations top

6 of 10

sched.cpu.affinity sched.cpu.affinity sched.cpu.affinity sched.cpu.affinity sched.cpu.affinity

= = = = =

"all" "2" "2,3,5" "2,3" "0,1,2,3,4,5,6,7"

specify the CPU affinity for a VM defaults to "all", all is the same as adding all core numbers (counting starts with 0)

sched.cpu.shares = "3158" sched.cpu.shares = "normal" sched.cpu.min = "0" sched.cpu.min = sched.cpu.max = "1400" sched.cpu.max = "1600" sched.cpu.max = "800" sched.cpu.htsharing = "any" sched.cpu.htsharing = "none" sched.cpu.htsharing = "internal" sched.cpu.units = "mhz" sched.mem.affinity = "all" sched.mem.affinity = "0,1,2,3,4,5,6,7" sched.mem.shares = "696" sched.mem.shares = "normal" sched.mem.maxmemctl sched.mem.minsize = "0" sched.mem.max = "384" sched.mem.max = "unlimited" sched.mem.softlimit sched.mem.swaplimit sched.mem.pshare.checkRate sched.mem.pshare.debug sched.mem.pshare.enable sched.mem.pshare.scanRate sched.mem.balloon.debugzerofrequency sched.mem.balloon.maxdebugtarget sched.swap.hostLocal sched.swap.derivedName sched.net.filter.class = "nfshaper" sched.net.filter.args = "30000000 70000000 4000000"

number of CPU shares CPU reservation

maximum CPU usage allowed for VM

sharing with HT capable CPUs Units for sched.cpu.min and sched.cpu.max memory affinity for NUMA systems number of memory shares ESX - specific ? memory reservation for a VM if this equals sched.mem.max or the configured memory size paging for the VM is disabled setting this also disables page sharing max memory allowed for the VM not useful since this is determined by the VM memory setting ESX - specific ? ESX - specific ?

ESX - specific ?

ESX - specific ? location of the VM swap file

ESX - specific ?

tools
toolScripts.afterPowerOn = "true" toolScripts.afterResume = "true" toolScripts.beforePowerOff = "true" toolScripts.beforeSuspend = "true" tools.remindInstall = "false" tools.syncTime = "false" tools.broadcastIP tools.capability.auto_upgrade tools.capability.copypaste_version tools.capability.display_topology_set tools.capability.dnd_version tools.capability.guest_temp_directory tools.capability.haltreboot tools.capability.hgfs_server tools.capability.open_url tools.capability.printer_set tools.capability.resolution_min tools.capability.resolution_set tools.capability.statechange tools.capability.upgrader_parameters tools.disableSoftPower tools.guestos.phase tools.guestUptime tools.hgfs.volumeInfoType tools.ipCheckInterval tools.os.haltreboot.status tools.os.statechange.status tools.set.version tools.setInfo.sizeLimit tools.state tools.statusMsgs.disable tools.syncTime.period tools.upgrade.policy

top run script after power on run script after resume run script before power off run script beforer resume do not remind to install VMware-tools disable time synchronisation via VMware-tools

7 of 10

pciSound
These parameters are somehow related but not dependant on the main-switch that pciSound.DAC2InterruptsPerSec = "16" top

used for MAC OS Tiger

pciSound.enableVolumeControl pciSound.ADCInterruptsPerSec pciSound.DAC1InterruptsPerSec pciSound.emulateMixer pciSound.hostSampleRateDelta pciSound.linearVolume pciSound.noIntrPriorityInheritance pciSound.noLockPriorityInheritance pciSound.noPollPriorityBoost pciSound.noPollThread pciSound.noSuperPriorityBoost pciSound.playBuffer pciSound.priorityBoost

see KB 853

snapshot

top

snapshot.action = "keep" snapshot.action = "autoRevert" snapshot.action = "autoCommit" snapshot.action = "prompt" snapshot.asyncConsolidate snapshot.crash.%d snapshot.crashTest snapshot.current snapshot.disabled snapshot.lastUID snapshot.mru%d.uid snapshot.mru.maxNum snapshot.needConsolidate snapshot.numSnapshots snapshot.protected snapshot.sanityTest snapshot.sanityTestIterations snapshot.sanityTestPeriod snapshot.version snapshot0.clone snapshot0.createTimeHigh snapshot0.createTimeLow snapshot0.description snapshot0.disk%d.fileName snapshot0.disk%d.mode snapshot0.disk%d.node snapshot0.displayName snapshot0.filename snapshot0.numClones snapshot0.numDisks snapshot0.numVPlays snapshot0.parent snapshot0.type snapshot0.uid snapshot0.vplay%d.displayName snapshot0.vplay%d.fileName

gui: just power off gui: revert to snapshot gui: take a new snapshot gui: ask me

vmx
vmx.acceptConnections vmx.allowNested vmx.alwaysUseSubsysID vmx.capability.copypaste_version vmx.capability.dnd_version vmx.capability.edit_devices vmx.capability.edit_scripts vmx.capability.ptr_grab_notification vmx.capability.tools_pkg_version vmx.capability.unified_loop vmx.connectserverd vmx.ipc.maxBufferedBytes vmx.ipc.maxBufferedPackets vmx.maxOutWSS vmx.noPriorityBoost vmx.noPriorityInheritance vmx.set_option vmx.superPriorityBoost vmx.useLegacySubsysID

top

guest.commands
guest.commands.allowAnonGuestCommands guest.commands.alwaysRelayVixCOmmands guest.commands.anonGuestCommandsRunAsConsoleUser guest.commands.anonGuestCommandsRunAsRoot guest.commands.anonGuestPassword guest.commands.anonGuestUserName

top

8 of 10

guest.commands.enabled

undopoint
undopoint.action undopoint.checkpointedOnline undopoint.disableSnapshots undopoint.protected undopoint.restoreFromCheckpoint undopoints.seqNum

top

chipset
chipset.useAcpiBattery chipset.useApmBattery chipset.enableGART chipset.onlineStandby chipset.type

top useful for notebooks this display battery status inside the VM if set to "true"

new in workstation 6 top use to force resume of a suspended VM when the VMware-version has changed use to force resume of a suspended VM when the CPU has changed - only makes sense in some very rare cases

checkpoint
checkpoint.overrideVersionCheck = "true"

checkpoint.disableCpuCheck = "true"

checkpoint.compressLevel checkpoint.cptConfigName checkpoint.fastMonSwitchID checkpoint.format.64bit checkpoint.mks.saveimage checkpoint.runSuspendTest checkpoint.stunTortureTest checkpoint.stunTortureTestIterations checkpoint.stunTortureTestPeriod checkpoint.stuntiming checkpoint.suspendTestIterations checkpoint.sync.timing checkpoint.vmState checkpoint.vmState.readOnly

msg
msg.autoAnswer = "TRUE"

top tries to automatically answer all questions that may occur at boot-time. top

hypervisor
hypervisor.xen.allow

keyboard
keyboard.allowTypematicInMKS keyboard.keyboardWait keyboard.mouseWait keyboard.softAutorepeat keyboard.typematicMinDelay

top

pref
pref.enableTopmost = "FALSE"

top see forum

pciBridge*

top In virtual hardware mark 7 you can have upto 8 PCI-bridges numbered from 0 to 7.

pciBridge0.pciSlotNumber = "17" pciBridge0.present = "TRUE" pciBridge0.virtualDev = "pciBridge" pciBridge0.functions = "8"

PCIbridge 0 use pcislot 17 as a silent default. You should not change anything with PCIbridge 0 unless you really know what you are doing.

Sorry at this time I do not know what the function-parameter is good for - do not change ! pciBridge6.functions = "8" pciBridge6.pciSlotNumber = "23" pciBridge6.present = "TRUE" pciBridge6.virtualDev = "pcieRootPort" The other PCIbridges can be disabled in most scenarios I have seen so far. Do not disable or edit them if you need "directpath" or SAS-controllers. The PCIbridges higher than number 0 seem to default to virtual Device type "pcieRootPort" = PCI-Express

devices

top In virtual hardware mark 7 several devices are seen as removable by the guest like for example networkcards. If you do not want this behaviour use this parameter - then the VM does not display network-cards as removable similar to older virtual hardware. Handle with care - may have other side-effects

devices.hotplug = "FALSE"

9 of 10

autoprotect

top this is a new feature in WS 7 - it is also used in Fusion.

rollingTier*.*

IMHO this is a very stupid feature - it is a snapshot-timer. Snapshots should be used with care and never by an automatic. DO NOT USE IT - unless you are ready to handle the consequences.

home

vmx

vmdk

about this site

forum

downloads

10 of 10

home

vmx

vmdk

about this site

forum

downloads

config.ini - settings
VMX-file parameters
The file configs.ini or config (in Linux) sets parameters for all users or if you prefer - it sets parameters for the host. If you want to use certain settings for all VMs you create, you can try to add this here - may not work for all parameter. memory priority copy and paste shared folders misc .... startup of VMs usage of SSL (server only) workspace and paths Cycling through VM and Host Switching directly to VM and Host prevent swapping on a Windows Host (tuned sample settings) Tip for Windows-user: this file can be found in C:\documents and settings\All Users\Application Data\VMware\VMware Workstation If you can't see it - fix your explorer settings to display hidden files

memory
prefvmx.minVmMemPct = "100" prefvmx.minVmMemPct = "50" prefvmx.minVmMemPct = "25" fit memory into RAM Whenever possible avoid settings lower 100% allow some memory to be swapped allow most memory to be swapped sets the maximum amount of RAM that can be used by VMsif this is less than at least 80% of the physical RAM something is going wrong: scan through preferences.ini and config.ini for memory-related entries, power down all running VMs and delete these lines and restart your host. Do not launch any other apps! Create a new VM and check if anything has changed.

prefvmx.allVMMemoryLimit = "1272"

mainMem.partialLazyRestore = "true" mainMem.partialLazyRestore = "false"

restore snapshots in background do not restore snapshots in background

mainMem.partialLazySave = "true" mainMem.partialLazySave = "false"

take snapshots in background do not take snapshots in background

mainMem.useNamedFile = "true"

creates a file the size of nominal RAM in working directory file uses random name doesn't use named-file - use for VMs on USB-disks or other slow disks Windows: useNamedFile= "FALSE" causes memory to be backed by the host's swap space. Linux: useNamedFile= "FALSE" causes a hidden file to be created in a temporary directory, which is immediately deleted when you power off the VM

mainMem.useNamedFile = "false"

priority
priority.grabbed = "high" priority.grabbed = "normal" priority.ungrabbed = "normal" priority.ungrabbed = "low" priority.ungrabbed = "idle"

top this host-wide settings can be over-ruled by settings in the vmx-file

this host-wide settings can be over-ruled by settings in the vmx-file

1 of 3

prevent swapping on a Windows Host

datastore.name = "local" defaultVMPath = "R:\vm\machines" datastore.localpath = "R:\vm\machines\" sched.mem.pshare.enable = "FALSE" prefvmx.useRecommendedLockedMemSize = "TRUE" prefvmx.minVmMemPct = "100" priority.grabbed = "normal" priority.ungrabbed = "normal" security.host.ruissl = "FALSE" mainMem.partialLazySave = "FALSE" mainMem.partialLazyRestore = "FALSE" mainMem.useNamedFile = "FALSE"

top

prevent swapping on a windows-host

This allocates all nominal guest-RAM completely into host-memory Sorry - doesn't work on Linux

copy and paste

Isolation.tools.copy.enable = "true" Isolation.tools.copy.enable = "false" Isolation.tools.paste.enable = "true" Isolation.tools.paste.enable = "false"

top enable copy function (vmware-tools) - use same settings for ... paste.enable disable copy function (vmware-tools) enable paste function (vmware-tools) disable paste function (vmware-tools)

shared folders
Isolation.tools.HGFS.disable = "true" Isolation.tools.HGFS.disable = "false"

top disables shared-folders - if implemented enables shared-folders - if implemented

misc
mks.ctlAltDel.ignore = "true" mks.fullscreen.allowScreenSaver = "true" fullScreenSwitch.onSeparateDesktop = "true"

top see see see

beep
mks.noBeep = "TRUE"

top in earlier versions you could add this entry to the vmx-file to get rid of anoying BIOS-beeps via the computer-speaker. looks like you have to add this to the config.ini with Workstation 6

startup
msg.autoAnswer = "true"

top tries to automatically answer all pop-ups at start of a VM

startup
msg.autoAnswer = "true"

top tries to automatically answer all pop-ups at start of a VM

security
security.host.muissl= "true" security.host.muissl = "false"

top use SSL for the remote-console don't use SSL for the remote-console

workspace
defaultVMPath = "path" datastore.name datastore.localpath = "path"

top This sets the workspace - new VMs will be created here

cycling through VM and Host

FullScreenSwitch.cycleKey = "0x13" FullScreenSwitch.cycleKey = "0x0" FullScreenSwitch.cycleHost = "true"

top http://www.vmware.com/support/ws5/doc /ws_special_config.html

switching directly to VM and Host

FullScreenSwitch.directKey = "0x70" FullScreenSwitch.directKey = "0x6" FullScreenSwitch.hostDirectKey = "0x78" FullScreenSwitch.hostDirectKey = "0x6"

top http://www.vmware.com/support/ws5/doc /ws_special_config.html

can't re-enable VT after host-suspend or hibernate

top

2 of 3

Workstation 6.5 only ??? hv.enableIfUnlocked = TRUE If you have a buggy BIOS which fails to re-enable VT when awakening from deep sleep, this option may help you:

top home vmx vmdk about this site forum downloads

3 of 3

home

vmx

vmdk

about this site

forum

downloads

preferences.ini - settings
VMX-file parameters
Preferences.ini - don't edit while VMs are running

in Linux you find the file in /home/user/.vmware/ in Windows it is in profiles dir\username\application data\vmware pref.console.openedObj0.type = "vm" pref.console.openedObj0.path = "/vm/|23499f8e40be892b71/" pref.console.openedObj0.file = "e:\multiple-snapshots\MS-DOS.vmx" pref.eula.1.appName = "VMware Workstation" pref.eula.1.buildNumber = "185517" pref.eula.2.appName = "VMware Player" pref.eula.2.buildNumber = "185517"

VMs are listed like this

this accepts the EULA for the listed build number.

pref.autoFitGuestToWindow = "FALSE" pref.autoFitFullScreen = "fitHostToGuest" pref.autoFit = "TRUE"

display

webUpdate.lastCheck.status = "done_updates" webUpdate.checkPeriod = "manual" hint.vmui.reset = "FALSE" hint.vmui.poweroff = "FALSE" hint.upgrade.legacyVM = "FALSE" hint.tools.toolsReminder = "FALSE" hint.nfsmounted.persistent = "FALSE" hint.loader.debug.beta = "FALSE" hint.leaveFullScreen = "FALSE" hint.guestos.xp = "FALSE" hint.buslogic.needDriver = "FALSE"

if you don't like any automatic updates - this settings are for you

Hints that you have disabled some time ago are listed here. If you want to see your favorite hint again next time use "true" This are just a few examples ...

pref.hotkey.shift = "true" pref.hotkey.alt = "true" pref.hotkey.control = "true"

pref.hotkey.disableExitFullScreenOnHotkeyRelease pref.hotkey.disableHotkeyDelete pref.hotkey.disableHotkeyEscape pref.hotkey.disableHotkeyInsert pref.hotkey.leftAlt pref.hotkey.leftControl pref.hotkey.leftShift pref.hotkey.rightAlt pref.hotkey.rightControl pref.hotkey.rightShift

In Linux-VMs you may not like the usual CTRL + ALT combination use this for CTRL + ALT + SHIFT

pref.view.homepage = "TRUE" pref.view.navBar = "TRUE" pref.view.statusBar = "TRUE" pref.view.tabs = "TRUE" pref.tip.startup = "FALSE" pref.tip.index = "3" pref.grabOnKeyPress = "TRUE" pref.grabOnMouseClick = "TRUE" home vmx vmdk

toolbars: use "true" to show, "false" to hide bars

startup-tips

VM grabs keyboard and mouse when set to "true"

about this site

forum

downloads

1 of 2

2 of 2