From: Alex Williamson <alex.williamson@redhat.com>
To: Alexander Lyakas <alex.bolshoy@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: PCI-Passthrough: VF ends up with no IRQ assigned on the physical machine
Date: Tue, 27 Mar 2012 07:57:20 -0600 [thread overview]
Message-ID: <1332856640.29722.72.camel@bling.home> (raw)
In-Reply-To: <CAGRgLy42g5Ki6beAupRMSRVtcCSzc_gkGEevJQ-eSezgH6fRog@mail.gmail.com>
On Tue, 2012-03-27 at 13:01 +0200, Alexander Lyakas wrote:
> Hi Alex,
> chances are not too high, but I can try.
> Should I try version 0.15.1? Will it be compatible with my kernel
> (2.6.38-8)? Or should I also take 'kvm-kmod' or 'kvm'?
Not new enough, try qemu-kvm.git. It should be compatible with your
kernel. Thanks,
Alex
> On Tue, Mar 27, 2012 at 12:38 AM, Alex Williamson
> <alex.williamson@redhat.com> wrote:
> > On Mon, 2012-03-26 at 18:34 +0200, Alexander Lyakas wrote:
> >> Greetings everybody,
> >> I am running stock ubuntu-natty 2.6.38-8, with KVM 0.14.0 and libvirt
> >
> > Any chance you can try upstream qemu-kvm? Interrupts, including msi-x
> > have been given an overhaul recently. Thanks,
> >
> > Alex
> >
> >> 0.8.8. I am using Intel 82599EB dual-port 10Gb NIC with VFs spawned by
> >> each one of the PFs. Those VFs are further assigned to KVM instances
> >> with PCI-passthrough using libvirt. Each instance receives 4 VFs (two
> >> VFs from each PF).
> >> Usually when KVM starts, messages like these appear in the kernel log
> >> of the physical machine:
> >> syslog.ubuntu-sata-51 146907 Mar 25 18:19:51 ubuntu-sata-51 kernel:
> >> [51267.029108] pci-stub 0000:03:13.1: claimed by stub
> >> syslog.ubuntu-sata-51 146908 Mar 25 18:19:51 ubuntu-sata-51 kernel:
> > ...
> >
prev parent reply other threads:[~2012-03-27 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 16:34 PCI-Passthrough: VF ends up with no IRQ assigned on the physical machine Alexander Lyakas
2012-03-26 22:38 ` Alex Williamson
2012-03-27 11:01 ` Alexander Lyakas
2012-03-27 13:57 ` Alex Williamson [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=1332856640.29722.72.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=alex.bolshoy@gmail.com \
--cc=kvm@vger.kernel.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