I’m writing a custom NVMe device model and I need to test ATS functionality.
For that, I need to enable the IOMMU.
I start QEMU with the following command line, using a stock Ubuntu 16.04 image:
% emu-system-x86_64 -M q35,accel=kvm,kernel_irqchip=off -m 8K -device
intel-iommu,intremap=on,device
Sorry, transcription error. Yes, I used intel-iommu=on on the guest command
line.
Correction to my correction: no “=on”. If I add “=on, I get ‘Parameter ‘driver’
missing'
> On Aug 21, 2019, at 14:15, Paul Lancaster wrote:
>
> Sorry, transcription error. Yes, I used intel-iommu=on on the guest command
> line.
>
On Wed, 2019-08-21 at 13:37 -0700, Paul Lancaster wrote:
> I’m writing a custom NVMe device model and I need to test ATS functionality.
> For that, I need to enable the IOMMU.
>
> I start QEMU with the following command line, using a stock Ubuntu 16.04
> image:
>
> % emu-system-x86_64 -M q35,ac
Doh! You meant iommu_intel=on kernel argument to the guest boot command line…
(sorry, I’m a HW guy, not a linux/kernel guy).
Just did. No change.
On Wed, 2019-08-21 at 14:17 -0700, Paul Lancaster wrote:
> Correction to my correction: no “=on”. If I add “=on, I get ‘Parameter
> ‘driver’ missing'
>
> > On Aug 21, 2019, at 14:15, Paul Lancaster
> > wrote:
> >
> > Sorry, transcription error. Yes, I used intel-iommu=on on the guest command
On Wed, 2019-08-21 at 14:30 -0700, Paul Lancaster wrote:
> Doh! You meant iommu_intel=on kernel argument to the guest boot command line…
> (sorry, I’m a HW guy, not a linux/kernel guy).
>
> Just did. No change.
You need intel_iommu=on on the guest's command line.
Best regards,
Maxim Levi
