Your message dated Mon, 03 Nov 2014 17:51:42 +0300
with message-id <[email protected]>
and subject line Re: Bug#760090: acpid: shutdown issues
has caused the Debian Bug report #760090,
regarding acpid: shutdown issues
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
760090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760090
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: acpid
Version: 1:2.0.23-1
Severity: important
I'm noticing I can shutdown Jessie properly but only from the outside
when using kvm. I'm also not exactly sure if this package is the problem
because kvm's own acpi was recently bugreported(and patched)
When I type 'halt' in the VM, the machine shutdown message displays, but
I later have to type "quit/kill" with a kvm monitor command.
(or simply kill -9 <kvm instance>.. quickly noting that a properly
working shutdown normally closes kvm)
* Not to add any more confusion, issuing "system_powerdown" with a kvm
monitoring console actually shuts down the entire VM including the kvm
process
(this is sounding very "kvm" related, but it should be failing from
outside the vm)
this may look a bit confusing at a quick glance but I've tested this
several times..
The kvm acpi bug report filed a few days ago has been "patched". I
tested the shutdown with the patched dsfg-4 release
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759522
^fwiw, the acpi kernel messages are now showing up more properly in the
VM as I was the one who filed this bugreport (reason I suspect it has
less to do with it)
thanks
-Scott
--- End Message ---
--- Begin Message ---
On Tue, 14 Oct 2014 01:31:16 -0400 westlake <[email protected]> wrote:
> Yep, the problem afaict is still here ..
>
> I use the following,
GOSH. If you want to have some support, don't turn a bugreport into an
assorted collection of bad-quality HOWTOs and ramblings. It is mostly
impossible to find real problem in between a ton of various semi-correct
semi-guesses. Skipping to the real issues....
> -> "system_powerdown" from the KVM console which I call "outside" the
> VM actually shuts down the VM entirely.(the VM then shutsdown and closes
> the qemu window on its own)
Okay, this is supposed to work, and it works fine.
> .. compare this to
>
> -> "halt" issued inside the VM which leaves the "qemu window" in an open
> state with the frozen text message "[<time>] Reboot: System halted"
>
> In order to close it, the window can be closed by clicking its
> top-right 'X' control, or can do "quit" in the kvm console.
And this is, again, exactly the way things supposed to work. Halt
stops the system execution but does not power-off the machine. Try
it on your bare-metal linux -- you should see the same "System halted"
text (it depends on the init system, but you should see the idea).
You need `halt -p' or `poweroff' to control the machine power (which
translates to termination of qemu for a virtual machine).
> Now I first noticed this problem on a "remote" hypervisor which I have
> no physical access to and it is like having "-display none" but I have
...
This is a problem of you using commands on the linux machine incorrectly
(ie, not reading the manpage).
Hence, closing this bugreport now.
Thanks,
/mjt
--- End Message ---
