Chris: >> I will do a fresh install and confirm again that disabling msi does the >> trick. > > Confirmed. I tweaked the command a bit because it removed the default kernel > options.
Depending on hardware, getting Qubes up and running can sometimes be the hardest part of using it. In comparison, the rest should be smooth sailing. :) Do remember to run backups, though. EXT3 on thin LVM is not as resilient as NTFS, for example. >> qvm-prefs sys-net kernelopts "nopat iommu=soft swiotlb=8192 pci=nomsi" > > Any idea if this would introduce any security vulnerabilities? > I've looked at the Xen/Qubes PCI virtualization code when troubleshooting a similar issue with interrupts on one of my systems. IIRC, MSI and standard interrupts get handled the same way and processed through the same code base, so I don't see any difference in exposure. For a canonical answer, you might try the qubes-devel mailing list since they get more in-depth. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3826c678-f998-1a7d-f0ee-b8a75243cf98%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
