ID #1086

Autogenerated parameters

Several parameters will be automatically added - in case they are not defined - on first boot of a VM.

In most cases there is no need to change any of these.




nvram = "Windows 2000 Professional.nvram"
if not defined the nvram-file will be created on first boot.
If you want to use a different name or different path you must set this.

extendedConfigFile = "Windows 2000 Professional.vmxf"
if not defined the vmxf-file will be created on first boot.
If you want to use a different name or different path you must set this.
The vmxf-file is used to configure the team-membership.

uuid.location = "56 4d 3f 87 35 d5 3e 8f-d0 61 82 c8 e4 fa 5e ce"
uuid.bios = "56 4d 3f 87 35 d5 3e 8f-d0 61 82 c8 e4 fa 5e ce"
This two parameters are autocreated on first boot.
They use a host-specific checksum which enables VMware to detect if a VM has been moved.
Usually there is no need to edit this manually.



pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "33"
sound.pciSlotNumber = "34"
ehci.pciSlotNumber = "35"
vmci0.pciSlotNumber = "36"

In virtualHardware 7 PCI-slots parameters are autoconfigured on first boot.
Changing the PCI-slots manually is not recommeded.
Especially do NOT change
scsi0.pciSlotNumber = "16"
unless you can handle the problems that may occur.
Misconfigured this can result in a boot-failure.

Tags: uuid, vmx

Related entries:

You can comment this FAQ

Comment of Patrick:
Does any one have working vmx file for wdoinws 2003 server?I have the followingconfig.version = 8 virtualHW.version = 3 ide0:0.present = TRUE ide0:0.filename = Windows2003.vmdk memsize = 256 MemAllowAutoScaleDown = FALSE ide1:0.present = TRUE ide1:0.fileName = auto detect ide1:0.deviceType = cdrom-raw ide1:0.autodetect = TRUE floppy0.present = FALSE ethernet0.present = TRUE usb.present = TRUE sound.present = TRUE sound.virtualDev = es1371 displayName = Windows 2003 Server guestOS = wdoinws2003pro nvram = Windows2003.nvram MemTrimRate = -1 ide0:0.redo = ethernet0.addressType = generated uuid.location = 56 4d b2 3d 65 f6 04 c1-44 9d 8c 88 d6 3c 1f af uuid.bios = 56 4d b2 3d 65 f6 04 c1-44 9d 8c 88 d6 3c 1f af ethernet0.generatedAddress = 00:0c:29:3c:1f:af ethernet0.generatedAddressOffset = 0 tools.syncTime = TRUE ide1:0.startConnected = TRUE uuid.action = create checkpoint.vmState = extendedConfigFile = Windows2003.vmxf virtualHW.productCompatibility = hosted tools.upgrade.policy = manual usb.autoConnect.device0 = tools.remindInstall = TRUE The error message is guest operating system wdoinws2003 is not supported
Added at: 2012-04-01 21:23