From: Igor Mammedov <imammedo@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Michal Privoznik <mprivozn@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Preconfig state reachable without --preconfig given
Date: Mon, 4 Jun 2018 14:05:12 +0200 [thread overview]
Message-ID: <20180604140512.1c43b186@redhat.com> (raw)
In-Reply-To: <24719f30-25c9-a80e-0db9-ae2f7f318c68@redhat.com>
On Mon, 4 Jun 2018 11:46:06 +0200
Max Reitz <mreitz@redhat.com> wrote:
> On 2018-06-02 12:46, Michal Privoznik wrote:
> > On 06/01/2018 03:28 PM, Max Reitz wrote:
> >> Hi,
> >>
> >> The @preconfig RunState documentation states:
> >>
> >>> The state is reachable only if the --preconfig CLI option is used.
> >>
> >> However, this is not true:
> >>
> >> $ echo | x86_64-softmmu/qemu-system-x86_64 -monitor stdio
> >> QEMU 2.12.50 monitor - type 'help' for more information
> >> (qemu)
> >> HMP not available in preconfig state, use QMP instead
> >
> > Not sure if this is the same bug, but I've noticed libvirt having
> > troubles detecting capabilities of qemu and debugging lead to this patch:
> >
> > http://lists.nongnu.org/archive/html/qemu-devel/2018-06/msg00367.html
> >
> > (which by no means I claim is proper solution. It might be viewed as
> > workaround by expert qemu devels)
>
> Well, it'd fix both of my issues, so it has that going for it. :-)
Acked patch.
Markus also suggested to drop HMP monitor altogether at this first loop,
I'll look into it some more taking in account demonize() issue.
>
> >> On IRC, Daniel proposed doing the runstate transition immediately after
> >> the command line has been read and no --preconfig option has been found.
> >> Doing that indeed fixes the issue for me (but I don't know whether
> >> that's the best solution).
> >
> > Oh has he? I can't find it anywhere.
>
> That was in #qemu on OFTC:
>
> [Friday, June 1 2018] [15:21:26 CEST] <danpb> if we've not passed
> --preconfig though, we should not be in PRECONFIG state in the first
> place IMHO
> [Friday, June 1 2018] [15:22:27 CEST] <danpb> eg vl.c should set the
> state to RUN_STATE_PRELAUNCH immediately after parsing CLI args if
> --preconfig wasn't given
That's not how it should be, PRECONFIG is there to replace PRELAUNCH
at early stages (which commit 8a36283e12 message states)
/me is to blame for miss-leading doc comment/
> Max
>
next prev parent reply other threads:[~2018-06-04 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 13:28 [Qemu-devel] Preconfig state reachable without --preconfig given Max Reitz
2018-06-01 13:44 ` Max Reitz
2018-06-02 10:46 ` Michal Privoznik
2018-06-04 9:46 ` Max Reitz
2018-06-04 12:05 ` Igor Mammedov [this message]
2018-06-05 11:35 ` Dr. David Alan Gilbert
2018-06-04 14:04 ` Max Reitz
2018-06-04 20:24 ` Igor Mammedov
2018-06-06 10:35 ` Max Reitz
2018-06-06 11:00 ` Igor Mammedov
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=20180604140512.1c43b186@redhat.com \
--to=imammedo@redhat.com \
--cc=mprivozn@redhat.com \
--cc=mreitz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.