How To Replace Libvirt Drivers

[Person]

I have Qubes 3.2, and whenever I try to create HVM domains, libvirt fails to create them.

Is there any way to replace libvirt drivers? If so, what drivers would you recommend using?

[Person]

And if so, what would the steps be to install those drivers?

[Yethal]

W dniu czwartek, 23 listopada 2017 02:19:46 UTC+1 użytkownik Person napisał:
> I have Qubes 3.2, and whenever I try to create HVM domains, libvirt fails to create them.
>
> Is there any way to replace libvirt drivers? If so, what drivers would you recommend using?

Enable VT-d in BIOS/UEFI

[Person]

I believe I already did. The error message for not having enabled VT-d is different from the error message I received: libvirtError.libvirt: libxenlight failed to create new domain “domain name”.

[Yethal]

W dniu piątek, 24 listopada 2017 19:18:06 UTC+1 użytkownik Person napisał:
> I believe I already did. The error message for not having enabled VT-d is different from the error message I received: libvirtError.libvirt: libxenlight failed to create new domain “domain name”.

sudo xl dmesg|grep VT-d

[Person]

I entered that command in the terminal, and I received this reply:

https://imgur.com/a/zH3hO

It seems that I haven’t enabled many things, and I don’t know how to enable them.

[Wael Nasreddine]

I'm having a similar issue, freshly installed Qubes 4.0-rc2, when it's running the first_install configuration, I receive the error `libvirtError.libvirt: libxenlight failed to create new domain “domain name”.`

- VT-x/VT-d is enabled in the bios
- I booted ArchLinux install CD and in /proc/cpuinfo I see vmx/vme and lscpu says VT-x is available but that's not the case in what I see in Qubes (lscpu list Virtualisation as None)

In an earlier install, after I got this error, I switched all VMs to using pv virt_mode and managed to get `qubes-dom0-update` to run, after doing that, I still got the same weird /proc/cpuinfo and lscpu output but VMs were booting OK with hvm.

I reinstalled Qubes because the initial_setup did not complete, and now I'm stuck with the same issue.

Is there a way to default all new VMs to PV so when the initial_setup creates sys-net and sys-firewall it would work and I'd be able to run `qubes-dom0-update` and then switch them back to hvm? If not, is there a way during the installation to use Qubes repos for packages as opposed to using the ISO?

- ArchLinux: https://imgur.com/3eb9lWY
- QubesOS: https://imgur.com/mSpZFeq

[Wael Nasreddine]

I forgot to add my HCL https://imgur.com/in30u6v

[Person]

https://imgur.com/a/Rx3TR
This is what I received when I typed in “lscpu”.
For some reason, the virtualization type is “none”.

[Person]

“In an earlier install, after I got this error, I switched all VMs to using pv virt_mode and managed to get `qubes-dom0-update` to run, after doing that, I still got the same weird /proc/cpuinfo and lscpu output but VMs were booting OK with hvm.”

How exactly do you switch VMs to using pv virt_mode? The only thing I actually want is for the VMs to book correctly, and that would save me a lot of trouble.

[Wael Nasreddine]

On Saturday, November 25, 2017 at 8:06:27 PM UTC-8, Person wrote:
> “In an earlier install, after I got this error, I switched all VMs to using pv virt_mode and managed to get `qubes-dom0-update` to run, after doing that, I still got the same weird /proc/cpuinfo and lscpu output but VMs were booting OK with hvm.”
>
> How exactly do you switch VMs to using pv virt_mode? The only thing I actually want is for the VMs to book correctly, and that would save me a lot of trouble.

sudo qvm-prefs <VM_NAME> virt_mode pv

[Person]

I tried the command on my only HVM, and I received the message:
***Running the tool as root is strongly discouraged, this will lead you in permissions problems. Retry as unprivileged user or use "--force-root" to continue anyway.
I wasn't using root user at the time, so I found that strange. And after I changed the HVM to pv virt_mode, I got the same virtualization error.

I then tried the command on every single VM. I still received the "--force-root" message, but there were no other errors in the command. When I submitted the commands, I received lists of information about the VMs. And when I changed them to pv virt_mode, I still got the same virtualization error.

(If dom0 doesn't say that the command was unsuccessful, it was successful, right? Otherwise, I may not have successfully set the VMs to pv virt_mode.)

It seems that we have different versions of Qubes (you have Qubes 4.0 and I have Qubes 3.2), so I can see why your method might not work for me.

[Wael M. Nasreddine]

My apologies, yes I'm running 4.0. My issue is not similar to yours afterall, as I understand it (never tried R3) it defaults to PV anyway.

 

--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/Go04b5VsYfw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c5a3a98e-70ab-4c31-b87a-5ad31c87d3eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Person]

Interesting. I wonder if there's any way to get rid of this problem other than changing it to pv virt_mode, changing the drivers, or reinstalling the hypervisor.

I wonder if I should just give up HVM and try seeing if there are any templates of the OS I want for Qubes (probably not).

[Person]

I’ve tried most of the solutions on https://github.com/QubesOS/qubes-issues/issues/3125, but they don’t seem to work. Or I probably am doing something wrong.

Would changing the drivers actually work? I don’t want to keep trying to fix libvirt.

[Person]

When I looked into the libvirt error, I received these messages:
https://imgur.com/a/drmaN
https://imgur.com/a/sSKQT

[Person]

Is this a common problem?