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
At this point I gather an update for open-vm-tools should solve this, but this has happened yet, as tested with ubuntu 24.04 cloud image from 10 July 2024.
In my case this probably results in the network interface not being attached after powering on the virtual machine, even if the original template does have the option checked.
That vmtools stop using hwclock and use timedatectl.
Additional context
I would like to know if there's been any progress here and if this is discussed anywhere. I've looked at the issues here and haven't found any mentions related to this topic, but I might have missed it.
The text was updated successfully, but these errors were encountered:
The Linux guest customization Perl scripts come from the vCenter Server, not from open-vm-tools.
The scripts have been updated to skip attempting setting the hardware clock if the hwclock command is not available on the system.
The updated scripts are in the recent releases of vCenter:
Describe the bug
This bug has been reported here https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206
At this point I gather an update for open-vm-tools should solve this, but this has happened yet, as tested with ubuntu 24.04 cloud image from 10 July 2024.
In my case this probably results in the network interface not being attached after powering on the virtual machine, even if the original template does have the option checked.
Reproduction steps
Expected behavior
That vmtools stop using
hwclock
and usetimedatectl
.Additional context
I would like to know if there's been any progress here and if this is discussed anywhere. I've looked at the issues here and haven't found any mentions related to this topic, but I might have missed it.
The text was updated successfully, but these errors were encountered: