IOMMU/VT-d/AMD-Vi
Interrupt Remapping
The installation went fine. I simply continued installing after the error message appeared just after the installation ISO completed its hardware check.
After installation, I was able to boot up to the desktop without any errors. I didn't do much additional testing because I thought that there might be a way to configure the BIOS on my machine to support the missing features; but alas, there is no such way.
Consequently, if I ever want to run 4.0, I am left with the following two choices:
A) Install 4.0 on this machine and live without the missing features.
B) Get a new computer that supports the missing features.
I prefer option A. Can anyone tell me what I might expect without IOMMU/VT-d/AMD-Vi and Interrupt Remapping?
I've heard that PCI passthrough won't work, but I could live without it.
What other problems might I encounter? Will 4.0 work without those features, or must I get a new machine to run 4.0?
Oh, darn. Worst case scenario.
Anyone interested in a pair of lightly used HP Z800 server work stations? Great machines. Cannot run Qubes 4.0 correctly.
-sigh-
Thanks for the link, Rusty.
Ah. I hadn't considered the Coreboot option. My understanding is that the chipset is at fault.
The only documentation I've found was forwarded to me from another user on this list. It explains a solution that Zen recommended for this particular hardware problem; but as far as I can tell, the best-available fix is still not capable of resolving the issue sufficiently for Qubes 4.0:
Recommendation, if you'd like, for a budget/beater VT-d:
I've picked up a couple of Lenovo Thinkpad W520 laptops off of Ebay recently. They were top of the line in 2011 (if you limited your choices to mobile CPUs only). They can be found around the $200-$300 mark (depending on luck, configuration and accessories).
Additional things to look out for:
Some units are dual core, but I'd look for the quad core ones: they have an i7-xxxxQM or XM processor which, unlike the duals, are built with with four working RAM slots giving a max of 32GB DDR3. Those without i7-xxxxQM or XM CPUs only have four slots but only two are working slots. 16GB can be a bit tight, esp. if you run any Win HVMs.
Machine also supports up to four native SATA devices, two 6Gbps (internal HD, hotswap ultrabay HD with optional carrier), two 3Gbps (mSATA and hotswap external eSATA with optional cable).
Always update the BIOS, most used w520 units come with the original 2011 BIOS but there is a 2015 or 2016 revision available that fixes some security issues (and may stop some linux kernel configs from having problems with the machine setup).
Lastly: set BIOS to integrated graphics (not NVidia nor Optimus, just Integrated). Occasionally the Nvidia GPUs go bad but if it isn't enabled in BIOS, it won't prevent you from posting. I learned the hard way with the W520 I bought back in 2011...they won't post into BIOS if you enable a bad Nvidia GPU and now you have a brick.
Brendan
PS - The W520 also is the last W5xx to support a nice Thinkpad keyboard. :)
Thank you for the confirmation, @awokd!
Thanks also to @Brendan & @Taiidan for the laptop recommendations as well. I've known about the G505S for a while now, but the W520 is a new option for me to consider.
Meanwhile, the machines I'm currently replacing are both server workstations with 96 gigs of EEC RAM. I'm looking to upgrade to something comparable, and I'm pretty certain at this point that I'll start building with either the KCMA-D8 or KGPE-D16. I've got one year after the release of 4.0 to make the transition, so I've got time to collect all the bits before 3.2 reaches end-of-life.
It's just too bad that the Z800 turns out to have a manufacturing defect. I bought them last year because they meet the minimum requirements for Qubes 4.0; or, they would have if they hadn't been borked at the chip factory.
My 440p has been great running qubes and fully supports 4.0 as well. 16g ram has been plenty for a laptop (not workstation replacement).
For a workstation I would rather build one so I could have as close to an ideal config as possible but certainly not cheap $ option.
I saw that, but the same page mentions Taiidan's solution for providing the needed microcode updates. Luckily, Taiidan seems to like Qubes, so he's an easy guy to find. :)