Hyper-V uptime mismatch
-
Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).
Any ideas?
-
I've noticed sometimes when I take a backup of my Hyper-V guests it resets the uptime that is displayed in the manager. It is real sporadic when it happens so I haven't been able to pin it down to what exactly is happening.
-
There are numerous different reports of this, from Veeam backups to Microsoft as well as quite a few others.
Not sure how true any of these might be in this case, just a thought.
-
@brianlittlejohn said in Hyper-V uptime mismatch:
I've noticed sometimes when I take a backup of my Hyper-V guests it resets the uptime that is displayed in the manager. It is real sporadic when it happens so I haven't been able to pin it down to what exactly is happening.
This system does a backup (with Veeam B&R) every 4 hours and this time is not exactly on that mark but close.
I will monitor this.
The non Windows VM's show the correct uptime.
-
Here is additional proof of the backup process causing this issue. Using Veeam of course. .
-
@jaredbusch said in Hyper-V uptime mismatch:
m, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).
Do your VMs go to Saved State when you reboot the host?
-
@dbeato said in Hyper-V uptime mismatch:
@jaredbusch said in Hyper-V uptime mismatch:
m, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).
Do your VMs go to Saved State when you reboot the host?
Host was also rebooted 15 days ago.. SO not relevant. But to answer the question, no, the Windows ones do not.
-
@JaredBusch "If you go inside of the Windows VM navigate to Task Manager -> Performance -> Check CPU, then you will see it correct or if it is linux vm run the uptime command."
Can you confirm if the time is accurate within the windows vm under the above settings?
-
@jaredbusch said in Hyper-V uptime mismatch:
@dbeato said in Hyper-V uptime mismatch:
@jaredbusch said in Hyper-V uptime mismatch:
m, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).
Do your VMs go to Saved State when you reboot the host?
Host was also rebooted 15 days ago.. SO not relevant. But to answer the question, no, the Windows ones do not.
Yes, it is not relevant. But Example below of my VMs:
For the same VM Hyperv Manager shows this:
I upgraded the Agents on the VMs but you probably did that already.
-
@dustinb3403 said in Hyper-V uptime mismatch:
@JaredBusch "If you go inside of the Windows VM navigate to Task Manager -> Performance -> Check CPU, then you will see it correct or if it is linux vm run the uptime command."
Can you confirm if the time is accurate within the windows vm under the above settings?
That screenshot was showing the uptime on the performance tab, which shows the same as you are driving towards. But yes, the 15 day mark is the correct uptime and everything is correct inside the VMs
-
So the simple thing here is to just watch the timer reset at the next backup and count the time. I bet that is what is happening.
Of course this is annoying as all hell. . . . and means you can't trust the hypervisor for the appropriate information. You have to dig into each VM. . .
I wonder if this same issue occurs on different hypervisors as well. . .
-
-
@jaredbusch said in Hyper-V uptime mismatch:
Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).
Is the VM getting paused or something like that?
-
@thwr said in Hyper-V uptime mismatch:
@jaredbusch said in Hyper-V uptime mismatch:
Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).
Is the VM getting paused or something like that?
Essentially yes.
-
@thwr said in Hyper-V uptime mismatch:
@jaredbusch said in Hyper-V uptime mismatch:
Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).
Is the VM getting paused or something like that?
That's what the article shows.
-
Another article
https://www.veeam.com/kb1896 -
@dbeato said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@jaredbusch said in Hyper-V uptime mismatch:
Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).
Is the VM getting paused or something like that?
That's what the article shows.
Missed it, sorry
-
@thwr said in Hyper-V uptime mismatch:
@dbeato said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@jaredbusch said in Hyper-V uptime mismatch:
Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).
Is the VM getting paused or something like that?
That's what the article shows.
Missed it, sorry
Oh no! I didn't mean it that way. Just agreeing with you
-
@dbeato said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@dbeato said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@jaredbusch said in Hyper-V uptime mismatch:
Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).
Is the VM getting paused or something like that?
That's what the article shows.
Missed it, sorry
Oh no! I didn't mean it that way. Just agreeing with you
Easy
I just haven't read the article (or even noticed the link) before posting. Was just the first thing coming to mind. -
The VM doesn't know what is happening, so when a backup kicks off, Veeam (with the hypervisor) pauses the VM for a moment, takes a snapshot and then resumes the VM.
The issue is that the VM doesn't and shouldn't count this as downtime as it's planned and thus the "uptime" counter remains.
Of course this throws a wrench into looking at the VM's because when you see X days (or hours depending on what you are looking at) of uptime when you know you've had backups completed you'll assume something is broken.
Restarting the drivers within the VM would likely fix the issue, but I honestly wouldn't think it's worth the effort.
