On Sun, 2017-09-10 at 14:07 -0700, Samuel Sieb wrote: > On 09/10/2017 07:07 AM, Patrick O'Callaghan wrote: > > as I update it every morning using dnf. That's my choice. The reboot > > generally takes about 30 seconds, unless I'm running a Windows VM in > > which case I usually try to shut it down properly, which can take a > > long time. If I were administering a mail and web service with several > > If you're using KVM/QEMU, you don't need to shut down the VM. It will > be paused for the reboot (memory saved) and then resumed when the server > comes back up. It is a very nice feature and I think it's the default > now, but obviously you should verify that before trying. The VM has a > higher uptime than the host. :-) Would that it were so simple :-) The VM is running VFIO passthrough for a second GPU which I use for gaming. The state of the GPU will not be saved by freezing the VM, even when a game is not actually running. Windows doesn't have a "hibernate" feature except for laptops, and there doesn't appear to be a way of convincing it that the VM is a laptop (the GPU drivers are a dead giveaway). Thus killing the libvirtd process is equivalent to a system reset AFAIK. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
