On 06/10/2018 10:21 AM, Patrick O'Callaghan wrote:
On Sun, 2018-06-10 at 09:28 -0400, Robert Moskowitz wrote:
Assuming you were logged into the guest when doing the host shutdown,
then if you had to log back in, the guest can't have been suspended and
resumed from where it left off.
I was log
On Sun, 2018-06-10 at 09:28 -0400, Robert Moskowitz wrote:
> > Assuming you were logged into the guest when doing the host shutdown,
> > then if you had to log back in, the guest can't have been suspended and
> > resumed from where it left off.
>
> I was logged in, but at the time, the session was
On 06/10/2018 08:50 AM, Patrick O'Callaghan wrote:
On Sun, 2018-06-10 at 08:02 -0400, Robert Moskowitz wrote:
Finally rebooted last night after a kernel update...
On 06/03/2018 01:16 PM, Samuel Sieb wrote:
On 06/03/2018 06:29 AM, Robert Moskowitz wrote:
On 06/03/2018 12:43 AM, Samuel Sieb w
On Sun, 2018-06-10 at 08:02 -0400, Robert Moskowitz wrote:
> Finally rebooted last night after a kernel update...
>
> On 06/03/2018 01:16 PM, Samuel Sieb wrote:
> > On 06/03/2018 06:29 AM, Robert Moskowitz wrote:
> > > On 06/03/2018 12:43 AM, Samuel Sieb wrote:
> > > > By default, libvirt and qemu
Finally rebooted last night after a kernel update...
On 06/03/2018 01:16 PM, Samuel Sieb wrote:
On 06/03/2018 06:29 AM, Robert Moskowitz wrote:
On 06/03/2018 12:43 AM, Samuel Sieb wrote:
By default, libvirt and qemu will pause the VM and save it when you
reboot. On startup, it resumes from wh
