vmware.vmware_rest.vcenter_vm_hardware_serial module – Manage virtual serial ports on a virtual machine.
Note
This module is part of the vmware.vmware_rest collection (version 5.0.0).
You might already have this collection installed if you are using the ansible package.
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install vmware.vmware_rest.
To use it in a playbook, specify: vmware.vmware_rest.vcenter_vm_hardware_serial.
New in vmware.vmware_rest 5.0.0
Synopsis
Create, update, and delete virtual serial ports attached to a VMware virtual machine.
A virtual serial port can be backed by a file on a datastore, a physical serial port device on the ESXi host, a named pipe, or a network location.
This module also supports connecting and disconnecting an existing virtual serial port at runtime using the
connectanddisconnectstates.Only
presentandabsentstates are idempotent.
Parameters
Parameter |
Comments |
|---|---|
Flag indicating whether the guest can connect and disconnect the device. Defaults to false if omitted. Choices:
|
|
Physical resource backing for the virtual serial port. If omitted, defaults to automatic detection of a suitable host device. |
|
Path of the file that should be used as the virtual serial port backing. Only relevant when type is |
|
Name of the host device that should be used as the virtual serial port backing. If omitted, the virtual serial port will be configured to automatically detect a suitable host device. Only relevant when type is |
|
URI specifying the location of the network service backing the virtual serial port. When type is When type is Only relevant when type is |
|
Flag that enables optimized data transfer over the pipe. When set to true, the host buffers data to prevent data overrun, allowing the virtual machine to read all of the data transferred over the pipe with no data loss. Defaults to false if omitted. Only relevant when type is Choices:
|
|
Name of the pipe that should be used as the virtual serial port backing. Only relevant when type is |
|
Proxy service that provides network access to the network backing. If set, the virtual machine initiates a connection with the proxy service and forwards the traffic to the proxy. If omitted, no proxy service is used. |
|
Backing type for the virtual serial port.
Choices:
|
|
Identifier of the virtual serial port to manage. Must be an identifier (MOID) for a Required when state is When state is |
|
Timeout in seconds for the whole operation including connection establishment, request sending, and response. Default: |
|
Flag indicating whether the virtual device should be connected whenever the virtual machine is powered on. Defaults to false if omitted. Choices:
|
|
The desired state of the resource. Use Use Use Use Only Choices:
|
|
The hostname or IP address of the vSphere vCenter. If the value is not specified in the task, the value of environment variable |
|
The vSphere vCenter password. If the value is not specified in the task, the value of environment variable |
|
The port number of the vSphere vCenter. If the value is not specified in the task, the value of environment variable |
|
Optional path to a log file for HTTP REST interaction. If the value is not specified in the task, the value of environment variable |
|
The vSphere vCenter username. If the value is not specified in the task, the value of environment variable |
|
Allows connection when SSL certificates are not valid. Set to If the value is not specified in the task, the value of environment variable Choices:
|
|
Identifier of the virtual machine that owns the serial port. Must be an identifier (MOID) for a |
|
CPU yield behavior. If set to true, the virtual machine will periodically relinquish the processor if its sole task is polling the virtual serial port. The amount of time it takes to regain the processor depends on the degree of other virtual machine activity on the host. Defaults to false if omitted. Choices:
|
Notes
Note
Generated from vSphere API spec 9.1.0.
Compatible with vSphere API 7.0.3.
Compatible with vSphere API 8.0.2.
Examples
- name: Add a virtual serial port backed by a file
vmware.vmware_rest.vcenter_vm_hardware_serial:
vm: vm-1001
backing:
type: FILE
file: "[datastore1] serial/port1.log"
start_connected: true
allow_guest_control: true
state: present
register: serial_result
- name: Add a virtual serial port backed by a host device
vmware.vmware_rest.vcenter_vm_hardware_serial:
vm: vm-1001
backing:
type: HOST_DEVICE
host_device: /dev/ttyS0
state: present
- name: Add a network-backed virtual serial port acting as a server
vmware.vmware_rest.vcenter_vm_hardware_serial:
vm: vm-1001
backing:
type: NETWORK_SERVER
network_location: telnet://:12345
yield_on_poll: true
state: present
- name: Update an existing virtual serial port
vmware.vmware_rest.vcenter_vm_hardware_serial:
vm: vm-1001
port: '{{ serial_result.id }}'
allow_guest_control: false
state: present
- name: Connect a virtual serial port
vmware.vmware_rest.vcenter_vm_hardware_serial:
vm: vm-1001
port: '{{ serial_result.id }}'
state: connect
- name: Disconnect a virtual serial port
vmware.vmware_rest.vcenter_vm_hardware_serial:
vm: vm-1001
port: '{{ serial_result.id }}'
state: disconnect
- name: Remove a virtual serial port
vmware.vmware_rest.vcenter_vm_hardware_serial:
vm: vm-1001
port: '{{ serial_result.id }}'
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
MOID of the managed virtual serial port. Returned: When state is present, or when a resource is deleted, or when state is set to a supported action. Sample: |
|
The raw API response body from the vCenter operation. Returned: On success Sample: |