public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Wen Congyang <wency@cn.fujitsu.com>
To: qemu-devel <qemu-devel@nongnu.org>,
	kvm list <kvm@vger.kernel.org>,
	Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: pci-assign can not work
Date: Fri, 16 Mar 2012 10:38:39 +0800	[thread overview]
Message-ID: <4F62A7AF.9020706@cn.fujitsu.com> (raw)
In-Reply-To: <4F61C2C5.6060700@cn.fujitsu.com>

At 03/15/2012 06:21 PM, Wen Congyang Wrote:
> Hi all
> 
> When I use pci-assign, I meet the following error:
> 
> Failed to assign irq for "hostdev0": Input/output error
> Perhaps you are assigning a device that shares an IRQ with another device?
> 
> Is it a bug or I miss something?

Hi, Jan

This problem is caused by your patch:
commit 6919115a8715c34cd80baa08422d90496f11f5d7
Author: Jan Kiszka <jan.kiszka@siemens.com>
Date:   Thu Mar 8 11:10:27 2012 +0100

    pci_assign: Flip defaults of prefer_msi and share_intx
    
    INTx sharing is a bit more expensive than exclusive host interrupts, but
    this channel is not supposed to be used for high-performance scenarios
    anyway. Modern devices support MSI/MSI-X and do not depend on using INTx
    under critical workload, real old devices do not support INTx sharing
    anyway.
    
    For those in the middle, the user experience is much better if they just
    work even when IRQ sharing is required. If there is nothing to share,
    share_intx=off can still be applied as tuning parameter.
    
    With INTx sharing as default, the primary reason for prefer_msi=on is
    gone. Make it default off, specifically as it is known to cause troubles
    with devices that have incomplete/broken MSI support or otherwise
    stumble if host IRQ configuration does not match guest driver
    expectation.
    
    Acked-by: Alex Williamson <alex.williamson@redhat.com>
    Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
    Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>

If I revert this commit. qemu can work.

Thanks
Wen Congyang

> 
> I use libvirt to start the guest, and the user/group is root/root(not qemu/qemu).
> 
> If I use the default qemu(provided in RHEL6.2), the guest can be started.
> 
> Thanks
> Wen Congyang
> 
> 

  reply	other threads:[~2012-03-16  2:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 10:21 pci-assign can not work Wen Congyang
2012-03-16  2:38 ` Wen Congyang [this message]
2012-03-16  8:27   ` [Qemu-devel] " Jan Kiszka
2012-03-16  8:38     ` Wen Congyang
2012-03-16 10:13       ` Jan Kiszka

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=4F62A7AF.9020706@cn.fujitsu.com \
    --to=wency@cn.fujitsu.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --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