VMX Reference

Home Documentation VM-Sickbay MOA News About

VMX-file parameters Welcome - this is the Xth version of the introduction to thevmx-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 VMware-documentation - but I guess that can't be helped

the shorter the betterMost of the times shorter vmx-files are better than long ones ;-)Don't use parameters just because they were listed once ina 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

IntroductionStarting small - minimal vmx-file

Files used by a VMWhat's new in Workstation 6 ?

Commented parameters for the virtual hardware:CD-settings Network Floppy-drivesIDE Parallel ports RAM SCSISerial portsSoundUSB port

Commented parameters for behaviour of the VM:Guest operating systemDisplaynameLogging GUI Movies

Advanced guides:Assigning PCI-slots: expect the unexpectedTranslating Linux - Windows - ESXUndoable mode for current VMserverThe 3 different Virtual-Hardware-modesConfigure the start date and time for a VM updated3 man in a boat (more than one VM in one directory)

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

Examples:ESX 3.0.* in a WS 6 VM

Advanced virtual hardware settings:bioscdromchipsetdisklibhard-diskpcisoundsvgakeyboard

Advanced interaction with the host:powerTyppriorityisolation.toolsmks (mouse, keyboard, screen)uuidmsgguest.commands

Advanced setup of the host:hostmainMemmonitor_controlvmxhypervisor

Server related settings:remoteDisplaysched

Snapshot handling:snapshotcheckpointundopoint

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

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

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 havescsi0.present = "TRUE"then lines likescsi0.virtualDev = "lsilogic" are used.If you havescsi0.present ="FALSE"all lines starting with scsi0 are ignored.What happens if you use unknown or mis-spelled lines? A line likezoo.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 ofelefants. 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

MemoryYou can change the amount of RAM that a VM will use like thismemsize = "128"If you don't assign a value for memory VMware will use the default-setting which is 32MBmemsize = "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 addingdisplayName = "VMX-Test"If you don't assign a nicname VMware will autogenerate one- useing the path and name of the vmx-filedisplayName = "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 webmastersPlease don't simply copy any of the vmx-pages. I have invited VMware to cooperate - I offered to skip the dangerous parameters inexchange 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 anyinformation 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


What's new in Workstation 6 / VMplayer 2VMX-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 morePCI-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


1 of 1


a minimal vmx-fileVMX-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 boxwith 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-messageGuest operating system `dos 397' is not supported

Available choices for "guestOS"

config.version = "8"virtualHW.version = "7"guestOS = "winxppro"

VMplayer 2.*Workstation 6.5VMserver 2ESX 4


VMplayer 2.*Workstation 6.*


VMplayer 1.*Workstation 5.*VMserver 1.*ESX 3


Workstation 4.5*ESX 2.5


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 VMserverThe 3 different Virtual-Hardware-modes

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

GrandPa-mode - seeUndoable mode for current VMserverThe 3 different Virtual-Hardware-modes

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

no need to set this - it will be automatically set

virtualHW.atLeastESX31virtualHW.atLeastWS20virtualHW.atLeastWS30virtualHW.atLeastWS40virtualHW.atLeastWS50virtualHW.atLeastWS60virtualHW.futurevirtualHW.latestvirtualHW.supportPartialWS6virtualHW.wasVersioned

Workstation 6 only


1 of 1

home

files used by a VMShort description of the files that are used by virtual machines (applies to VMplayer, VMserver and Workstation 5.5)

File-extension

neededwhenVM ismoved

type size content

*.vmx yes 1-4 kb main configuration file

*.vmdk yes text 1-4 kb virtual disk descriptorfile

*.vmdk yes binarycan be very largemaximum 950Gb

virtual disk of type monolithic-sparse

*0000000*.vmdk yes binary can be very largethis file contains the changes since snapshotX

*.nvram no binary 8 kbnon volatile RAM: contains currentsettings of the virtual BIOS

*.vmem no binary nominal RAMthis file only exists if you usemainMem.useNamedFile = "true"

*s00*.vmdk yes binary can be very large maximum 2Gbthis extension is used for thedata chunks ofgrowing-split disks

*0000000*-s00*.vmdk yes binary can be very large maximum 2Gbthis file contains the changes since snapshotX

*f00*.vmdk yes binary can be very large maximum 2Gbthis extension is used for thedata chunks ofpreallocated-split disks

*0000000*-f00*.vmdk yes binary can be very large maximum 2Gbthis file contains the changes since snapshotX

*flat.vmdk yes binarycan be very largemaximum 950Gb

this extension is used for thedata chunk ofpreallocated monolithic disks

*0000000*-flat.vmdk yes binary can be very largethis file contains the changes since snapshotX

*.vmsndon'tmove ifpresent

binary variescontains current snapshotdatalike nvram and a copy of the vmx-fileexample

*.vmsddon'tmove ifpresent

text varies descriptorfile for current snapshot

*.vmssdon'tmove ifpresent

binary nominal RAM contains RAM of a suspended VM

*.REDO_a03180

onlyappearswithrunningVMs

binary can be very largethis file is used when a disk is in"independent-nonpersistent" mode

*lck

onlyappearswithrunningVMs

very smalllockfile - is used to lock files that arecurrently in use

back to startpage | about this site | forum

1 of 1

home moa vmx vmdk links about donate forum downloads

CD-rom settingsVMX-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

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

This mode will detect a VMware CDrom and use a real CDrom drive ofyour host. Specify which device to use by giving the driveletter onWindows-hosts.This settings will allow booting from CDrom.Failsafe option when you need to use a physical CDromDevice is detected as:NECVMWar_VMware_IDE_CDR10

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

This mode will detect a VMware CDrom and use a real CDrom drive ofyour host. Specify which device to use like /dev/hdc on LinuxThis settings will allow booting from CDrom.Failsafe option when you need to use a physical CDromDevice is detected as:NECVMWar_VMware_IDE_CDR10

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

This mode will detect the CDrom like it is detected by your host.You can specify which device to use by giving the driveletter onWindows-hosts.This settings will allow booting from CDrom.

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

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 namelike /dev/hdcThis settings will allow booting from CDrom.

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

This mode will detect the CDrom like it is detected by your host.You can specify which device to use by giving the driveletter onWindows-hosts.This settings will not allow booting from CDrom - but it can be used forCD-writing.

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


Network settingsVMX-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 nicWARNING: 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-bitguests

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"


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


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


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"


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


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


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"


about this site - forum

2 of 2


floppy settingsVMX-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 slackware-boot-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 maychange 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/fd0This setting allows booting from Floppy.Failsafe option when you need to use a physical Floppy

floppy0.allowGuestConnectionControl = "true" Use to allow control via the vmware-tools from within a guest.

floppy0.clientDevice = "TRUE"

use to select an image on a remote-host - (VMserver)

floppy.minVirtualTime old fix - no longer required - see kb

floppy0.changeTimeoutfloppy0.trackCachefloppy.synchronousfloppy.raw.aiomgrfloppy.minVirtualTimeReadIDfloppy.image.aiomgrfloppy.force144mbfloppy.asyncTimeoutfloppy.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.


1 of 1


ide settingsVMX-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 devicetype

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

ide0:0.startConnected = "FALSE"

if you don't want that CDs or ISOs are connectedat boot-time you have to add this.Don't use with virtual disks

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 itproduces unpredictable results on hosts with more than one CDrom.If you have problems with Virtual CD-drives like Daemon Tools - check thisfirst.

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 youaccidentaly format it, the only way to restore your files is the use of forensictools.All changes are written to the vmdk directly and the disk will not be includedin snapshots.

ide0:0.mode = "independent-nonpersistent"

This mode writes all changes to a temporary file which will be deleted whenyou power off the virtual machine.The temporary files are named like this2k-ide-system.vmdk.REDO_a02144Obviously 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 onlyThis mode writes all changes to a temporary file. This time the file will not bedeleted when you power off the virtual machine.The temporary file are named like this 2k-ide-system.vmdk.REDO_a02144Current 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 - butyou can not commit/ discard/ keep these REDOlogs when you power downa VM with current VMserver.To commit or discard these REDOs you need a special hack that should beused by experts only ...

1 of 2

ide0:0.dmaCapableide0:0.forcelba48ide0:0.noDMA

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


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 value type usage

parallel0.presenttrue or

falseswitch main switch

parallel0.startConnectedtrue or

falseswitch true connects device at startup

parallel0.autodetecttrue or

falseswitch use to autodetect host device

parallel0.fileTypefile or

deviceswitch

parallel0.bidirectionaltrue or

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

parallel0.allowGuestConnectionControltrue or

falseswitch true allows control via vmware-tools

parallel0.present true switch

this settings use a textfile "parport2txt.txt" for the output

the device will start connected

parallel0.startConnected true switch

parallel0.fileType file switch

parallel0.fileName parport2txt.txtfile or

device

parallel0.present true switch this settings use a automatically detected host-device


the device uses bidirectional mode


parallel0.bidirectional true switch

parallel0.fileType device switch

parallel0.present true switch this settings use a automatically detected host-device


the device does not use bidirectional mode


parallel0.bidirectional false switch


parallel0.present true switch

this settings use host-device LPT1



parallel0.bidirectional true switch


parallel0.fileName LPT1file or

device

Home Top

© Ulli Hankeln - mail to webmaster at sanbarrow dot com

1 of 1


scsi settingsVMX-file parameters scsi-controller

device is a virtual disk - exampledevice is a virtual cdrom - examples

parameters for virtual disksparameters for CD-roms

scsi-controller

scsi0.present = "true"scsi1.present = "true"scsi2.present = "true"scsi3.present = "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 ofthumb.

Warning: this parameter depends on the settings for "guestOS"

scsi0..pciSlotNumber = "16"

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

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.returnBusyOnNoConnectStatusscsi0.sharedBusscsi0.unsafeReordering

advanced ...

top

parameters for virtual disks

scsi0:0.fileName = "system.vmdk" path to vmdk - avoid absolute paths

scsi0:0.mode = "persistent"scsi0:0.mode = "undoable"scsi0:0.mode = "nonpersistent"

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

scsi0:0.deviceType = "plainDisk"scsi0:0.deviceType = "PhysicalDrive0"scsi0:0.deviceType = "rawDisk"scsi0:0.deviceType = "scsi-hardDisk"scsi0:0.deviceType = "scsi-passthru"scsi0:0.deviceType = "scsi-nonpassThru-rdm"scsi0:0.deviceType = "scsi-passthru"scsi0:0.deviceType = "scsi-passThru-rdm"

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.RESLCKscsi0:0.sharedscsi0: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"

path to iso-file, driveletter or device-name

scsi0:0.deviceType = "cdrom-image"scsi0:0.deviceType = "atapi-cdrom"scsi0:0.deviceType = "cdrom-raw"

Sets the number of the used vmnet.Only use with connection type "custom"also see additional notes

scsi0:0.allowGuestConnectionControl allow control of device from with the guest (VMware-tools)

scsi0:0.autodetect = "true" autodetect a physical CDrom (unreliable)

scsi0:0.clientDevice Server-versions only

scsi0:0.exclusive = "true" only this VM may use this physical CDrom (don't use unless you need to)

scsi0:0.startConnected = "true" 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.availablescsi.EnableBIOSscsi.lsilogic.availablescsi.passthru.aiomgrscsi.passthru.loggingscsi.passthru.logmaxdata

?

top


2 of 2


serial portsVMX-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"

Linux-hostuseing physical device /dev/ttyS0

serial0.present = "TRUE"serial0.fileType = "device"serial0.fileName = "COM1"serial0.tryNoRxLoss = "FALSE"serial0.autodetect = "FALSE"

Windows-hostuseing a physical device com1

serial0.present = "TRUE"serial0.fileType = "device"serial0.tryNoRxLoss = "FALSE"serial0.autodetect = "TRUE"

this settings use an autodetected host-device

serial0.present = "TRUE"serial0.fileType = "file"serial0.fileName = "serial-port-2-file.txt"serial0.tryNoRxLoss = "FALSE"

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

serial0.present = "TRUE"serial0.fileType = "pipe"serial0.fileName = "\\.\pipe\com_1"serial0.tryNoRxLoss = "TRUE"serial0.pipe.endPoint = "server"

useing a named pipe

this end is the serverthe other end is an application

serial0.present = "TRUE"serial0.fileType = "pipe"serial0.fileName = "\\.\pipe\com_1"serial0.tryNoRxLoss = "FALSE"serial0.pipe.endPoint = "server"

useing a named pipe

this end is the serverthe other end is a VM

serial0.present = "TRUE"serial0.fileType = "pipe"serial0.fileName = "\\.\pipe\com_1"serial0.tryNoRxLoss = "TRUE"serial0.pipe.endPoint = "client"

useing a named pipe

this end is the clientthe other end is an application

serial0.present = "TRUE"serial0.fileType = "pipe"serial0.fileName = "\\.\pipe\com_1"serial0.tryNoRxLoss = "FALSE"serial0.pipe.endPoint = "client"

useing a named pipe

this end is the clientthe other end is a VM

serial0.present main switch

serial0.startConnected true connects device at startup

serial0.fileNameserial0.fileTypeserial0.tryNoRxLosserial0.autodetectserial0.pipe.endPoint

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

serial0.yieldOnMsrRead yuild CPU on poll

serial0.baseAddr

serial0.irq

serial0.allowGuestConnectionControl use true to allow control via vmware-tools

serial0.hardwareFlowControl = "TRUE"

1 of 2


2 of 2


soundVMX-file parametersI 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 VMbad examplethe parameters in detailsadvanced example

drivers for win9xdrivers 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 = TRUEsound.virtualDev = sb16sound.filename = -1sound.autodetect = TRUEsound.deviceNr = -1sound.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 thelogs!

the parameters

sound.present = "true" main-switch to enable sound

sound.startConnected = "true" enables sound at VM-start

sound.allowGuestConnectionControl = "true" allow control via VMware-tools

sound.virtualDev = "sb16"sound.virtualDev = "es1371"

all newer VMware-versions use the ES 1371 per default

sound.autodetect = "true" VMware will detect the appropriate sound device automatically

sound.fileName = "Creative SB Live! Series"sound.fileName = "Creative Sound Blaster PCI"sound.fileName = "Crystal WDM Audio"sound.fileName = "NVIDIA(R) nForce(TM) Audio"sound.fileName = "SB Audigy 2 ZS Audio [A000]"sound.fileName = "SoundMAX Digital Audio"sound.fileName = "YAMAHA AC-XG WDM Audio"

sound.fileName = "-1"

If VMware finds a sound-device that can be used it sets appropriate valueautomatically

"-1" means assign automatically

sound.synth.operational = "true"set to "true" to enable OPL3 / Yamaha synthesizer -AFAIK this only works with "sb16"

sound.baseAddr = "0x220"sound.dma16 = "7"sound.dma8 = "1"sound.irq = "5"sound.mpu401baseAddr = "0x330"sound.Opl3BaseAddr = "0x388"

try these settings to enable sound withDOS 6.2.2

sound.maxLength = "value"sound.smallBlockSize = "value"

use with values like 2 64 128 256 512 1024see KB 617 for info

sound.disableMasterVolume see KB 853

sound.highPriority 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"

try these settings to enable sound withDOS 6.2.2

sound.bufferingsound.copyDelayFactorsound.devicesound.deviceNrsound.devNrsound.directSoundsound.ignoreOverflowssound.logFragmentSizesound.mixersound.virtualrealcorrection

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"

advanced example posted by andremachado

top


2 of 2

Sanbarrow.com

VMX-file parameters - usb ports


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 type gui usage

usb.present true or false switch x main switch

usb.generic.autoconnect true or false switch xuse true to automaticallyconnect when guest hasfocus

usb.generic.resetOnDisconnect true or false switch -

usb.generic.allowHID true or false switch -

usb.generic.devfsPath path_to_usbdevfs path -see .../support/ws55/doc/ws_devices_usb_linux.html

usb.generic.devicesFileName

usb.asapTransfer -

usb.autoConnect.device%d -

usb.FrameLen

usb.idleFrameLen -

usb.options -

usb.stickyConnect true or false switch -

usb.ZeroBasedInterface -

usb.analyzer.enable true or false switch -use true if you want extraverbose logging to debugUSB problems

usb.generic.skipsetconfig true or false switch -skip the low-level USB "setconfiguration" command

uhci.syncWriteback true or false switch -use for Dell 1450 WirelessUSB 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


2 of 2


guestOSVMX-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 thewindows.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 -

guest operatingsystem

PLAYER

SERVER

WS

55

legacy

WS

32

ESX

3

ESX

25

installuses

ether-net

virtualdevicetype

scsivirtualdevicetype

defaultinstalluses

amountofRAM

disk-size

gui-option

comments

darwin x (not available via GUI)

dos x x IDE vlance BUS 16 MS-DOS

freebsd x x IDE vlance LSI 256 Freebsd

freebsd-64 x LSI e1000 LSI 256 FreeBSD 64-bit

other x x IDE vlance BUS 256 Other

other-64 x IDE e1000 LSI 256 Other 64-bit

Netware guests

netware4 x IDE vlance BUS 256 NetWare 4

netware5 x x IDE vlance LSI 256 NetWare 5

netware6 x x LSI vlance LSI 512 NetWare 6

Solaris guests

solaris6 x (not available via GUI) Solaris 6



solaris9 x x IDE vlance LSI 128 Solaris 9 (experimental)

solaris10 x x IDE vlance LSI 512 Solaris 10 (experimental)

solaris10-64 x LSI e1000 LSI 512 Solaris 10 64-bit (experimental)

Linux guests

linux x (not available via GUI) Linux

mandrake x x BUS vlance BUS 256 Mandrake Linux

mandriva-64 x LSI e1000 LSI 256 Mandriva Linux 64-bit

mandriva x LSI vlance LSI 256 Mandriva Linux

nld9 x IDE vlance BUS 256 Novell Linux Desktop 9

other24xlinux x x BUS vlance BUS 256 Other Linux 2.4.x kernel

1 of 3

other24xlinux-64 x LSI e1000 LSI 256 Other Linux 2.4.x kernel 64-bit

other26xlinux x x LSI vlance LSI 256 Other Linux 2.6.x kernel

other26xlinux-64 x LSI e1000 LSI 256 Other Linux 2.6.x kernel 64-bit

otherlinux-64 x LSI e1000 LSI 256 Other Linux 64-bit

otherlinux x BUS vlance BUS 256 Other Linux

redhat x x BUS vlance BUS 256 Red Hat Linux

rhel2 x x BUS vlance BUS 256 Red Hat Enterprise Linux 2

rhel3 x x LSI vlance LSI 256 Red Hat Enterprise Linux 3

rhel3-64 x LSI e1000 LSI 256 Red Hat Enterprise Linux 3 64-bit

rhel4 x LSI vlance LSI 256 Red Hat Enterprise Linux 4

rhel4-64 x LSI e1000 LSI 256 Red Hat Enterprise Linux 4 64-bit

sjds x LSI vlance LSI 256 Sun Java Desktop System

suse x x LSI vlance LSI 256 SUSE Linux

suse-64 x LSI e1000 LSI 256 SUSE Linux 64-bit

sles x x LSI vlance LSI 256 SUSE Linux Enterprise Server

sles-64 x LSI e1000 LSI 256 SUSE Linux Enterprise Server 64-bit

turbolinux x x BUS vlance BUS 256 Turbolinux

ubuntu x LSI vlance LSI 256 Ubuntu

ubuntu-64 x LSI e1000 LSI 256 Ubuntu 64-bit

Windows guests

win2000advserv x x BUS vlance BUS 384 Windows 2000 Advanced Server

win2000pro x x BUS vlance BUS 256 Windows 2000 Professional

win2000serv x x BUS vlance BUS 384 Windows 2000 Server

win31 x x IDE vlance BUS 16 Windows 3.1

win95 x x IDE vlance BUS 64 Windows 95

win98 x x IDE vlance BUS 256 Windows 98

winme x x IDE vlance BUS 256 Windows Me

winnt x x BUS vlance BUS 256 Windows NT

winnetenterprise x x LSI vlance LSI 384 Windows Server 2003 Enterprise Edition

winnetenterprise-64 x LSI e1000 LSI 384 Windows Server 2003 Enterprise x64 Edition

winnetbusiness x x LSI vlance LSI 384 Windows Server 2003 Small Business

winnetstandard x x LSI vlance LSI 384 Windows Server 2003 Standard Edition

winnetstandard-64 x LSI e1000 LSI 384 Windows Server 2003 Standard x64 Edition

winnetweb x x LSI vlance LSI 384 Windows Server 2003 Web Edition

longhorn x x LSI vlance LSI 512 16 Windows Vista (experimental)

longhorn-64 x LSI e1000 LSI 512 24 Windows Vista x64 Edition (experimental)

winxphome x x IDE vlance BUS 256 Windows XP Home Edition

winxppro x x IDE vlance BUS 256 Windows XP Professional

winxppro-64 x LSI e1000 LSI 256 Windows XP Professional x64 Edition

winvista x no defaults(not available via GUI)

winvista-64 x no defaults(not available via GUI)

OS2

os2experimental x x no defaults(not available via GUI)

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

VMware

vmkernel x x no defaults(not available via GUI)

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

2 of 3


3 of 3

Sanbarrow.com

VMX-file parameters - logging


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 logs/vm.log path path to logfile

log.append false switch append to old log ?

log.keepOld 3 value number of logs to keep

log.throttleBytesPerSec value

log.throttleThreshold value

log.timeStamp

log.vmmstats

monitor_control.log_vmsample false switchlog virtual machine progress periodically

GUI-option of newer versions

Home Top


1 of 1


gui settingsVMX-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.managementUIgui.powerOnAtStartup

gui.restrictedgui.shellMsggui.silentRebootOnOsCrash

Advanced


1 of 1


Advanced parametersVMX-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:

bioscdromchipsetdevicesdisklibhard-diskpcisoundpcibridgesvgakeyboard

advanced interaction with the host: answerpowerTyppriorityisolation.toolsmks (mouse, keyboard, screen)uuidmsgguest.commands

advanced setup of the host:hostmainMemmonitor_controlmonitorvmxhypervisor

server related settings:remoteDisplaysched

snapshot handling:snapshotcheckpointundopoint

stupid featuresautoprotect

answer top

answer.msg.serial.file.open = "Replace"answer.msg.serial.file.open = "Append"

automatically answers the question if you want to replace or append an already existingfile used as a serial port

answer.msg.<question_ID> = <answer> manually answer the question once - next look up the question_ID in the vmware.log

bios top

bios.bootDelay = "5000"sets the boot delay in millisecondsWS 6.0.1 / Fusion

bios.forceSetupOnce = "TRUE"force the VM to enter BIOS on next bootWS 6.0.1 / Fusion

bios440.fileName = "name of replacement bios file"replace theoriginalVMware BIOS with your own one - highly experimental andunsupported of course

bios.bootOrder = "ethernet2"

in WS 7 and Fusion 3 you can set the boot-device ...the example boots from the second nicother values that may be used :ide0:0 = boots from IDE-disk or CDrom

1 of 10

scsi0:0 = boots from scsi-disk at controller 0 : 0

the device must be present - otherwise this will be ignored

cdrom top

cdrom.minVirtualTime see knowledgebase

cdrom.aiomgrcdrom.asyncTimeoutcdrom.bufferedPassThroughcdrom.defaultCdbLengthcdrom.directPassThroughcdrom.iso.aiomgrcdrom.lockCDOnReadscdrom.loggingcdrom.logMaxCmdcdrom.logMaxRescdrom.modeSenseIntervalcdrom.raw.aiomgrcdrom.releaseTimeoutcdrom.reopenOnMediaChangecdrom.synchronouscdrom.useNonUnifiedcdrom.useSGIO

?

hard-disk top

hard-disk.useUnbuffered = "true"aiomgr.buffered = "TRUE"

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

hard-disk.asyncTimeouthard-disk.dropiohard-disk.enableIBRhard-disk.minVirtualTimehard-disk.synchronous

?

host top

host.TSC.noForceSync = "true" see kb 928

host.useFastclock = "false" fix timing issues - see kb 892

host.TSC.forcedDeltahost.TSC.maxDeltahost.cpukHzhost.dumpDI

host.noTSCptsc.noTSC

Timekeeping and power management kb article 1227

mainMem top

mainMem.useNamedFile = "true"

silently defaults to "true" - set to "false" if you don't want to use mem-file forswapping - see config.ini

this parameters is used on all Windows platformson 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 withmainmem.backing - see below

mainMem.partialLazyRestore available via GUI

mainMem.partialLazySave available via GUI

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

Workstation 7 on Linux only"swap" only works on 64bit host"named" uses mem file in VM-directory"unnamed" uses mem file in /tmp

mainMem.freeSpaceCheck = "FALSE"

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.allow8GBmainMem.ioBlockPagesmainMem.ioWaitmainMem.pageFileSavemainMem.preAllocVACachemainMem.prefetchMBmainMem.sharedMemHashTableSizemainMem.traceSavemainMem.vaAlignSizemainMem.vaCacheSizemainMem.vaTileSize

dangerous - may affect performance

mks top

mks.ctlAltDel.ignore non functional ???

mks.disableHotkeys

mks.enable3d = "true" required to enable experimental 3d support

mks.noBeep = "true" disable annoying guest-beeps

2 of 10

mks.movie.config.high.recordSound = "true" video-capture with sound - workstation only

mks.movie.config.high.bppDepthmks.movie.config.high.byteBudgetPerFramemks.movie.config.high.byteThresholdWeightmks.movie.config.high.keyFrameThresholdmks.movie.config.high.pixelThresholdWeightmks.movie.config.high.sampleRatemks.movie.config.high.stereomks.movie.config.high.useADPCMmks.movie.config.high.usecPerFramemks.movie.config.high.useVMC2

workstation only

mks.absoluteMousemks.alwaysWatermarkmks.correctRemoteDesktopDirectInputScalemks.debugChainMgrmks.fullscreen.allowScreenSavermks.fullScreenMonitormks.gaffleInjectedModKeysmks.gl.dontLogErrorsmks.gl.doubleBuffermks.gl.fbomks.gl.magFiltermks.gl.minFiltermks.gl.noTimeInfomks.gl.useCopyContextmks.gl.useFBTexturemks.glConsolemks.keyboard.swapAltmks.keyboardFiltermks.maxRefreshRatemks.minFullscreenHeightmks.minFullscreenWidthmks.mouseDebugmks.noEmulateResolutionmks.noGLmks.noHostCursormks.noThinkPadWorkaroundmks.scaleModemks.setMouseParamsmks.showCursormks.stayInFullScreenmks.threadPrioritymks.thumb.fileNamemks.thumb.scaleFactormks.thumb.scaleModemks.thumb.targetHeightmks.thumb.targetWidthmks.thumb.updatePeriodSecsmks.useDirectInputmks.windowed.allowScreenSavermks.x.screenSaverTimeout

?

disklib top

disk.locking = "false" usually VMware use a *lck file to lock vmdks - use "false" to override this -

diskLib.dataCacheMaxReadAheadSize = "0"sets max amount of data that should be read aheadfor clustering use 0 to disable caching at all

diskLib.dataCacheMinReadAheadSize = "0"sets min amount of data that should be read aheadfor clustering use 0 to disable caching at all

diskLib.dataCacheMaxSize = "0"diskLib.dataCachePageSize = "4096"diskLib.maxUnsyncedWrites = "0"

use for clustering

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

diskLib.defaultEmbeddedDescSize sets size of embedded descriptor for monolithic-sparse ???

diskLib.twoGBFlatExtentSize = "2147221504"sets size of the split flat 2GB chunkcould be used in earlier versions to create custom-size split disks

diskLib.twoGBSparseExtentSize = "2146435072"sets size of the split sparse 2GB chunkcould be used in earlier versions to create custom-size split disks

diskLib.sparseMaxFileSizeCheck= "false"disables WS6 overeager filesystem check - (prevents using disks via drivers forext2/3 on Windows or ntfs on Linux ...)

diskLib.bufferedMigratediskLib.createSpaceSafetyMargin

diskLib.dataCacheMaxRABusyCntdiskLib.dataCacheMaxSeqRAdiskLib.dataCachePageSizediskLib.dataCacheSeqThresholddiskLib.dataCacheUpdateFrequencydiskLib.dataCacheUseExtraRA

diskLib.defaultGTEsPerGTdiskLib.disableSparseCheckerdiskLib.flatAllocWriteSizediskLib.grainCoalescing

3 of 10

diskLib.gtCacheModediskLib.gtCacheSizediskLib.ignorePermissionsdiskLib.legacyCheckerTolerateHolesdiskLib.maxNumGrainsCoalesceddiskLib.redoGrainSizediskLib.redundantGrainMetadata

disklib.sparse.bigJobGTWritePolicydisklib.sparse.bigJobMaxChangesBeforeFlushdisklib.sparse.bigJobMaxDirtyGTEsdisklib.sparse.bigJobRGTWritePolicydisklib.sparse.gtWritePolicydisklib.sparse.maxChangesBeforeFlushdisklib.sparse.rgtWritePolicydiskLib.sparseOpenForceCheckdiskLib.sparseRFPWriteSizeThresholddiskLib.sparseSplitStress

diskLib.traceLeveldiskLib.vmhsDefaultSimpleAioMgrdiskLib.vmhsDefaultUnbufAioMgr

priority top

priority.grabbed = "high"priority.grabbed = "normal"

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

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

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

powerType top

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

available via GUI

svga top

svga.vramSizesvga.maxHeightsvga.maxWidth

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

svga.3d.disableStateCachingsvga.3d.floatTexturessvga.3d.maxLightssvga.3d.maxTextureUnitssvga.3d.renderTargetssvga.alwaysAccelFrontsvga.autodetectsvga.capabilitiesMasksvga.debug.fpsFrameCountsvga.debug.portsvga.debug.showFPSsvga.enableOverlaysvga.fitHostDimensionssvga.forceTracessvga.ignoreSavedStatesvga.ignoreVGAPalettesvga.loghwsvga.maxChangeCountsvga.maxChangeTicksvga.maxFullscreenRefreshTicksvga.maxLocalChangeTicksvga.maxNoChangeTicksvga.mergeRectCmdssvga.no3dsvga.no8BitEmulationsvga.noAlphaCursorsvga.noCursorBypasssvga.noCursorBypass2svga.noExtendedFIFOsvga.noFIFOAccelFrontsvga.noFIFOFencesvga.noHWCursorsvga.noMultimonsvga.noOpromsvga.noPitchLocksvga.noPitchLockFifoRegsvga.noPitchLockRegsvga.noRectCopysvga.numDisplayssvga.PCIAccelSizesvga.PCIFBSizesvga.syncTimeLimit

?

4 of 10

svga.yes3dsvga.yesAlphaBlendsvga.yesGlyphClippingsvga.yesGlyphssvga.yesLegacyOffscreensvga.yesOffscreensvga.yesRasterOpsvga.yesRectFill

uuid top

uuid.action = "create"

generate new uuidthis is this the "I copied the VM" answergenerates new MAC for ethernet*-devicesuse for first boot of copied or cloned VMS

uuid.action = "keep"

keep uuidthis is this the "I moved the VM" answerkeeps existing MACuse when you often move your VM

uuid.biosuuid.location

autogeneratedvalues like "56 4d 8e a8 77 69 80 ea-db d7 a2 77 40 fd fd 37"

don't change this manually !

uuid.getHostUuiduuid.newScheme

?

RemoteDisplay top

RemoteDisplay.vnc.enabled = "true"RemoteDisplay.vnc.port = "<port>"RemoteDisplay.vnc.password = "password"

RemoteDisplay.vnc.ipRemoteDisplay.vnc.keyRemoteDisplay.vnc.keyMapRemoteDisplay.vnc.keyMapFileRemoteDisplay.vnc.zlibLevelRemoteDisplay.vncWheelStep

vnc-settings

RemoteDisplay.depth = "24"RemoteDisplay.depth = "16"RemoteDisplay.depth = "8"

set color depth for remote display - server only

RemoteDisplay.bppremoteDisplay.forceDepthRemoteDisplay.maxConnectionsRemoteDisplay.maxHeightRemoteDisplay.maxWidthRemoteDisplay.noRemoteDisplay.noRingBellRemoteDisplay.noVMWCursorEncodingsRemoteDisplay.noVMWEncodings

?

monitor_control

dangerous - may affect performance

top

monitor_control.virtual_rdtsc = "false" This should turn off TSC virtualisation

monitor_control.restrict_backdoor = "true"if you want to run VMware inside a VM you will need this setting - it may cheat anyprogram that scans for the VMware-backdoor channel like Ken Katos vmchk.exeIt is NOT enough to cheat advanced VM-scanning methods like redpill or scoopy

monitor_control.enable_extended_svm = "true"required to run ESX inside aWS 6.0. VM- use with AMD CPUs

monitor_control.vt32 = "true"required to run ESX inside a WS 6.0 VM- use with Intel CPUs

monitor_control.disable_apic = "true"some older versions of FreeBSD needed this entry to install- no longer necessary

monitor_control.simmmu = "true"monitor_control.mmu_adaptive = "true"

very old - used to install OpenStep- no longer necessary

monitor_control.disable_longmode = "1" force Solaris to install in 32bit-mode - see forum

monitor_control.pseudo_perfctr = "true" timing issues ? - see forum

monitor_control.log_vmsample = "false"

monitor_control.disable_checkcodeexpire = "true"monitor_control.disable_checkcode = "true"

used for MAC OS Tiger

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"

disable VM-detection

monitor_control.enable_extended_core

monitor_control.enable_paravirt

5 of 10

monitor_control.enable_vmeopt = "true"

see kb 461

monitor top

monitor.usecHostedVSMPMaxSkew = 0monitor.usecHostedVSMPYieldPoint = 0

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

isolation.tools top

isolation.tools.osNotFound.disable = "false" per default VMware displays the "os not found" message

isolation.tools.copy.disableisolation.tools.copy.enableisolation.tools.paste.disableisolation.tools.paste.enable

isolation.tools.dnd.disable

copy and paste

isolation.tools.hgfs.disable = "false" 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"

this example prevents that the appSword of the New Worlddetects that it is running in a VM

isolation.device.edit.disableisolation.monitor.control.disableisolation.tools.ACPI.disable

isolation.tools.autoConnect.disableisolation.tools.diskShrink.disableisolation.tools.diskWiper.disableisolation.tools.getDiskGeo.disableisolation.tools.getGuiOptions.disableisolation.tools.getInfo.disableisolation.tools.getMachineId.disableisolation.tools.getMemSize.disableisolation.tools.getMhz.disableisolation.tools.getOS2IntCursor.disableisolation.tools.getPtrLocation.disableisolation.tools.getScreenSize.disableisolation.tools.getTime.disableisolation.tools.getUUId.disableisolation.tools.getVersion.disableisolation.tools.haltReboot.disableisolation.tools.haltRebootStatus.disable

isolation.tools.hostCopy.disableisolation.tools.initScsiIoprom.disableisolation.tools.Int13.disableisolation.tools.log.disableisolation.tools.message.disable

isolation.tools.osStateChange.disableisolation.tools.osStateChangeStatus.disableisolation.tools.removeImage.disableisolation.tools.rsvd0.disableisolation.tools.rsvd1.disableisolation.tools.rsvd2.disableisolation.tools.setGUIOptions.disableisolation.tools.setGUIOptions.enableisolation.tools.setInfo.disableisolation.tools.setOption.disableisolation.tools.setPtrLocation.disableisolation.tools.setVersion.disableisolation.tools.stopCatchup.disableisolation.tools.unifiedLoop.disableisolation.tools.updateTools.disableisolation.tools.vmdbpipeSend.disable

schedsorry folks - this is mostly unknown area to me - thanks Oliverfor explanations

top

6 of 10

sched.cpu.affinity = "all"sched.cpu.affinity = "2"sched.cpu.affinity = "2,3,5"sched.cpu.affinity = "2,3"sched.cpu.affinity = "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 corenumbers (counting starts with 0)

sched.cpu.shares = "3158"sched.cpu.shares = "normal"

number of CPU shares

sched.cpu.min = "0"sched.cpu.min =

CPU reservation

sched.cpu.max = "1400"sched.cpu.max = "1600"sched.cpu.max = "800"

maximum CPU usage allowed for VM

sched.cpu.htsharing = "any"sched.cpu.htsharing = "none"sched.cpu.htsharing = "internal"

sharing with HT capable CPUs

sched.cpu.units = "mhz" Units for sched.cpu.min and sched.cpu.max

sched.mem.affinity = "all"sched.mem.affinity = "0,1,2,3,4,5,6,7"

memory affinity for NUMA systems

sched.mem.shares = "696"sched.mem.shares = "normal"

number of memory shares

sched.mem.maxmemctl ESX - specific ?

sched.mem.minsize = "0"memory reservation for a VM if this equals sched.mem.max or the configuredmemory size paging for the VM is disabled setting this also disables page sharing

sched.mem.max = "384"sched.mem.max = "unlimited"

max memory allowed for the VM not useful since this is determined by the VMmemory setting

sched.mem.softlimit ESX - specific ?

sched.mem.swaplimit ESX - specific ?

sched.mem.pshare.checkRatesched.mem.pshare.debugsched.mem.pshare.enablesched.mem.pshare.scanRate

ESX - specific ?

sched.mem.balloon.debugzerofrequencysched.mem.balloon.maxdebugtarget

ESX - specific ?

sched.swap.hostLocalsched.swap.derivedName

location of the VM swap file

sched.net.filter.class = "nfshaper"sched.net.filter.args = "30000000 70000000 4000000"

ESX - specific ?

tools top

toolScripts.afterPowerOn = "true" run script after power on

toolScripts.afterResume = "true" run script after resume

toolScripts.beforePowerOff = "true" run script before power off

toolScripts.beforeSuspend = "true" run script beforer resume

tools.remindInstall = "false" do not remind to install VMware-tools

tools.syncTime = "false" disable time synchronisation via VMware-tools

tools.broadcastIPtools.capability.auto_upgradetools.capability.copypaste_versiontools.capability.display_topology_settools.capability.dnd_versiontools.capability.guest_temp_directorytools.capability.haltreboottools.capability.hgfs_servertools.capability.open_urltools.capability.printer_settools.capability.resolution_mintools.capability.resolution_settools.capability.statechangetools.capability.upgrader_parameterstools.disableSoftPowertools.guestos.phasetools.guestUptimetools.hgfs.volumeInfoTypetools.ipCheckIntervaltools.os.haltreboot.statustools.os.statechange.statustools.set.versiontools.setInfo.sizeLimittools.statetools.statusMsgs.disabletools.syncTime.periodtools.upgrade.policy

7 of 10

pciSound

These parameters are somehow related but not dependant onthe main-switch that

top

pciSound.DAC2InterruptsPerSec = "16" used for MAC OS Tiger

pciSound.enableVolumeControl see KB 853

pciSound.ADCInterruptsPerSecpciSound.DAC1InterruptsPerSecpciSound.emulateMixerpciSound.hostSampleRateDeltapciSound.linearVolumepciSound.noIntrPriorityInheritancepciSound.noLockPriorityInheritancepciSound.noPollPriorityBoostpciSound.noPollThreadpciSound.noSuperPriorityBoostpciSound.playBufferpciSound.priorityBoost

snapshot top

snapshot.action = "keep" gui: just power off

snapshot.action = "autoRevert" gui: revert to snapshot

snapshot.action = "autoCommit" gui: take a new snapshot

snapshot.action = "prompt" gui: ask me

snapshot.asyncConsolidatesnapshot.crash.%dsnapshot.crashTestsnapshot.currentsnapshot.disabledsnapshot.lastUIDsnapshot.mru%d.uidsnapshot.mru.maxNumsnapshot.needConsolidatesnapshot.numSnapshotssnapshot.protectedsnapshot.sanityTestsnapshot.sanityTestIterationssnapshot.sanityTestPeriodsnapshot.version

snapshot0.clonesnapshot0.createTimeHighsnapshot0.createTimeLowsnapshot0.descriptionsnapshot0.disk%d.fileNamesnapshot0.disk%d.modesnapshot0.disk%d.nodesnapshot0.displayNamesnapshot0.filenamesnapshot0.numClonessnapshot0.numDiskssnapshot0.numVPlayssnapshot0.parentsnapshot0.typesnapshot0.uidsnapshot0.vplay%d.displayNamesnapshot0.vplay%d.fileName

vmx top

vmx.acceptConnectionsvmx.allowNestedvmx.alwaysUseSubsysIDvmx.capability.copypaste_versionvmx.capability.dnd_versionvmx.capability.edit_devicesvmx.capability.edit_scriptsvmx.capability.ptr_grab_notificationvmx.capability.tools_pkg_versionvmx.capability.unified_loopvmx.connectserverdvmx.ipc.maxBufferedBytesvmx.ipc.maxBufferedPacketsvmx.maxOutWSSvmx.noPriorityBoostvmx.noPriorityInheritancevmx.set_optionvmx.superPriorityBoostvmx.useLegacySubsysID

guest.commands top

guest.commands.allowAnonGuestCommandsguest.commands.alwaysRelayVixCOmmandsguest.commands.anonGuestCommandsRunAsConsoleUserguest.commands.anonGuestCommandsRunAsRootguest.commands.anonGuestPasswordguest.commands.anonGuestUserName

8 of 10

guest.commands.enabled

undopoint top

undopoint.actionundopoint.checkpointedOnlineundopoint.disableSnapshotsundopoint.protectedundopoint.restoreFromCheckpointundopoints.seqNum

chipset top

chipset.useAcpiBatterychipset.useApmBattery

useful for notebooksthis display battery status inside the VM if set to "true"

chipset.enableGARTchipset.onlineStandbychipset.type new in workstation 6

checkpoint top

checkpoint.overrideVersionCheck = "true"

use to force resume of a suspended VM when the VMware-version has changed

checkpoint.disableCpuCheck = "true"use to force resume of a suspended VM when the CPU has changed - only makessense in some very rare cases

checkpoint.compressLevelcheckpoint.cptConfigNamecheckpoint.fastMonSwitchIDcheckpoint.format.64bitcheckpoint.mks.saveimagecheckpoint.runSuspendTestcheckpoint.stunTortureTestcheckpoint.stunTortureTestIterationscheckpoint.stunTortureTestPeriodcheckpoint.stuntimingcheckpoint.suspendTestIterationscheckpoint.sync.timingcheckpoint.vmStatecheckpoint.vmState.readOnly

msg top

msg.autoAnswer = "TRUE" tries to automatically answer all questions that may occur at boot-time.

hypervisor top

hypervisor.xen.allow

keyboard top

keyboard.allowTypematicInMKSkeyboard.keyboardWaitkeyboard.mouseWaitkeyboard.softAutorepeatkeyboard.typematicMinDelay

pref top

pref.enableTopmost = "FALSE" see forum

pciBridge* top

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

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

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

Sorry at this time I do not know what the function-parameter is good for - do notchange !

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

devices.hotplug = "FALSE"

In virtual hardware mark 7 several devices are seen as removable by the guest likefor example networkcards.If you do not want this behaviour use this parameter - then the VM does not displaynetwork-cards as removable similar to older virtual hardware.

Handle with care - may have other side-effects

9 of 10

autoprotect top

rollingTier*.*

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

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.


10 of 10


config.ini - settingsVMX-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.

memoryprioritycopy and pasteshared foldersmisc ....startup of VMsusage of SSL (server only)workspace and pathsCycling through VM and HostSwitching directly to VM and Host

prevent swapping on a Windows Host (tuned sample settings)

Tip for Windows-user: this file can be found inC:\documents and settings\All Users\Application Data\VMware\VMware WorkstationIf you can't see it - fix your explorer settings to display hidden files

memory

prefvmx.minVmMemPct = "100"fit memory into RAMWhenever possible avoid settings lower 100%

prefvmx.minVmMemPct = "50" allow some memory to be swapped

prefvmx.minVmMemPct = "25" allow most memory to be swapped

prefvmx.allVMMemoryLimit = "1272"

sets the maximum amount of RAM that can be used by VMs-if this is less than at least 80% of the physical RAMsomething is going wrong:scan through preferences.ini and config.ini for memory-relatedentries, power down all running VMs and delete these lines andrestart your host.Do not launch any other apps! Create a new VM and check ifanything has changed.

mainMem.partialLazyRestore = "true" restore snapshots in background -

mainMem.partialLazyRestore = "false" do not restore snapshots in background

mainMem.partialLazySave = "true" take snapshots in background

mainMem.partialLazySave = "false" do not take snapshots in background

mainMem.useNamedFile = "true"creates a file the size of nominal RAM in working directoryfile uses random name

mainMem.useNamedFile = "false"

doesn't use named-file - use for VMs on USB-disks or other slowdisksWindows: useNamedFile= "FALSE" causes memory to be backedby the host's swap space.Linux: useNamedFile= "FALSE" causes a hidden file to be created ina temporary directory, which is immediately deleted when youpower off the VM

priority top

priority.grabbed = "high"priority.grabbed = "normal"

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

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

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

1 of 3

prevent swapping on a Windows Host top

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"

prevent swapping on a windows-host

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

copy and paste top

Isolation.tools.copy.enable = "true"enable copy function (vmware-tools) - use same settings for ...paste.enable

Isolation.tools.copy.enable = "false" disable copy function (vmware-tools)

Isolation.tools.paste.enable = "true" enable paste function (vmware-tools)

Isolation.tools.paste.enable = "false" disable paste function (vmware-tools)

shared folders top

Isolation.tools.HGFS.disable = "true" disables shared-folders - if implemented

Isolation.tools.HGFS.disable = "false" enables shared-folders - if implemented

misc top

mks.ctlAltDel.ignore = "true" see

mks.fullscreen.allowScreenSaver = "true" see

fullScreenSwitch.onSeparateDesktop = "true" see

beep top

mks.noBeep = "TRUE"in earlier versions you could add this entry to the vmx-file to get ridof anoying BIOS-beeps via the computer-speaker.looks like you have to add this to the config.ini with Workstation 6

startup top

msg.autoAnswer = "true" tries to automatically answer all pop-ups at start of a VM

startup top

msg.autoAnswer = "true" tries to automatically answer all pop-ups at start of a VM

security top

security.host.muissl= "true" use SSL for the remote-console

security.host.muissl = "false" don't use SSL for the remote-console

workspace top

defaultVMPath = "path"datastore.namedatastore.localpath = "path"

This sets the workspace - new VMs will be created here

cycling through VM and Host top

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

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

switching directly to VM and Host top

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

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

hv.enableIfUnlocked = TRUE

Workstation 6.5 only ???

If you have a buggy BIOS which fails to re-enable VT whenawakening from deep sleep, this option may help you:

top


3 of 3


preferences.ini - settingsVMX-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"

VMs are listed like this

pref.eula.1.appName = "VMware Workstation"pref.eula.1.buildNumber = "185517"pref.eula.2.appName = "VMware Player"pref.eula.2.buildNumber = "185517"

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"

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

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"

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.disableExitFullScreenOnHotkeyReleasepref.hotkey.disableHotkeyDeletepref.hotkey.disableHotkeyEscapepref.hotkey.disableHotkeyInsertpref.hotkey.leftAltpref.hotkey.leftControlpref.hotkey.leftShiftpref.hotkey.rightAltpref.hotkey.rightControlpref.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"

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

pref.tip.startup = "FALSE"pref.tip.index = "3"

startup-tips

pref.grabOnKeyPress = "TRUE"pref.grabOnMouseClick = "TRUE"

VM grabs keyboard and mouse when set to "true"


1 of 2

2 of 2

VMX Reference

Documents

Transcript of VMX Reference