Re: [qubes-users] 3840x2160 Resolution - How to change: Icon, Windows and Text Sizes?

[Ivan Mitev]

Hi,

On 08/08/2018 11:31 PM, Daniil .Travnikov wrote:
> среда, 1 августа 2018 г., 14:27:14 UTC-4 пользователь Ivan Mitev написал:
>> Hi,
>>
>> On 08/01/2018 07:15 PM, Daniil .Travnikov wrote:
>>> Hi,
>>>
>>> I bought Oryx Pro recently which has 3840x2160 resolution.
>>>
>>>
>>> Do you know how to change in Dom0 Windows, Texts and Icon sizes? Maybe 
>>> existing some software for this options?  Or it could be done in setings 
>>> somwhere?
>>
>> This may help:
>>
>> https://github.com/Qubes-Community/Contents/blob/master/docs/customization/dpi-scaling.md
>>
>>>
>>>
>>> Screenshot of my situation: 
>>> https://drive.google.com/open?id=1V8Yg2nGd5A44laCGwMvAo71kHxb5DCqi
>>>
> 
> It helps in Dom0 and Fedora templates, so thank you very much.
> 
> But what about Debian 9 template? How did you resolve this problem?
> 
> 
> I even tried to change in Debian
> 
> /usr/share/glib-2.0/schemas/org.gnome.desktop.interface.gschema.xml
> 
> "text-scaling-factor" and "scaling-factor"
> 
> and Re-compile the schemas:
> 
> glib-compile-schemas /usr/share/glib-2.0/schemas
> 
> 
> All this instructions from 
> https://mike42.me/blog/2018-02-how-to-use-hidpi-displays-on-debian-9 did not 
> helps too.
> 
> 
> Maybe do you have any recommendations for Debian?

Sorry, I'm not familiar with Debian. I thought that the instructions in
the doc I've linked to would be generic - ie. either you have gnome
settings daemon installed/running, or you don't.
Did you try to change the Xft.dpi X resource ?

If you find a solution for debian, please post it so that I can update
the doc (or if you're familiar with git/github, you could send a pull
request with changes to the doc !).

Cheers,
Ivan

-- 
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/41d957ff-5b29-40e5-49ff-b6246112a3b7%40maa.bz.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 sluggish feel

[cooloutac]

I get this problem sometimes when I update templates,   then restart all the 
vms.  Solution is to reboot the pc.  Only happens to me on 4.0

-- 
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/629de0f1-c2ec-4da6-b82c-d61e5f350706%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 sluggish feel

[Outback Dingo]

On Wednesday, August 8, 2018 at 9:05:54 AM UTC+2, awokd wrote:
> On Wed, August 8, 2018 3:14 am, Outback Dingo wrote:
> > Nothing ??
> > On Tue, Aug 7, 2018 at 1:50 AM Outback Dingo 
> > wrote:
> >
> >>
> >> I dont remeber qubes being so sluggish on a skylake laptop with 64Gb,
> >> qubes is installed on a SSD, however it now seems to take an awful long
> >> time to switch windows, change tabs in firefox and chhrome, launch VMs
> >>
> >> also note that screen rendering, i can actually watch web pages paint,
> >> as though video is being quirly or something, it is an NVIDIA card
> >>
> >> any suggestions, nothing is swapping, memory seems ok, ive even
> >> allocated 8192 mb to 2 vms which i see it in, both fedora and debian,
> >> and i am up to date update wise.
> 
> Sounds similar to this Intel problem:
> https://www.qubes-os.org/doc/intel-igfx-troubleshooting/#software-rendering-or-video-lags.
> Review your logs and see if your video card driver is reporting any errors
> when it loads.


not sure how this would be appplicable its an Nvidia card..

-- 
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/bed2b5ba-0659-4987-ba35-85d59705c0f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - ASUS Z170-P w/ i7-6700k

[zebmccorkle]

All seems to work, incl. nouveau acceleration. VT-d not tested, but enabled and 
detected. No TPM header AFAICT.

-- 
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/371ef5d74103188d8a6a21b5dd87750a%40asymptote.club.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-System_manufacturer-System_Product_Name-20180808-213517.cpio.gz
Description: GNU Zip compressed data


Qubes-HCL-System_manufacturer-System_Product_Name-20180808-213517.yml
Description: Binary data

[qubes-users] Re: newbie question about converting pictures into a trusted image

[smcmj]

I am using 4.0 and it works.

3.2 and 4.0 always created "untrusted" in the name when I converted an 
image...never quite undertood why but I doubt it just you "tirej..." 

-- 
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/ee54df2c-0f56-48f1-b0cb-6178e90b63cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Can't find a guide to setup a new fedora-28 template

[smcmj]

Did you upgrade from Fedora 27 to Fedora 28:
https://www.qubes-os.org/doc/template/fedora/upgrade-27-to-28/ 

Or install a fresh template:
https://www.qubes-os.org/doc/templates/fedora/



-- 
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/79c7a3df-c803-48c1-81d2-31bd4a90d983%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: VM Manager update / VMM setup for AppQube for web or mail only?

[smcmj]

I take a more whitelist/controlled approach with my multiple DVM. With 4.0 you 
can have multiple DVMs and have different DVMs for each domain(This can be 
changed in the "Advanced" tab in the AppVMs in 4.0). Very cool feature...

For example:

I have a DVM setup for printing only, the firewall rules on that DVM are:

Address: Printers wireless IP = 192.168.1.6 (fixed IP in my case)
Service(or port): 515 (Canon) or 9100 (HP) or other ports might be needed 
including 631, 427. Research your printer for whats required...
Protocol: TCP only

For my email IMAP AppVM(In the email AppVM "Firewall" tab):

2 Rules-
Address: 66.11.4.135 (imap.fastmail.com)
Service(or port): 993
Protocol: TCP

Address: 66.11.4.140 (smtp.fastmail.com)
Service(or port): 465
Protocol: TCP

(To be honest I use a different email provider so the IP and ports are 
different but you get the idea. This info as with my own is usually published 
on thesite or available by asking the network admin)

My "Web Surfing" DVM has no firewall rules i.e. "Allow All" which I can also 
print from. This could be tightened up if needed...

I have played with my VPN AppVM as follows(kinda kill switch?):
Address: 168.1.75.17 (IP address to my VPN connection)
Service(or port): 1194
Protocol: TCP

You might have a AdminVM for your router, firewall or switch which could be:
Address: 192.168.4.6
Service(or port): 31006 (I think there are +65000 ports available)
Protocol: TCP

My sys-firewall does not have any restrictions


With this set up, I can:
a) Assign the Print DVM to my Vault and Email AppVM, I think most important for 
email Appvm to prevent a malicious attachment from "calling home" when 
opened(Althoug it could go thru my printer?). 
b) Assign the web surfing DVM to my "untrusted" domain
c) Have a restricted AppVM for Web GUI admin functions

I just take a more strict approach and block ALL then whitelist when 
needed...for me this gives me what I need. Again open to feedback if this is 
wrong...
 

-- 
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/12604ad6-67b4-42ec-90a0-8692337b61fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Question about template VMs, modules, and kernels

[drogo]

On Monday, July 30, 2018 at 5:15:14 PM UTC-4, awokd wrote:
> On Mon, July 30, 2018 8:47 pm, drogo wrote:
> > I've cloned the fedora-28 template to a new one for use with ZFS (just in
> > the template/app VMs).
> >
> > The installation process went OK, but the zfs modules don't load. I
> > noticed that i have several kernels loaded;
> > kernel-core-4.17.7-200.fc28.x86_64 kernel-core-4.17.9-200.fc28.x86_64
> > kernel-core-4.17.4-200.fc28.x86_64
> >
> > But the running kernel is the xen kernel 4.14.41-1.pvops.qubes.x86_64.
> >
> >
> > I tried "dkms autoinstall" and it tried to build for the qubes version,
> > but it error'd out due to missing the 4.14.41-1.pvops kernel-devel source
> > code.
> >
> > Is there a trick to getting dkms to compile modules for that kernel? Or
> > do I have to install the kernel modules in dom0?
> >
> > I would prefer to just build them in the template VM.
> 
> Sounds like you'll need to run HVM. See
> https://www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm-r40
> .

Yep. That seems to have worked. I set the template and appVM to both be HVM, 
ran the grub setup on the template, and now zfs modules load properly.

Thanks!

Thanks!

-- 
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/fa4d5104-8bae-4729-9038-edeb301c54a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] X470 and IOMMU Groups...

[taii...@gmx.com]

I would instead consider the purchase of an owner controlled KCMA-D8 or
KGPE-D16 motherboard which you can install libre board+bmc firmware on.

They support qubes 4.0 very well and all devices have their own IOMMU group.

They are a much better choice than a proprietary firmware PSP laden
non-owner controlled new intel/amd system and are the last and best
owner controlled x86 motherboards...now the only new performance CPU
arch that is owner controlled is POWER such as the TALOS 2 system which
currently doesn't have a xen port although it supports other virts such
as KVM/QEMU.

-- 
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/03915a86-7cbe-344e-05eb-909bad715f90%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] When 4.1? I want Heads - issue #3388 + Rowhammer?

[taii...@gmx.com]

On 08/08/2018 02:18 PM, Andreas Moreiro wrote:
> github.com/QubesOS/qubes-issues/issues/3388
> I hope you guys will fix the issue in 4.1. I would do it myself, but don't
> have experience.
> 
> Has there been any talk of Qubes and the older Rowhammer attack?
> Becase Xen is probably vulnerable:

"Xen" isn't vulnerable this is not a software issue it is a cheap (as in
poor manufacturing standards not price) RAM issue and it only really
effects laptops with high density ram not desktops and servers.

If you want security you can buy a workstation such as the KCMA-D8 or
KGPE-D16 boards that have available libre board/bmc firmware and support
ECC memory which means you are immune to all known rowhammer attacks if
you purchase decent ram (again quality not price)

The above two boards work great with qubes 4.0 and are the last and best
owner controlled x86 boards.

Another option if you aren't using xen/qubes is the TALOS 2 running an
OpenPOWER9 CPU - POWER is now the only owner controlled CPU arch and
what I recommend for new systems. It is arguably more secure to use
POWER with trustworthy open source POWER-KVM virt and set up a virt
environment that mimics the qubes features than have an ME/PSP qubes
system and I very much hope qubes/xen will be ported to POWER soon.

If you want a laptop the best choice is the G505S which is an older
pre-PSP AMD system that supports open source cpu/ram init coreboot[1] -
after the rowhammer issue went public the ram refresh rate was increased
as a patch for rowhammer which makes it much harder to exploit (this is
the same thing the major OEM's did

[1]There are dishonest companies selling new intel "open firmware
coreboot" systems but in reality the hardware init is entirely performed
by the Intel FSP binary blob instead of coreboot and their ME is not
actually disabled (It is impossible to disable ME - the kernel and init
code still run on those "disabled" systems)

> https://www.usenix.org/system/files/conference/usenixsecurity16/sec16_paper_xiao.pdf
> https://www.wired.com/2016/08/new-form-hacking-breaks-ideas-computers-work/
> 
> I belive RAM encryption to be a good 

It isn't.

Don't drink the wintel kool-aid - intel/amd's ram crypto is made for DRM
and DRM only and it is easily defeated by malicious applications.

Both intel/amd's "feature" is yet another ME/PSP application that is not
owner controlled.

-- 
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/b531b2f7-efe3-bf17-a49b-daf167312f47%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] 3840x2160 Resolution - How to change: Icon, Windows and Text Sizes?

[Daniil .Travnikov]

среда, 1 августа 2018 г., 14:27:14 UTC-4 пользователь Ivan Mitev написал:
> Hi,
> 
> On 08/01/2018 07:15 PM, Daniil .Travnikov wrote:
> > Hi,
> > 
> > I bought Oryx Pro recently which has 3840x2160 resolution.
> > 
> > 
> > Do you know how to change in Dom0 Windows, Texts and Icon sizes? Maybe 
> > existing some software for this options?  Or it could be done in setings 
> > somwhere?
> 
> This may help:
> 
> https://github.com/Qubes-Community/Contents/blob/master/docs/customization/dpi-scaling.md
> 
> > 
> > 
> > Screenshot of my situation: 
> > https://drive.google.com/open?id=1V8Yg2nGd5A44laCGwMvAo71kHxb5DCqi
> >

It helps in Dom0 and Fedora templates, so thank you very much.

But what about Debian 9 template? How did you resolve this problem?


I even tried to change in Debian

/usr/share/glib-2.0/schemas/org.gnome.desktop.interface.gschema.xml

"text-scaling-factor" and "scaling-factor"

and Re-compile the schemas:

glib-compile-schemas /usr/share/glib-2.0/schemas


All this instructions from 
https://mike42.me/blog/2018-02-how-to-use-hidpi-displays-on-debian-9 did not 
helps too.


Maybe do you have any recommendations for Debian?

-- 
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/b62be71b-fede-455e-8f2c-7ef42c5b1f13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: VM Manager update / VMM setup for AppQube for web or mail only?

[John S.Recdep]

On 08/04/2018 02:04 PM, smcmj-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org wrote:
> I'll take a shot, also willing to learn more if I am missing something:
> 
> I would try to find the IP of the email provider if you are using a VM for 
> email, e.g. Tutanota's IP address is: 81.3.6.162(no IMAP wit them), therefore 
> my firewall settings for that VM would be:
> 
> IP: 81.3.6.162
> Service: https (or port 443)
> Protocol: TCP
> 
> Things I have learned about the firewall include:
> 1) You can type a port number into the service field vs just using whats in 
> the "Services" dropdown selection
> 2) MXToolbox is a good tool to find an IP address of a website
> 3) I created a print VM that only allows access to my networked printer IP 
> and the network printer's port. With this VM I can access only the printer. 
> Maybe your vault uses this VM as its DVM. I don't trust printers in general 
> but at least its restricted
> 
> For web only 443(https) and 80(http) are all that is needed for the most 
> part. I believe ICMP(pings) and port 53(DNS) are allowed automatically. Open 
> to being corrected? It would be nice to control the DNS more (Quad9 DNS 
> resolver or OpenDNS). Not sure how to do this with ease.
> 
> For Thunderbird, you could research your email providers IP and change the 
> "*"/ANY for the specific IPs or IP.

And what do you use to make it so your Network Printer is all that is
allowed access.

Thats true, as per the Qubes docs on network printers, I cloned the F
Template and installed the printer driver in it, then use it as the
Template for an AppVM that just does printing, but occasional I'll
browse to some URL to print a webpage.  BUT, I also use the AppVM as the
default for disp appvm's to be based on so I can print from attachments
to emails etc ,  and hence,  for the vault, it was also the default...

so did go and change that fwiw :)

PS
AM not using webmail, as primary, so would need more something for IMAP
or ? IMAPS ,  not sure if it is really necessary on top of whatever
sys-firewall does  etc

which is why I was asking what if anything typical qubes users do with
the  firewall tab in the VMM

-- 
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/7dade891-d9fd-778f-3053-d07865abb031%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] When 4.1? I want Heads - issue #3388 + Rowhammer?

[Andreas Moreiro]

github.com/QubesOS/qubes-issues/issues/3388
I hope you guys will fix the issue in 4.1. I would do it myself, but don't
have experience.

Has there been any talk of Qubes and the older Rowhammer attack?
Becase Xen is probably vulnerable:
https://www.usenix.org/system/files/conference/usenixsecurity16/sec16_paper_xiao.pdf
https://www.wired.com/2016/08/new-form-hacking-breaks-ideas-computers-work/

I belive RAM encryption to be a good solution.I could see in the Whonix
forum that there was a xen patch for RAM encryption that as designed for
qubes.
https://www.whonix.org/blog/ram-encryption

Maybe this can help


-- 
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/9e16ccc543181acfb4945fa9391ee3fd.squirrel%40bitmailendavkbec.onion.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Whonix 14 installation stalled

[remarcus via qubes-users]

On Wednesday, August 8, 2018 at 10:42:55 AM UTC-7, rema...@protonmail.com wrote:
> On Wednesday, August 8, 2018 at 10:18:56 AM UTC-7, rema...@protonmail.com 
> wrote:
> > Hey all,
> > 
> > In Qubes 4, after entering sudo qubesctl state.sls qvm.anon-whonix in dom0, 
> > the command is accepted, but nothing happens. I've been waiting for almost 
> > 20 minutes and there's been no output in the terminal. I followed the 
> > Whonix documentation instructions up to this step.
> > 
> > Is there something I need to configure before salt commands will work 
> > properly? Am I just being impatient? Or is there something else that I've 
> > missed?
> 
> Update: I ran sudeo qubes-dom0-update qubes-core-admin-addon-whonix in 
> another terminal window to check I had it installed, and received a new error 
> message:
> 
> *** ERROR while receiving updates: Error while verifing 
> qubes-template-whonix-ws-14-4.0.1-201807171801.noarch.rpm signature: 
> /var/lib/qubes/updates/rpm/qubes-template-whonix-ws-14-4.0.1-201807171801.noarch.rpm:
>  rsa sha1 (MD5) PGP MD5 NOT OK
> 
> Domain sys-firewall sent not signed rpm: 
> qubes-template-whonix-ws-14-4.0.1-201807171801.noarch.rpm --->if you want to 
> use packages that were downloaded correctly, use yum directly now

Double checked the docs so I now know to ignore the signature error. The 
whonix-ws-14 template seems to have installed correctly (not sure if re-doing 
sudo qubes-dom0-update qubes-core-admin-addon-whonix caused this or the salt 
process just took that long to complete), but the gw template hasn't appeared. 

At this point I'm assuming gw will be installed after enough time passes, so 
this bug can probably be diagnosed as user error: impatience, unfamiliarity 
with salt

-- 
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/9103cdd7-4052-4f7e-88bc-0c6060f38e6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Where to add command to turn wifi off

[Chris Laprise]

On 08/08/2018 12:05 PM, trueriver wrote:

Chris's suggestion was not quite right, but near enough for me to get it 
working. This is no reflection on Chris but is down to inconsistent naming 
conventions between different devs on different projects.

Chris said


You can open a terminal in your template and run the following:

sudo touch /var/run/qubes-service/network-manager


up to here is correct, but there are two points with the following line


sudo service network-manager start


Firstly, it tries to do it but suggests we use systemctl instead.

Secondly systectl does not know of a service by this name. I then did a bit of 
searching and it turns out that the correct command is

sudo systemctl start NetworkManager


Yes, I should have mentioned I worked that out on Debian 9. Fedora 
service names are different.



--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
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/cdcb1349-4440-9ef2-5edf-fb566f9145d6%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Fullscreenmode on my Windows HVM/VM

[myblackcatisback]

Hey,

before i had the semless mode installed and now i can make the Window into 
fullscreen. :) 

I try now to make the screen big like the original Qubes window ( That the 
screen have the origina size like the Domain:work )

The configs on my HVM/VM Windows7 is set to 1440*900. When i set up the Display 
higher i not see the Windows button (Where i can make the settings, shut 
down...)

What can i do to solve the probleme? Changes to VGA? 

About help i very happy.

regards


-- 
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/6c2ad4fa-bea1-4cec-b1f8-d9fb7dc7f9d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] I want to use a HVM as a NetVM, cat assign vif+ interface

[Andreas Moreiro]

Qubes dev said in his last post here, that it can not be done in 2014.
https://groups.google.com/d/topic/qubes-users/RFXoZ3zt-PE

I tried it for myself, and I can assign the PCI device, and get an eth0
interface, however I can't assign the virtual interface vif+ to the HVM.

I tried attaching in Dom0 with:
xl network-attach whonix-gw-clone-1
script=/etc/xen/scripts/vif-route-qubes ip=... backend=firewallVM
and got an error:
libx: error:libx.c:2044device_addrm_aocomplete: unable to add device


Tried to start the firewallvm, with the HVM as its netVM, and got these
errors in the log:

libxl_device.c:1081:device_backend_callback: unable to add device with path
libxl_device.c:1512:device_attach_devices: unable to add nic devices
libxl_device.c:1081:device_backend_callback: unable to remove device with
path
libxl.c:1669:devices_destroy_cb: libxl_devices_destroy failed

i used some parts of this tutorial for inspiration:
https://garlicgambit.wordpress.com/2016/04/22/how-to-run-tails-from-a-qubes-live-cd/

Thanks for reading. Any suggestions?


-- 
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/9a91ce8a15b97a6cae4cf0e71d96c181.squirrel%40bitmailendavkbec.onion.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Whonix 14 installation stalled

[remarcus via qubes-users]

On Wednesday, August 8, 2018 at 10:18:56 AM UTC-7, rema...@protonmail.com wrote:
> Hey all,
> 
> In Qubes 4, after entering sudo qubesctl state.sls qvm.anon-whonix in dom0, 
> the command is accepted, but nothing happens. I've been waiting for almost 20 
> minutes and there's been no output in the terminal. I followed the Whonix 
> documentation instructions up to this step.
> 
> Is there something I need to configure before salt commands will work 
> properly? Am I just being impatient? Or is there something else that I've 
> missed?

Update: I ran sudeo qubes-dom0-update qubes-core-admin-addon-whonix in another 
terminal window to check I had it installed, and received a new error message:

*** ERROR while receiving updates: Error while verifing 
qubes-template-whonix-ws-14-4.0.1-201807171801.noarch.rpm signature: 
/var/lib/qubes/updates/rpm/qubes-template-whonix-ws-14-4.0.1-201807171801.noarch.rpm:
 rsa sha1 (MD5) PGP MD5 NOT OK

Domain sys-firewall sent not signed rpm: 
qubes-template-whonix-ws-14-4.0.1-201807171801.noarch.rpm --->if you want to 
use packages that were downloaded correctly, use yum directly now

-- 
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/6190fe33-f96a-42e8-800f-a09a9e2ced28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] yubikey password

[Arnulf Maria Bultmann]

Hello,
I use my yubikey besides other things as a password safe. under windows there 
is no problem to use the yubikey to type in the password into keepass.
Now I want to use the yubikey for thesame procedure under qubes 4.0.
I use a security-vm for keepass and connect the yubikey from sys-usb to 
security-vm. It's no problem to use the personalization gui. but how can I use 
the yubikey in this vm as a kind of usb-keyboard to put the stored password 
into keepass or for example an editor?
thanks in advance for your help
Arnulf

-- 
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/dc6f66f0-17bb-48fc-8c31-923f71e085be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] X470 and IOMMU Groups...

[3mptyy]

Hi everyone,

actually I'm a happy Qubes 3.2 user on Intel platform for more than a year now !

I'm looking to upgrade my actual Skylake build with an AMD one with the new 
Ryzen Pinnacle Ridge CPU (R7 2700) and installing Qubes 4.0 on the same 
occasion. The Asrock X470 Taichi seems a really nice motherboard for it.

I've found the IOMMU Groups of this motherboard on reddit : 
https://www.reddit.com/r/VFIO/comments/8i8yqq/iommu_groups_for_asrock_taichi_x470/

and it seems there's a big group 13 with LAN, USB and SATA controllers. I 
wonder if the netVM and USB VM will actually be able to passthrough these 
controllers if they are in the same IOMMU Group ?

Any Ryzen / Qubes users can confirm this works OK or this is a no go ?

Thanks for your help !

-- 
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/c359faec-ee8a-4709-9c2d-43f77445e647%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Whonix 14 installation stalled

[remarcus via qubes-users]

Hey all,

In Qubes 4, after entering sudo qubesctl state.sls qvm.anon-whonix in dom0, the 
command is accepted, but nothing happens. I've been waiting for almost 20 
minutes and there's been no output in the terminal. I followed the Whonix 
documentation instructions up to this step.

Is there something I need to configure before salt commands will work properly? 
Am I just being impatient? Or is there something else that I've missed?

-- 
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/ad1a81b5-2b03-4d33-97c6-d12ab09ab9fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Where to add command to turn wifi off

[trueriver]

Chris's suggestion was not quite right, but near enough for me to get it 
working. This is no reflection on Chris but is down to inconsistent naming 
conventions between different devs on different projects.

Chris said
> 
> You can open a terminal in your template and run the following:
> 
> sudo touch /var/run/qubes-service/network-manager

up to here is correct, but there are two points with the following line

> sudo service network-manager start

Firstly, it tries to do it but suggests we use systemctl instead.

Secondly systectl does not know of a service by this name. I then did a bit of 
searching and it turns out that the correct command is

sudo systemctl start NetworkManager

The rest all works as advertised.

> nmcli radio wifi off
> 
> Then shutdown the template and restart sys-net. NM should remember the 
> setting you made in the template and start with wifi turned off. It can 
> be turned on by right-clicking the systray icon and enabling the wifi 
> checkbox.
> 

Many thanks Chris for putting me on the right path. 

Comment on Qubes design:

Now I have seen it working I am also impressed with the way that touching that 
file makes it possible to start the service, just once, in the template, and 
the way that that file magically disappears before the template is rebooted. I 
had not realised that some template changes are volatile. As I say I am 
impressed :)

Warmly
River~~

-- 
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/f32ab626-56de-47d5-8696-4b968897748e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Updated HCL report - Dell Precision 5520

[Yassine ILMI]

There was a mistake in the install kernel parameter I shared, instead
of "nouveau.modeset=1"
it should be "nouveau.modeset=0"

On Wed, 8 Aug 2018 at 08:20, Yassine  wrote:

> On Tuesday, 7 August 2018 14:49:33 UTC+1, Jim Snider  wrote:
> > On Monday, May 7, 2018 at 12:03:17 AM UTC-5, Yassine wrote:
> > > On Sunday, 6 May 2018 14:46:32 UTC+1, Yassine  wrote:
> > > > Updating previous report as reinstalling from 4.0-rc3 to 4.0
> > > >
> > > > Needed to edit xen EFI config to remove mapbs/noexitboot keys and
> disable nouveau modesetting (nouveau.modeset=0)
> > >
> > > After install I tested different configuration and was able to get
> discrete gpu hardware support:
> > > - Removed nouveau.modeset=0
> > > - Added kernel param: acpi_osi=!
> > > - Changed iommu support from iommu=no-igfx to iommu=on
> >
> > Yassine
> >
> > I have a Dell Precision 5520 like yours except mine has the Xeon
> E3-1505M v6 processor, so I think your solution should work on my Dell. I
> have not been able to get it to work.
> >
> > Problem : Qubes 4.0 Installer hangs at anaconda screen.
> >
> > I made the install USB using Rufus 3.1 in dd mode. I have tried and
> tried to edit the BOOTX64.cfg on the USB install drive but it is write
> protected and I have not been able to writew changes using several
> different approaches.
> > I booted UEFI,  The results of the install:
> >
> > message :  "Not asking for VNC because we don't have a network"
> > message :  "44.288997 watchdog: BUG: soft lockup - CPU#5 stuck fot 23s!
> [Xorg:1383]
> >
> > I then made a ISO mode install USB using Rufus and edited the
> BOOTX64.cfg as follows:
> >
> > [global]
> > default=qubes-verbose
> >
> > [qubes-check]
> > options=console=none
> > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64
> i915.alpha_support=1 quiet rhgb rd.live.check
> > ramdisk=initrd.img
> >
> > [qubes]
> > options=console=none
> > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64
> i915.alpha_support=1 quiet rhgb
> > ramdisk=initrd.img
> >
> > [qubes-verbose]
> > options=console=vga efi=attr=uc
> > # noexitboot=1
> > # mapbs=1
> > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64
> i915.alpha_support=1
> > ramdisk=initrd.img
> >
> > [qubes-rescue]
> > options=loglvl=all
> > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 rescue
> > ramdisk=initrd.img
> >
> > I booted the ISO USB Legacy, At Blue Qubes screen, Trouble Shooting,
> TAB, added nouveau.modeset=0
> > The results of the install:
> >
> > message :  "Not asking for VNC because we don't have a network"
> > message :  "X starting failed, aborting installation"
> > message :  "The installation cannot continue the system will be
> rebooted   Press ENTER to continue"
> >
> > Yassine,
> >
> > I have searched high and low on the internet and your 5520 / Qubes
> sucess is rare. There is very little discussion of this specific
> combination.
> >
> > If you could Please give me some guidance and edit my BOOTX64 above to
> match yours verbatim, I can try that.
> >
> > Anyone else reading this post that may have suggestions, please add to
> the discussion
> >
> > Thank you so much
>
> Hi Jim,
>
> Try changing the default boot entry to the following:
>
> [qubes-verbose]
> options=console=vga efi=attr=uc
> kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1
> nouveau.modeset=1
> ramdisk=initrd.img
>
> Once you've installed Qubes successfully, try tuning your xen.cfg file
> from dom0 with the following configuration:
>
> [global]
> default=4.14.57-1.pvops.qubes.x86_64
>
> [4.14.57-1.pvops.qubes.x86_64]
> options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=on
> ucode=scan
> kernel=vmlinuz-4.14.57-1.pvops.qubes.x86_64
> root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-some-uuid 
> rd.lvm.lv=qubes_dom0/root
> rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 acpi_osi=! rhgb
> rd.qubes.hide_all_usb
> ramdisk=initramfs-4.14.57-1.pvops.qubes.x86_64.img
>
> Hope this help
>
> Yassine
>
> --
> 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/WMc88pfT-hM/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/75ac78ff-42ef-422f-a3ed-8d9efafa1f26%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 

[qubes-users] Re: standalone HVM installed from ISO: swap disk initialisation

[trueriver]

(later: thinks) or is there a nifty Qubes way to get the virtual disk xvdc 
always initialised to an empty but swap-formatted disk? A kind of swap 
template? That would allow the installed image to run unaltered.

Seems to me this issue must have arisen before?

Equally a windows user could format xvdc and create the virtual memory file on 
it (whose name I forget) and add nothing else. 

Coming back to Linux, AFAIK mkswap only writes 1kB or so to mark the 
disk/partition usuable by swap, and I understand it does this to avert 
embarrasssing mistakes like mounting you OS disk as swap... If this is correct, 
an image of an unused but initialised swap disk would only take up 1k while the 
machine is inactive

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/333f18c3-51b8-45b9-99a7-44ac68e8b9a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] standalone HVM installed from ISO: swap disk initialisation

[trueriver]

hi

I have installed a Debian headless system from iso in an HVM.

Now I am wondering the best way to set up swap. The Debian installer created 
swap for me, but of course this is getting wiped by Qubes between reboots.

This means the VM fails to find its swap disk, and the resulting shortage of 
virtual memory causes it to fail to start MySQL.

My short term fix is to give it 1.8G of swap on the system disk (in fact it 
only uses about 200M so that is overkill)

What is the best place to include a script in systemd startup so that EITHER

- I can run mkswap before fstab is applied

OR

- I can run mkswap and swapon before systemd starts mysql

Is there a standard Qubes way to do this (presumably there is, as the official 
Debian templates must deal with the same issue). If so, please direct me to the 
appropriate doc page. I tried looking but if it is there I missed it.

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/262dcb31-174a-4916-9f73-7bd9e0654a07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Where to add command to turn wifi off

[Chris Laprise]

On 08/08/2018 09:10 AM, trueriver wrote:

What I am actually wanting to do is to alter sys-net so that the wifi does not 
start without my deliberate intervention, regardless of whether it was enabled 
at the most recent shutdown.

This is not to disable it totally, but to ensure that it only starts if I right 
click the widget and tick the enable wifi checkbox.

At present the wifi is enabled on sys-net startup, even when disabled from the 
system tray widget on the previous shutodwm. This is the exact reverse of what 
I want!

I apologise for raising this here (it is more appropriately a NetwrokManager or 
Fedora question) but it arises for me in the context of Qubes.

I have identified the command

nmcli radio wifi off

and am wondering where to insert this command in the start-up sequence. And do 
you recommend it to be in the sys-net Qube /rw space, or in the template (so 
that it actually runs at every startup).

Also, I am wondering if I have missed a config setting for NetworkManager that 
will do this for me. I have pored over the man pages and googled NetwokrManager 
disable but not found an answer. Plenty of ways to disable power management but 
that turns out to be something different.

R~~



You can open a terminal in your template and run the following:

sudo touch /var/run/qubes-service/network-manager
sudo service network-manager start
nmcli radio wifi off

Then shutdown the template and restart sys-net. NM should remember the 
setting you made in the template and start with wifi turned off. It can 
be turned on by right-clicking the systray icon and enabling the wifi 
checkbox.


--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
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/be5e9436-14d0-bbf0-082d-c1f2d46a38b7%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] installing stand-alone from iso: what are the three different disks intended for?

[trueriver]

Thanks

10G seems huge for a swap file for a non-gui system. Can I ask for a smaller 
one? The settings in the advanced Settings tab clearly relate to system and 
user.

Or should I just rely on the fact that it won't grow to its full allocated size 
if it is not used and will disappear anyway between boots.

R~~

On Wednesday, 8 August 2018 07:19:54 UTC+1, awokd  wrote:
> On Mon, August 6, 2018 9:56 pm, trueriver wrote:
> > installing from an iso, creating a new, standalone HVM, I get offered a
> > total of three virtual disks called xvda, xvdb, and xvdc
> >
> > What is the intended use for each of these?
> >
> >
> > If it is system, swap, and user, which disk for which purpose
> 
> xvda, xvdb, xvdc = system, user, swap

-- 
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/b3685b0a-db03-4e0a-9444-3415668a110d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Where to add command to turn wifi off

[trueriver]

What I am actually wanting to do is to alter sys-net so that the wifi does not 
start without my deliberate intervention, regardless of whether it was enabled 
at the most recent shutdown.

This is not to disable it totally, but to ensure that it only starts if I right 
click the widget and tick the enable wifi checkbox.

At present the wifi is enabled on sys-net startup, even when disabled from the 
system tray widget on the previous shutodwm. This is the exact reverse of what 
I want!

I apologise for raising this here (it is more appropriately a NetwrokManager or 
Fedora question) but it arises for me in the context of Qubes.

I have identified the command 

nmcli radio wifi off

and am wondering where to insert this command in the start-up sequence. And do 
you recommend it to be in the sys-net Qube /rw space, or in the template (so 
that it actually runs at every startup).

Also, I am wondering if I have missed a config setting for NetworkManager that 
will do this for me. I have pored over the man pages and googled NetwokrManager 
disable but not found an answer. Plenty of ways to disable power management but 
that turns out to be something different.

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/fbcf0c6d-db7f-4931-b4b7-2b1ebb96dbad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] R4.0 Error in org.qubes.DomainManager1 proxy.get()

[Steve Coleman]

I just did a dom0 update this morning and rebooted. Upon logging in the 
system attempted to start the Qube manager but appears to be having 
issues in connecting to dbus:


python error stack trace

line: 0, timeout_to_glib(timeout), None)
func: get
line no.: 47
file: /usr/lib/python3.5/site-packages/pydbus/proxy.py

line: manager = self.bus.get("org.qubes.DomainManager1")
func: __init__
line no.: 391
file: /usr/lib/python3.5/site-packages/qubesmanager/qube_manager.py

line: manager_window = VmManagerWindow(qt_app, qubes_app)
func: main
line no.: 1332
file: /usr/lib/python3.5/site-packages/qubesmanager/qube_manager.py

line: load_entry_point('qubesmanager==4.0.19', 'console_scripts', 
'qubes-qube-manager')()

func: 
line no.: 9
file: /usr/bin/qubes-qube-manager


lines of code:

Line 391 in qube_manager.py is:

manager = self.bus.get("org.qubes.DomainManager1");

The proxy.get() function died when it received an error here:

ret = self.con.call_sync(
   bus_name, object_path,
   'org.freedesktop.DBus.Introspectable',"Introspect",
   None,GLib.VariantType.new("(s)"),
   0 , timeout_to_glib(timeout), None)


If I am correct the dbus was just added to give the system a realtime 
update when we have state changes? Perhaps I'm missing a package 
dependency, or the dbus service didn't start correctly? Or the 
DomainManager1 does not exist to get its state?


Not sure what to check to get this working.





--
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/fd4274ed-785f-bf4d-00f7-6e362f4f27c8%40jhuapl.edu.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] occasional hangs that stop trackpad and keyboard entry

[trueriver]

Asus laptop UX 360 c. Trackpad, touchscreen, 4G memory (yes I know, that is 
small for Qubes), SSD drive.

I am getting occasional hangups where actions on the keyboard and trackpad are 
ignored. Sometimes this is a few seconds, sometimes longer, very occasionally 
it is a cup of tea job.

One guess as to what is happening is that the trackpad driver in Dom0 gets some 
vital part swapped out, and it is a while before it is swapped back in. To test 
this guess, is there a way I can lock the trackpad driver in real memory?

Another guess is that this is due to an unwanted "takeover" by the unwanted 
touch screen. How can I permanently disable the touch screen in Dom0 to test 
this guess.

IF either guess turns out to be right, it will of course be elevated to have 
been a hypothesis all along ;)

-- 
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/ffc644bb-fee8-431d-8840-6276a7a1bfe6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Android-x86 on Qubes 4

[trueriver]

Rex, you have got further than me with this!

I strongly endorse Olivie's request quoted below.

I am one of the many persons he mentions.

Warmly
R~~

On Wednesday, 8 August 2018 09:41:46 UTC+1, Olivie Médoc  wrote:
> ... 
> Is it possible that you sent brief notes about how you modified the
> android cd in order to make it installable ?
> 
> 
> 
> A lot of persons are apparently digging through this problem and it
> would help a lot.
>...

-- 
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/11471ce7-5c1e-4899-8967-c6893f5bd189%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Has anyone tried to run non-classical OS/nix* on the Qubes 4 machine?

[get]

For example, NixOS/GuixSD/Sabotage/Plan9 and other.
Any guides please?

-- 
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/849357db-0483-40da-a9e6-c83b83abb4e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Android-x86 on Qubes 4

['Olivie Médoc' via qubes-users]

On 08/02/18 15:32, Mat Rex wrote:
> I was able to install android-x86 7.1.2 on Qubes 4.0.
>  
> I created an android-x86 CD with a custom kernel and a change to the
> android init script.

Is it possible that you sent brief notes about how you modified the
android cd in order to make it installable ?

A lot of persons are apparently digging through this problem and it
would help a lot.

There is also a qubes issue related to that:
https://github.com/QubesOS/qubes-issues/issues/2233

This would be greatly appreciated.


>  
> I created a standalone HVM, booted linux from a CD to create ext2
> filesystem and installed legacy grub. [if you have a hard disk drive,
> YMMV. I think old grub and SSD do not like each other via all these VM
> layers, but this is untested - for now I just stick to ext2]
>  
> Booting the android-x86 CD I could install android. I refused to
> convert the filesystem to ext3 or to ext4 when the installer gave the
> option and skipped installing grub from android-x86.
>  
> Booting linux from CD again I updated the grub configuration
> (menu.lst) to boot android-x86.
>  
> After this the android installation can be booted. It has the known
> tablet-mouse issue. I can configure networking from the terminal -
> sometimes. Other times it takes me a lot of repeated entering of
> commands I saw on various forums. I am looking into the best way to
> automate this, will probably need to create a new cd. [this is an AOS
> CD, no google play, no proprietary drivers.]
>  
> However: You cannot attach a microphone or camera to this VM (except
> if you assign the hardware controller to it), so its use is limited.
> The VM does not even shut down, it needs a kill.
>  
> If there is any interest at this early stage, I can provide the CD as
> is or the pointers/patches/configurations how to create it. I hope to
> automate networking configuration in some form in a week or two.

Networking works out of the box in my case. I use an HVM with Android
x86_64 7.1.2 and booting on the live version.

>  
> I am not planing to further deal with the tablet-mouse issue. Using
> the keyboard more and the "mouse" less, you can get by. That should
> not be hard to fix on the qubes side, IMHO. It is not clear yet how
> usb devices can be attached to this VM, but that is something I would
> like solve, but given that on the windows side it has a separate
> maintainer, it might take a while.
> -- 
> 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/5742571533216758%40sas1-38f90f4f25ea.qloud-c.yandex.net
> .
> 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/c1ccd8fd-7dc0-1b51-cabb-1e5d667530e1%40yahoo.fr.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Updated HCL report - Dell Precision 5520

[Yassine]

On Tuesday, 7 August 2018 14:49:33 UTC+1, Jim Snider  wrote:
> On Monday, May 7, 2018 at 12:03:17 AM UTC-5, Yassine wrote:
> > On Sunday, 6 May 2018 14:46:32 UTC+1, Yassine  wrote:
> > > Updating previous report as reinstalling from 4.0-rc3 to 4.0
> > > 
> > > Needed to edit xen EFI config to remove mapbs/noexitboot keys and disable 
> > > nouveau modesetting (nouveau.modeset=0)
> > 
> > After install I tested different configuration and was able to get discrete 
> > gpu hardware support:
> > - Removed nouveau.modeset=0
> > - Added kernel param: acpi_osi=!
> > - Changed iommu support from iommu=no-igfx to iommu=on
> 
> Yassine
> 
> I have a Dell Precision 5520 like yours except mine has the Xeon E3-1505M v6 
> processor, so I think your solution should work on my Dell. I have not been 
> able to get it to work.
> 
> Problem : Qubes 4.0 Installer hangs at anaconda screen.
> 
> I made the install USB using Rufus 3.1 in dd mode. I have tried and tried to 
> edit the BOOTX64.cfg on the USB install drive but it is write protected and I 
> have not been able to writew changes using several different approaches.
> I booted UEFI,  The results of the install:
> 
> message :  "Not asking for VNC because we don't have a network"
> message :  "44.288997 watchdog: BUG: soft lockup - CPU#5 stuck fot 23s! 
> [Xorg:1383]
> 
> I then made a ISO mode install USB using Rufus and edited the BOOTX64.cfg as 
> follows:
> 
> [global]
> default=qubes-verbose
> 
> [qubes-check]
> options=console=none
> kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 
> quiet rhgb rd.live.check
> ramdisk=initrd.img
> 
> [qubes]
> options=console=none
> kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 
> quiet rhgb
> ramdisk=initrd.img
> 
> [qubes-verbose]
> options=console=vga efi=attr=uc 
> # noexitboot=1
> # mapbs=1
> kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1
> ramdisk=initrd.img
> 
> [qubes-rescue]
> options=loglvl=all
> kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 rescue
> ramdisk=initrd.img
> 
> I booted the ISO USB Legacy, At Blue Qubes screen, Trouble Shooting, TAB, 
> added nouveau.modeset=0
> The results of the install:
> 
> message :  "Not asking for VNC because we don't have a network"
> message :  "X starting failed, aborting installation"
> message :  "The installation cannot continue the system will be rebooted   
> Press ENTER to continue"
> 
> Yassine,
> 
> I have searched high and low on the internet and your 5520 / Qubes sucess is 
> rare. There is very little discussion of this specific combination.
> 
> If you could Please give me some guidance and edit my BOOTX64 above to match 
> yours verbatim, I can try that.
> 
> Anyone else reading this post that may have suggestions, please add to the 
> discussion
> 
> Thank you so much

Hi Jim,

Try changing the default boot entry to the following:

[qubes-verbose]
options=console=vga efi=attr=uc
kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 
nouveau.modeset=1
ramdisk=initrd.img

Once you've installed Qubes successfully, try tuning your xen.cfg file from 
dom0 with the following configuration:

[global]
default=4.14.57-1.pvops.qubes.x86_64

[4.14.57-1.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=on ucode=scan
kernel=vmlinuz-4.14.57-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root 
rd.luks.uuid=luks-some-uuid rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap 
i915.alpha_support=1 acpi_osi=! rhgb rd.qubes.hide_all_usb
ramdisk=initramfs-4.14.57-1.pvops.qubes.x86_64.img

Hope this help

Yassine

-- 
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/75ac78ff-42ef-422f-a3ed-8d9efafa1f26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Updated HCL report - Dell Precision 5520

['awokd' via qubes-users]

On Tue, August 7, 2018 1:49 pm, jim.h.sni...@gmail.com wrote:

Can you disable the nvidia in your UEFI config? Try that first if so.

> I booted the ISO USB Legacy, At Blue Qubes screen, Trouble Shooting, TAB,
> added nouveau.modeset=0 The results of the install:
>
>
> message :  "Not asking for VNC because we don't have a network" message :
> "X starting failed, aborting installation"
> message :  "The installation cannot continue the system will be rebooted
> Press ENTER to continue"

At this point in the install, can you ctrl-C that and get to a prompt? Or
try ctrl-alt-F1 through ctrl-alt-F10 (not sure which is the right one). If
you can get to a prompt, check the install logs in /var/log and see if you
can figure out what's causing X to fail (probably some issue loading the
video driver).


-- 
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/17427691f0374a8c1dcf229b467d0293.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 sluggish feel

['awokd' via qubes-users]

On Wed, August 8, 2018 3:14 am, Outback Dingo wrote:
> Nothing ??
> On Tue, Aug 7, 2018 at 1:50 AM Outback Dingo 
> wrote:
>
>>
>> I dont remeber qubes being so sluggish on a skylake laptop with 64Gb,
>> qubes is installed on a SSD, however it now seems to take an awful long
>> time to switch windows, change tabs in firefox and chhrome, launch VMs
>>
>> also note that screen rendering, i can actually watch web pages paint,
>> as though video is being quirly or something, it is an NVIDIA card
>>
>> any suggestions, nothing is swapping, memory seems ok, ive even
>> allocated 8192 mb to 2 vms which i see it in, both fedora and debian,
>> and i am up to date update wise.

Sounds similar to this Intel problem:
https://www.qubes-os.org/doc/intel-igfx-troubleshooting/#software-rendering-or-video-lags.
Review your logs and see if your video card driver is reporting any errors
when it loads.


-- 
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/5a859ee2d1173096514736e8068f443d.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] MSI-x support in domU

['awokd' via qubes-users]

On Tue, August 7, 2018 10:41 pm, perme...@gmail.com wrote:
> I have a Mellanox 10G adapter in my Qubes box.
> When I spin up a domU with the device passed-thru, I am unable to load the
> device driver due to what appears to be a lack of support for MSI-x
> interrupt mapping.
>
> There was some chatter a while back regarding MSI support:
>
>
> https://www.google.com/url?q=https%3A%2F%2Fwww.qubes-os.org%2Fnews%2F2017
> %2F10%2F18%2Fmsi-support%2F=D=1=AFQjCNGXTUp6QSX9Fb0v5Q6hyVc0i
> 6NwfQ
>
>
> One might hope that this would enable MSI-x support as well, but
> apparently, not.  My guess is that someone added a kluge to permit
> writing to the MSI enable regions in PCI config space for a device,
> neglecting to add the kluges for MSI-x as well.
>
> I find that I need to flag the mellanox as 'permissive' or else I get
> errors flagged on the dom0 console log regarding attempts to write to PCI
> config space.  Once I do so, I am still unable to load the device driver
> for the ConnectX 4-LX device (mlx5_core).  It fails when it attempts to
> allocate the set of MSIX vectors sized based on the # of CPUs online.
>
> The driver assumes MSIx are available.  No fall-back to MSI.  No
> fall-back to INT A/ INT B.
>
> Are there some other magic knobs I need to tweak?
>
>
>
> MSIx and Xen does raise some interesting issues.  I would like to have to
> option of spinning up a domU with, say, 20 VCPU and, knowing that the
> Mellanox will assign queues to MSIx and I can assign MSIx to CPUs, I
> would like to have dom0 bind the vCPU to real CPU so that the interrupt
> mapping works correctly.  This would be for some network performance work
> I have to do occasionally.
>
>
> I am also keen to enable the VF devices in the adapter (using  some domU
> instance to enable) so that these VF instances can be passed to other
> domU instances.   Also want to see if I can get hardware offload working
> and OVS working in qubes.  Just for fun.
>
> Q: if a domU kernel enables VF devices in a mapped PF device instance,
> will the dom0 kernel discover the VF devices?  IE: what is the mechanism
> whereby a kernel discovers the need for a bus-walk? This has to work
> correctly for Xen, no?

I had somewhat similar weirdness with an old Atheros AR9280- see
https://github.com/QubesOS/qubes-issues/issues/3609. It initialized
properly in a stock Xen HVM, but the driver would crash on a Qubes HVM.
Never did manage to figure it out. Mine could have been memory mapping
related, though.

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

Re: [qubes-users] installing stand-alone from iso: what are the three different disks intended for?

['awokd' via qubes-users]

On Mon, August 6, 2018 9:56 pm, trueriver wrote:
> installing from an iso, creating a new, standalone HVM, I get offered a
> total of three virtual disks called xvda, xvdb, and xvdc
>
> What is the intended use for each of these?
>
>
> If it is system, swap, and user, which disk for which purpose

xvda, xvdb, xvdc = system, user, swap


-- 
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/8b9bd59832c5c9d100091b86f6556d12.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: installing a CLI-only standalone VM. Possible? How?

['awokd' via qubes-users]

On Mon, August 6, 2018 9:52 pm, trueriver wrote:
> I have made some progress - don't know what I am doing differently but
> now the console appears without effort when I boot

Often I check the "debug" box when doing installs to help see the console
immediately.


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

Re: [qubes-users] qubes clipboard mangles text character (emdash)

['awokd' via qubes-users]

On Mon, August 6, 2018 7:45 pm, Ryan Tate wrote:
> When pasting text through the Qubes Clipboard, I noticed the emdash
> character (—) is silently removed.
>
> Reproduction:
>
>
> Copy this text, paste it elsewhere in SAME AppVM (so no Qubes Clipboard
> involvement): One — two three.
>
>
> It should paste fine.
>
>
> Copy the same text to the Qubes Clipboard (Control-C Control-Shift-C),
> paste into same program in DIFFERENT AppVM with Control-Shift-V
> Control-V.
>
>
> Expected: Text is same
>
>
> Seen: Text is mangled, no more "—".
>
>
> Now, Joanna of the Qubes team has written that Qubes only uses the
> passive X11 clipboard with no "rich text"
> (https://groups.google.com/forum/#!msg/qubes-devel/fgjEKCOnM7E/zciO65Vm_l
> cJ). But this is still just plain text, albeit utf-8, it should work fine
> in passive mode. From what I can tell googling around, X11 clipboard
> supports utf8/Unicode so even if emdash is non ASCII shouldn't it still
> be supported? Is there some security risk to pasting unicode text, or is
> this a bug?
>
> Thanks for any insights.

Can confirm the behaviour but afraid no insights here. Could maybe try
asking on qubes-devel or just submitting as an issue?


-- 
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/35bdad5b4041f0dea55932036f6a4dfc.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: off topic - invite codes to 'riseup'

[sucarogates]

can you give me one too please thank you. my email is sucaroga...@gmail.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/e43796b6-c330-4100-a757-d731bddadb3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.