From: Alex Williamson <alex.williamson@redhat.com>
To: "Goutham GS" <goutham@zadarastorage.com>
Cc: <kvm@vger.kernel.org>
Subject: Re: vfio issue in qemu 2.5
Date: Thu, 4 Feb 2016 23:02:15 -0700 [thread overview]
Message-ID: <20160204230215.1051c2f3@t450s.home> (raw)
In-Reply-To: <214201d15fd4$c9024650$5b06d2f0$@zadarastorage.com>
On Fri, 5 Feb 2016 10:49:23 +0530
"Goutham GS" <goutham@zadarastorage.com> wrote:
> Hello Alex,
>
> Sorry, I got the timestamps wrong yesterday.
>
> I see the following messages in kern.log at the time of the issue:
>
> Jan 31 03:46:39 qa2-sn2 kernel: [228419.858857] vfio-pci 0000:04:01.4:
> enabling device (0000 -> 0002)
> Jan 31 03:46:39 qa2-sn2 kernel: [228419.970492] vfio-pci 0000:04:02.7:
> enabling device (0000 -> 0002)
> Jan 31 03:46:39 qa2-sn2 kernel: [228420.082435] IOMMU: no free domain
> ids Jan 31 03:46:39 qa2-sn2 kernel: [228420.124440] IOMMU: no free
> domain ids
>
> Does this say anything?
That's kind of a big deal. Kernel v3.17 introduced a domain ID leak
that didn't get fully fixed until kernel v4.2. To make matters worse,
even though the fixes were tagged for stable, the last one doesn't seem
to have been backported to any pre-4.2 stable series. Long story
short, you'll need to move to v4.2 or backport this to your kernel:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=46ebb7af7b93792de65e124e1ab8b89a108a41f2
Thanks,
Alex
next prev parent reply other threads:[~2016-02-05 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 15:01 vfio issue in qemu 2.5 Goutham GS
2016-02-04 17:02 ` Alex Williamson
2016-02-04 18:23 ` Goutham GS
2016-02-05 5:19 ` Goutham GS
2016-02-05 6:02 ` Alex Williamson [this message]
2016-02-05 6:30 ` Goutham GS
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=20160204230215.1051c2f3@t450s.home \
--to=alex.williamson@redhat.com \
--cc=goutham@zadarastorage.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