Deprecated Directives

The following directives are deprecated and should not be used in new pod designs.

pod.requires.vm_same_host

Require all virtual machines in a pod to run on the same virtual machine host.

Deprecated - Version 22 and Higher

Virtual machines of a single pod always run on the same host.

Synopsis

pod.requires.vm_same_host=<value>

Values

Meaning

1

Virtual machines for this must reside on same host (default).

0

Virtual machines need not reside on same host (ignored).

pod.requires.vm_types

This directive previously enforced the types of virtual machines that can be used with this pod.

Deprecated - Version 22 and Higher

This setting is now ignored.

Synopsis

pod.requires.vm_types=<value>

Values

Meaning

AVMI

Virtual machines of type AVMI are required.

vswitch.<n>.name.include.pod_id

If enabled, the pod ID is included in the virtual switch name. This is the default behavior.

Deprecated - Version 25 and Higher

This setting is now deprecated and only relevant to VMware vSphere. This directive has no effect in the Proxmox/KVM environment.

Syntax

vswitch.<n>.name.include.pod_id=<value>

  • <n> is the virtual switch number: 0, 1, 2, etc.

  • <value> is either 1 or 0

Value

Meaning

1

Include the pod ID in the virtual switch name (default).

0

Do not include the pod ID in the virtual switch name.

Examples

# For the following examples assume:
# Global system ID is 001, virtual switch number is 0, and pod ID is 529.

# Creates a virtual switch using the default pod_id and suffix settings (recommended).
# The resulting virtual switch name is NETLAB001_POD529_VS0.
vswitch.0.name.include.pod_id=1

# Same as above but omit the pod ID from the virtual switch name.
# The virtual switch is named NETLAB001_VS0.
# The resulting virtual switch name is NETLAB001_VS0.
vswitch.0.name.include.pod_id=0

# Creates a virtual switch named NETLAB001_POD529_MGT with suffix MGT.
vswitch.0.name.include.pod_id=1
vswitch.0.name.suffix=MGT

# Creates a virtual switch named NETLAB001_DMZ with suffix DMZ.
# This is a static name that is not unique across pods!
vswitch.0.name.include.pod_id=0
vswitch.0.name.suffix=DMZ

Tip

Setting vswitch.<``n>.name.include.pod_id=0 in combination with vswitch.<n>.suffix will result in a static virtual switch name that is not unique across pods. If that is your intent and you wish to attach virtual NICs to shared networks that cross pod boundaries, please see the Static Networking section for caveats.

vswitch.<n>.name.suffix

An optional suffix that can be added to the virtual switch name. If omitted, the label VS followed by the virtual switch number is used.

Deprecated - Version 25 and Higher

This setting is now deprecated and only relevant to VMware vSphere. This directive has no effect in the Proxmox/KVM environment.

Syntax

vswitch.<n>.name.suffix=<text>

  • <n> is the virtual switch number: 0, 1, 2, etc.

  • <text> is a text string to append to the virtual switch name. If omitted, the label VS followed by the virtual switch number is used.

Restrictions

  • Only use ASCII character A-Z, a-z, 0-9, and _ (underscore).

  • Do not use spaces or enclose in quotes.

  • The entire virtual switch name cannot exceed exceed 32 characters, including the system ID and pod ID.

  • Suffix should not exceed 10 characters.

Tip

Setting vswitch.<n>.name.include.pod_id in combination with vswitch.<n>.suffix will result in a static virtual switch name that is not unique across pods. This is usually not recommended, but may be useful when targeting a static network name.

Example

# For the following examples assume:
# Global system ID is 001, virtual switch number is 0, and pod ID is 529.
# Creates a virtual switch named NETLAB001_POD529_MGT with suffix MGT.
vswitch.0.name.include.pod_id=1
vswitch.0.name.suffix=MGT

# Creates a virtual switch named NETLAB001_DMZ with suffix DMZ.
# This is a static name that is not unique across pods!
vswitch.0.name.include.pod_id=0
vswitch.0.name.suffix=DMZ

Tip

Setting vswitch.<n>.name.include.pod_id in combination with vswitch.<n>.suffix will result in a static virtual switch name that is not unique across pods. This is usually not recommended, but may be useful when targeting a static network name.

vswitch.<n>.portgroup.<p>.name.include.pod_id

If enabled, the pod ID is included in the port group name. This is the default behavior.

Deprecated - Version 25 and Higher

This setting is now deprecated and only relevant to VMware vSphere. This directive has no effect in the Proxmox/KVM environment.

Syntax

vswitch.<n>.portgroup.<p>.name.include.pod_id=<value>

  • <n> is the virtual switch number (0, 1, 2, etc.)

  • <p> is the port group number (0, 1, 2, etc.)

  • <value> is either 1 (include) or 0 (omit)

Value

Meaning

1

Include the pod ID in the port group name (default).

0

Do not include the pod ID in the port group name.

vswitch.<n>.portgroup.<p>.name.suffix

An optional suffix that can be added to the port group name. If omitted, the label PG followed by the port group number is used.

Deprecated - Version 25 and Higher

This setting is now deprecated and only relevant to VMware vSphere. This directive has no effect in the Proxmox/KVM environment.

Syntax

vswitch.<n>.portgroup.<p>.name.suffix=<text>

  • <n> is the virtual switch number (0, 1, 2, etc.)

  • <p> is the port group number (0, 1, 2, etc.)

  • <text> is a text string to append to the port group name.

    • The entire port group name cannot exceed exceed 32 characters, including the system ID and pod ID.

    • Thus, suffix should be 10 characters or less.

    • Use ASCII A-Z, a-z, 0-9, and underscore (_) characters only.

    • Do not use spaces or enclose in quotes.

vswitch.<n>.portgroup.<p>.name.suffix

An optional suffix that can be added to the port group name. If omitted, the label PG followed by the port group number is used.

Deprecated - Version 25 and Higher

This setting is now deprecated and only relevant to VMware vSphere. This directive has no effect in the Proxmox/KVM environment.

Syntax

vswitch.<n>.portgroup.<p>.name.suffix=<text>

  • <n> is the virtual switch number (0, 1, 2, etc.)

  • <p> is the port group number (0, 1, 2, etc.)

  • <text> is a text string to append to the port group name.

    • The entire port group name cannot exceed exceed 32 characters, including the system ID and pod ID.

    • Thus, suffix should be 10 characters or less.

    • Use ASCII A-Z, a-z, 0-9, and underscore (_) characters only.

    • Do not use spaces or enclose in quotes.

pc.<i>.vmx_vhv_enable

Enables the virtual hardware virtualization (VHV) feature for a virtual machine.

Deprecated

This setting is now deprecated and only relevant to VMware vSphere. This directive has no effect in the Proxmox environment. Use the setting pc.<i>.nested_vm_support instead.

The VHV feature allows a virtual machine to run nested 64-bit virtual machines. This feature is required for running 64-bit virtual machines inside a virtual machine.

Tip

Enable this feature if you plan to run 64-bit virtual machines inside a virtual machine (i.e. nested virtualization). Some hypervisors do not require this setting for nested virtualization, however, it is recommended to enable this setting for all hypervisors to ensure compatibility. It is ignored by hypervisors that do not support or require it.

Synopsis

pc.<i>.vmx_vhv_enable=<value>

  • <i> is the remote PC index number (1, 2, etc.) starting at 1 (not 0).

  • <value> is either 1 (enabled) or 0 (disabled).

Value

Meaning

1

Enable the VHV feature for the virtual machine.

0

Disable the VHV feature for the virtual machine. (default)

Examples

pc.1.name=esx1
pc.1.vmx_vhv_enable=1