| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Intel S3420GPLX VT-d VF question
On Tue, Dec 07, 2010 at 11:52:24PM -0500, Michael A. Collins wrote:
> I have successfully booted xen on Fedora 14 x86_64 with iommu=force
Ok.. Um, what Fedora kernel are we taking about here? Do you have
the full serial log?
> on the kernel line, I can unbind a pci device and rebind to pci-stub
> and see it with xm pci-list-assignable-devices. That's cool. Now I
> have an Intel 82576 dual-port ET Adapter that supports SR-IOV and
> started configuring everything to enable it's virtual functions:
> added pci_pt_e820_access=on to the module line that contains the
> vmlinuz
Why? It doesn't automatically load without that parameter?
> created igb.conf under /etc/modprobe.d with options igb max_vfs=7
> added blacklist igbvf to /etc/modprobe.d/blacklist.conf
Why blacklist it?
>
> I was under the impression that I should see some kind of message
> about MMCONFIG in xm dmesg, but there isn't anything. I do a xm
> dmesg | grep -i pci and it finds nothing with MMCONFIG. I guess my
Huh? Why? Do you see the 7 ethernet PCI device being created?
> next question is what do I do next? How do I troubleshoot further?
What are you trying to troubleshoot? Did you lspci output change
after you loaded the igbvf?
> Below is the VT-d messages from xm dmesg:
> (XEN) Intel VT-d Snoop Control supported.
> (XEN) Intel VT-d DMA Passthrough not supported.
> (XEN) Intel VT-d Queued Invalidation supported.
> (XEN) Intel VT-d Interrupt Remapping not supported.
>
> Does MMCONFIG have something to do with the fact the Interrupt
> Remapping not supported message is displayed?
No. It just means your VT-D chipset does not support interrupt
remapping.
> Mike
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home