Thinkpad Yoga 2014, Virtualization on, Legacy boot (aka no UEFI), worked perfectly on Qubes 3.2.
Did the backup and decided to install 4.0 today. I've reinstalled it 2 times already, and I always get an error related to sys-firewall (similar to this - https://groups.google.com/forum/#!topic/qubes-users/hZejgU5E5zA). Disregarding the error, I enter the desktop and no vms are on. I try to boot literally any vm and I have an error related to libxenlight (failed to create new domain - see log file). In the log file, the errors are "PCI device cannot be assigned - no IOMMU?" repeated 3 times, "unable to add pci devices".
What can I try? Anyone faced this problem?
I've investigated a bit further. The error says that it's impossible for the system to assign the PCI 0000:04:00.0 to sys-net. This is the network card, no other vm has this assigned to it. The perms on the qube's config assign it to sys-net, what can be wrong with it?
Tried using PV mode. It fixed it, but obviously carries it's concerns. Is there a safer option? Would the tutorial on pci passthrough be a shot worth a try? https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues
On Fri, June 1, 2018 4:52 pm, Hugo Costa wrote:
> On Friday, 1 June 2018 17:45:59 UTC+1, Hugo Costa wrote:
>
>> On Friday, 1 June 2018 17:38:23 UTC+1, Hugo Costa wrote:
>>> errors are "PCI device cannot be assigned - no IOMMU?" repeated 3
>>> times, "unable to add pci devices".
Is VT-d available and enabled for your system?
> Tried using PV mode. It fixed it, but obviously carries it's concerns. Is
> there a safer option? Would the tutorial on pci passthrough be a shot
> worth a try?
> https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues
I'd try those options before PV mode.