Hyper-V uptime mismatch
-
@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.
-
@JaredBusch can you restart the Veeam drivers on one of these VM's and see if the issue is "corrected".
On a side thought I would think you want to keep the VM uptime as accurate as possible, since the VM isn't being rebooted or shutdown changing this time could effect your troubleshooting strategy (reboot first) sort of issues. . .
I think the better option would be to have the host pull in the actual uptime of the VM from the VM it's self . . . why should it think the VM has been rebooted because of a backup . .
-
@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).
Any ideas?
Didn't read any replies yet so may have been mentioned... if a VM is put into a saved state, Hyper-V resets the uptime counter, but the OS has no idea it went "down". Because technically, it didn't. It was paused. So from Hyper-V's view, it was off.
-
@tim_g 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).
Any ideas?
Didn't read any replies yet so may have been mentioned... if a VM is put into a saved state, Hyper-V resets the uptime counter, but the OS has no idea it went "down". Because technically, it didn't. It was paused. So from Hyper-V's view, it was off.
Which it is, from a technical point of view.
-
@thwr said in Hyper-V uptime mismatch:
@tim_g 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).
Any ideas?
Didn't read any replies yet so may have been mentioned... if a VM is put into a saved state, Hyper-V resets the uptime counter, but the OS has no idea it went "down". Because technically, it didn't. It was paused. So from Hyper-V's view, it was off.
Which it is, from a technical point of view.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup/hyper-v mechanism. Backups shouldn't reset uptime counters for VM's.
-
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@tim_g 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).
Any ideas?
Didn't read any replies yet so may have been mentioned... if a VM is put into a saved state, Hyper-V resets the uptime counter, but the OS has no idea it went "down". Because technically, it didn't. It was paused. So from Hyper-V's view, it was off.
Which it is, from a technical point of view.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup mechanism. Backups shouldn't reset uptime counters for VM's.
A paused VM isn't executing anything. It's in a freezed state. I would compare that to something like a hibernated computer maybe (that's not correct, but you could think like that).
-
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@tim_g 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).
Any ideas?
Didn't read any replies yet so may have been mentioned... if a VM is put into a saved state, Hyper-V resets the uptime counter, but the OS has no idea it went "down". Because technically, it didn't. It was paused. So from Hyper-V's view, it was off.
Which it is, from a technical point of view.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup/hyper-v mechanism. Backups shouldn't reset uptime counters for VM's.
There's no flaw. It's working as designed.
Hyper-V sees this: VM is not running
Guest OS sees this: Nothing happened. I never stopped running. (the whole point of paused/saved state... running memory gets saved)
-
The technicality of it is, a paused VM doesn't equate to being an off or restarted VM, because the VM can track these changes, shutdown, power up, reboot etc. The VM is blind to the backup operation, it wholly "believes" that it is operating continuously.
-
@tim_g said in Hyper-V uptime mismatch:
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@tim_g 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).
Any ideas?
Didn't read any replies yet so may have been mentioned... if a VM is put into a saved state, Hyper-V resets the uptime counter, but the OS has no idea it went "down". Because technically, it didn't. It was paused. So from Hyper-V's view, it was off.
Which it is, from a technical point of view.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup/hyper-v mechanism. Backups shouldn't reset uptime counters for VM's.
There's no flaw. It's working as designed.
Hyper-V sees this: VM is not running
Guest OS sees this: Nothing happened.
But this is where the issue lies. The uptime of the VM is the thing that matters to most people. Not the "unpaused timer" as displayed in Hyper-V.
-
@dustinb3403 said in Hyper-V uptime mismatch:
@tim_g said in Hyper-V uptime mismatch:
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@tim_g 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).
Any ideas?
Didn't read any replies yet so may have been mentioned... if a VM is put into a saved state, Hyper-V resets the uptime counter, but the OS has no idea it went "down". Because technically, it didn't. It was paused. So from Hyper-V's view, it was off.
Which it is, from a technical point of view.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup/hyper-v mechanism. Backups shouldn't reset uptime counters for VM's.
There's no flaw. It's working as designed.
Hyper-V sees this: VM is not running
Guest OS sees this: Nothing happened.
But this is where the issue lies. The uptime of the VM is the thing that matters to most people. Not the "unpaused timer" as displayed in Hyper-V.
Yeah, the VM is not running. THE VM... is not running. It's paused or in a saved state. Why would hyper-v show the uptime of a VM that is not running as being running? That doesn't make sense.
If you want guest OS uptime, look at the guest OS. If hte guest OS is paused (at the VM level), the guest OS never goes down. Think about it...
