From: Paolo Bonzini <pbonzini@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Peter Krempa <pkrempa@redhat.com>,
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: Mon, 11 Jan 2016 12:29:34 +0100 [thread overview]
Message-ID: <5693921E.3060506@redhat.com> (raw)
In-Reply-To: <56938474.3060401@openvz.org>
On 11/01/2016 11:31, Denis V. Lunev wrote:
>>>
>>> IMO, after a reset, main_loop_should_exit should actually transition
>>> to VM_STATE_PRELAUNCH (*not* RUN_STATE_PAUSED) for *all* states except
>>> RUN_STATE_INMIGRATE, RUN_STATE_SAVE_VM (which I think cannot happen
>>> there) and (of course) RUN_STATE_RUNNING. Some changes will be required
>>> to the transition table as well.
>>>
>>> This will fix similar bugs for other runstates as well, though most of
>>> them probably cannot be triggered from libvirt.
>>
>> ok. Thank you for this input. I'll analyse this and come with
>> corrected patch :)
>
> What would be correct procedure to handle this state?
>
> Setting VM_STATE_PRELAUNCH in main_loop_should_exit does not
> move QEMU into VM_STATE_RUNNING and thus subsequent 'resume'
> command is necessary.
>
> In this case the processing of 'reset' command should be different
> in libvirt, i.e. libvirt should send two commands ('reset' and 'resume')
> in this state.
Either that, or libvirt's client should send two of them.
As far as QEMU is concerned, a paused VM remains paused after a reset,
no matter why it was reset. I'm not sure what are the desired semantics
for libvirt.
Paolo
prev parent reply other threads:[~2016-01-11 11:29 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
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 [this message]
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=5693921E.3060506@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=dandreev@virtuozzo.com \
--cc=den@openvz.org \
--cc=pkrempa@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).