Hardware not supported on Qubes 4.0 rc2

[Anirban Kar]

My Hardware:

Processor- AMD Athlon X2 5200

Mobo- Asrock 960GC-GS FX

RAM- DDR2 800 MHz 2× 2GB

HDD - Seagate 250 GB SATA 7200 rpm

I can install and use Qubes 3.2 without any hassel but facing a hardware incompatibility notification while installing Qubes 4.0 rc2. Ignoring the notification and installing Qubes 4.0 rc2 results to a system which does not have a sys-net vm. I am adding a screenshot of the notification. I am quite sure that my processor supports AMD-V.

[Foppe de Haan]

is iommu support present and enabled in your bios?

[joev...@gmail.com]

In Qubes 3.2.... run an HCL Report and make sure directio is shown. Post the report here.

[Foppe de Haan]

On Thursday, October 26, 2017 at 7:37:10 PM UTC+2, Anirban Kar wrote:

googling a bit, I see that your CPU is from 2006, and afaik AMD only added iommu support around 2007, and then 'upgraded' it around 2013/14, so it's not likely to fully support hvm/pvh virtualization. You can probably get sys-net to run by running 'qvm-prefs sys-net virt_mode pv' from dom0 shell, though.

[Marco Silva]

Funny thing that I've installed qubes 4.0 RC1 on an old laptop with a I7-2670 cpu who doesn't support VT-d.

On my workstation(Tyan s7050 & 2X Xeons E5-2670 +64GB ram) I've installed RC2 without any warnings, but when I've start the initial setup i have a LIBwhatever error and doesn't install any VM :(

[Anirban Kar]

Here is the HCL attached as per your request.

[Anirban Kar]

On Friday, 27 October 2017 08:58:55 UTC+5:30, Anirban Kar wrote:
> Here is the HCL attached as per your request.

Also sending the .cpio.gz as attachment.

[joev...@gmail.com]

On Thursday, 26 October 2017 13:37:10 UTC-4, Anirban Kar wrote:

iommu:
'no'

Says it all.
Read the release notes and blog posts on rc1 and rc2. PV vs. HVM was the difference between the two.

qvm-prefs sys-net virt_mode pv

This may work, but future versions of qubes are going away from PV all together, so AMD-Vi (IOMMU) will be a requirement.
I upgraded my hardware for this reason.

[Sergio Matta]

Dear Anirban, I have the same problem and I will change my motherboard. But until there, I changed to PV, insert some ip commands(ip link, ip addr, ip route) in /rw/config/rc.local (sys-net and sys-firewall) to enable networking. It is not the best solution but works.