From: "Denis V. Lunev" <den@openvz.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Dmitry Andreev <dandreev@virtuozzo.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] qmp: process system-reset event in paused state
Date: Wed, 16 Dec 2015 12:32:13 +0300 [thread overview]
Message-ID: <56712F9D.4000406@openvz.org> (raw)
In-Reply-To: <56712AF4.9030105@redhat.com>
On 12/16/2015 12:12 PM, Paolo Bonzini wrote:
>
> On 16/12/2015 10:00, Denis V. Lunev wrote:
>> With pvpanic or HyperV panic devices could be moved into the paused state
>> with ' <on_crash>preserve</on_crash>'. In this state VM reacts only to
>> 'virsh destroy' or 'continue'.
>>
>> 'virsh reset' command is usually used to force guest reset. The expectation
>> of the behavior of this command is that the guest will be force restarted.
>> This is not true at the moment.
> Does "virsh reset" + "virsh continue" work, and if not why?
as far as I can see there is no such command in virsh at all :(
hades ~/src/qemu $ dpkg -l libvirt-bin
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii libvirt-bin 1.2.16-2ubun amd64 programs for the libvirt
library
hades ~/src/qemu $
hades ~/src/qemu $ virsh continue fedora20
error: unknown command: 'continue'
hades ~/src/qemu $
hades ~/src/libvirt $ cfind . | xargs fgrep \"continue\"
./src/conf/nwfilter_conf.c: "continue");
hades ~/src/libvirt $ cfind . | xargs fgrep \"reset\"
./src/util/virpci.c: STREQ(ent->d_name, "reset")) {
./src/conf/domain_conf.c: "reset",
./src/conf/domain_conf.c: if (STREQ(tmp, "reset")) {
./src/qemu/qemu_monitor_json.c: "none", "pause", "reset",
"poweroff", "shutdown", "debug", "inject-nmi");
./src/vmware/vmware_driver.c: "reset", PROGRAM_SENTINEL, "soft", NULL
./src/access/viraccessperm.c: "start", "stop", "reset",
./tools/virsh-domain.c: {.name = "reset",
./tools/virsh-domain.c: if (vshCommandOptBool(cmd, "reset"))
./tools/virsh-domain.c: * "reset" command
./tools/virsh-domain.c: N_("reset"),
./tools/virsh-domain.c: {.name = "reset",
hades ~/src/libvirt $
Do you propose to kludge libvirt and send 'continue' unconditionally
before a 'reset'? We can but there is not much sense not to implement
this is QEMU.
Sending command in 'crashed' state only is a bit racy. The event
moving domain into 'crashed' state could be not processed at
the moment.
Den
next prev parent reply other threads:[~2015-12-16 9:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 9:00 [Qemu-devel] [PATCH 1/1] qmp: process system-reset event in paused state Denis V. Lunev
2015-12-16 9:12 ` Paolo Bonzini
2015-12-16 9:32 ` Denis V. Lunev [this message]
2015-12-16 9:35 ` Paolo Bonzini
2015-12-16 9:50 ` Denis V. Lunev
2015-12-16 9:37 ` Peter Krempa
2015-12-16 9:50 ` Peter Krempa
2015-12-16 9:55 ` Denis V. Lunev
2015-12-16 12:02 ` Paolo Bonzini
2015-12-16 14:47 ` Denis V. Lunev
2016-01-11 10:31 ` Denis V. Lunev
2016-01-11 11:29 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56712F9D.4000406@openvz.org \
--to=den@openvz.org \
--cc=armbru@redhat.com \
--cc=dandreev@virtuozzo.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).