qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: spice-devel <spice-devel@lists.freedesktop.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Spice-devel] Current qemu-master hangs when used with qxl + linux guest
Date: Tue, 08 Oct 2013 21:09:18 +0200	[thread overview]
Message-ID: <5254585E.8040601@redhat.com> (raw)
In-Reply-To: <20131008143049.GK14446@redhat.com>

Hi,

On 10/08/2013 04:30 PM, Daniel P. Berrange wrote:
> On Tue, Oct 08, 2013 at 04:27:38PM +0200, Hans de Goede wrote:
>> Hi All,
>>
>> I'm having this weird problem with qemu master + spice/qxl using
>> guests. As soon as the guest starts Xorg, I get the following message
>> from qemu:
>>
>> main-loop: WARNING: I/O thread spun for 1000 iterations
>>
>> And from then on the guest hangs and qemu consumes 100% cpu. The qemu
>> console still works, and I can quit qemu that way.
>>
>> Doing ctrl+c + a thread apply all bt in qemy shows one cpu thread waiting
>> for the iothread-lock, and all other threads waiting in poll.
>>
>> This happens both with non kms guests (tried RHEL-6.5, older Fedoras)
>> as well as with kms guests (tried a fully up2date F-19).
>>
>> Since I've not seen any similar reports, I assume it is something
>> with my setup ...
>>
>> I've tried changing various things:
>> -removing the spice agent channel
>> -changing the number of virtual cpus (tried 1 and 2 virtual cpus)
>> -upgrading spice-server to the latest git master
>>
>> But all to no avail.
>>
>> This is with qemu-master build from source on a fully up2date
>> F-20 system, using the F-20 seabios files.
>>
>> If someone has any clever ideas I'll happily try debugging this further.
>
> Does the QEMU build in F20 work correctly ?

Ah, yes it does, good dea.

> If so that'd give you a
> starting point from which to 'git bisect' the problem.

Yep, note I asked for a "clever" idea, iow not the big hammer of bisecting :)

But since 1.6.0 in F-20 worked it was not such a large bisect, so I went
ahead and bisected anyways, which pointed me to commit 7b595f35d8 :
"aio / timers: Convert mainloop to use timeout"

After careful review of that commit I had a hunch what might be wrong, and
it turned out to be right. So after this mail I'm going to send a patch
fixing this. If you want to know the details see the patch, titled:
"main-loop: Don't lock starve io-threads when main_loop_tlg has pending events"

Regards,

Hans

  reply	other threads:[~2013-10-08 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 14:27 [Qemu-devel] Current qemu-master hangs when used with qxl + linux guest Hans de Goede
2013-10-08 14:30 ` [Qemu-devel] [Spice-devel] " Daniel P. Berrange
2013-10-08 19:09   ` Hans de Goede [this message]
2013-10-08 15:24 ` Christophe Fergeau

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=5254585E.8040601@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=spice-devel@lists.freedesktop.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).