Re: F28 - Today's updates messed up writing to USB

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2018-06-04 at 10:21 -0700, Samuel Sieb wrote:
> On 06/04/2018 02:40 AM, Patrick O'Callaghan wrote:
> > On Sun, 2018-06-03 at 10:19 -0700, Samuel Sieb wrote:
> > > No, it's a qemu function that saves the currently used VM memory and
> > > state.  You do need to have enough free disk space available to be able
> > > to store that.  The VM OS doesn't get notified about it, other than
> > > probably noticing that the clock time suddenly jumps unexpectedly.
> > 
> > In my case suddenly rebooting the host *is* detected by the guest
> > (running Windows 10). I notice this because on reconnecting to it after
> > a reboot it is always on the login screen, not on the desktop where I
> > left it.
> 
> You did say that you were using VFIO, so it won't work anyway.

Indeed.

> But did you enable and start the "libvirt-guests" service?

AFAIK it has always been enabled and running:
 systemctl status libvirt-guests
● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/usr/lib/systemd/system/libvirt-guests.service; enabled; vendor preset: disabled)
   Active: active (exited) since Mon 2018-06-04 13:22:56 BST; 5h 30min ago
     Docs: man:libvirtd(8)
           https://libvirt.org
  Process: 1375 ExecStart=/usr/libexec/libvirt-guests.sh start (code=exited, status=0/SUCCESS)
 Main PID: 1375 (code=exited, status=0/SUCCESS)

Jun 04 13:22:43 bree systemd[1]: Starting Suspend/Resume Running libvirt Guests...
Jun 04 13:22:53 bree libvirt-guests.sh[1375]: Resuming guests on default URI...
Jun 04 13:22:56 bree libvirt-guests.sh[1375]: Resuming guest NewWin10: done
Jun 04 13:22:56 bree systemd[1]: Started Suspend/Resume Running libvirt Guests.

So it tells me the Win10 guest has been resumed. However internally the
guest will presumably have panicked and restarted because the GPU was
reset by the host reboot. (I'm not enough of a Windows user to be able
to tell when it restarted but if anyone knows I can check).

poc
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/P7BVEGDF4XWQ54MII646ZZNWKKTWCSPQ/



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux