Re: [qubes-users] Re: How To Replace Libvirt Drivers

2017-12-02 Thread Person
Is this a common problem?

-- 
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/d5af2039-d133-4f68-9746-d696621edc09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: How To Replace Libvirt Drivers

2017-12-01 Thread Person
When I looked into the libvirt error, I received these messages:
https://imgur.com/a/drmaN
https://imgur.com/a/sSKQT

-- 
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/fd16314c-cfb0-4d76-ad51-4ad50c2b6f7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: How To Replace Libvirt Drivers

2017-11-29 Thread Person
Also, are there any driver updates that would fix this?

-- 
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/027a20d4-1068-41cf-b992-5c7a54baf768%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: How To Replace Libvirt Drivers

2017-11-27 Thread Person
On Sunday, November 26, 2017 at 11:51:23 PM UTC-5, Wael Nasreddine wrote:
> On Sun, Nov 26, 2017 at 8:22 PM Person  wrote:
> 
> 
> On Saturday, November 25, 2017 at 11:11:30 PM UTC-5, Wael Nasreddine wrote:
> 
> > 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  virt_mode pv
> 
> 
> 
> 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.
> 
> 
> 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.

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).

-- 
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/27d86bb0-3f5d-4283-960d-bff38f1a5578%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: How To Replace Libvirt Drivers

2017-11-26 Thread Wael M. Nasreddine
On Sun, Nov 26, 2017 at 8:22 PM Person  wrote:

> On Saturday, November 25, 2017 at 11:11:30 PM UTC-5, Wael Nasreddine wrote:
> > 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  virt_mode pv
>
> 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.
>
> 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+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/c5a3a98e-70ab-4c31-b87a-5ad31c87d3eb%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CA%2BkKtKCWv3ja%2BRH1%3D02EnMUKa8LsTQOMsERT_cFAgPLO3jyo7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How To Replace Libvirt Drivers

2017-11-26 Thread Person
On Saturday, November 25, 2017 at 11:11:30 PM UTC-5, Wael Nasreddine wrote:
> 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  virt_mode pv

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.
 

-- 
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/c5a3a98e-70ab-4c31-b87a-5ad31c87d3eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How To Replace Libvirt Drivers

2017-11-25 Thread 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  virt_mode pv

-- 
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/5f034717-237a-45aa-a158-bfaa00ca4110%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How To Replace Libvirt Drivers

2017-11-25 Thread 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. 

-- 
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/25968877-e1f4-4c00-afb5-2849ff70e21a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How To Replace Libvirt Drivers

2017-11-24 Thread Wael Nasreddine
On Friday, November 24, 2017 at 9:44:50 PM UTC-8, Wael Nasreddine wrote:
> On Friday, November 24, 2017 at 9:04:01 PM UTC-8, Person wrote:
> > 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.
> 
> 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

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

-- 
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/5e2079de-37cc-4e20-9019-58053bf0c838%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How To Replace Libvirt Drivers

2017-11-24 Thread Wael Nasreddine
On Friday, November 24, 2017 at 9:04:01 PM UTC-8, Person wrote:
> 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.

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

-- 
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/65044589-6a38-4c86-b80a-9d4d44f585b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How To Replace Libvirt Drivers

2017-11-24 Thread 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.

-- 
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/06c28d76-2db4-434b-a2f0-cb63f13d1b0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How To Replace Libvirt Drivers

2017-11-24 Thread 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

-- 
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/f5e03e31-ffcd-4c45-a2de-5141cde7fd21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How To Replace Libvirt Drivers

2017-11-24 Thread 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”.

-- 
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/df7eca57-960c-4411-84b5-807dd83cf7b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How To Replace Libvirt Drivers

2017-11-23 Thread 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

-- 
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/b2b2d778-5827-4ab5-b192-a72cf30853dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.