VT-d on XPS 9310

25 views
Skip to first unread message

Fabrizio Romano Genovese

unread,
Jan 31, 2021, 11:16:38 AM1/31/21
to qubes-users

Hello all,

My problem is quite simple: I tried to install qubes 4.0.4-rc2. During the installation procedure, it says that I don't have IOMMU/VT-d. Accordingly, I cannot even start sys-net once the installation completes because of lack of VT-d.
The problem is that my computer supports VT-d (CPU is intel i7 1165G7). VT-d is moreover enabled in my bios. Any clue about what the problem could be?

Fab

donoban

unread,
Jan 31, 2021, 11:37:36 AM1/31/21
to qubes...@googlegroups.com
Maybe dom0 'dmesg' and 'xml dmesg' help. Also try to upgrade your BIOS.

OpenPGP_signature

donoban

unread,
Jan 31, 2021, 11:41:13 AM1/31/21
to qubes...@googlegroups.com
On 1/31/21 5:37 PM, donoban wrote:
> Maybe dom0 'dmesg' and 'xml dmesg' help. Also try to upgrade your BIOS.

Wops, I meant 'xl dmesg'.

OpenPGP_signature

qubesth...@gmail.com

unread,
Jan 31, 2021, 11:46:30 AM1/31/21
to qubes-users

Probably a dumb question, but is VT-x also enabled?

Fabrizio Romano Genovese

unread,
Jan 31, 2021, 12:26:28 PM1/31/21
to qubes-users
Ok, I found something: Running `xl dmesg` there's a line that says:
(XEN) Failed to parse ACPI DMAR. Disabling VT-d.

The output of `dmesg` looks very technical and is unreadable to me if I don't know what I'm looking for.

...I guess VT-x is enabled as well. In bios I have only the options to enable VT and VT-d. I guess the former refers to VT-x?

Fab

donoban

unread,
Jan 31, 2021, 2:01:51 PM1/31/21
to qubes...@googlegroups.com
On 1/31/21 6:26 PM, Fabrizio Romano Genovese wrote:
> Ok, I found something: Running `xl dmesg` there's a line that says:
> (XEN) Failed to parse ACPI DMAR. Disabling VT-d.

I only think to try updating BIOS or using Qubes R4.1 which has newer
Xen version (although is pretty unstable yet). It will help to know if a
newer Xen version runs ok.

OpenPGP_signature

awokd

unread,
Jan 31, 2021, 3:05:07 PM1/31/21
to qubes...@googlegroups.com
donoban:
Try donoban's suggestions for sure, but if that still doesn't help you
might get more pointers in the log from messages just prior to the one
quoted above. Disabling onboard/PCIe devices such as USB
controllers/network cards might let you work around the problem as well.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

Fabrizio Romano Genovese

unread,
Jan 31, 2021, 7:07:48 PM1/31/21
to qubes-users
Ok, my BIOS wasn't updated. That solved the VT-d problem.

Everything seems to work aside of wifi. I have a Killer AX500, which is currently supported only in kernel 5.10+. For what I understand, in Qubes Fedora comes with Kernel 5.4.something at the moment. I've found some tutorials to update a generic Fedora kernel to 5.10, but I suppose the kernel I'm running now is customized to be ran within a qubes environment. If I try to compile and update sys-net to kernel 5.10 how likely it is that I'll make a mess?

Fab

donoban

unread,
Feb 1, 2021, 5:02:16 AM2/1/21
to qubes...@googlegroups.com
On 2/1/21 1:07 AM, Fabrizio Romano Genovese wrote:
> Ok, my BIOS wasn't updated. That solved the VT-d problem.
>
> Everything seems to work aside of wifi. I have a Killer AX500, which is
> currently supported only in kernel 5.10+. For what I understand, in
> Qubes Fedora comes with Kernel 5.4.something at the moment. I've found
> some tutorials to update a generic Fedora kernel to 5.10, but I suppose
> the kernel I'm running now is customized to be ran within a qubes
> environment. If I try to compile and update sys-net to kernel 5.10 how
> likely it is that I'll make a mess?

Great!

Take a look in https://www.qubes-os.org/doc/managing-vm-kernel/
specially in 'Using kernel installed in the VM' section. Last time I've
tried it with Centos template it failed and finally I installed a HVM,
(could work using a HVM as sys-net?).

OpenPGP_signature
Reply all
Reply to author
Forward
0 new messages