You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/r/virtual_machine.html.markdown
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1518,6 +1518,25 @@ When cloning from a template, there are additional requirements in both the reso
1518
1518
1519
1519
You can use the [`vsphere_virtual_machine`][tf-vsphere-virtual-machine-ds] data source, which provides disk attributes, network interface types, SCSI bus types, and the guest ID of the source template, to return this information. See the section on [cloning and customization](#cloning-and-customization) for more information.
1520
1520
1521
+
1522
+
## USB Controller
1523
+
1524
+
When creating a virtual machine or cloning one from a template, you have the option to add a virtual USB controller device.
1525
+
1526
+
**Example**:
1527
+
1528
+
```hcl
1529
+
resource "vsphere_virtual_machine" "vm" {
1530
+
# ... other configuration ...
1531
+
usb_controller {
1532
+
usb_version = "3.1"
1533
+
}
1534
+
# ... other configuration ...
1535
+
}
1536
+
```
1537
+
1538
+
~> **NOTE:** Supported versions include 2.0 or 3.1. This setting is only available on new builds and reconfiguration to add a USB controller; removal is not supported in the provider.
1539
+
1521
1540
## Virtual Machine Migration
1522
1541
1523
1542
The `vsphere_virtual_machine` resource supports live migration both on the host and storage level. You can migrate the virtual machine to another host, cluster, resource pool, or datastore. You can also migrate or pin a virtual disk to a specific datastore.
0 commit comments