IPv4 is required when triggering Guest OS Customization via vSphere API

Products

• VMware vCenter Server

Issue/Introduction

The vpxd service in vCenter Server 8.0 might crash with a core dump, when you attempt to initiate a guest OS customization using a Guest Customization Spec for a virtual machine in vSphere 8.0 via the vSphere API.

Environment

VMware vCenter Server 8.0.x

Cause

When creating a Guest Customization Specification and using Customization to customize the guest OS via the APIs, it needs to set the 'ipv4' configuration(https://developer.broadcom.com/xapis/vsphere-automation-api/latest/vcenter/data-structures/Guest_Ipv4/) in the Customization Specification. The 'ipv4' settings are required, otherwise vpxd core dump will occur in the vSphere 8.0 environment.

E.g.
The correct configuration in the "adapter":
"interfaces": [
{
    "adapter": {
        "ipv4": {
            "gateways": ["##.XX.##.##"],
            "ip_address": "##.XX.##.##",
            "prefix": 28,
            "type": "STATIC"
        }
    }
}
]

The incorrect configuration in the "adapter":
"interfaces": [
{
"adapter": {}
}
]

Resolution

This issue has been fixed in VMware vCenter Server 8.0 Update 3g, released on July 29, 2025.

As a workaround, add the 'ipv4' settings in the "adapter" of the customization specification. Both DHCP and Static types are OK.