What Are You Doing Right Now
-
TGIF!!!! It's been a week.... can't wait for it to be over.
-
Half day today... then Dr. Appointment and to PA to see my In-laws. It is going to be a long weekend.
-
yeah.. another dentist appointment today.
-
@coliver said:
Half day today... then Dr. Appointment and to PA to see my In-laws. It is going to be a long weekend.
@johnhooks I'll be in your area all weekend... good thing it is supposed to be sunny and 60.
-
Our neighbor took his motorcycle to work today. Awesome sound on December 11th!
-
@Minion-Queen said:
Our neighbor took his motorcycle to work today. Awesome sound on December 11th!
I got mine out over the weekend. Short, cold, ride but very refreshing.
-
@art_of_shred got rid of his a few years ago, working from home means you never have time to ride. But it is so cool to see people out and riding this time of year. Usually we are freezing and roads are icy half the time at this point in the year.
-
@Minion-Queen said:
TGIF!!!! It's been a week.... can't wait for it to be over.
Same here. Looking forward to weekend downtime.
-
Gorgeous morning on the Gulf. Bright sun, rough sea. Expecting a bit storm tomorrow.
-
@JaredBusch said:
getting ready to click yes on crypto (I think) as soon as I get this user data copied to usb.
You are actually going to let them pay the ransom?
-
Digging through Server log and such to see why a server cycled four times over night. As near as I can tell, the server didn't cycle,.. maybe the ISP did... I went back to my CLI Up Time
C:\Users\ntgadmin>systeminfo | find "System Boot Time" System Boot Time: 12/10/2015, 12:25:14 PM -
That system OS did not cycle, but the hypervisor it is on might have, of course. What is leading people ot think that the "server cycled"?
-
@scottalanmiller said:
That system OS did not cycle, but the hypervisor it is on might have, of course. What is leading people ot think that the "server cycled"?
Yup,.. I looked at that first. It still reports 10/5/2015 as the last reboot
-
@scottalanmiller said:
That system OS did not cycle, but the hypervisor it is on might have, of course. What is leading people ot think that the "server cycled"?
How can the hypervisor cycle and not the VM, unless the VM is on HA?
-
@Dashrender said:
@scottalanmiller said:
That system OS did not cycle, but the hypervisor it is on might have, of course. What is leading people ot think that the "server cycled"?
How can the hypervisor cycle and not the VM, unless the VM is on HA?
The hypervisor puts the VM on suspend, as in stops executing all commands to and from that VM. To the VM it doesn't even realize it didn't exist for a few moment while the hypervisor rebooted.
-
@Dashrender said:
@scottalanmiller said:
That system OS did not cycle, but the hypervisor it is on might have, of course. What is leading people ot think that the "server cycled"?
How can the hypervisor cycle and not the VM, unless the VM is on HA?
How can it not? The VM doesn't have any way to know that the world has stopped for a few minutes unless it has crashed or been told to shut down. To it, time just leaps forward and it doesn't remember what happened during those minutes.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
That system OS did not cycle, but the hypervisor it is on might have, of course. What is leading people ot think that the "server cycled"?
How can the hypervisor cycle and not the VM, unless the VM is on HA?
How can it not? The VM doesn't have any way to know that the world has stopped for a few minutes unless it has crashed or been told to shut down. To it, time just leaps forward and it doesn't remember what happened during those minutes.
What about what was in RAM? Is that some how saved? I suppose I could understand if the hypervisor paused the VM (saving the RAM state), rebooted, then started the VM again - is that a thing? if so - huh, didn't know.
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
That system OS did not cycle, but the hypervisor it is on might have, of course. What is leading people ot think that the "server cycled"?
How can the hypervisor cycle and not the VM, unless the VM is on HA?
How can it not? The VM doesn't have any way to know that the world has stopped for a few minutes unless it has crashed or been told to shut down. To it, time just leaps forward and it doesn't remember what happened during those minutes.
What about what was in RAM? Is that some how saved? I suppose I could understand if the hypervisor paused the VM (saving the RAM state), rebooted, then started the VM again - is that a thing? if so - huh, didn't know.
Yup, RAM flushes to disk. It is called a "saved state." Same as your desktop going to sleep except that the VM has no idea it is happening because the VM itself has nothing to do with it.
-
@Dashrender said:
I suppose I could understand if the hypervisor paused the VM (saving the RAM state), rebooted, then started the VM again - is that a thing? if so - huh, didn't know.
It's not just a thing, it's the default behaviour
If you use VirtualBox on your desktop you will get the same thing.Think of the VM as being put into stasis. Time passes outside the VM but the VM is "frozen". When it wakes up it feels like it just blinked, but the world outside is at a different point in time.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
That system OS did not cycle, but the hypervisor it is on might have, of course. What is leading people ot think that the "server cycled"?
How can the hypervisor cycle and not the VM, unless the VM is on HA?
How can it not? The VM doesn't have any way to know that the world has stopped for a few minutes unless it has crashed or been told to shut down. To it, time just leaps forward and it doesn't remember what happened during those minutes.
What about what was in RAM? Is that some how saved? I suppose I could understand if the hypervisor paused the VM (saving the RAM state), rebooted, then started the VM again - is that a thing? if so - huh, didn't know.
Yup, RAM flushes to disk. It is called a "saved state." Same as your desktop going to sleep except that the VM has no idea it is happening because the VM itself has nothing to do with it.
Is this a typical thing that one would do when needing to reboot the VM host in a non HA environment?
For example - my power outage the other day, would I have been OK just saved stating my VMs and having the host be offline for a few hours instead of shutting them down?
