| 1 |
On Wed, Aug 24, 2011 at 12:18 AM, Hilco Wijbenga |
| 2 |
<hilco.wijbenga@×××××.com>wrote: |
| 3 |
|
| 4 |
> On 23 August 2011 20:38, Mark Knecht <markknecht@×××××.com> wrote: |
| 5 |
> > Hi all, |
| 6 |
> > Can someone point me toward somehow enabling CONFIG_IOMMU_SUPPORT? |
| 7 |
> > It is apparently a kernel config option no required by |
| 8 |
> > virtualbox-drivers but I'm not finding it in the 3.0.3 kernel. I |
| 9 |
> > suspect there's something else I need to enable before this option |
| 10 |
> > becomes available? Unfortunately I haven't been able to Google what I |
| 11 |
> > need to do to find it. |
| 12 |
> |
| 13 |
|
| 14 |
IOMMU_SUPPORT is a derived value that becomes set when any of the various |
| 15 |
IOMMU |
| 16 |
devices are enabled. I enabled the IBM "CALGARY" IOMMU and the AMD IOMMU to |
| 17 |
get the |
| 18 |
VBox build to stop complaining. |
| 19 |
|
| 20 |
I was also getting complaints about PCI_STUB support from VBox, but the |
| 21 |
running VMs don't |
| 22 |
need the vboxpcistub.ko driver to work. |
| 23 |
|
| 24 |
-- |
| 25 |
G.Wolfe Woodbury |
Archives