[time in guest advances by 1 hour on every restart of the vm or unraid...]

On 10/23/2023 at 7:30 PM, SimonF said:

Do you not have time update enabled in Windows? I have not seen this issue on my Windows VM. Quick review of the code the value is being used to Identify Windows vs other so it is not just a default change. Also timer section is currently only written for a new VM.

 

I do have this enabled but for some reason, Windows doesn't execute this frequently enough for it to fix the issue. Before I made the change suggested above, it literally set the wrong time every boot from the emulated UEFI without checking with the NTP servers

[time in guest advances by 1 hour on every restart of the vm or unraid...]

On 3/14/2021 at 11:21 AM, reyo said:

Just view it as XML, find the clock section and change the  <clock offset='localtime'> to <clock offset='utc'> . Seems like Windows wants UTC as base and adds the timezone to that. Thats why the time goes wrong: it gets localtime from host (which is already +3h e.g) like 14:00, adds offset +3 and you get 17:00. Which is 3 hours ahead.

This works like a charm. Which just begs the question: How can we get this implemented as default when users create a VM with the Windows presets? Windows has been like this for at least the better part of the last decade. Is there some way we can flag this 1 minute fix to Lime Tech to implement?

[INTEL 12TH GEN ALDERLAKE UHD770 /GT1 IGPU PASSTHROUGH NO DISPLAY]

Have there been any developments on this at all? I got the SR-IOV working with the thread linked above (not smooth on 6.12.4 but workable) but similarly to Ryan that does not really cover my use-case. I'd rather not have to add a dedicated GPU to use the GPU with display outputs from a power consumption perspective.