Hallo we the same problem and cannot use this module for IPv6 configuration.
The example configuration of @TheMysteriousX c would be really nice to use.

+1

For the record, it looks like there's a ipV6Config in HostIpConfig(vim.host.IpConfig).

For the record, it looks like there's a ipV6Config in HostIpConfig(vim.host.IpConfig).

would it work out of the box to use that in the ansible module?

well tried it out, does not work out of the box with the ansible module

Unsupported parameters for (community.vmware.vmware_vmkernel) module: network.ipV6Config. Supported parameters include: default_gateway, ip_address, subnet_mask, tcpip_stack, type.

I've had a closer look at this, and it turns out to be more complicated than I thought. The ipV6Config doesn't only allow DHCPv6 and static configuration, but also auto configuration.

Additionally, it expects a list of IPv6 addresses. And they look a little bit more complicated than just address + netmask / prefix length.

Actually, I'm not really sure that I understand enough about IPv6 and how it's implemented in ESXi to come up with a solution in this module :-/

The HostIpConfigIpV6AddressConfiguration object is simpler than it looks - it is valid to have dhcp, autoconfig, and static addressing all switched on simultaneously, all disabled, or any combination thereof, so it's enough to just expose the toggles. They don't need to be mutually exclusive.

The extra options in HostIpConfigIpV6Address are there as the same object type is used when you query for the list of addresses, so can be mostly ignored - lifetime and dadState are populated by the hypervisor when the list of addresses is queried via the API.

For origin, you probably need to just allow the choice of 'manual' and 'other'. I don't see a valid use case for the others, as creating a DHCP or SLAAC address via the API makes no sense.