how to (properly) shut down a fedora 20 virtual machine?

Robert P. J. Day rpjday at crashcourse.ca
Wed Dec 18 11:25:41 UTC 2013


Quoting Chris Murphy <lists at colorremedies.com>:

>
> On Dec 17, 2013, at 1:46 PM, Chris Murphy <lists at colorremedies.com> wrote:
>
>> [  118.522477] PM: Syncing filesystems ... done.
>> [  118.986063] Freezing user space processes ... (elapsed 0.005  
>> seconds) done.
>> [  119.045554] Freezing remaining freezable tasks ... (elapsed  
>> 0.001 seconds) done.
>> [  119.689884] PM: suspend of devices complete after 636.182 msecs
>> [  119.693836] PM: late suspend of devices complete after 0.193 msecs
>> [  119.702168] PM: noirq suspend of devices complete after 5.163 msecs
>> [  119.704754] ACPI: Preparing to enter system sleep state S3
>> [  119.706818] PM: Saving platform NVS memory
>> [  119.708309] Disabling non-boot CPUs ...
>> [  119.711815] Unregister pv shared memory for cpu 1
>> [  119.717559] Broke affinity for irq 1
>> [  119.718393] Broke affinity for irq 9
>> [  119.718393] Broke affinity for irq 14
>> [  119.836051] smpboot: CPU 1 is now offline
>>
>
> Yet another pmsuspend on GUI shut down request. That's supposed to  
> be the behavior if the host is shutdown, but that's not what I'm  
> doing. And virsh dompmwakeup doesn't work.
>
> # virsh dompmwakeup fedora20
> Domain fedora20 successfully woken up
>
> Yet serial console remains unresponsive, until I disconnect and  
> reconnect, and then I get:
>
> [  253.170908] ACPI Error: No installed handler for fixed event -  
> PM_Timer (0), disabling (20130517/evevent-286)
> [  253.171840] ACPI Error: No installed handler for fixed event -  
> SleepButton (3), disabling (20130517/evevent-286)
> [  253.171840] ACPI Error: Could not disable RealTimeClock events  
> (20130517/evxfevnt-266)
> [  253.199507] ACPI Error: No installed handler for fixed event -  
> PM_Timer (0), disabling (20130517/evevent-286)
> [  253.200441] ACPI Error: No installed handler for fixed event -  
> SleepButton (3), disabling (20130517/evevent-286)
> [  253.200441] ACPI Error: Could not disable RealTimeClock events  
> (20130517/evxfevnt-266)
> [  253.223361] ACPI Error: No installed handler for fixed event -  
> PM_Timer (0), disabling (20130517/evevent-286)
> [  253.224296] ACPI Error: No installed handler for fixed event -  
> SleepButton (3), disabling (20130517/evevent-286)
> [  253.224296] ACPI Error: Could not disable RealTimeClock events  
> (20130517/evxfevnt-266)
>
> So I'd say the VM is confused. I'm not sure where the problem is.

   just catching up here and have to admit i'm out of my comfort
zone ... is it safe to say that all of this represents an actual
bug/issue and i wasn't doing anything imbecilic earlier? as in,
when i was using the VMM to allegedly "Shut Down" a fedora 20
VM that didn't actually, you know, *shut down*?

   should this be covered further on one of the virt lists? is
someone going to file something on bugzilla that i can follow
along with? thanks.

rday



More information about the users mailing list