[vfio-users] Resume a suspended/sleeping guest from the guest side

[Erik Adler]

That’s a good idea.

Activity on a USB controller that should be assigned to a sleeping
guest sends off a wake up. Seems so obvious when you say it like that.
Thanks!

Any ETA on when qemu is going to incorporate your patch for
hv_vendor_id ? Using the diagnostic CPUID leaf at 0x40000000 like that
was “a little” less obvious. Brilliant!

All the best


On Thu, Oct 22, 2015 at 5:31 PM, Blank Field <ihatethisfield at gmail.com> wrote:
> I thought libvirt disables S3 acpi state purely for memory reallocation
> reasons. Strange...
>
> On Thu, 2015-10-22 at 03:39 +0200, Erik Adler wrote:
>> I would really like to be able to resume a suspended/sleeping guest
>> from the guest side. Is there anyway to be able to do that? Non
>> technical people that do not have access to the host need to be able
>> to start their Windows10 clients.
>
> If you're using USB passthrough rather than assignment, have you thought
> about monitoring /dev/input on the host and translating that into virsh
> wakeup calls?  A suspended VM doesn't have hardware running to wake it
> from sleep like a real physical system does.  What benefit are you
> hoping to achieve by suspending the VM?  This is not really a vfio-users
> question unless you want to talk about how a vfio assigned device could
> wake a VM, but I don't have an answer for you there either.
>
> _______________________________________________
> vfio-users mailing list
> vfio-users at redhat.com
> https://www.redhat.com/mailman/listinfo/vfio-users