[qubes-users] Re: whonix-gw and whonix-ws not running on qubes 4.0 rc1

2017-10-22 Thread Foppe de Haan
On Monday, October 23, 2017 at 12:26:57 AM UTC+2, Francesco Rmp wrote:
> Hi again,
> i'm sorry that i'm posting so many help requests all of a sudden.
> 
> I was trying to get whonix to work on qubes 4, i've followed some tutorials 
> and with some helps from the bug tracker on github i could get the template 
> VMs installed and both the sys-whonix and anon-whonix domains.
> 
> The problem is that they just don't start up, and i don't know how to debug 
> the problem
> 
> I've also tried setting the VMs in debug mode, but i cant get any output that 
> i can look up for to understand what's going on.
> 
> The only thing i can get is the boot up windows (with black border) when i do 
> qvm-start -v sys-whonix
> but it disappears too fast for me to read the output. Appearently there is 
> something wrong in there that causes the VM to die.
> 
> can anyone help me out in understanding what's wrong?
> 
> i ised the suggetions in this issue: 
> https://github.com/QubesOS/qubes-issues/issues/2954
> 
> to set things up by configuring the repositories and keys needed to install 
> the community templates.
> 
> all other domains work fine.

any info in /var/log/xen/console/guest-sys-whonix.log?

-- 
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/e1aff7b7-0ea8-465a-8484-4d8dd95a90c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] whonix-gw and whonix-ws not running on qubes 4.0 rc1

2017-10-22 Thread Francesco Rmp
Hi again,
i'm sorry that i'm posting so many help requests all of a sudden.

I was trying to get whonix to work on qubes 4, i've followed some tutorials and 
with some helps from the bug tracker on github i could get the template VMs 
installed and both the sys-whonix and anon-whonix domains.

The problem is that they just don't start up, and i don't know how to debug the 
problem

I've also tried setting the VMs in debug mode, but i cant get any output that i 
can look up for to understand what's going on.

The only thing i can get is the boot up windows (with black border) when i do 
qvm-start -v sys-whonix
but it disappears too fast for me to read the output. Appearently there is 
something wrong in there that causes the VM to die.

can anyone help me out in understanding what's wrong?

i ised the suggetions in this issue: 
https://github.com/QubesOS/qubes-issues/issues/2954

to set things up by configuring the repositories and keys needed to install the 
community templates.

all other domains work fine.

-- 
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/42a5820d-9685-44dd-be87-80930ce7c66d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: qubes 4.0 RC1 networking problems

2017-10-22 Thread Francesco Rmp
Il giorno domenica 22 ottobre 2017 16:29:14 UTC-4, yura...@gmail.com ha scritto:
> On Sunday, October 22, 2017 at 5:27:17 PM UTC, Francesco Rmp wrote:
> > Hello everyone,
> > i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the 
> > 3.2 to install because of the kernel compatibility).
> > 
> > The installation went smooth and i can boot fine in the system, but i'm 
> > having some networking issues.
> > 
> > Making the long story short: i cant get any VM to go online.
> > 
> > I'm no that familiar with the networking in qubes, but i tried to do some 
> > troubleshooting myself, and here is what i get.
> > 
> > - The sys-net VM works fine, it gets the IP from DHCP, gateway, DNS and 
> > everything and this is the only VM that goes online. i can ping hosts and 
> > communicate with the network. I didn't do anything fency in this VM but 
> > using some terminal commads to check i could actually go online, and it 
> > works.
> > 
> > This network fetches the IPs from my DHCP and is set to a 192.168.1.0/24
> > 
> > - the sys-firewall VM doesn't go online at all. I checked the VM 
> > configuration in qubes manager, and according to the configuration, it 
> > looks like it's using sys-net as its gateway, but still nothing.
> > Curious that when i check in the terminal, it has a network interface with 
> > class 10.xxx (i dont' remember exactly) and an additional interface for 
> > each appVM that i spin up (this is fine).
> > My question is.. how can this VM masquarade any traffic to the sys-net VM 
> > if the class of the network interface is completely different and the 
> > gateway is actually not set to the sys-net VM ip?
> > 
> > - As a consequence of the fact that the sys-firewall VM doesn't go online, 
> > all the appVMs suffer the same problem.
> > 
> > Can anyone help me out in troubleshooting this problem?
> > Am i right to assume that this is not an hardware problem? considering that 
> > the physical network interface assigned to sys-net works fine?
> > 
> > thanks in advance for your kind reply and support.
> 
> 
> Typically the Firewall AppVM is not happy to go online if there are problems 
> with the sys-net AppVM. The issue is therefore likely in the sys-net AppVM, 
> and not the firewall AppVM. For example if you take a fully functioning Qubes 
> system, and you kill off the sys-net AppVM, while allowing the firewall AppVM 
> to stay online, and then start up sys-net again, will cause issues with the 
> Firewall AppVM. You'll have to shutdown the firewall AppVM and start it 
> again, to establish a proper tied connection with the sys-net. Something 
> similar is likely happening here, if there is something not properly working 
> in your sys-net.
> 
> There are likely two reasons to the problems you face, that I can think of.
>  
> - The first issue is the planned premature release of Qubes 4 (kind of alpha 
> release), does not always support PCI passthourgh too well, which might 
> explain why your network card can't be passed through properly. Indeed it 
> might work for a single VM, but if it can't communicate perfectly, it might 
> cause the Firewall AppVM to bug out (A possibility). This major Qubes 4-RC1 
> issue has very recently been fixed, as early as last week. But since you 
> don't have networking, you can't fetch the patch that fixes it. You're in 
> luck though, Qubes 4-RC2 is planned to be released tomorrow, as you can see 
> here https://www.qubes-os.org/doc/releases/4.0/schedule/
> It shouldn't be delayed once more, a major issue holding it back, is exactly 
> the issue up above causing problems with PCI passthrough hardware in Qubes 4. 
> If this still does not work,then you can try turn your Passthrough AppVM's 
> into PV virtualization mode, instead of HVM mode, which Qubes 4 can do with a 
> single command. I believe it should be in terminal dom0: QVM-prefs "AppVM 
> name" -l
> somewhere. I don't run Qubes 4 atm, so I can't check, but it should be easy 
> to do, from what I've heard. 
> 
> - The other issue, that I can think of, is Ryzen. The kernel that almost 
> fully supports Ryzen should be around version 9.12+. For example I've seen 
> Qubes with Ryzen that only partially allow USB passthrough, but not fully 
> passtrough, causing weird issues. Qubes does not run version 9.12 just yet 
> (as far as I know at least), but it should happen soon since 9.12 longterm 
> status is close now. This, as you probably already know, typically happens 
> when newer kernels are pushed out regularly, check https://www.kernel.org/
> 
> You might know this already too, but the reason you can boot with Ryzen, is 
> that Ryzen basic support works, but extra features such as PCI devices and 
> such, might not work until you get a proper 9.12+ version kernel. Also be 
> careful, my friend who runs Qubes on Ryzen, has had some kernel issues when 
> upgrading, where earlier kernels allowed Ryzen to boot Qubes, but a newer 
> version did not which resulted in kernel 

[qubes-users] Re: qubes 4.0 RC1 networking problems

2017-10-22 Thread yuraeitha
On Sunday, October 22, 2017 at 5:27:17 PM UTC, Francesco Rmp wrote:
> Hello everyone,
> i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the 3.2 
> to install because of the kernel compatibility).
> 
> The installation went smooth and i can boot fine in the system, but i'm 
> having some networking issues.
> 
> Making the long story short: i cant get any VM to go online.
> 
> I'm no that familiar with the networking in qubes, but i tried to do some 
> troubleshooting myself, and here is what i get.
> 
> - The sys-net VM works fine, it gets the IP from DHCP, gateway, DNS and 
> everything and this is the only VM that goes online. i can ping hosts and 
> communicate with the network. I didn't do anything fency in this VM but using 
> some terminal commads to check i could actually go online, and it works.
> 
> This network fetches the IPs from my DHCP and is set to a 192.168.1.0/24
> 
> - the sys-firewall VM doesn't go online at all. I checked the VM 
> configuration in qubes manager, and according to the configuration, it looks 
> like it's using sys-net as its gateway, but still nothing.
> Curious that when i check in the terminal, it has a network interface with 
> class 10.xxx (i dont' remember exactly) and an additional interface for each 
> appVM that i spin up (this is fine).
> My question is.. how can this VM masquarade any traffic to the sys-net VM if 
> the class of the network interface is completely different and the gateway is 
> actually not set to the sys-net VM ip?
> 
> - As a consequence of the fact that the sys-firewall VM doesn't go online, 
> all the appVMs suffer the same problem.
> 
> Can anyone help me out in troubleshooting this problem?
> Am i right to assume that this is not an hardware problem? considering that 
> the physical network interface assigned to sys-net works fine?
> 
> thanks in advance for your kind reply and support.


Typically the Firewall AppVM is not happy to go online if there are problems 
with the sys-net AppVM. The issue is therefore likely in the sys-net AppVM, and 
not the firewall AppVM. For example if you take a fully functioning Qubes 
system, and you kill off the sys-net AppVM, while allowing the firewall AppVM 
to stay online, and then start up sys-net again, will cause issues with the 
Firewall AppVM. You'll have to shutdown the firewall AppVM and start it again, 
to establish a proper tied connection with the sys-net. Something similar is 
likely happening here, if there is something not properly working in your 
sys-net.

There are likely two reasons to the problems you face, that I can think of.
 
- The first issue is the planned premature release of Qubes 4 (kind of alpha 
release), does not always support PCI passthourgh too well, which might explain 
why your network card can't be passed through properly. Indeed it might work 
for a single VM, but if it can't communicate perfectly, it might cause the 
Firewall AppVM to bug out (A possibility). This major Qubes 4-RC1 issue has 
very recently been fixed, as early as last week. But since you don't have 
networking, you can't fetch the patch that fixes it. You're in luck though, 
Qubes 4-RC2 is planned to be released tomorrow, as you can see here 
https://www.qubes-os.org/doc/releases/4.0/schedule/
It shouldn't be delayed once more, a major issue holding it back, is exactly 
the issue up above causing problems with PCI passthrough hardware in Qubes 4. 
If this still does not work,then you can try turn your Passthrough AppVM's into 
PV virtualization mode, instead of HVM mode, which Qubes 4 can do with a single 
command. I believe it should be in terminal dom0: QVM-prefs "AppVM name" -l
somewhere. I don't run Qubes 4 atm, so I can't check, but it should be easy to 
do, from what I've heard. 

- The other issue, that I can think of, is Ryzen. The kernel that almost fully 
supports Ryzen should be around version 9.12+. For example I've seen Qubes with 
Ryzen that only partially allow USB passthrough, but not fully passtrough, 
causing weird issues. Qubes does not run version 9.12 just yet (as far as I 
know at least), but it should happen soon since 9.12 longterm status is close 
now. This, as you probably already know, typically happens when newer kernels 
are pushed out regularly, check https://www.kernel.org/

You might know this already too, but the reason you can boot with Ryzen, is 
that Ryzen basic support works, but extra features such as PCI devices and 
such, might not work until you get a proper 9.12+ version kernel. Also be 
careful, my friend who runs Qubes on Ryzen, has had some kernel issues when 
upgrading, where earlier kernels allowed Ryzen to boot Qubes, but a newer 
version did not which resulted in kernel panic. So some kernels are a hit and 
miss, probably until you reach version 4.12+. 
If you boot with Grub, then it's easy to switch to an older kernel. Also you 
can increase the kernel to be saved to be more than 3, so in case multiple of 
broken kernels are 

[qubes-users] Re: qubes 4.0 RC1 networking problems

2017-10-22 Thread Francesco Rmp
Il giorno domenica 22 ottobre 2017 13:41:33 UTC-4, Foppe de Haan ha scritto:
> On Sunday, October 22, 2017 at 7:27:17 PM UTC+2, Francesco Rmp wrote:
> > Hello everyone,
> > i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the 
> > 3.2 to install because of the kernel compatibility).
> > 
> > The installation went smooth and i can boot fine in the system, but i'm 
> > having some networking issues.
> > 
> > Making the long story short: i cant get any VM to go online.
> > 
> > I'm no that familiar with the networking in qubes, but i tried to do some 
> > troubleshooting myself, and here is what i get.
> > 
> > - The sys-net VM works fine, it gets the IP from DHCP, gateway, DNS and 
> > everything and this is the only VM that goes online. i can ping hosts and 
> > communicate with the network. I didn't do anything fency in this VM but 
> > using some terminal commads to check i could actually go online, and it 
> > works.
> > 
> > This network fetches the IPs from my DHCP and is set to a 192.168.1.0/24
> > 
> > - the sys-firewall VM doesn't go online at all. I checked the VM 
> > configuration in qubes manager, and according to the configuration, it 
> > looks like it's using sys-net as its gateway, but still nothing.
> > Curious that when i check in the terminal, it has a network interface with 
> > class 10.xxx (i dont' remember exactly) and an additional interface for 
> > each appVM that i spin up (this is fine).
> > My question is.. how can this VM masquarade any traffic to the sys-net VM 
> > if the class of the network interface is completely different and the 
> > gateway is actually not set to the sys-net VM ip?
> > 
> > - As a consequence of the fact that the sys-firewall VM doesn't go online, 
> > all the appVMs suffer the same problem.
> > 
> > Can anyone help me out in troubleshooting this problem?
> > Am i right to assume that this is not an hardware problem? considering that 
> > the physical network interface assigned to sys-net works fine?
> > 
> > thanks in advance for your kind reply and support.
> 
> try setting debian-8 as your sys-net template.

By swapping the template for the net-vm now internet works, but the problem is 
only partially solved.

For some odd reasons, which i couldn't giure out myself.. all of a sudden 
internet stops working again, and the only way to get it back to work is by 
disabling and reenabling the wired connection (using the network manager icon 
on the top right corner).

This is really troublesome because i can't get qubes to update or install 
additional template VMs, as it always stops in the middle of the task and i 
have to start over.

-- 
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/eca0acda-c61e-47ba-9630-1862d610100a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Anyone disabled the Intel ME yet?

2017-10-22 Thread Theo
On Monday, 18 September 2017 13:33:31 UTC-7, alexc...@gmail.com  wrote:
> Has anyone here successfully disabled the Intel ME yet?


Purism says they are diabling it by default on all laptops they are sending out 
now.

Ref:
https://puri.sm/posts/deep-dive-into-intel-me-disablement/

Now if only the hardware was just slightly more powerfull and future oriented.

-- 
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/9e0e4519-012d-4b92-8ebd-e70f95377f6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Audio in Debian VMs just disappeared?

2017-10-22 Thread yuraeitha
On Sunday, October 22, 2017 at 1:39:39 PM UTC, Stumpy wrote:
> On 19.10.2017 01:59, Stumpy wrote:
> > On 18.10.2017 20:16, qubenix wrote:
> >> Foppe de Haan:
> >>> On Wednesday, October 18, 2017 at 12:38:05 AM UTC+2, Stumpy wrote:
>  hm...
>  
>  Is there something else I can post that would make this easier to 
>  diag?
>  I really really would like to resolve this.
>  
>  On 16.10.2017 02:28, Stumpy wrote:
> > No one?
> > I still haven't figured this one out
> > 
> > in case the private/paste bin was causing no responses here is the
> > output from VLC:
> > from the vlc window:
> > "Audio output failed:
> > The audio device "default" could not be used:
> > No such file or directory."
> > 
> > and from the term that I started vlc from:
> > VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c)
> > [5e890a526938] pulse audio output error: PulseAudio server
> > connection failure: Connection refused
> > [5e890a4410e8] core libvlc: Running vlc with the default
> > interface. Use 'cvlc' to use vlc without interface.
> > ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
> > ALSA lib conf.c:4528:(_snd_config_evaluate) function
> > snd_func_card_driver returned error: No such file or directory
> > Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
> > object file: No such file or directory
> > ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
> > ALSA lib conf.c:4528:(_snd_config_evaluate) function 
> > snd_func_concat
> > returned error: No such file or directory
> > ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
> > ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer
> > returned error: No such file or directory
> > ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such 
> > file
> > or directory
> > ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default
> > [5e890a526938] alsa audio output error: cannot open ALSA device
> > "default": No such file or directory
> > [5e890a526938] core audio output error: module not functional
> > [76de94d7eaa8] core decoder error: failed to create audio 
> > output
> > Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
> > object file: No such file or directory
> > [76de74001268] xcb_xv vout display error: no available XVideo
> > adaptor
> > 
> > anyone?
> > 
> > 
> > On 07.10.2017 23:12, Stumpy wrote:
> >> For some reason the audio in all my Debian VMs has stopped 
> >> working?
> >> AFAIK I haven't done anything other than regular updates. I didn't
> >> notice until recently so I am not sure about exactly when it 
> >> started.
> >> 
> >> In the audio mixer window none of the debian vms are showing up. I
> >> tried plaing something in VLC and it gave the follwoing errors:
> >> 
> >> https://privatebin.net/?f36509f33694a053#821JIyu4z/YqpQ61qGRYFP9Bspo7DAP8HmkPJCAk9Q8=
> >> 
> >> Also,  another strange, maybe unrelated thing happened, I don' 
> >> thave
> >> nautilus in my debian VMs any more and I tried to reinstall then 
> >> but
> >> error saying I had some missing dependencies?
> >>> 
> >>> pulseaudio-qubes is still installed?
> >>> 
> >> 
> >> Must be something with version 11.1-1 of pulseaudio. I've got the same
> >> problem on a Kali VM that has the following pulse packages:
> >> 
> >> $ sudo dpkg -l | grep pulse
> >> ii  gstreamer1.0-pulseaudio:amd64
> >> 1.12.3-1 amd64GStreamer plugin for
> >> PulseAudio
> >> ii  libpulse-mainloop-glib0:amd64
> >> 11.1-1   amd64PulseAudio client
> >> libraries (glib support)
> >> ii  libpulse0:amd64
> >> 11.1-1   amd64PulseAudio client
> >> libraries
> >> ii  libpulse0:i386
> >> 11.1-1   i386 PulseAudio client
> >> libraries
> >> ii  libpulsedsp:amd64
> >> 11.1-1   amd64PulseAudio OSS
> >> pre-load library
> >> ii  pulseaudio
> >> 11.1-1   amd64PulseAudio sound 
> >> server
> >> ii  pulseaudio-utils
> >> 11.1-1   amd64Command line tools 
> >> for
> >> the PulseAudio sound server
> >> 
> >> However on another Debian stretch template audio is normal. The pulse
> >> packages there are:
> >> 
> >> $ sudo dpkg -l | grep pulse
> >> ii  gstreamer1.0-pulseaudio:amd64 1.10.4-1
> >>amd64GStreamer plugin for PulseAudio
> >> ii  libpulse-mainloop-glib0:amd64 10.0-1+deb9u1
> >>amd64PulseAudio client libraries (glib support)
> >> ii  libpulse0:amd64   10.0-1+deb9u1
> >>amd64PulseAudio client libraries
> >> ii  

Re: [qubes-users] Re: Audio in Debian VMs just disappeared?

2017-10-22 Thread yuraeitha
On Sunday, October 22, 2017 at 1:39:39 PM UTC, Stumpy wrote:
> On 19.10.2017 01:59, Stumpy wrote:
> > On 18.10.2017 20:16, qubenix wrote:
> >> Foppe de Haan:
> >>> On Wednesday, October 18, 2017 at 12:38:05 AM UTC+2, Stumpy wrote:
>  hm...
>  
>  Is there something else I can post that would make this easier to 
>  diag?
>  I really really would like to resolve this.
>  
>  On 16.10.2017 02:28, Stumpy wrote:
> > No one?
> > I still haven't figured this one out
> > 
> > in case the private/paste bin was causing no responses here is the
> > output from VLC:
> > from the vlc window:
> > "Audio output failed:
> > The audio device "default" could not be used:
> > No such file or directory."
> > 
> > and from the term that I started vlc from:
> > VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c)
> > [5e890a526938] pulse audio output error: PulseAudio server
> > connection failure: Connection refused
> > [5e890a4410e8] core libvlc: Running vlc with the default
> > interface. Use 'cvlc' to use vlc without interface.
> > ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
> > ALSA lib conf.c:4528:(_snd_config_evaluate) function
> > snd_func_card_driver returned error: No such file or directory
> > Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
> > object file: No such file or directory
> > ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
> > ALSA lib conf.c:4528:(_snd_config_evaluate) function 
> > snd_func_concat
> > returned error: No such file or directory
> > ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
> > ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer
> > returned error: No such file or directory
> > ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such 
> > file
> > or directory
> > ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default
> > [5e890a526938] alsa audio output error: cannot open ALSA device
> > "default": No such file or directory
> > [5e890a526938] core audio output error: module not functional
> > [76de94d7eaa8] core decoder error: failed to create audio 
> > output
> > Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
> > object file: No such file or directory
> > [76de74001268] xcb_xv vout display error: no available XVideo
> > adaptor
> > 
> > anyone?
> > 
> > 
> > On 07.10.2017 23:12, Stumpy wrote:
> >> For some reason the audio in all my Debian VMs has stopped 
> >> working?
> >> AFAIK I haven't done anything other than regular updates. I didn't
> >> notice until recently so I am not sure about exactly when it 
> >> started.
> >> 
> >> In the audio mixer window none of the debian vms are showing up. I
> >> tried plaing something in VLC and it gave the follwoing errors:
> >> 
> >> https://privatebin.net/?f36509f33694a053#821JIyu4z/YqpQ61qGRYFP9Bspo7DAP8HmkPJCAk9Q8=
> >> 
> >> Also,  another strange, maybe unrelated thing happened, I don' 
> >> thave
> >> nautilus in my debian VMs any more and I tried to reinstall then 
> >> but
> >> error saying I had some missing dependencies?
> >>> 
> >>> pulseaudio-qubes is still installed?
> >>> 
> >> 
> >> Must be something with version 11.1-1 of pulseaudio. I've got the same
> >> problem on a Kali VM that has the following pulse packages:
> >> 
> >> $ sudo dpkg -l | grep pulse
> >> ii  gstreamer1.0-pulseaudio:amd64
> >> 1.12.3-1 amd64GStreamer plugin for
> >> PulseAudio
> >> ii  libpulse-mainloop-glib0:amd64
> >> 11.1-1   amd64PulseAudio client
> >> libraries (glib support)
> >> ii  libpulse0:amd64
> >> 11.1-1   amd64PulseAudio client
> >> libraries
> >> ii  libpulse0:i386
> >> 11.1-1   i386 PulseAudio client
> >> libraries
> >> ii  libpulsedsp:amd64
> >> 11.1-1   amd64PulseAudio OSS
> >> pre-load library
> >> ii  pulseaudio
> >> 11.1-1   amd64PulseAudio sound 
> >> server
> >> ii  pulseaudio-utils
> >> 11.1-1   amd64Command line tools 
> >> for
> >> the PulseAudio sound server
> >> 
> >> However on another Debian stretch template audio is normal. The pulse
> >> packages there are:
> >> 
> >> $ sudo dpkg -l | grep pulse
> >> ii  gstreamer1.0-pulseaudio:amd64 1.10.4-1
> >>amd64GStreamer plugin for PulseAudio
> >> ii  libpulse-mainloop-glib0:amd64 10.0-1+deb9u1
> >>amd64PulseAudio client libraries (glib support)
> >> ii  libpulse0:amd64   10.0-1+deb9u1
> >>amd64PulseAudio client libraries
> >> ii  

[qubes-users] Re: qubes 4.0 RC1 networking problems

2017-10-22 Thread Foppe de Haan
On Sunday, October 22, 2017 at 7:27:17 PM UTC+2, Francesco Rmp wrote:
> Hello everyone,
> i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the 3.2 
> to install because of the kernel compatibility).
> 
> The installation went smooth and i can boot fine in the system, but i'm 
> having some networking issues.
> 
> Making the long story short: i cant get any VM to go online.
> 
> I'm no that familiar with the networking in qubes, but i tried to do some 
> troubleshooting myself, and here is what i get.
> 
> - The sys-net VM works fine, it gets the IP from DHCP, gateway, DNS and 
> everything and this is the only VM that goes online. i can ping hosts and 
> communicate with the network. I didn't do anything fency in this VM but using 
> some terminal commads to check i could actually go online, and it works.
> 
> This network fetches the IPs from my DHCP and is set to a 192.168.1.0/24
> 
> - the sys-firewall VM doesn't go online at all. I checked the VM 
> configuration in qubes manager, and according to the configuration, it looks 
> like it's using sys-net as its gateway, but still nothing.
> Curious that when i check in the terminal, it has a network interface with 
> class 10.xxx (i dont' remember exactly) and an additional interface for each 
> appVM that i spin up (this is fine).
> My question is.. how can this VM masquarade any traffic to the sys-net VM if 
> the class of the network interface is completely different and the gateway is 
> actually not set to the sys-net VM ip?
> 
> - As a consequence of the fact that the sys-firewall VM doesn't go online, 
> all the appVMs suffer the same problem.
> 
> Can anyone help me out in troubleshooting this problem?
> Am i right to assume that this is not an hardware problem? considering that 
> the physical network interface assigned to sys-net works fine?
> 
> thanks in advance for your kind reply and support.

try setting debian-8 as your sys-net template.

-- 
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/0e8a4875-2028-480b-9bc2-12f0acd82ef5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] qubes 4.0 RC1 networking problems

2017-10-22 Thread Francesco Rmp
Hello everyone,
i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the 3.2 
to install because of the kernel compatibility).

The installation went smooth and i can boot fine in the system, but i'm having 
some networking issues.

Making the long story short: i cant get any VM to go online.

I'm no that familiar with the networking in qubes, but i tried to do some 
troubleshooting myself, and here is what i get.

- The sys-net VM works fine, it gets the IP from DHCP, gateway, DNS and 
everything and this is the only VM that goes online. i can ping hosts and 
communicate with the network. I didn't do anything fency in this VM but using 
some terminal commads to check i could actually go online, and it works.

This network fetches the IPs from my DHCP and is set to a 192.168.1.0/24

- the sys-firewall VM doesn't go online at all. I checked the VM configuration 
in qubes manager, and according to the configuration, it looks like it's using 
sys-net as its gateway, but still nothing.
Curious that when i check in the terminal, it has a network interface with 
class 10.xxx (i dont' remember exactly) and an additional interface for each 
appVM that i spin up (this is fine).
My question is.. how can this VM masquarade any traffic to the sys-net VM if 
the class of the network interface is completely different and the gateway is 
actually not set to the sys-net VM ip?

- As a consequence of the fact that the sys-firewall VM doesn't go online, all 
the appVMs suffer the same problem.

Can anyone help me out in troubleshooting this problem?
Am i right to assume that this is not an hardware problem? considering that the 
physical network interface assigned to sys-net works fine?

thanks in advance for your kind reply and support.

-- 
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/9f2b71c5-a5ef-42e9-b271-70d51ed43fca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Increasing the number of Dom0 and VM kernels one can have at same time

2017-10-22 Thread daltong defourne
Thanks! 

On Wednesday, October 11, 2017 at 12:22:03 PM UTC+3, Foppe de Haan wrote:
> /etc/dnf/dnf.conf 
> installonly_limit

-- 
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/3b84d1ef-916d-4e10-9208-f9f3b950444d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Audio in Debian VMs just disappeared?

2017-10-22 Thread Stumpy



On 19.10.2017 01:59, Stumpy wrote:

On 18.10.2017 20:16, qubenix wrote:

Foppe de Haan:

On Wednesday, October 18, 2017 at 12:38:05 AM UTC+2, Stumpy wrote:

hm...

Is there something else I can post that would make this easier to 
diag?

I really really would like to resolve this.

On 16.10.2017 02:28, Stumpy wrote:

No one?
I still haven't figured this one out

in case the private/paste bin was causing no responses here is the
output from VLC:
from the vlc window:
"Audio output failed:
The audio device "default" could not be used:
No such file or directory."

and from the term that I started vlc from:
VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c)
[5e890a526938] pulse audio output error: PulseAudio server
connection failure: Connection refused
[5e890a4410e8] core libvlc: Running vlc with the default
interface. Use 'cvlc' to use vlc without interface.
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4528:(_snd_config_evaluate) function
snd_func_card_driver returned error: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
object file: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4528:(_snd_config_evaluate) function 
snd_func_concat

returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer
returned error: No such file or directory
ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such 
file

or directory
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default
[5e890a526938] alsa audio output error: cannot open ALSA device
"default": No such file or directory
[5e890a526938] core audio output error: module not functional
[76de94d7eaa8] core decoder error: failed to create audio 
output

Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
object file: No such file or directory
[76de74001268] xcb_xv vout display error: no available XVideo
adaptor

anyone?


On 07.10.2017 23:12, Stumpy wrote:
For some reason the audio in all my Debian VMs has stopped 
working?

AFAIK I haven't done anything other than regular updates. I didn't
notice until recently so I am not sure about exactly when it 
started.


In the audio mixer window none of the debian vms are showing up. I
tried plaing something in VLC and it gave the follwoing errors:

https://privatebin.net/?f36509f33694a053#821JIyu4z/YqpQ61qGRYFP9Bspo7DAP8HmkPJCAk9Q8=

Also,  another strange, maybe unrelated thing happened, I don' 
thave
nautilus in my debian VMs any more and I tried to reinstall then 
but

error saying I had some missing dependencies?


pulseaudio-qubes is still installed?



Must be something with version 11.1-1 of pulseaudio. I've got the same
problem on a Kali VM that has the following pulse packages:

$ sudo dpkg -l | grep pulse
ii  gstreamer1.0-pulseaudio:amd64
1.12.3-1 amd64GStreamer plugin for
PulseAudio
ii  libpulse-mainloop-glib0:amd64
11.1-1   amd64PulseAudio client
libraries (glib support)
ii  libpulse0:amd64
11.1-1   amd64PulseAudio client
libraries
ii  libpulse0:i386
11.1-1   i386 PulseAudio client
libraries
ii  libpulsedsp:amd64
11.1-1   amd64PulseAudio OSS
pre-load library
ii  pulseaudio
11.1-1   amd64PulseAudio sound 
server

ii  pulseaudio-utils
11.1-1   amd64Command line tools 
for

the PulseAudio sound server

However on another Debian stretch template audio is normal. The pulse
packages there are:

$ sudo dpkg -l | grep pulse
ii  gstreamer1.0-pulseaudio:amd64 1.10.4-1
   amd64GStreamer plugin for PulseAudio
ii  libpulse-mainloop-glib0:amd64 10.0-1+deb9u1
   amd64PulseAudio client libraries (glib support)
ii  libpulse0:amd64   10.0-1+deb9u1
   amd64PulseAudio client libraries
ii  libpulsedsp:amd64 10.0-1+deb9u1
   amd64PulseAudio OSS pre-load library
ii  pulseaudio10.0-1+deb9u1
   amd64PulseAudio sound server
ii  pulseaudio-utils  10.0-1+deb9u1
   amd64Command line tools for the PulseAudio sound server


I am not totally sure about the output but it seems to show up in my 
debAppVMs?:


user@debappvm:~$ dpkg -l | grep pulse
ii  gstreamer1.0-pulseaudio:amd64
1.10.4-1  amd64GStreamer plugin for
PulseAudio
ii  libpulse-mainloop-glib0:amd64
1:1.1-0ubuntu15.4 amd64PulseAudio client
libraries (glib support)
ii  libpulse0:amd64
1:1.1-0ubuntu15.4 amd64PulseAudio client
libraries
ii  libpulsedsp:amd64
1:1.1-0ubuntu15.4 amd64  

[qubes-users] gcc-plugins issue when installing vagrant on qubes

2017-10-22 Thread J.M. Porup
Hi everyone,

I'm following xahare's guide [0] to getting Vagrant running on Qubes.
Specifically, I'm trying to get Varying Vagrant Vagrants [1] running
in Qubes for a data journalism project I'm working on.

The snag I hit comes when installing virtualbox.

According to /var/log/vbox-install.log, the source of the problem
seems to be gcc latent entropy plugin:

cc1: error: cannot load plugin ./scripts/gcc-plugins/latent_entropy_plugin.so

Has anyone else experienced this problem? Can you help me with a
workaround? On deadline.

thanks,
jmp

[0] https://gist.github.com/xahare/0f2078fc8c52e7ddece1e5ba70c6d5fc
[1] https://varyingvagrantvagrants.org/docs/en-US/installation/

-- 
J.M. Porup
www.JMPorup.com

-- 
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/20171022133400.GA915%40fedora-23-dvm.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Problems with restore backup

2017-10-22 Thread BM-2cTRx1tL5LG8CfAuuGi8npSyEKfcjsR3gM
Hi, from a long time I used Qubes OS R3.2. But I wanted install version
R4.0. I maked backup with encryption and save it on my second partition.
After this I installed Qubes OS R4.0 with encrypt my Qubes partition.
After this I run Qubes R4.0 and run command qubes-backup-restore (all this
is on photo) and I tryed restore my VM but I saw problems. But when I
click menu I see all my restored VM.
All is on photos and in log file. What I should do ? I want restore all my
VM and I want know how I could check whether my VM was restored correctly.
Immediately after installation of Qubes OS R4.0 I run update dom0 , even
fedora template and even debiant template I upgraded. After all upgrades I
tried restore backup.

https://imgur.com/a/TZKd9  (photos)
https://0bin.net/paste/Y5heHwSf+y0bNUaE#B2Aj5nWAs6gnL4nPS4Lol0MHWjo8B8F3kALQpsbstFc
  (log)


Sorry for new post but I don't know how to respond in old post if I don't
have Google account.


-- 
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/fcf7a8733529ba249dc37a20f75880e5.squirrel%40bitmessage.ch.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Yubikey in challenge/response mode to unlock LUKS on boot

2017-10-22 Thread __ __
Hello,

sorry for the long delay. Didnt had time to answer.

If some of you is willing to help with testing LUKS-on-LVM could you please
provide the output of the commands below?

sudo su -
. /usr/lib/dracut/modules.d/99base/dracut-lib.sh
getarg rd.ykluks.uuid

If you have not modified your grub config for the ykluks dracut module yet
use this getarg command:
getarg rd.luks.uuid


Regarding the other questions/problems.

2) If you want to unlock the luks device without yubikey you can use the
steps from the "Something went wrong :(" section, skipping step 4. This
should disable the ykluks module and re-enable normal luks handling for one
boot.

3) I do have two notebooks with Qubes 3.2 and yubikey for luks unlock Both
do a re-prompt on wrong password. Can you please describe in detail what
steps could be used to reproduce?

Thanks
the2nd



On Tue, Oct 3, 2017 at 5:11 AM, Ron Hunter-Duvar  wrote:

> On 10/02/2017 08:34 PM, joevio...@gmail.com wrote:
>
>> On Saturday, 5 August 2017 11:20:27 UTC-4, the2nd  wrote:
>>
>>> Hi,
>>>
>>> i switched to Qubes OS 3.2 on my notebook some weeks ago. Besides some
>>> issues i had it works very well.
>>>
>>> One problem was to get the installer to install qubes on LVM-on-LUKS. I
>>> preferred this over the default LUKS-on-LVM setup because you dont have to
>>> encrypt any LV separately.
>>> ...
>>> Please note that the current version will probably not work with a
>>> default qubes LUKS-on-LVM installation. But if some experienced user is
>>> willing to help testing i'll try to come up with a version that supports
>>> this too.
>>>
>>> Besides the yubikey/luks stuff the module handles the
>>> rd.qubes.hide_all_usb stuff via its own rd.ykluks.hide_all_usb command line
>>> parameter because the yubikey is connected via USB and needs to be
>>> accessable until we got the challenge from it. i am still unsure if this is
>>> the best method to implement this. So if anyone with a deeper knowledge of
>>> qubes/dracut does have a better/more secure solution i happy about any help.
>>>
>>> Regards
>>> the2nd
>>>
>> This is working great for me.
>> A few questions though:
>>
>> 1)  The default Qubes 3.2 install seems to be LVM-on-LUKS where there is
>> only one LUKS encryption and root/swap LVMs within that.  So your
>> instructions work with the default install.
>>
>> ...
>>
> I'd have to say that the2nd is right. I didn't notice on my first Qubes
> 3.2 install, because I only had one encrypted partition on my OS drive
> (skipped a swap partition, despite the installer's whining). Second time
> around I gave in and created one.
>
> lsblk shows sda2 with a luks-encrypted / within it, and sda3 with a
> luks-encrypted swap. If it were LVM-on-LUKS, it would be a single
> luks-encrypted partition two logical volumes within it.
>
> Ron
>
> PS: I'm a Qubes-noob, but long-time Linux user.
>
> --
> 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/to
> pic/qubes-users/hB0XaquzBAg/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/ms
> gid/qubes-users/814cee70-0b5c-12a4-ee3e-bdb1f5479f3e%40shaw.ca.
>
> 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/CAA0%2BMPc4-cyKchwsxWwtMdiOqwe_YK3JD_R0YHAOf79i8nisAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Network chain (VPN)

2017-10-22 Thread aaron williams
thank you all for your help


Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sat, Oct 21, 2017 at 11:55 PM, Chris Laprise  wrote:

> On 10/20/2017 03:58 PM, variableap...@gmail.com wrote:
>
>> Hello
>>
>> In this doc https://www.qubes-os.org/doc/vpn/, a configuration is
>> described where app vms connect to the firewall VPN, which connects to the
>> VPN proxy, and finally the net vm.
>>
>> Was this correctly documented as a configuration? Should the VPN proxy
>> sit behind the firewall?
>>
>> Thanks
>>
>
> You should theoretically be able to use VPNVM as a firewall. However,
> there is a bug in qubes-firewall that causes "Deny Except" mode to block
> all DNS traffic when a VPN/tunnel is used. The obvious workaround is to
> create another proxyVM to be placed between appVM and VPNVM.
>
> If you would rather avoid creating an extra proxyVM, you can use a VPN
> project that contains a fix for the DNS bug:
>
> https://github.com/tasket/Qubes-vpn-support
>
>
> Also, in most cases no firewallVM is needed between VPNVM and sys-net, so
> the following chain is OK:
> appVM -> VPNVM -> sys-net
>
> --
>
> Chris Laprise, tas...@posteo.net
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
>
>

-- 
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/CACbN6r3ptd1LuEAQCFTBvvFgDL%2BPK5-LeD1AS4TdiPADA9sEDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL Asrock AB350 Pro4 + Ryzen 5 1600 (Qubes R4)

2017-10-22 Thread mail
Dne sobota 2. září 2017 11:32:04 UTC+2 Foppe de Haan napsal(a):
> works

Hi, works with this gpu card out-of-the-box?

-- 
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/e4ff7d23-fd2c-4e8a-93db-1350daa99947%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.