qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] virtio-blk issues
Date: Tue, 3 Mar 2009 16:23:49 +0100	[thread overview]
Message-ID: <20090303152349.GA21900@lst.de> (raw)
In-Reply-To: <200903031422.44151.paul@codesourcery.com>

On Tue, Mar 03, 2009 at 02:22:43PM +0000, Paul Brook wrote:
> On Tuesday 03 March 2009, Christoph Hellwig wrote:
> > I've been trying to move setup from kvm 72 in debian testing to the current
> > qemu CVS.  The setup is using 7 virtio_blk disks and used to work on the
> > old setup, but with current qemu the kernel (current Linus' HEAD from a few
> > days ago) hangs when trying to setup the irq routing for the virtio_pci
> > devices:
> >
> > virtio pci 0000:00:06.0: can't derive routing for PCI INT A
> > virtio pci 0000:00:06.0: PCI INT A: no GSI - using IRQ 9
> 
> IIRC this is partly a bios issue. Real PIIX3 based systems never have more 
> than ~5 PCI slots, so it doesn't have interrupt routing for more devices.
>
> There are two solutions: Fix the bios to handle machines with large numbers of 
> PCI slots, or have create multifunction PCI devices so lots of virtio 
> instances don't use so many virtual PCI slots.
> 

Or we could try to create a pc+PIIX style VM.  Surely having more than
two disks should not be that uncommon..

  reply	other threads:[~2009-03-03 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 12:54 [Qemu-devel] virtio-blk issues Christoph Hellwig
2009-03-03 14:22 ` Paul Brook
2009-03-03 15:23   ` Christoph Hellwig [this message]
2009-03-03 17:22   ` Anthony Liguori
2009-03-16 13:22   ` Avi Kivity
2009-03-18  8:08     ` Christoph Hellwig
2009-03-18  8:41       ` Avi Kivity

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=20090303152349.GA21900@lst.de \
    --to=hch@lst.de \
    --cc=paul@codesourcery.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).