Hello,
I really enjoy my LibremV3, however I have discovered a significant problem. It seems VT-d is not enabled on Purism devices.
$ sudo qubes-hcl-report personal
Qubes release 3.2 (R3.2)
Brand: Purism
Model: Librem 15 v3
BIOS: 4.6-a86d1b-Purism-4
Xen: 4.6.5
Kernel: 4.9.35-19
RAM: 16282 Mb
CPU:
Intel(R) Core™ i7-6500U CPU @ 2.50GHz
Chipset:
Intel Corporation Skylake Host Bridge/DRAM Registers [8086:1904] (rev 08)
VGA:
Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller])
Intel Corporation Device [8086:9d24] (rev 21)
Net:
Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
SCSI:
Samsung SSD 850 Rev: 2B6Q
Samsung SSD 850 Rev: 1B6Q
HVM: Active
I/O MMU: Not active
HAP/SLAT: Yes
TPM: Device not found
Remapping: no
Qubes HCL Files are copied to: ‘personal’
Qubes-HCL-Purism-Librem_15_v3-20170819-150425.yml - HCL Info
$ cat /proc/cpuinfo | grep lm
flags : fpu de tsc msr pae mce cx8 apic sep mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc arch_perfmon rep_good nopl nonstop_tsc eagerfpu pni pclmulqdq monitor est ssse3 sdbg fma cx16 sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch fsgsbase bmi1 avx2 bmi2 erms rdseed adx xsaveopt xsavec dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
$ cat /proc/cpuinfo | grep vmx
$
This is a major blocker to your users running qubes or even KVM inside of PureOS. Its my understanding the Qubes 4.0 will not support devices without VT-d or VT-x enabled, not to mention the significant performance impact. Additionally, VT-d and VT-x provide key security protections for virtualized systems. Is this a setting that needs to be enabled in coreboot? Once installed can coreboot be flashed via software or does it still require additional hardware & expertise?
Edit: I found a thread on coreboot relating to this issue: [coreboot] VT-d on Pixel 2015 (samus)
if I read correctly, coreboot leaves it to the user to enable. Not wanting to experiment on my new device, has this been tested on Purism devices and if so, what is the recommended way of enabling these features on Purism devices?