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 VMware- documentation - 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 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 Commented parameters for behaviour of the VM: Guest operating system Displayname Logging GUI Movies 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) 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: bios cdrom chipset disklib hard-disk pcisound svga keyboard 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 Server related settings: remoteDisplay sched Snapshot handling: snapshot checkpoint undopoint 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 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
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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
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
home vmx vmdk about this site forum downloads
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
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
home vmx vmdk about this site forum downloads
1 of 1
home vmx vmdk about this site forum downloads
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
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
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
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
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.
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.
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
home vmx vmdk about this site forum downloads
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.
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"
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
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"
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
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.
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
about this site - forum
2 of 2
home vmx vmdk about this site forum downloads
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
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 !!!
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
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
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
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.
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.
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 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 will start connected
the device uses bidirectional mode
parallel0.startConnected true switch
parallel0.bidirectional true switch
parallel0.fileType device switch
parallel0.present true switch this settings use a automatically detected host-device
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
home vmx vmdk about this site forum downloads
2 of 2
home vmx vmdk about this site forum downloads
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
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
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
solaris7 x (not available via GUI) Solaris 7
solaris8 x (not available via GUI) Solaris 8
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
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 ...
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
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
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 ...)
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
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
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.
home vmx vmdk about this site forum downloads
10 of 10
home vmx vmdk about this site forum downloads
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
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
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 ...