qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio-blk/qdev failure in the current git tree
Date: Tue, 11 Aug 2009 21:28:41 +0200	[thread overview]
Message-ID: <4A81C669.8070300@redhat.com> (raw)
In-Reply-To: <20090811163638.GA4891@lst.de>

On 08/11/09 18:36, Christoph Hellwig wrote:
> On Tue, Aug 11, 2009 at 06:13:02PM +0200, Christoph Hellwig wrote:
>> With the fix pulled it the guest kernel now hangs after
>>
>> 	input: ImExPS/2 Generic Explorer Mouse as /class/input/input2
>> 	Clocksource tsc unstable (delta = -782142631 ms)
>>
>> when reducing the config to just one virtio-blk device it books, but
>> with a longish break at the point where the original config hangs.
>
> The culprit is commit d176c495b6664b72dc1e595f6e89dc5648aa248b
>
> 	qdev-ify virtio-blk.
>
> reverting it (needs some manual work due to the macrofication of the
> qdev attributes) fixes the boot again.

Hmm.  I suspect this is not related to qdev and virtio-blk at all.  I've 
noticed now and then that some pci devices don't work if you have many 
of them.  Didn't try (yet) to root-cause that one.

The commit changes the initialization order of the virtio-blk devices, 
which probably makes them being placed in other PCI slots, which in turn 
might uncover the bug mentioned above in your setup.

How are the pci devices assigned to slots with and without the patch?

Does removing the balloon device (-balloon none) change the behavior?
Does removing the nic (-net none) too change the behavior?

cheers,
   Gerd

  parent reply	other threads:[~2009-08-11 19:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 23:56 [Qemu-devel] virtio-blk/qdev failure in the current git tree Christoph Hellwig
2009-08-11  0:29 ` Anthony Liguori
2009-08-11 16:13   ` Christoph Hellwig
2009-08-11 16:36     ` Christoph Hellwig
2009-08-11 18:45       ` Anthony Liguori
2009-08-11 19:28       ` Gerd Hoffmann [this message]
2009-08-12  9:26         ` Gerd Hoffmann
2009-08-12 10:00           ` Avi Kivity
2009-08-12 10:19             ` Gerd Hoffmann
2009-08-12 10:40               ` Gerd Hoffmann
2009-08-12 10:51                 ` Avi Kivity
2009-08-12 11:45                   ` Reimar Döffinger
2009-08-12 21:50             ` Christoph Hellwig
2009-08-12 22:01               ` Anthony Liguori
2009-08-13  9:00                 ` Avi Kivity
2009-08-13 12:07                   ` Gerd Hoffmann
2009-08-13 12:47                   ` Gerd Hoffmann
2009-08-13 13:15                     ` Anthony Liguori
2009-08-13 13:38                       ` Gerd Hoffmann
2009-08-12 10:08           ` Gerd Hoffmann
2009-08-12 21:54             ` Christoph Hellwig

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=4A81C669.8070300@redhat.com \
    --to=kraxel@redhat.com \
    --cc=hch@lst.de \
    --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).