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
Vote on this issue by adding a 馃憤 reaction to the original issue initial description to help the maintainers prioritize.
Do not leave "+1" or other comments that do not add relevant information or questions.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Terraform
v1.7.5, v1.8.1
Terraform Provider
v2.7.0
VMware vSphere
v8.0 u2b
Description
The support for hot add CPU and memory is currently broken. A change to CPU and memory causes an VM to reboot. This is 100% reproducible.
Affected Resources or Data Sources
VM/
Terraform Configuration
#VMware vSphere Provider
provider "vsphere" {
#Set of variables used to connect to the vCenter
vsphere_server = var.vsphere_server
user = var.vsphere_user
password = var.vsphere_password
#If you have a self-signed cert
allow_unverified_ssl = true
}
#Name of the Datacenter in the vCenter
data "vsphere_datacenter" "dc" {
name = "DC1"
}
#Name of the Cluster in the vCenter
data "vsphere_compute_cluster" "cluster" {
name = "Cluster"
datacenter_id = data.vsphere_datacenter.dc.id
}
#Name of the Datastore in the vCenter, where VM will be deployed
data "vsphere_datastore" "datastore" {
name = "vSAN"
datacenter_id = data.vsphere_datacenter.dc.id
}
#Name of the Portgroup in the vCenter, to which VM will be attached
data "vsphere_network" "external_network" {
name = "External"
datacenter_id = data.vsphere_datacenter.dc.id
}
#Name of the Portgroup in the vCenter, to which VM will be attached
data "vsphere_network" "internal_network" {
name = "Public"
datacenter_id = data.vsphere_datacenter.dc.id
}
#Name of the Templete in the vCenter, which will be used to the deployment
data "vsphere_virtual_machine" "rocky9-template" {
name = "rocky9-temp"
datacenter_id = data.vsphere_datacenter.dc.id
}
#Set VM parameteres
resource "vsphere_virtual_machine" "rocky9-vm" {
name = "rocky91"
num_cpus = 2
memory = 4096
firmware = "efi"
cpu_hot_add_enabled = "true"
memory_hot_add_enabled = "true"
guest_id = "rockylinux_64Guest"
resource_pool_id = data.vsphere_compute_cluster.cluster.resource_pool_id
datastore_id = data.vsphere_datastore.datastore.id
network_interface {
network_id = data.vsphere_network.external_network.id
}
network_interface {
network_id = data.vsphere_network.internal_network.id
}
disk {
label = "disk0"
thin_provisioned = true
size = 50
}
clone {
template_uuid = data.vsphere_virtual_machine.rocky9-template.id
#Linux_options are required section, while deploying Linux virtual machines
customize {
linux_options {
host_name = "rocky91"
domain = "net.local"
}
network_interface {
ipv4_address = "10.10.1.5"
ipv4_netmask = "23"
}
network_interface {
#ipv4_address = "192.168.80.11"
#ipv4_netmask = "24"
}
ipv4_gateway = "10.10.1.1"
}
}
lifecycle {
ignore_changes = [hv_mode, ept_rvi_mode]
}
}
#Outup section will display vsphere_virtual_machine.ubu-testing Name and IP Address
output "VM_Name" {
value = vsphere_virtual_machine.rocky9-vm.name
}
output "VM_IP_Address" {
value = vsphere_virtual_machine.rocky9-vm.guest_ip_addresses
}
Community Guidelines
Terraform
v1.7.5, v1.8.1
Terraform Provider
v2.7.0
VMware vSphere
v8.0 u2b
Description
The support for hot add CPU and memory is currently broken. A change to CPU and memory causes an VM to reboot. This is 100% reproducible.
Affected Resources or Data Sources
VM/
Terraform Configuration
Debug Output
Above two changes should not reboot the target VMs.
Panic Output
No response
Expected Behavior
Increasing CPU cores or memory size should take effect immediately without rebooting the target VM.
Actual Behavior
Increasing CPU core and memory size both cause the target VM reboot.
Steps to Reproduce
Environment Details
No response
Screenshots
No response
References
No response
The text was updated successfully, but these errors were encountered: