topic Re: clock offset in HPE Morpheus VM Essentials Software

clock offset

dya — Thu, 06 Aug 2026 07:46:21 GMT

Hello,

I am having trouble because I cannot change the following virtual machine setting from the WebUI:

While this is fine for Linux, I would like to change it to "localtime" or similar for Windows. Even though the guest synchronizes time via NTP, I feel that having a time offset upon boot makes logs harder to read. Also, while other KVM-based virtualization platforms should allow this to be changed, VME does not allow it from the WebUI, and I am struggling because even if I modify it directly using virsh edit, there is no guarantee that the setting will be preserved.

Am I the only one experiencing this...?

*Apologies if anything is unclear due to machine translation.

Re: clock offset

DiegoDelgado — Wed, 05 Aug 2026 02:06:43 GMT

This is already in the process of being looked at by our engineering teams. We still need to scope it and get it in our roadmap, please be patient.

Can you provide any insights on other platforms that allow it?

Re: clock offset

dya — Wed, 05 Aug 2026 08:23:00 GMT

@DiegoDelgado

Thank you for checking.
I hope this will also be supported in VME.
For reference, I have included the link below.

・Proxmox
QEMU/KVM Virtual Machines
※localtime:

・oVirt
Virtual Machine Management Guide | oVirt
※Hardware Clock Time Offset

Re: clock offset

dya — Fri, 28 Aug 2026 19:01:20 GMT

I have verified this on v9.0.2.
I thought it might take some time so it wasn't completely unexpected, but it still hasn't changed.
Regarding the time/clock issue, rather than overthinking minor details like the scope of impact, I just want it to be in a "natural" state, so I hope it will be addressed soon.

Re: clock offset

dya — Tue, 22 Sep 2026 00:02:52 GMT

Regarding the issue where the clock offset cannot be changed from UTC, I assume it will take time even if it is to be fixed in the future. Therefore, I would like to know the workaround on the guest OS (Windows) side. I believe the following method is common, but is my understanding correct that the workaround provided for VME would be the same as this? Also, is there any possibility that problems could occur as a result of implementing this?

https://discourse.ubuntu.com/t/how-to-keep-windows-11-time-sychronized-alone-with-ubuntu/83952/2 *reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /t REG_DWORD /d 1 /f

While this relates to Windows specifications, VME provides the execution environment for virtual machines. Therefore, I believe it is necessary to present a workaround as VME.

Re: clock offset

dya — Sat, 26 Sep 2026 05:06:10 GMT

I used "HPE_VM_Essentials_SW_image_v9.0.2_2_S6E64-11258.iso", but I was unable to change the "clock offset".