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

Robert P. J. Day rpjday at
Tue Dec 17 19:29:46 UTC 2013

Quoting Chris Murphy <lists at>:

> On Dec 17, 2013, at 11:42 AM, Robert P. J. Day <rpjday at> wrote:
>> Quoting Chris Murphy <lists at>:
>>> On Dec 17, 2013, at 8:43 AM, Robert P. J. Day  
>>> <rpjday at> wrote:
>>>> not sure what list would be appropriate for this but i'll start here.
>>>> currently running RHEL 6.5 on a 64-bit laptop, and installed a new
>>>> fedora 20 VM using the Virtual Machine Manager -- seemed to work fine,
>>>> f20 came up, looks good, but now i want to shut it down, so from the
>>>> f20 console, i selected "Virtual Machine" -> "Shut Down" -> "Shut Down",
>>>> whereupon it *looks* like the VM shuts down, but the VMM window shows
>>> That command should be the same as 'virsh shutdown <vmname>'. I'm  
>>> not sure how the message gets to the VM to shut it down cleanly  
>>> but I'm guessing some sort of message gets to systemd in the VM.
>>> How long have you waited for it to shutdown? You might be running  
>>> into this bug:
>>> slow shutdown unit user at 0.service entered failed state
>>> I'm running into that delayed reboot/shutdown bug a lot. Not every  
>>> time, but maybe 1/3 of the time? It happens on baremetal and in  
>>> VMs. New F20 installs, and updated ones.
>>  ok, here's what i'm testing right now, and reporting on in real
>> time.
>>  first, i noticed earlier that a fast way to shut down the f20 VM is
>> to simply type:
>>  # init 0
>> if the VMM showed "f20 Running", within seconds of typing that command,
>> the console disconnected and the VMM showed "f20 Shutoff", so that's
>> the response time i'm looking for.
>>  so ... start the VM again, let it boot, log in, then return to
>> VMM and "Shut Down" -> "Shut Down." As before, console goes black,
>> but VMM continues to show "f20 Running" (even though CPU monitor in
>> VMM seems to be totally quiet for that VM).
>>  ok, it's been over a minute and still "f20 Running." i won't
>> worry about it too much more since i know that "init 0" works,
>> but it's still kind of weird.
> If you do it within the VM, what result do you get with 'poweroff'?  
> systemd maps init 0 to poweroff, as of course there is no init with  
> systemd, but it maintains compatibility with init scripts so I  
> expect init 0 to work the same as poweroff.

   unsurprisingly, "poweroff" was equivalent to "init 0" in terms
of how quickly the VMM moved to displaying "f20 Shutoff".

> I wonder if the GUI Shutdown option is mapped to halt rather than  
> halt -p? That could be a bug. I'd expect Shutdown in the GUI to be  
> the equivalent of power off within the VM, or of 'virsh shutdown'  
> from the host.

   ah, and doing "virsh shutdown f20" blanks the console of the VM,
but leaves the VMM displaying "f20 Running". so "virsh shutdown"
isn't even shutting down the VM properly.


More information about the users mailing list