Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upMMU enabled in BIOS but not active in Q4 rc5 #3684
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Mar 9, 2018
Member
Qubes 3.2 did not strictly required IOMMU (but it improved security there), now it is strictly required. So it's possible it didn't worked there either.
Anyway, I suspect there is some hardware related issue. You may need to update BIOS.
See xl dmesg output for details.
|
Qubes 3.2 did not strictly required IOMMU (but it improved security there), now it is strictly required. So it's possible it didn't worked there either. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
decnet
commented
Mar 10, 2018
|
Updated BIOS to 2.70 and now it works. Thanks for your help! |
decnet
closed this
Mar 10, 2018
andrewdavidwong
added
the
resolved
label
Mar 10, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
decnet commentedMar 9, 2018
•
edited
Edited 1 time
-
decnet
edited Mar 9, 2018 (most recent)
Qubes OS version:
Qubes Release 4.0 (R4.0)
Affected component(s):
core
Steps to reproduce the behavior:
qvm-start sys-netExpected behavior:
IOMMU should be enabled and the VMs should start without error.
Actual behavior:
When I start any non-template VM I get the following error:
start failed: internal error: libxenlight failed to create new domain 'sys-net', see /var/log/libvirt/libxl-driver.log for detailsand in var/log/libvirt/libxl-driver.log for details
...libxl__device_pci_add: PCI device 0000:00:19.0 cannot be assigned - no IOMMU? ...libxl__add_pcidevs: libxl_device_pci_add failed -1 ...libxlcreate_attach_devices: unable to add pci devicesGeneral notes:
MMU is enabled in the BIOS, however is shown as "not active" when I run qubes-hcl-report. I've been running Q3.2 for ages with no problems, but i've not attempted to run any previous 4.0 release candidates. Its a lenovo x230.
Related issues: