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

2017-10-17 Thread 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?

-- 
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/152d197e-be50-49f6-84db-f40ec8e495ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-10-17 Thread Stumpy 

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?


--
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/14e4b48e9a893c405425bbc162930a49%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Connect to the AppVM with VNC using Xen capabilities

2017-10-17 Thread msgheap 
On Monday, October 16, 2017 at 8:52:14 AM UTC-4, msg...@gmail.com wrote:
> воскресенье, 15 октября 2017 г., 1:46:40 UTC-4 пользователь msg...@gmail.com 
> написал:
> > Hello.
> > 
> > I want to connect to one of my AppVMs with VNC from remote host using Xen 
> > capabilities.
> > I wanted to do it with the custom Xen config, but I can't figure out how to 
> > change the default Xen config or use custom Xen config to start my AppVM. I 
> > think it was possible in Qubes OS 3.2 with "qvm-start 
> > –custom-config=CUSTOM_CONFIG", but I've installed Qubes OS 4.0 
> > (current-testing) and there is no such option now.
> > I've found the location of the Xen configs used for VMs in 
> > /etc/libvirt/libxl/vmname.xml and tried to change the graphics type 
> > parameter from 'qubes' to 'vnc' in my AppVM config with virsh and then 
> > start the AppVM, but the Xen config keep reverting back to its original 
> > state after I start AppVM. Is it hardcoded for Qubes OS to overwrite this 
> > file every time when I start VM?
> > How can I enable vnc in Xen config for Qubes OS VM?
> > Rdp/x11vnc and other services that can be installed in the quest OS are not 
> > an options, because I need to access the VM even if the network is broken 
> > in the VM.
> 
> I've found the way to do it in this document:
> https://github.com/QubesOS/qubes-core-admin/blob/master/doc/libvirt.rst
> It works fine.
> 
> Also, there was an error in this libvirt.rst document, it states that it 
> looks for the files:`/etc/qubes/templates/libvirt/by-name/.xml` but it 
> actually looks for 
> files:`/etc/qubes/templates/libvirt/xen/by-name/.xml` in the source 
> code:
> https://github.com/QubesOS/qubes-core-admin/blob/master/qubes/vm/__init__.py

I can change the Xen config, but I can't figure out how to make VNC work 
properly.
With the default HVM, the Qubes OS will configure Xen to use device model stub 
domain for the devices (), including the 
. So the VNC server will be started for the stub domain.
When I try to connect to the VNC server from dom0 I can see this message:
"Guest has not initialized the display (yet)"
https://i.stack.imgur.com/D5HsM.png
VNC client connects to the vmname-dm VM.
When I searched for this problem, I've found this config, suggesting that VNC 
should work with stub domain emulator (but it's not certain):
https://www.mail-archive.com/libvirt-users@redhat.com/msg00118.html
There is also example Xen config for stub domain with VNC that seems to work:
https://wiki.xenproject.org/wiki/StubDom
But there are two separate configs: for HVM and HVM-dm, but in my case there is 
singe libvirt config and I don't know how to use these example configs for my 
case.
Can someone suggest how to fix this issue? Is it just wrong libvirt config or 
does Qubes OS somehow interfere with video/graphics/something else that is 
breaking VNC.

-- 
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/ae49dab1-dcf0-46dc-a190-a7b1a3b59654%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Screen blanks instead of power off

2017-10-17 Thread Roy Bernat 
On Saturday, 12 November 2016 18:31:05 UTC-5, tai...@gmx.com  wrote:
> I have tried all the options in the power control menu but my screen 
> still doesn't turn off it just disconnects the output so the screen will 
> say "NO VGA/DVI DETECTED" when power save mode turns on.
> 
> Ideas?

same problem   ideas ?

-- 
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/feaf6406-67ed-49cf-9236-1d70ef309de7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] qubes 4 rc1 start appvm & error boot sys-net and sys-firewall

2017-10-17 Thread Roy Bernat 
pressing the appVm for example on firefox seems that the vm is started but 
after couple of minutes its disappear.when i check qvm-ls it halted . 

only when i start the machine with qvm start  vmname it started ok . 

further more i can see now that on boot the sys-net and the sys-firewall gets 
an error while trying to boot . 

roy 

-- 
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/71c7309b-cd10-4a13-b3fe-b11bbd785f18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO - Potential fix for GUI sluggishness

2017-10-17 Thread Yethal 
W dniu wtorek, 17 października 2017 20:26:29 UTC+2 użytkownik Roy Bernat 
napisał:
> On Sunday, 15 October 2017 05:58:03 UTC-4, Yethal  wrote:
> > I reported the issue yesterday but more people browse the mailing group 
> > than the qubes-issues repo so I'll repost this here. Hopefully it'll help 
> > someone.
> > 
> > (On my PC at least) the AppVMs internally use 24hz screen refresh rate 
> > instead of my monitor native 60hz which caused the GUI to be very 
> > unresponsive, sluggish and to tear like crazy. In order to fix that:
> > 
> > 1. Launch terminal in TemplateVM on which your AppVMs depend
> > 2. Open /etc/X11/xorg-qubes.conf in test editor
> > 3. Scroll to the VertRefresh parameter
> > 4. Change 23-24 to 59-60 (or higher if your display supports it)
> > 5. Save changes
> > 6. Shutdown TemplateVM
> > 7. Restart AppVMs based on that TemplateVM
> > 8. Repeat for all other TemaplteVMs
> > 9. Enjoy buttersmooth GUI
> > 
> > Github issue:
> > https://github.com/QubesOS/qubes-issues/issues/3175
> 
> can you point me to this script ?

/usr/bin/qubes-run-xorg.sh

-- 
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/de15597d-a669-40ec-ae7e-6f334407ac48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: HOWTO - Potential fix for GUI sluggishness

2017-10-17 Thread donoban 
On 10/17/2017 09:23 AM, Roy Bernat wrote:
> tried your solution on template vm .  the changes are not saved .
> 
> any suggestion ? 
> 
> R
> 

Same 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/f1c3c66b-74db-3115-b8a7-738a8f759590%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO - Potential fix for GUI sluggishness

2017-10-17 Thread Roy Bernat 
On Sunday, 15 October 2017 05:58:03 UTC-4, Yethal  wrote:
> I reported the issue yesterday but more people browse the mailing group than 
> the qubes-issues repo so I'll repost this here. Hopefully it'll help someone.
> 
> (On my PC at least) the AppVMs internally use 24hz screen refresh rate 
> instead of my monitor native 60hz which caused the GUI to be very 
> unresponsive, sluggish and to tear like crazy. In order to fix that:
> 
> 1. Launch terminal in TemplateVM on which your AppVMs depend
> 2. Open /etc/X11/xorg-qubes.conf in test editor
> 3. Scroll to the VertRefresh parameter
> 4. Change 23-24 to 59-60 (or higher if your display supports it)
> 5. Save changes
> 6. Shutdown TemplateVM
> 7. Restart AppVMs based on that TemplateVM
> 8. Repeat for all other TemaplteVMs
> 9. Enjoy buttersmooth GUI
> 
> Github issue:
> https://github.com/QubesOS/qubes-issues/issues/3175

can you point me to this script ?

-- 
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/bf234a2e-deab-4404-a093-e5ad2f277b60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO - Potential fix for GUI sluggishness

2017-10-17 Thread Yethal 
W dniu wtorek, 17 października 2017 09:23:08 UTC+2 użytkownik Roy Bernat 
napisał:
> On Sunday, 15 October 2017 05:58:03 UTC-4, Yethal  wrote:
> > I reported the issue yesterday but more people browse the mailing group 
> > than the qubes-issues repo so I'll repost this here. Hopefully it'll help 
> > someone.
> > 
> > (On my PC at least) the AppVMs internally use 24hz screen refresh rate 
> > instead of my monitor native 60hz which caused the GUI to be very 
> > unresponsive, sluggish and to tear like crazy. In order to fix that:
> > 
> > 1. Launch terminal in TemplateVM on which your AppVMs depend
> > 2. Open /etc/X11/xorg-qubes.conf in test editor
> > 3. Scroll to the VertRefresh parameter
> > 4. Change 23-24 to 59-60 (or higher if your display supports it)
> > 5. Save changes
> > 6. Shutdown TemplateVM
> > 7. Restart AppVMs based on that TemplateVM
> > 8. Repeat for all other TemaplteVMs
> > 9. Enjoy buttersmooth GUI
> > 
> > Github issue:
> > https://github.com/QubesOS/qubes-issues/issues/3175
> 
> Hi 
> 
> tried your solution on template vm .  the changes are not saved .
> 
> any suggestion ? 
> 
> R

Yeah, later I found out that the file is reconstructed from a template by 
qubes-run-xorg script. Until this is permanently fixed you may want to try 
editing the script so that it always echoes correct value. This is a workaround 
until a permanent solution is developed.

-- 
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/9a469497-ff7f-4a9c-a85f-4de1984f464f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] iommu=no-igfx

2017-10-17 Thread Roy Bernat 
On Tuesday, 17 October 2017 11:01:04 UTC-4, David Hobach  wrote:
> > i have dell xps 9360 ( kaby lake i7 intel 620 )
> > 
> > when i installed qubes after installation the qubes didnt succeeded to 
> > start .
> > 
> > work around that worked was to remove from grub the iommu=no-igfx  and 
> > after this
> > 
> > everything went well .   is there an issue to add this option ?
> 
> No, it should even be more secure that way. Apparently the Qubes devs 
> only added it due to some problems without it (which you don't seem to 
> have). There's a related bug @qubes-issues.

But when i add this the computer cant load qubes .  It restart the machine . 

-- 
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/d0a72582-bcf2-41b2-8858-c26b283cc93c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] BIOS did not enable IDB for VT properly. - TUXEDO InfinityBook Pro 13

2017-10-17 Thread Patrick Schleizer 
Qubes R4 RC1 with TUXEDO InfinityBook Pro 13 [1]. Xen crashes. Boot aborts.

> BIOS did not enable IDB for VT properly. crash Xen for security purposes

Did anyone see this error ever before? Any idea how to fix it?

Cheers,
Patrick

[1]
https://www.tuxedocomputers.com/Linux-Hardware/Linux-Notebooks/10-14-Zoll/TUXEDO-InfinityBook-Pro-13-matt-Full-HD-IPS-Aluminiumgehaeuse-Intel-Core-i7-U-CPU-bis-32GB-RAM-zwei-HDD/SSD-bis-12h-Akku-Typ-C-Thunderbolt.geek

-- 
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/0f69a6fe-6478-8f58-fe51-8d9f3f4ce5f5%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes Live Images

2017-10-17 Thread Michael Carbone 
On 10/16/2017 06:32 PM, Unman wrote:
> I had some enforced spare time last week and dusted off some old Live
> images for r3.2. They need tidying up but are usable now.
> 
> There are two iso images, suitable for burning to DVD or USB.
> Both use Debian templates.
> The smaller (2GB) is pretty vanilla, with some additional non-free
> drivers for wifi adapters.
> The larger (2.4GB) has a TorVM, and Tor Browser in an online qube.
> There are restrictive iptables on sys-net and TorVM, and MAC spoofing
> set on sys-net. The offline qube has libre office and veracrypt
> installed.
> 
> The menu system is simple, and wont update if you create new qubes.
> You'll need to use 'qvm-run -a  ', or practice working with
> the mysteries of xdg menus.
> 
> Both images will run(sort of) in 4GB RAM - 8 is better.
> 
> If you use DVD then get used to the sound of the disc thrashing. The
> faster DVD drive you have the better. (That said they work reasonably well
> on an old MacBook with 8GB RAM.) You also need patience - generally it
> seems better to start new qubes discretely.
> 
> Running from USB is fine. If you have ample RAM you'll forget it's a
> live system, unless you hammer the (limited) free disk space.
> 
> Both images are available from http://qubes.3isec.org - hashes and
> signatures to check included.
> 
> I hope to have updated versions ready for 4.0-rc2, along with a tidy build
> system, and (maybe) an installer.
> 
> Cheers
> 
> unman

hi unman,

this is really great, thanks for all your efforts! I've updated the
associated ticket with your email:

https://github.com/QubesOS/qubes-issues/issues/1552#issuecomment-337277453

and the more general live image ticket:

https://github.com/QubesOS/qubes-issues/issues/1018

there's also a ticket on documenting how to create live images for
developers, which you seem to have navigated:

https://github.com/QubesOS/qubes-issues/issues/1970

once Marek has had a chance to check it out it would be good to move it
over to the downloads page.

I also like your work on the QubesTor iso, moves us a bit towards
Tails-like functionality:

https://github.com/QubesOS/qubes-issues/issues/2024

-- 
Michael Carbone

Qubes OS | https://www.qubes-os.org
@QubesOS 

PGP fingerprint: D3D8 BEBF ECE8 91AC 46A7 30DE 63FC 4D26 84A7 33B4



-- 
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/b7228cdb-8bac-0daf-0e03-efa8d84e2483%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] VMWare machine on Qubes

2017-10-17 Thread Alejandro Berlanga 
El lunes, 16 de octubre de 2017, 18:43:09 (UTC-4), Unman  escribió:
> On Mon, Oct 16, 2017 at 01:57:50PM -0700, Alejandro Berlanga wrote:
> > Hello everyone,
> > 
> > FIrst of all I am very noob to Qubes. And my problem is that I have a vm 
> > machine created for vmware and I was hoping if there is a way to install it 
> > on Qubes?
> > 
> > P.D. If you need more info tell me please!!
> > 
> > Thank You
> > 
> 
> You can convert the disk to raw format and then try to use it in a qube.
> Something like 'qvm-img convert -S -O raw  '
> Then configure a new qube and use the new raw img as root.img
> The chances of this working are dependent on what OS is involved - some
> wont boot given a substantial hardware change, some may require
> relicensing.
> 
> hth
> 
> unman

Thanks for the answer and the machine has a fedora 24 OS I think.

-- 
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/c08233a9-85d6-4b67-94e1-e46343b6d16b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] iommu=no-igfx

2017-10-17 Thread David Hobach 

i have dell xps 9360 ( kaby lake i7 intel 620 )

when i installed qubes after installation the qubes didnt succeeded to start .

work around that worked was to remove from grub the iommu=no-igfx  and after 
this

everything went well .   is there an issue to add this option ?


No, it should even be more secure that way. Apparently the Qubes devs 
only added it due to some problems without it (which you don't seem to 
have). There's a related bug @qubes-issues.


--
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/bbad6eea-c94e-ee18-8b05-579211e02cef%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature

[qubes-users] iommu=no-igfx

2017-10-17 Thread Roy Bernat 
Hi 

i have dell xps 9360 ( kaby lake i7 intel 620 ) 

when i installed qubes after installation the qubes didnt succeeded to start . 

work around that worked was to remove from grub the iommu=no-igfx  and after 
this 

everything went well .   is there an issue to add this option ? 

i have qubes 4 rc1 ( latest testing repo kernel 4.9.54-21 .

R

-- 
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/55260f3d-5447-40ed-986f-6f33bb405c30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HOWTO - Potential fix for GUI sluggishness

2017-10-17 Thread Roy Bernat 
On Sunday, 15 October 2017 05:58:03 UTC-4, Yethal  wrote:
> I reported the issue yesterday but more people browse the mailing group than 
> the qubes-issues repo so I'll repost this here. Hopefully it'll help someone.
> 
> (On my PC at least) the AppVMs internally use 24hz screen refresh rate 
> instead of my monitor native 60hz which caused the GUI to be very 
> unresponsive, sluggish and to tear like crazy. In order to fix that:
> 
> 1. Launch terminal in TemplateVM on which your AppVMs depend
> 2. Open /etc/X11/xorg-qubes.conf in test editor
> 3. Scroll to the VertRefresh parameter
> 4. Change 23-24 to 59-60 (or higher if your display supports it)
> 5. Save changes
> 6. Shutdown TemplateVM
> 7. Restart AppVMs based on that TemplateVM
> 8. Repeat for all other TemaplteVMs
> 9. Enjoy buttersmooth GUI
> 
> Github issue:
> https://github.com/QubesOS/qubes-issues/issues/3175

Hi 

tried your solution on template vm .  the changes are not saved .

any suggestion ? 

R

-- 
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/61c46c93-a3de-46ec-a8ed-6e27800f9f4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Re: Idea for (resonable secure) cloud-storage usage with Qubes

2017-10-17 Thread '[799]' via qubes-users 
Hello Ron,

Thank you for the feedback.

> Have you considered using SSHFS rather than
> NFS? I'm no security expert, but it would
> seem to me to be more secure than NFS.

Actually yes, I thought about it after other mentioned that enabling NFS would 
offer another attack window.
Even when I am unsure as I have but some encryption and firewall restrictions 
in place.
The Access VM is the only one connected to the internet and the NFS 
Storage VM.
The other AppVMs who will connect to the storage VM don't have an online 
connection.
>From my understanding an attacker must come through the Access VM and 
>then attack the Storage VM.

Unfortunately I don't how those attacks take place and how much time is 
necessary. It could be possible to launch the access VM only 
periodically just to sync the data.
Keep in mind, that all data is encrypted from the view of the access+transfer 
VM.

I'd like to setup firewall rules, which will only allow traffic from the 
access+transfer VM to the cloud storage provider, but this need some further 
investigation.
As far as I understand Qubes Firewall GUI will not work with domain names but 
with IPs.

Regarding sshfs I will give it a try, as ssh is used to connect remotly I am 
(reasonable) sure that it has less attack possibilities than NFS.

Even when enabling inter-VM networking I feel more secure when I can keep my 
data encrypted+synced and have the data access separated in different VMs.

[799]

-- 
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/_HKrGSpPkv_IGVU_nDSatjZ4QDQ6hwh-gT4QSoB4PQBtS3JIYwjXXpKVyGXELcaiaBLgo1y39vRZtqjP9gQYalHxJ0pLn2IHdrDe088ZrDQ%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.