qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Eric Blake <eblake@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Oliver Francke <Oliver.Francke@filoo.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vl: take iothread lock very early
Date: Thu, 05 Mar 2015 11:07:27 +0100	[thread overview]
Message-ID: <54F82ADF.1040005@de.ibm.com> (raw)
In-Reply-To: <54F7A5EB.1080209@redhat.com>

Am 05.03.2015 um 01:40 schrieb Eric Blake:
> On 03/03/2015 10:32 AM, Paolo Bonzini wrote:
>>
>>
>> On 03/03/2015 18:19, Oliver Francke wrote:
>>>
>>> #0  __GI_exit (status=1) at exit.c:104
>>> #1  0x000055555575cf15 in os_daemonize () at os-posix.c:227
>>> #2  0x0000555555773f2e in main (argc=50, argv=0x7fffffffe0d8,
>>> envp=0x7fffffffe270) at vl.c:3770
>>>
>>> compiled with "--enable-debug" and in gdb "b exit". Not a coder, so if
>>> this is _not_ sufficient, please give me some adivce ;)
>>
>> Try removing -daemonize (hmm, that might actually fix the bug).
> 
> I've confirmed that libvirt required -daemonize, and that (temporarily)
> removing -daemonize makes things work again.  So we definitely need this.
> 
> Tested-by: Eric Blake <eblake@redhat.com>

Yes, came to the same conclusion.
Is there a chance to harden the error detection of libvirt somewhat?
I got things like 
"unsupported OS type hvm"
"unsupported configuration: QEMU 2.2.50 is too new for help parsing"

which made it quite hard to find out what was wrong.

Christian

      reply	other threads:[~2015-03-05 10:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 10:36 [Qemu-devel] [PATCH] vl: take iothread lock very early Paolo Bonzini
2015-03-03 11:13 ` Christian Borntraeger
2015-03-03 11:29 ` Gonglei
2015-03-03 13:43 ` Peter Maydell
2015-03-03 16:03 ` Oliver Francke
2015-03-03 16:51   ` Paolo Bonzini
2015-03-03 17:19     ` Oliver Francke
2015-03-03 17:32       ` Paolo Bonzini
2015-03-03 18:02         ` Oliver Francke
2015-03-04 22:20         ` Christian Borntraeger
2015-03-05  0:40         ` Eric Blake
2015-03-05 10:07           ` Christian Borntraeger [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=54F82ADF.1040005@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=Oliver.Francke@filoo.de \
    --cc=eblake@redhat.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).