qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michal Privoznik <mprivozn@redhat.com>
To: Max Reitz <mreitz@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Preconfig state reachable without --preconfig given
Date: Sat, 2 Jun 2018 12:46:40 +0200	[thread overview]
Message-ID: <d453da2c-92fe-5ef8-239c-656c1822b9e0@redhat.com> (raw)
In-Reply-To: <d714d8ac-6642-f2f3-ad9c-ac7e3bdf30e0@redhat.com>

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)

> 
> 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.

Michal

  parent reply	other threads:[~2018-06-02 10:46 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 [this message]
2018-06-04  9:46   ` Max Reitz
2018-06-04 12:05     ` Igor Mammedov
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=d453da2c-92fe-5ef8-239c-656c1822b9e0@redhat.com \
    --to=mprivozn@redhat.com \
    --cc=imammedo@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 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).