On Wed, Oct 16, 2013 at 10:04 AM, James Hubbard <jameshubbard(a)gmail.com>wrote:
On Wed, Oct 16, 2013 at 9:11 AM, Cole Robinson
<crobinso(a)redhat.com>wrote:
> On 10/16/2013 09:03 AM, James Hubbard wrote:
> > On Wed, Oct 16, 2013 at 7:31 AM, Cole Robinson <crobinso(a)redhat.com
> > <mailto:crobinso@redhat.com>> wrote:
> >
> > Sounds like your system doesn't have an iommu or it isn't enabled,
> confirm
> > with the 'verify' steps here:
> >
> >
>
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM#Assi...
> >
> > > BTW, this is not generating an error message in virt-manager like
> it was
> > prior
> > > to updating to virt-preview.
> > >
> >
> > Make sure you restart virt-manager after updating. If after that
> you can see
> > the error in the --debug output but not from the UI, please file a
> bug and
> > make sure to mention your virt-manager version.
> >
> >
> > The setting intel_iommu is enabled. I was able to get the Intel i350
> cards
> > setup with SR-IOV. The DMAR and IOMMU items show up fine.
> >
>
> Are there any dmesg messages about vfio? The module was autoloaded for me
> on
> f19, that lack of autoload coupled with the libvirt error make me think
> something is weird with your hardware, or at least the kernel thinks so.
>
> Regardless, please file a libvirt bug so we can track this.
>
I'm not seeing any error messages in dmesg when attempting to start. When
I do modprobe vfio-pci I do see:
VFIO - User Level meta-driver version: 0.3
It wouldn't suprise me if it was a hardware problem. The motherboard is a
SuperMicro X9DRD-iF with a version 1.0 firmware. I've seen some flakiness
with another SuperMicro motherboard when intel_iommu=on is set.
I upgraded the firmware, no change. I added two bug reports.