-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-08-18 10:19, Foppe de Haan wrote:
> I've been slowly figuring out how qubes works, and configuring it the way
> I want, while getting used to linux at the same time (which means I'm not
> very good at things other than diagnosing and prodding around yet).
> 
> As such, I found out today that IOMMU doesn't appear to be enabled, and 
> qubes-hcl-report lists it as 'no', even though it "should" be there and
> work. The reason why this is the case eludes me, as I am not really seeing
> any errors beyond the exceedingly uninformative outcome -- "error
> initialization" in xl dmesg. Can anyone help me along on the way to
> figuring out why this may be the case?
> 
> My CPU is listed as supporting IOMMU (amd athlon x4 845, carrizo core), my 
> BIOS has the option enabled, and lspci lists a IOMMU device.
> 
> I've attached a few log files that contain information that googling
> around told me may be relevant; I have also searched the qubes-users and
> -devel groups, but not really found much, apart from outdated information
> (referring to xen 4.3, 4.4, 3.x).
> 
> Thank you in advance. :)
> 
> For reference: what I believe are the most directly relevant bits from the 
> attached files:
> 
> xl dmesg: (XEN) ACPI: IVRS CC9AD968, 00D0 (r2    AMD BANTRY          1 AMD 
> 0 (XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs ... (XEN) alt table 
> ffff82d0802c6b30 -> ffff82d0802c7d90 (XEN) PCI: MCFG configuration 0: base 
> f0000000 segment 0000 buses 00 - 3f (XEN) PCI: MCFG area at f0000000
> reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-3f (XEN)
> AMD-Vi: Error initialization (XEN) I/O virtualisation disabled (XEN)
> nr_sockets: 3 (XEN) ENABLING IO-APIC IRQs (XEN) HVM: ASIDs enabled. (XEN)
> SVM: Supported advanced features: (XEN)  - Nested Page Tables (NPT) (XEN)
> - Last Branch Record (LBR) Virtualisation (XEN)  - Next-RIP Saved on
> #VMEXIT (XEN)  - VMCB Clean Bits (XEN)  - DecodeAssists (XEN)  -
> Pause-Intercept Filter (XEN)  - TSC Rate MSR (XEN) HVM: SVM enabled (XEN)
> HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes:
> 4kB, 2MB, 1GB (XEN) HVM: PVH mode not supported on this platform
> 
> lscpu: Vendor ID:             AuthenticAMD CPU family:            21
> Model: 96 Model name:            AMD Athlon(tm) X4 845 Quad Core Processor
> Stepping: 1 CPU MHz:               3493.540 BogoMIPS:              6987.08
> Hypervisor vendor:     Xen Virtualization type:   none
> 
> lspci: 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 1577
> 
> xlinfo: virt_caps              : hvm xen_version            : 4.6.1
> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p 
> hvm-3.0-x86_64 xen_scheduler          : credit xen_pagesize           :
> 4096 platform_params        : virt_start=0xffff800000000000 xen_changeset :
> xen_commandline        : loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M
> 

Just a shot in the dark:

In order for IOMMU to work, it has to be supported by the CPU, chipset, and
motherboard. According to this previous guide, a common problem faced by many
users looking for compatible hardware is that even though their CPU supports
VT-d/IOMMU, their chipset does not:

https://groups.google.com/d/topic/qubes-users/Sz0Nuhi4N0o/discussion

Is it possible that, even though your CPU supports IOMMU, your chipset does not?

IIRC, some users have even found that their motherboard does not properly
support VT-d/IOMMU, despite the option to enable it being available in the BIOS.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXt1GcAAoJENtN07w5UDAwpbUQAMF/RBTo3SuYdkp4dKV8oWRm
NQBdoLRJMQJKgTqn/91HEEEPZAmTJ9w+EtLPtcP9IMJWiooAIHuTeQtTryMAHxhF
c7HCQqV1oOkLygNaY656wOGXgdd41vguYGXL1heDtfcwCliUC0Q1SE9tJ0BN+cV6
8xqjMkvF11evhhF0NPvpgGSqQHjgFPactIJ2L0UFnLI/bDa0j6152CF9/iDWsc18
tK05WfVJNCBX/VaM4SrkZoDcwdP5Nr90h1L6tBTN2Xn+1xHGwKt6lzumIjkX9Gtu
ykCd5geeM3Bs/OWVu2IJcQlBNXS3w2fdxlIC6OF5KDJkJVifITZViiJth3GRjCyx
lgvpe5bO0jREcRGT47WBy1opSxrQhxsZlGgXvowseS/HJeIRiGHkeTqddlqCZLy1
0UNIuvXvWv82iMy/lmQfUHH2SxqjMkWA9RZ4cjQm8Tyq2TkoLxlxN4MVZQ8BEQs1
RXR2mmK+sMAQJnZm4phtVzKze3bHXiJfaykaG4mvlTFtBOU5rkVLpSwGgzzQsVnU
8C4YjFoVOQAuDCn7Ibm4tc6Vw/JDUIaDOKaQHpzCIntTY/ZXt+briiILXV2lGadw
tWVFdHUQt7Q9D4isVnUYPDQgsKHdogIpkwl/8STrqpyeZ7o5KbESq2yl13256ygT
VNRTy+RgFOTo/aaqrVrk
=M+cM
-----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a83643c0-f5f7-bb5c-2297-1dd1a10a1906%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to