Domain Time off for some members
-
@DustinB3403 said in Domain Time off for some members:
Is your hypervisor time off?
Exactly - if the VM's are pulling time via the hypervisor tools - then checking against AD, they will continue to bounce.
you should disable syncing with the host hypervisor.
-
If your DC is reaching out to pool.ntp.org, I would set your hypervisor to hit the same time server.
-
hypervisor or host?
-
@Donahue said in Domain Time off for some members:
hypervisor or host?
Those are generally the same thing.
-
@Donahue said in Domain Time off for some members:
hypervisor or host?
The hypervisor is a type 1, yes? Hyper-V, ESXi, XenServer or XCP-NG or KVM? (the hypervisor and host should be one in the same)
-
@Dashrender said in Domain Time off for some members:
@Donahue said in Domain Time off for some members:
hypervisor or host?
Those are generally the same thing.
Damn are we reading each other's minds today!
-
ok, host time was wrong, but it was way wrong, more than the 6 minutes. How do I tell ESXi not to sync with host?
-
@Donahue said in Domain Time off for some members:
ok, host time was wrong, but it was way wrong, more than the 6 minutes. How do I tell ESXi not to sync with host?
That's the wrong thing to look at. You want your VM's to not sync with ESXi. And maybe you don't want ESXi to sync with the hardwarde (because you can sync to the internet).
In the settings for VMWare tools in the VMs there should be setting - sync with ESXi or something... disable that.
-
@Donahue said in Domain Time off for some members:
ok, host time was wrong, but it was way wrong, more than the 6 minutes. How do I tell ESXi not to sync with host?
You can set your guests time server to be something other than the host.
-
ok, that setting was already disabled in the VMWare tools options, so that's not the problem.
-
@Donahue said in Domain Time off for some members:
ok, that setting was already disabled in the VMWare tools options, so that's not the problem.
Fix it anyway. The host time needs to be right.
Also, your VM sets time on boot to that even if that option is not checked. Until the VM network comes online and sets itself to whatever source it has.
-
The host time has been set correctly, but I don't think that was the source of the problem.
-
@JaredBusch said in Domain Time off for some members:
Also, your VM sets time on boot to that even if that option is not checked. Until the VM network comes online and sets itself to whatever source it has.
But this VM has not been rebooting, it just keeps changing while running.
-
@Donahue said in Domain Time off for some members:
@JaredBusch said in Domain Time off for some members:
Also, your VM sets time on boot to that even if that option is not checked. Until the VM network comes online and sets itself to whatever source it has.
But this VM has not been rebooting, it just keeps changing while running.
Didn't say it was. Just saying fix this problem also.
-
@JaredBusch said in Domain Time off for some members:
@Donahue said in Domain Time off for some members:
@JaredBusch said in Domain Time off for some members:
Also, your VM sets time on boot to that even if that option is not checked. Until the VM network comes online and sets itself to whatever source it has.
But this VM has not been rebooting, it just keeps changing while running.
Didn't say it was. Just saying fix this problem also.
oh ok, I understand.
I feel like maybe there is some sort of group policy that should be set to make this sync work correctly, and that somehow mine is not set. Although, this problem is only recent.
-
I just realized it must be related to this host. I recently moved the main VM that I am having a problem with to this host.
-
@Donahue said in Domain Time off for some members:
I just realized it must be related to this host. I recently moved the main VM that I am having a problem with to this host.
Windows could be checking hte hardware clock. This has nothing to do with VM tools settings.
And your host (the hardware) was off.
But Windows was not moving it too far..
Answer: Windows sucks.
-
@JaredBusch said in Domain Time off for some members:
@Donahue said in Domain Time off for some members:
I just realized it must be related to this host. I recently moved the main VM that I am having a problem with to this host.
Windows could be checking hte hardware clock. This has nothing to do with VM tools settings.
And your host (the hardware) was off.
But Windows was not moving it too far..
Answer: Windows sucks.
Interesting - does EXSi not virtualized the hardware clock to itself as well?
-
@Dashrender said in Domain Time off for some members:
@JaredBusch said in Domain Time off for some members:
@Donahue said in Domain Time off for some members:
I just realized it must be related to this host. I recently moved the main VM that I am having a problem with to this host.
Windows could be checking hte hardware clock. This has nothing to do with VM tools settings.
And your host (the hardware) was off.
But Windows was not moving it too far..
Answer: Windows sucks.
Interesting - does EXSi not virtualized the hardware clock to itself as well?
English please?
-
@JaredBusch said in Domain Time off for some members:
@Dashrender said in Domain Time off for some members:
@JaredBusch said in Domain Time off for some members:
@Donahue said in Domain Time off for some members:
I just realized it must be related to this host. I recently moved the main VM that I am having a problem with to this host.
Windows could be checking hte hardware clock. This has nothing to do with VM tools settings.
And your host (the hardware) was off.
But Windows was not moving it too far..
Answer: Windows sucks.
Interesting - does EXSi not virtualized the hardware clock to itself as well?
English please?
Does ESXi provide direct access the the real hardware clock, or does it create a virtual HW clock that is basically the time EXSi has itself - which could be different from the real hardware.
