On Sunday, November 26, 2017 at 6:38:01 AM UTC, Wael Nasreddine wrote: > Just installed Qubes 4.0-RC2. I had issues with the installation (was getting > libvirt errors), I solved the errors by temporarily switching all VMs to PV, > update dom0 and restore them back to HVM.
I got Qubes 4 RC-2 running on a similar motherboard for someone else, the Asus z170 Pro Gaming. I don't use this system actively my self, but it ran smoothly from the hours I used to set it all up and to configure it, and it had no libvirt errors. So the basic chipset features of the z170 line should not be an issue, and you got immou enabled in your HCL rapport file, so I assume your VT-d must be enabled in your UEFI (BIOS). Also the processor doesn't look like an issue either. However, I remember this particular motherboard had two separate places to activate the virtualisation technology, you may have only enabled one of them in the UEFI? Both settings came disabled on the Asus z170 Pro Gaming board I set up with Qubes 4. In your UEFI Advanced menu, try look for both: - VT-d. (I suspect this is the one you enabled). - Virtualization (something closely worded to this, I suspect this might be the setting you miss to enable). So if the two boards are anything alike, then this might be it. If you can't find this extra setting, then perhaps your model is different and it doesn't have it extra required step. But it may very well be similar. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/73dec1cb-e047-46bb-b5d1-58d0f7959676%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
