date:20180107


On 01/07/2018 12:49 PM, Samupaha wrote:


How difficult it is to get Qubes to boot from NVMe drive in KGPE-D16? I'm 
thinking about buying it and I'd like to have NVMe drive for the OS. But I have 
very limited experience with coreboot/BIOS stuff, so hopefully I don't need to 
spend several days fighting to get it work.

Very easy - same as a regular drive as both grub and SeaBIOS support 
nvme devices. I do not know anything about the vendor bios and NVME but 
it will definitely work via coreboot.


Get the board while you still can as soon they will stop making them :[

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3446b79b-31e4-3184-afb6-396afd0a54c2%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] qubes 4 qvm-trim not exist

2018-01-07 Thread Roy Bernat

Hi All , 

What is the best practice to trim disk inside qubes 4 . 

the qvm-trim-template dont exist anymore . 

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/25ba890a-40d0-471b-96e3-568e3e4be059%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Intel ME Backdoor, called Odin's Eye

2018-01-07 Thread haaber

> воскресенье, 7 января 2018 г., 18:14:26 UTC пользователь haaber написал:
>>> https://i.redditmedia.com/5mA7LrMiwgmmhrwfYF8Jks0WEng66fxWoCcGw33dhCA.jpg?w=597=339d919645f1de31a42913c748d1d7fb
>>>
>>>
>>> Summary:
>>>
>>> Intel Whistleblower leaks details about his role in backdooring all IME 
>>> chips on behalf of Intelligence Agencies. 
>> The post is unspecific. Of course ME is a problem: the allegations could
>> be true or could be disinformation. "I know exactly" is an unplausible
>> formulation for a backdooring engineer - it is almost surely a wrong ot
>> statement if it was not himself who spied ...  To conclude: unless some
>> details are given to enhance trustworthyness (a specific backdoor,
>> protocol, communication interface, whatsoever), I personally consider
>> this troll post.
> 
> Sorry but you haven't seen the full story. This "Intel guy" is legit, he 
> provided proofs like this one:
> 
> https://i.warosu.org/data/g/img/0595/40/1490327898699.png
Maybe, maybe not. Who can verify scanned and blacked papers? I would
appreciate him helping me to remove it from my mainboard though! How to
do THIS is the right discussion to my pov.

-- 
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/506eac1a-d270-e5aa-ab72-27088ddd7fea%40web.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes 4 qvm-trim not exist

2018-01-07 Thread Andrew David Wong

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-01-07 12:48, Roy Bernat wrote:
> Hi All ,
> 
> What is the best practice to trim disk inside qubes 4 .
> 
> the qvm-trim-template dont exist anymore .
> 
> R
> 

You can use the `fstrim` command in the TemplateVM:

$ sudo fstrim -v /

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpSg2AACgkQ203TvDlQ
MDAlIQ//dJsCrtqcQ5iOWiZd2iDmhGv/SlE0R4omxq8W6d4kUGJfhZ2mLbedoRBs
9nz4AqnQhfdOy8HLoYtAKXosO8dbEkZDDkQO6lTua0nUnrEEOar9r8QBuNWq8Ihe
VQ97sIFAvxJ0Q4LAwiTjfp+8ciFcyzAbDOePsf+z9wGGanQuNxtGAep8FZkE8EWl
7LnA+9Kl4F24BwdsYLEVIlKhtcitHoGmn3vVzE/yZ7Ouyuzt4tNj3jkwh1n6KNT6
aqiBIVsD/bqfaDANwxZyQxOPtigW63gm4t4EZZeVarjWNo1OsmFyuRJk+s6gIB5b
4Zez8QZgKiVwi/isSNLxRejJ8qMEkPHEMWIblQPVa9eBlUTEP6SFok7MRJY14TmQ
qR+L5I7WT6OAXAujIrvw1phiAwW/uY5t2WGNdLXELk+M2ycBme4te5dV6hhuG6Iy
f8ayZXwWg/cUHYGbWSLlTNAhf1L40VQ9EfaRYDoujZdwBt64YSO1Q2I09SZKkW2Z
yRP0tHXENebaYnCRqPYyp5xE40uKcvggfRdHDVqlNukgnH4aXkl7P3153Yo/j7bj
aCulOGO1PjRsEKPNNx4oT4fKB1GAGqX5cuaITkhAcbFX9Hbicw6y3AVnqSIk9Fee
15Sd+D297E6SgZ5rQdIVqymWsAYjd65BmYST9+xMq3+hpznjvOA=
=BJL6
-END PGP SIGNATURE-

-- 
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/a41233ea-3182-f8fc-4538-23f4d342e256%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Intel ME Backdoor, called Odin's Eye


On 01/07/2018 02:46 AM, dangmad...@gmail.com wrote:


Summary:

Intel Whistleblower leaks details about his role in backdooring all IME chips 
on behalf of Intelligence Agencies. Posted 3/22/2017. Codename: Odin's Eye

That isn't an "intel whistleblower" that is simply a random dude with 
too much time on his hands making up a bullshit story, besides there is 
no "backdooring" IME as it already is a backdoor.


Intel doesn't need to add a specific backdoor for such a thing nor would 
a TLA ever ask as:

They already have knowledge of various exploits that do the same thing
A specific func_backdoor has zero plausible deniability
Any foreign intel agency could easily obtain proof and tell the media.

--
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/2cc06a17-fbab-a4b5-d24e-ba3b49c09e6d%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: new Desktop build recommendation


On 01/07/2018 12:14 PM, Wael M. Nasreddine wrote:


On Sat, Jan 6, 2018 at 1:57 PM taii...@gmx.com  wrote:


On 01/04/2018 01:23 PM, Wael M. Nasreddine wrote:


I read a bit more on M/B connectors and


https://www.newegg.com/Product/Product.aspx?Item=N82E16817153218=1

has one EPS (8 pin) and one ATX (8 pin as well), so it's all good.

Taiidan, what GPU do you use? The board has only a VGA, which is OK for
setting it up, but I want to run a 1080p widescreen (one, for now, more

for

later. I have a GeForce GTX 760
<

https://www.geforce.com/hardware/desktop-gpus/geforce-gtx-760/specifications

laying
around, would it work? It says required PCI-E 3 and the board has PCI-E 2
so probably not, but would be good to know.

Hmm curious is this your first time building a PC? :0 I thought you had
done this before? All PCI-e stuff is backwards and forwards compatible I
would get this all set up before you buy a newer GFX card - that one
will work fine for now.


I did build PCs before, but that was literarly a life time ago (early
2000's), and since then, I've been with laptops. I was aware of PCI-e
compatibility, but I did not know to what degree the difference in speed
might affect the GPU. Would a GTX 1080 work for instance?
There is no real difference between 3.0 and 2.0 even with 4K, Crossfire 
and the latest cards so having v2.0 is fine.
As I have stated before nvidia is a bad company and you shouldn't buy 
from them, they do not support owner-control, actively hinder linux 
driver development and VM gaming.


Don't forget your board standoffs, and don't confuse the PCI-e power 
cables with EPS12V.
Since it has been a long time you should brush up and watch some vids 
from reputable places, you gotta be careful considering how much $$$ you 
have spent :]

Hey when you get this let me know if you need any help setting up VM
gaming it is very difficult but very rewarding.
One gotcha I have noticed is NUMA alignment, each 16 core CPU contains
two NUMA nodes and performance will suffer greatly if things are not
properly aligned (gets tricker in VM's too)


I will definitely do that.
I eagerly await your gaming benchmarks, there are several triple A games 
out there that support 16 cores and you must try them.

TPM:
I am not sure about TPM's I would call ASUS and ask for a board
compatible part number.

I might have to return the one I got then, it's a Gigabyte TPM module.

Like I said call and ask asus what model number you need for the board.

Ideally you could simply use whatever same-generation of TPM (board is 
v1.2 not v2.0) as it uses a simple LPC bus for communication but you 
might as well buy whatever asus tells you to so to avoid trouble. 
Coreboot devs tested with asus's infineon brand TPM.

I assume you have bought a TPM 2.0, if so that definitely won't work.

Newegg Links:
I can't view newegg links, you would have to find a OEM link to show me.
I would get a 1KW PSU from a reputable company, like I said dual EPS12V,
modular and japanese capacitors is what you want.



I got this one, https://www.evga.com/products/product.aspx?pn=220-G3-1000-X1
I usually don't recommend evga as I don't like companies who sell both 
good and bad products (their lower end stuff is crappy) but that seems 
fine, good reviews japanese caps and a nice 10 year warranty.

Case Price - no more than $200 unless it includes nice front HDD hot
swap bays - Don't use the PSU that comes with the case.

Unfortunately, it ended up closer to 400. I got this one

http://www.norcotek.com/product/rpc-4220/ it was difficult finding EEB
cases. Depending on the noise it makes, there's a braket that I can switch
in it to change the 4 80mm fans with 3 120mm fans. In anycase, I wanted a
case that has wide support for boards (CEB, EEB, ATX and mini ATX) so later
on I can update the components and not have to reinvenst in the case.
Nice case, pricey but with an HBA or RAID card you can install all the 
drives you'll ever want.

It has good reviews that mention the high quality, good choice!

I would also get front drive bay HDD enclosures that have a fan
otherwise your drives will get hot inside the case and be a pain to
service.


this one does not have a fan, I'll add a braket if I see a need, but I
think it'll be alright with the 6 fans it has.
Yeah you sure will, since the bays came with the case you won't need 
additional cooling as they have already taken care of that (with the 
assorted case fans)


Send me links, titles, prices and used/new status for the rest of the 
stuff you got and I can look it over.


--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit

[qubes-users] Re: qubes 4 qvm-trim not exist

On Sunday, January 7, 2018 at 7:48:48 PM UTC+1, Roy Bernat wrote:
> Hi All , 
> 
> What is the best practice to trim disk inside qubes 4 . 
> 
> the qvm-trim-template dont exist anymore . 
> 
> R

Basically, it's no more. Better explained here; 

Quote: "Qubes R4.0 will have a new storage scheme which utilizes LVM thin 
provisioning (and over-provisioning) to achieve similar capabilities with 
greater flexibility." Follow link for source and further details - 
https://unix.stackexchange.com/questions/315345/using-ssd-on-qubes-os

Also, as per my current understanding, this automated trimming feature was not 
fully developed after Qubes 4 RC-1 was released, but has gradually been refined 
and perfected till this day. But there are still some issues, i.e. no visual 
interface to show your overall disk space useage (the other month, you had to 
pull and combine several commands to make it show accurately). I'm not sure if 
this disk space useage reporting issue has been fixed today 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/adc23879-ad51-4328-8bdc-7e6e17c3bd07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4.0 rc3 boot and performance is quite slow

On Sunday, January 7, 2018 at 1:59:45 PM UTC+1, Fabrizio Romano Genovese wrote:
> Ok, I dug a bit deeper into this. It doesn't look like a problem of how much 
> memory I give to VMs. Essentially, my QubesOS boots in two different ways:
> 
> - When QubesOS is happy, it starts in ~1 min (yup, starting up all the VMs 
> still takes a while). The overall system is very reactive, for instance if I 
> type qvm-ls I obtain some output straight away. Moreover, if I start a VM the 
> notification "VM blabla is starting" is displayed immediately.
> 
> - When QubesOS is not happy, it starts in ~3mins. The overall system is very 
> slow, qvm-ls takes 3-4 seconds to display output, and starting a VM takes up 
> to 20 seconds. Even the notification "VM blabla is starting" is displayed 4-5 
> seconds after the command is issued. Moreover the battery is drained much 
> much quicker (200% quicker give or take).
> 
> What makes Qubes happy or not happy to start seems to be completely random. I 
> have a slight suspect that this may depend on booting the laptop while 
> plugged/unplugged, but I cannot confirm this.
> Essentially my Qubes experience atm can be exemplified as follows: "At boot, 
> throw a coin. If it's heads then it's fine, otherwise it's fubar". Any 
> suggestion (or report of similar behavior) would be greatly appreciated!
> 
> Cheers,
> Fab

After you type in your drive encryption password, followup by typing F1 key on 
your keyboard. This way you can follow the booting process in details as it 
happens. If any booting processes are hanging, you'll be able to take note 
"which one", and thereby narrow down the possible culprit. 

You can also do a "sudo journalctl --boot" or akin to that, after booting. But 
remember to do so after a fresh bootup, unless you want a mountain of extra 
unneeded information.

Also, if the booting is slow before you type in your drive encryption, then you 
know it's related to settings or features EFI/UEFI or Legacy-Boot/BIOS. It 
could also possibly be because you got a thumb-drive or external-harddrive 
sitting in your USB; which on some systems can make the booting process 
significantly slower as the system tries to identify bootable systems on the 
extra external-drives/thumb-drives.

-- 
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/2969094e-6594-4f75-90c3-65c5869ba631%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Intel ME Backdoor, called Odin's Eye

2018-01-07 Thread Ivan Ivanov

Yes, sadly not whistleblowers are reasonable, but we need any
whistleblowers - not just the Snowden tier! ;-)

-- 
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/CAAaskFD8Env%3D%3DwM80yU%3DV3p2ZitEKEkhvtzT46ABPL-Lvc4SJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Intel ME Backdoor, called Odin's Eye

2018-01-07 Thread Ivan Ivanov

*not all the whistleblowers

2018-01-07 20:22 GMT+00:00 Ivan Ivanov :
> Yes, sadly not whistleblowers are reasonable, but we need any
> whistleblowers - not just the Snowden tier! ;-)

-- 
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/CAAaskFABwYJ1%3Dyc4f5BoH0ttA5_vjRMwOENr%2BRF83gR8k%2BvyAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Announcement: Fedora 26 TemplateVM Upgrade

2018-01-07 Thread Andrew David Wong

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-01-06 18:15, Andrew David Wong wrote:
> Dear Qubes Community,
> 
> Fedora 25 reached EOL ([end-of-life]) on 2017-12-12. We sincerely
> apologize for our failure to provide timely notice of this event. It
> is strongly recommend that all Qubes users upgrade their Fedora 25
> TemplateVMs and StandaloneVMs to Fedora 26 immediately. We provide
> step-by-step [upgrade instructions] for upgrading your existing
> TemplateVMs and StandaloneVMs in-place on both Qubes 3.2 and Qubes
> 4.0. For a complete list of TemplateVM versions supported for your
> specific version of Qubes, see [Supported TemplateVM Versions].
> 
> We also provide fresh Fedora 26 TemplateVM packages through the
> official Qubes repositories, which you can get with the following
> commands (in dom0).
> 
> Standard Fedora 26 TemplateVM:
> 
> $ sudo qubes-dom0-update qubes-template-fedora-26
> 
> [Minimal] Fedora 26 TemplateVM:
> 
> $ sudo qubes-dom0-update qubes-template-fedora-26-minimal
> 
> After upgrading to a Fedora 26 TemplateVM, please remember to set all
> qubes that were using the old template to use the new one. The
> instructions to do this can be found in the [upgrade instructions]
> for your specific version.
> 
> Please note that no user action is required regarding the OS version
> in dom0. If you're using Qubes 3.2 or 4.0, there is no dom0 OS
> upgrade available, since none is currently required. For details,
> please see our [Note on dom0 and EOL].
> 
> If you're using an older version of Qubes than 3.2, we strongly
> recommend that you upgrade to 3.2, as older versions are no longer
> supported.
> 
> 
> [end-of-life]: 
> https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule

Here are the reference links with complete URLs:

[upgrade instructions]: 
https://www.qubes-os.org/doc/template/fedora/upgrade-25-to-26/
[Supported TemplateVM Versions]: 
https://www.qubes-os.org/doc/supported-versions/#templatevms
[Minimal]: https://www.qubes-os.org/doc/templates/fedora-minimal/
[Note on dom0 and EOL]: 
https://www.qubes-os.org/doc/supported-versions/#note-on-dom0-and-eol

> 
> This announcement is also available on the Qubes website:
> https://www.qubes-os.org/news/2018/01/06/fedora-26-upgrade/
> 

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpSgbUACgkQ203TvDlQ
MDDuehAAr4D9wYq8Z+YeCPrOtQUMsHrW20cHCVd1Vxint2fSh2BlwvwElhVr8XKb
UYpnGNNwIZNIVL/PzLJzAXgtyu7tmHOHWqP9jV6d/YzJ+vcCH69X2WG3k9uclNJc
RorgK7YbHOq/LSZfyDgYoNnPfhfywcf9nVuFvaYvlFwwBC6njK0PAhvr16hbbEF+
U7jXIspcqr5THcVS5jYpl7r4fnXtC3UB5PlwlN33G65C7kc7SaDl03G1R/loJNkJ
PSTV9vba7R16e7rfGaN0VVu42xrj4XG+eqU3/RGaTyZxHKdexOsNrjuQouv+AinM
M4JklLQTYpgcClvwMkkgYklr4RPlhg9gJXYeLdArxRNAedCufgc+mUwS3qeBbPeo
tIhh46w3feZr1q0OG2O0s4IejZiq6Eqt8WdZfOVuyhtbEMSJR/iMEkjRgUgZx3A3
g1p5XEh2ofZ7HAYbsJGXKWAwDqgrVpjqtPYULaVMtmOl+q1g2+6vSUD8sJI0VRwE
U/ieNm+pKUd7bYyFaicMaskFT1yZHsArmrVoAAkBTwpM+MWTu4CntMAuXLp+sH/0
iLJgP1yvJEsgOzZcYr2urCqmZEMu892Q42f5Xyvw0sRFaL/GWpsyoNC9L9Fu583F
2ogsn68cc90N5IhOQ0OOA/HmZW3pS1qsvZ5Sy+I1fYlRgab471Q=
=wCzE
-END PGP SIGNATURE-

-- 
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/6d3e3b1e-067e-fbe7-7a49-c829b6303621%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Recommended wireless or Ethernet card / chipset


On 01/06/2018 11:14 PM, Sven Semmler wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 12/18/2017 11:07 PM, 'EW' via qubes-users wrote:


I tried a lot of things from various posts but to no avail, I'm
going to just assume for now that the HW is not compatible (they
are USB 3 adapters, some posts are at least opening the possibility
that USB 3 is no really supported yet). The system worked off of a
USB 3 based SD card though (before I installed to bullt-in SSD).

Yep, got trouble with USB3 too. As far as USB-to-Ethernet adapters are
concerned I had success with Apple's (which is USB2)...

https://www.apple.com/shop/product/MC704LL/A/apple-usb-ethernet-adapter
Apple? seriously? not only will you pay way too much money but you will 
be supporting a company that truly hates hardware freedom and products 
you can actually use for real work.


--
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/e86dab9c-17f3-21ab-a6f2-0a86c8e43d5d%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Announcement: Fedora 26 TemplateVM Upgrade

2018-01-07 Thread bowabos

On Sunday, 7 January 2018 00:15:29 UTC, Andrew David Wong  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Dear Qubes Community,
> 
> Fedora 25 reached EOL ([end-of-life]) on 2017-12-12. We sincerely
> apologize for our failure to provide timely notice of this event. It
> is strongly recommend that all Qubes users upgrade their Fedora 25
> TemplateVMs and StandaloneVMs to Fedora 26 immediately. We provide
> step-by-step [upgrade instructions] for upgrading your existing
> TemplateVMs and StandaloneVMs in-place on both Qubes 3.2 and Qubes
> 4.0. For a complete list of TemplateVM versions supported for your
> specific version of Qubes, see [Supported TemplateVM Versions].
> 
> We also provide fresh Fedora 26 TemplateVM packages through the
> official Qubes repositories, which you can get with the following
> commands (in dom0).
> 
> Standard Fedora 26 TemplateVM:
> 
> $ sudo qubes-dom0-update qubes-template-fedora-26
> 
> [Minimal] Fedora 26 TemplateVM:
> 
> $ sudo qubes-dom0-update qubes-template-fedora-26-minimal
> 
> After upgrading to a Fedora 26 TemplateVM, please remember to set all
> qubes that were using the old template to use the new one. The
> instructions to do this can be found in the [upgrade instructions]
> for your specific version.
> 
> Please note that no user action is required regarding the OS version
> in dom0. If you're using Qubes 3.2 or 4.0, there is no dom0 OS
> upgrade available, since none is currently required. For details,
> please see our [Note on dom0 and EOL].
> 
> If you're using an older version of Qubes than 3.2, we strongly
> recommend that you upgrade to 3.2, as older versions are no longer
> supported.
> 
> 
> [end-of-life]: 
> https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
> [upgrade instructions]: /doc/template/fedora/upgrade-25-to-26/
> [Supported TemplateVM Versions]: /doc/supported-versions/#templatevms
> [Minimal]: /doc/templates/fedora-minimal/
> [Note on dom0 and EOL]: /doc/supported-versions/#note-on-dom0-and-eol
> 
> This announcement is also available on the Qubes website:
> https://www.qubes-os.org/news/2018/01/06/fedora-26-upgrade/
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpRZpEACgkQ203TvDlQ
> MDA30xAAhvx58l16DPzWdjTkCDAu8X/oIJVsidabezigI3x8BFcMWuNvGpfO9wD0
> 4oJVhXvLIrqPvWK6HBz5o8zld8rZd8r+OVB7Aivh34WIdVdxZZY9vwCvbWZifdbU
> jGpAMX+ivfXTB1DM4y3hZ/gq+7kScYzIPw9TRC8CykkCySqwwWJEEMCXvqGJvYxC
> HspnoiCo+LP63ta438yTHPFgk6chnlKlU2rK5KsdUE69tZl3s6t1NoZaxMHUCuMz
> sxmT081xqCh4+DCPZ6WzPKiKNEc8AMVD/5Axdt5mBn2rZqGYntEX0UWh7pak3Dk5
> MZBBdevbOFj0mlQ8/wStkBjNaRSOLT//PyPCeKKNf/wvOYDPI3PfUjxYM0LaKzl9
> X6go9tlbc7e43e9lbtArmvYGY7hXsAi721dvKnpng1vuDUZjKPWOFtSVS+MX/zIl
> yGmYDEK/UhFYRfaaKXP2vf5YRpRPGyl/MkTN/4akEttgnXxJ/ztR8WB3+PY73R4G
> AeT4zhbLSTptIneDH9wsRujBt1l1As/9ApVxt8e0nOtyou4LdVhDlkaO6Qt2FCAs
> Iprz5CYWBFD7qR9qmtDHSR99rldK0uau9Ihzabe5WK+9wtMNp3+6qaIemBUS9293
> m/Wf9H63xfjrdFMsjIiduZHFBw0Q4IQeKOlT7072QFJBvr2WmD4=
> =/ZvF
> -END PGP SIGNATURE-

Hi,

FYI, In order to update the new template for the first time, I had to launch:
dnf update --best --allowerasing
there was a pb with yum-utils which was preventing the QubesManager method (dnf 
update --best) to work.

Regards,
Alex

-- 
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/b0ef9f44-a855-4d0d-968b-26af3455f801%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Atheros AR928X & Q4.0rc3 Passthrough

Got Xen debugging enabled (thank you, Marek!) and am seeing the following
in the log now. If I understand the code right, which is a big assumption
on my part, it's crashing because it's attempting to do a type 5 access to
a page setup in mode 3. So my questions to anyone in general or myself
are:

1. Why does it try to do that?
2. Why does it work in regular Fedora 26's Xen 4.8.2-7.fc26 but not Qubes'
Xen 4.8.2-11.fc25?
3. How can I fix it?


(XEN) AMD-Vi: Setup I/O page table: device id = 0x200, type = 0x1, root
table = 0x22f674000, domain = 0, paging mode = 3

(XEN) AMD-Vi: Disable: device id = 0x200, domain = 0, paging mode = 3
(XEN) AMD-Vi: Setup I/O page table: device id = 0x200, type = 0x1, root
table = 0x264921000, domain = 9, paging mode = 3
(XEN) AMD-Vi: Re-assign :02:00.0 from dom0 to dom9

(d9) pci dev 05:0 bar 10 size 1: 0f2020004
(XEN) memory_map:add: dom9 gfn=f2020 mfn=f0100 nr=10

(XEN) memory_map:add: dom9 gfn=f2020 mfn=f0100 nr=10
(XEN) irq.c:275: Dom9 PCI link 0 changed 5 -> 0
(XEN) irq.c:275: Dom9 PCI link 1 changed 10 -> 0
(XEN) irq.c:275: Dom9 PCI link 2 changed 11 -> 0
(XEN) irq.c:275: Dom9 PCI link 3 changed 5 -> 0
(XEN) svm.c:1540:d9v0 SVM violation gpa 0x00f2020040, mfn 0xf0100, type 5
(XEN) domain_crash called from svm.c:1541
(XEN) Domain 9 (vcpu#0) crashed on cpu#1:
(XEN) [ Xen-4.8.2  x86_64  debug=y   Not tainted ]
(XEN) CPU:1
(XEN) RIP:0010:[]
(XEN) RFLAGS: 0296   CONTEXT: hvm guest (d9v0)
(XEN) rax:    rbx: 8fb606b115c0   rcx: 0005
(XEN) rdx: 0040   rsi: b0eac0d00040   rdi: 
(XEN) rbp: b0eac0c938f8   rsp: b0eac0c938c8   r8:  
(XEN) r9:  ff90   r10: 003f   r11: 
(XEN) r12:    r13: c04d97d0   r14: 0100
(XEN) r15: 8fb606b18028   cr0: 80050033   cr4: 000406f0
(XEN) cr3: 00010688d000   cr2: 
(XEN) ds:    es:    fs:    gs:    ss: 0018   cs: 0010
(XEN) grant_table.c:3388:d0v3 Grant release (0) ref:(151) flags:(2) dom:(0)
(XEN) grant_table.c:3388:d0v3 Grant release (1) ref:(52) flags:(2) dom:(0)
(XEN) grant_table.c:3388:d0v3 Grant release (2) ref:(120) flags:(6) dom:(0)
(XEN) AMD-Vi: Disable: device id = 0x200, domain = 9, paging mode = 3
(XEN) AMD-Vi: Setup I/O page table: device id = 0x200, type = 0x1, root
table = 0x22f674000, domain = 0, paging mode = 3
(XEN) AMD-Vi: Re-assign :02:00.0 from dom9 to dom0




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

Re: [qubes-users] Qubes 4.0 rc3 boot and performance is quite slow

On Sunday, January 7, 2018 at 1:59:45 PM UTC+1, Fabrizio Romano Genovese wrote:
> Ok, I dug a bit deeper into this. It doesn't look like a problem of how much 
> memory I give to VMs. Essentially, my QubesOS boots in two different ways:
> 
> - When QubesOS is happy, it starts in ~1 min (yup, starting up all the VMs 
> still takes a while). The overall system is very reactive, for instance if I 
> type qvm-ls I obtain some output straight away. Moreover, if I start a VM the 
> notification "VM blabla is starting" is displayed immediately.
> 
> - When QubesOS is not happy, it starts in ~3mins. The overall system is very 
> slow, qvm-ls takes 3-4 seconds to display output, and starting a VM takes up 
> to 20 seconds. Even the notification "VM blabla is starting" is displayed 4-5 
> seconds after the command is issued. Moreover the battery is drained much 
> much quicker (200% quicker give or take).
> 
> What makes Qubes happy or not happy to start seems to be completely random. I 
> have a slight suspect that this may depend on booting the laptop while 
> plugged/unplugged, but I cannot confirm this.
> Essentially my Qubes experience atm can be exemplified as follows: "At boot, 
> throw a coin. If it's heads then it's fine, otherwise it's fubar". Any 
> suggestion (or report of similar behavior) would be greatly appreciated!
> 
> Cheers,
> Fab

The battery issue, btw, as far as I recall is nothing new in Qubes 4. It's not 
something specifc to your system, and if it gets fixed, it'll probably be an 
update to fix all the Qubes 4 systems out there. But maybe there are settings 
you can flip to fix it manually, however it's not something I've checked. 

Make sure the VM's that start at boot, are starting just as slow (or quick) as 
if you started them on an already running Qubes system. If the speed is 
similar, then at least you can assume it has nothing to do with the actual 
booting process. 

It sounds weird that it happens randomly, maybe a few more clues are needed to 
hunt down the actual reason as to why it happens, unless someone with better 
insight drops by.

-- 
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/8eb9e2cd-8f34-457b-b238-238d95d23fe0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Intel ME Backdoor, called Odin's Eye

2018-01-07 Thread Franz

On Sun, Jan 7, 2018 at 4:26 PM, qma ster  wrote:

> воскресенье, 7 января 2018 г., 18:20:37 UTC пользователь tai...@gmx.com
> написал:
> > On 01/07/2018 02:46 AM, d@gmail.com wrote:
> >
> > > Summary:
> > >
> > > Intel Whistleblower leaks details about his role in backdooring all
> IME chips on behalf of Intelligence Agencies. Posted 3/22/2017. Codename:
> Odin's Eye
> > >
> > That isn't an "intel whistleblower" that is simply a random dude with
> > too much time on his hands making up a bullshit story, besides there is
> > no "backdooring" IME as it already is a backdoor.
> >
> > Intel doesn't need to add a specific backdoor for such a thing nor would
> > a TLA ever ask as:
> > They already have knowledge of various exploits that do the same thing
> > A specific func_backdoor has zero plausible deniability
> > Any foreign intel agency could easily obtain proof and tell the media.
>
> Sorry but you haven't seen the full story. This "Intel guy" is legit, he
> provided proofs like this one:
>
> https://i.warosu.org/data/g/img/0595/40/1490327898699.png
>
>
Hmmm, which is the sense to avoid telling the Intel guy name, but providing
enough information for Intel to understand who is writing? If it was real,
Intel and intelligence agencies would immediately act and deprive him/her
of the freedom to tell or confirm more. The only working way to do that is
how Snowden taught, taking full responsibility, providing plenty of
evidence, getting media help  and moving to a country willing to protect
you.

 It seems

> Best regards,
> Ivan Ivanov
>
> --
> 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/ac501523-14ca-4938-a074-0fd5a51fc6bc%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAPzH-qBVeKwdy2nhVLu_j1KtAqxzsibiuyGqsK7igPJiXuLXkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-devel] Announcement: Fedora 26 TemplateVM Upgrade

2018-01-07 Thread Peter Todd

On Sat, Jan 06, 2018 at 06:15:21PM -0600, Andrew David Wong wrote:
> Dear Qubes Community,
> 
> Fedora 25 reached EOL ([end-of-life]) on 2017-12-12. We sincerely
> apologize for our failure to provide timely notice of this event. It
> is strongly recommend that all Qubes users upgrade their Fedora 25
> TemplateVMs and StandaloneVMs to Fedora 26 immediately. We provide
> step-by-step [upgrade instructions] for upgrading your existing
> TemplateVMs and StandaloneVMs in-place on both Qubes 3.2 and Qubes
> 4.0. For a complete list of TemplateVM versions supported for your
> specific version of Qubes, see [Supported TemplateVM Versions].
> 
> We also provide fresh Fedora 26 TemplateVM packages through the
> official Qubes repositories, which you can get with the following
> commands (in dom0).
> 
> Standard Fedora 26 TemplateVM:
> 
> $ sudo qubes-dom0-update qubes-template-fedora-26

This template seems to be broken out of the box. After installation, yum
upgrade gives the following:

[user@fedora-26 ~]$ sudo yum upgrade
Last metadata expiration check: 0:26:15 ago on Sun 07 Jan 2018 03:00:32 PM 
EST.
Dependencies resolved.

 Problem 1: package salt-2017.7.2-1.fc26.noarch requires dnf-utils, but 
none of the providers can be installed
  - package dnf-utils-2.1.5-1.fc26.noarch conflicts with yum-utils < 
1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
  - package dnf-utils-2.1.1-1.fc26.noarch conflicts with yum-utils < 
1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
  - cannot install the best update candidate for package 
yum-utils-1.1.31-512.fc26.noarch
  - cannot install the best update candidate for package 
salt-2016.11.5-3.fc26.noarch
 Problem 2: problem with installed package yum-utils-1.1.31-512.fc26.noarch
  - package dnf-utils-2.1.5-1.fc26.noarch conflicts with yum-utils < 
1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
  - package salt-2017.7.2-1.fc26.noarch requires dnf-utils, but none of the 
providers can be installed
  - package dnf-utils-2.1.1-1.fc26.noarch requires dnf-plugins-core = 
2.1.1-1.fc26, but none of the providers can be installed
  - package salt-ssh-2017.7.2-1.fc26.noarch requires salt = 
2017.7.2-1.fc26, but none of the providers can be installed
  - cannot install both dnf-plugins-core-2.1.1-1.fc26.noarch and 
dnf-plugins-core-2.1.5-1.fc26.noarch
  - cannot install the best update candidate for package 
salt-ssh-2016.11.5-3.fc26.noarch
  - cannot install the best update candidate for package 
dnf-plugins-core-2.1.5-1.fc26.noarch


 PackageArch VersionRepository 
Size


Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 dnf-plugins-core   noarch   2.1.1-1.fc26   fedora 
49 k
 dnf-utils  noarch   2.1.1-1.fc26   fedora 
39 k
 dnf-utils  noarch   2.1.5-1.fc26   updates
40 k
Skipping packages with broken dependencies:
 salt   noarch   2017.7.2-1.fc26updates   
7.8 M
 salt-ssh   noarch   2017.7.2-1.fc26updates
21 k

Transaction Summary


Skip  5 Packages

Nothing to do.
Complete!
[user@fedora-26 ~]$ 

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

-- 
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/20180107202821.GA9346%40savin.petertodd.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: [qubes-users] Intel ME Backdoor, called Odin's Eye

2018-01-07 Thread Ivan Ivanov

Yes, hopefully one day we would see more leaks, that could help us to
truly get rid of ME ;)
Meanwhile, perhaps the only thing we could do is to stockpile those
few computer models
that are both coreboot (or libreboot) supported and without Intel ME / AMD PSP

2018-01-07 20:01 GMT+00:00 haaber :
>> воскресенье, 7 января 2018 г., 18:14:26 UTC пользователь haaber написал:
 https://i.redditmedia.com/5mA7LrMiwgmmhrwfYF8Jks0WEng66fxWoCcGw33dhCA.jpg?w=597=339d919645f1de31a42913c748d1d7fb


 Summary:

 Intel Whistleblower leaks details about his role in backdooring all IME 
 chips on behalf of Intelligence Agencies.
>>> The post is unspecific. Of course ME is a problem: the allegations could
>>> be true or could be disinformation. "I know exactly" is an unplausible
>>> formulation for a backdooring engineer - it is almost surely a wrong ot
>>> statement if it was not himself who spied ...  To conclude: unless some
>>> details are given to enhance trustworthyness (a specific backdoor,
>>> protocol, communication interface, whatsoever), I personally consider
>>> this troll post.
>>
>> Sorry but you haven't seen the full story. This "Intel guy" is legit, he 
>> provided proofs like this one:
>>
>> https://i.warosu.org/data/g/img/0595/40/1490327898699.png
> Maybe, maybe not. Who can verify scanned and blacked papers? I would
> appreciate him helping me to remove it from my mainboard though! How to
> do THIS is the right discussion to my pov.
>
> --
> 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/bqRSuU3T6MA/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/506eac1a-d270-e5aa-ab72-27088ddd7fea%40web.de.
> 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/CAAaskFB9FS1esuD2NrYiEyNntb4U%3DCRaN%2BYvND5p1dyst679%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] New HCL Entry: Lenovo ThinkPad T470 (20HDCTO1WW)

2018-01-07 Thread kototamo

Thanks everyone for the replies. I finally opted for RC3 and after fixing the 
iso with a live fedora and livecd-tools it went almost almost without problems. 
The only problem was that the keyboard layout chosen during the installation 
was not taken in account for promting the encryption password when booting.

I hope I will not encounter too much bugs with it and be able to work. It seems 
okay for the few hours I had to use it and even more resistant to usb devices 
being physically disconnected without detaching them than 3.2. 

-- 
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/05645d61-3235-4a1e-99e6-5a17eef97d5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Dom0 terminal color is blue?

2018-01-07 Thread bowabos

Stupid question, I rarely fire dom0 terminal... is the color blue? I remember 
it being grey long ago...

-- 
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/8a6e4ede-4624-4b20-94d3-318f0ab732cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-devel] Announcement: Fedora 26 TemplateVM Upgrade

2018-01-07 Thread Peter Todd

On Sun, Jan 07, 2018 at 02:48:29PM -0600, Andrew David Wong wrote:
> This is a known issue:
> 
> https://github.com/QubesOS/qubes-issues/issues/3442
> 
> You can simply use `--best --allow-erasing`.

Thanks! That worked.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

-- 
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/20180107210436.GA9742%40savin.petertodd.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: [qubes-users] Qubes freezing (hangs) always in less than 1 hour

2018-01-07 Thread Sameer Vao

 If you havent already, try running sudo 
qubes-dom0-update as soon as you get in to Qubes.Thank you 
awokd. I did but havent solved it.Im thinking something limiting 
memory or CPU may be the way to solve it, but may be something else.Any 
other ideas anybody?After much search and trials last 5 days, still found 
nothing online to solve this problem. Another notebook not an option for me at 
this time unfortunately.If I cant fix it I will have to install another 
linux distribution - but that would be sad. Anybody else have other ideas 
so I can keep qubes? Thank you

-- 
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/1515018212.S.1626.27737.f5mail-224-106.rediffmail.com.1515373163.24136%40webmail.rediffmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Funding Program

2018-01-07 Thread 'Mary William' via qubes-users

Greetings From United Arab Emirate,
Let me introduce to you about National Investment Corporation (NIC) Funding
Program.
I have to start by introducing myself as an investment consultant working under
the mandate of National Investment Corporation (NIC) here in Abu Dhabi UAE to
reach out to project owners and business men and women for funding cooperation
between their companies/firms and National Investment Corporation (NIC).
In introducing the company I represent, NIC is a private Investment Company, is
one of the leading strategic investors based in the of Abu Dhabi, United Arab
Emirates.
Since its establishment the company has focused on contributing to the
sustainable development of the region while creating value through investments
in fundamental growing sectors Today National Investment Corporation presents
an optimal balance between return on investments and growth, through focusing
on essential sectors including Oil & Gas, Banking & Finance, project
management, tourism, Aviation, Real estate, Business Investment, Marine
Projects, Solar project and industrialization.
Furthermore, NIC has put forward unique investment opportunities and
facilitated the development of various projects that meet the local and
international market needs.
National Investment Corporation (NIC) is acting as a lender and the loan will
be disbursed on a clear Loan of 3.5% Interest annually to project owners and
Equity Partners for their Investment Projects. They focus on seed Capital,
Early-stage, start-up ventures, existing LLC and total completion and expansion
of Investment Projects with immediate Funding.
NIC can invest in any country on a good conduct with the both parties.
Hope to hear from you if we have a common goal of a better tomorrow through
investments.
Best Regards,
Mary William (Investment Consultant)National Investment Corporation (NIC)Marina
Mall, Al Marina, Abu DhabiUnited Arab Emirates

--
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/720878376.2083842.1515358000349%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] do i need to configure usb printer in disposalVM? to print from there

2018-01-07 Thread jerry57

which vm do i attach it to (for example fedora-23 or debian-8)
using the command qvm-usb
so usb printer will dispay in disposablevm when right clicking a file and 
opening in dispVM

note: i don't know how to comment to the original theard, i've tried clicking 
reply button, it didn't respond in the original thread

January 7, 2018 2:34 AM, "awokd' via qubes-users" 
 wrote:

> On Sat, January 6, 2018 9:38 pm, jerr...@disroot.org wrote:
> 
>> i just configured a usb printer, by going to devices tab (can be accessed
>> through start menu > in your appvm clicking add more shortcuts), moving
>> the printer to the selected area printer is not recognized in the
>> disposable vm only... (when right clicking it > open in DisposableVM)
> 
> How did you connect the USB printer to your dispVM? Did you use qvm-usb to
> attach it? You'd need to do at least that first.
> 
> --
> 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/934c689655c28eaf77e9137c20b8f08d.squirrel%40tt3j2x4k5y
> aa5zt.onion.
> 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/5268c19bbaae01642f99ac24af9103cc%40disroot.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] hey, Please confirm we cannot install Qubes 4.0 on DVD, and the minimum on flash drive to install

2018-01-07 Thread russlyatoslav

On Saturday, January 6, 2018 at 10:39:34 PM UTC-5, awokd wrote:
> On Sun, January 7, 2018 3:02 am, russlyatos...@gmail.com wrote:
> 
> 
> > 1. We are able also to install actual OS on one flash drive using another
> > flash drive with ISO image on it (or also DVD ISO image)? True for Qubes
> > 4.0 ?
> yes
> 
> > 2. In order to install OS on flash drive the minimum size should be 32GB
> > on it?
> yes
> 
> > 3. Minimum size to burn Qubes 4.0 ISO on flash drive need to have 16GB on
> > it?
> no, 8GB

Hey, thanks.
Do you know a lot about Qubes?
Is it possible I can bother you here or somewhere else with few questions?
I'm new to Qubes, Whonix, and Tails.
I'm trying to make my PC - with high security and anonymity.

1. Do I need to install additional "internetz.me vpn in a special Proxy VM (the 
gui way )" on Qubes? Is it necessary? My question based on this video 
https://www.youtube.com/watch?v=wYEmDZebow4

2. Can I and do I need to install Whonix OS inside Qubes OS for more security?

3. Can I run Tails on my flash drive using Qubes OS (also can I run Tails on 
Whonix OS within Qubes OS)? 

-- 
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/0e286399-f320-43f8-8691-9ed1ba9aab13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4.0 rc3 boot and performance is quite slow

2018-01-07 Thread Marek Marczykowski-Górecki

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jan 07, 2018 at 04:59:44AM -0800, Fabrizio Romano Genovese wrote:
> Ok, I dug a bit deeper into this. It doesn't look like a problem of how much 
> memory I give to VMs. Essentially, my QubesOS boots in two different ways:
> 
> - When QubesOS is happy, it starts in ~1 min (yup, starting up all the VMs 
> still takes a while). The overall system is very reactive, for instance if I 
> type qvm-ls I obtain some output straight away. Moreover, if I start a VM the 
> notification "VM blabla is starting" is displayed immediately.
> 
> - When QubesOS is not happy, it starts in ~3mins. The overall system is very 
> slow, qvm-ls takes 3-4 seconds to display output, and starting a VM takes up 
> to 20 seconds. Even the notification "VM blabla is starting" is displayed 4-5 
> seconds after the command is issued. Moreover the battery is drained much 
> much quicker (200% quicker give or take).
> 
> What makes Qubes happy or not happy to start seems to be completely random. I 
> have a slight suspect that this may depend on booting the laptop while 
> plugged/unplugged, but I cannot confirm this.
> Essentially my Qubes experience atm can be exemplified as follows: "At boot, 
> throw a coin. If it's heads then it's fine, otherwise it's fubar". Any 
> suggestion (or report of similar behavior) would be greatly appreciated!

Is it Dell Latitute by a chance? I have very similar problem on such
system, regardless of Qubes version: when it is on AC power, performance
is normal, but on battery it is significantly slower. Some workaround is
to change CPU scaling governor, by executing in dom0:

xenpm set-scaling-governor performance

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpSuRQACgkQ24/THMrX
1yyUiQgAhD98/UgCgmUIhyu77ShIccLqV0WqE+pPnFmC8uAije3wRztS6JE83ioP
/KI0GuCiGMgSDy/zodPkeh9CTG5pRE8K6qvkN6Xp0jBKWdvoV+DUyFw/Fx1ZX/yz
UpvMFdmIZCeF6HNndKI4jWTsJS/ypg8H8mZQ4odRtFXUiYaiRt1mbp6zS10cmMpB
kl0OQM8z3JBCrVaytYCGHEGvNoDU/fXnd485S35Nu4W00/1f2vIhDvsDPpk/PVa2
AxRC6LnWxxmO1UTEo30m7VJOE8ylezd0ZwwtahMGUUN8NyBWgstJA3UUQL9bVUuE
F1kXEZ7iAW9YvxQHPFpm18BAHxfaaA==
=r0ng
-END PGP SIGNATURE-

-- 
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/20180108001932.GB12450%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] live Distro

2018-01-07 Thread Leo Reitano

Hi all,
I would love to know if is possible to use Qube as live distro on a usb or a 
dvd and what is the procedure step by step

Moreover what is the release stage? alpha, beta? 

Thanks

Leo

-- 
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/5b7fd9c8-816a-417e-8155-916d849d88de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-devel] Announcement: Fedora 26 TemplateVM Upgrade

2018-01-07 Thread Andrew David Wong

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-01-07 14:28, Peter Todd wrote:
> On Sat, Jan 06, 2018 at 06:15:21PM -0600, Andrew David Wong wrote:
>> Dear Qubes Community,
>>
>> Fedora 25 reached EOL ([end-of-life]) on 2017-12-12. We sincerely
>> apologize for our failure to provide timely notice of this event. It
>> is strongly recommend that all Qubes users upgrade their Fedora 25
>> TemplateVMs and StandaloneVMs to Fedora 26 immediately. We provide
>> step-by-step [upgrade instructions] for upgrading your existing
>> TemplateVMs and StandaloneVMs in-place on both Qubes 3.2 and Qubes
>> 4.0. For a complete list of TemplateVM versions supported for your
>> specific version of Qubes, see [Supported TemplateVM Versions].
>>
>> We also provide fresh Fedora 26 TemplateVM packages through the
>> official Qubes repositories, which you can get with the following
>> commands (in dom0).
>>
>> Standard Fedora 26 TemplateVM:
>>
>> $ sudo qubes-dom0-update qubes-template-fedora-26
> 
> This template seems to be broken out of the box. After installation, yum
> upgrade gives the following:
> 
> [user@fedora-26 ~]$ sudo yum upgrade
> Last metadata expiration check: 0:26:15 ago on Sun 07 Jan 2018 03:00:32 
> PM EST.
> Dependencies resolved.
> 
>  Problem 1: package salt-2017.7.2-1.fc26.noarch requires dnf-utils, but 
> none of the providers can be installed
>   - package dnf-utils-2.1.5-1.fc26.noarch conflicts with yum-utils < 
> 1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
>   - package dnf-utils-2.1.1-1.fc26.noarch conflicts with yum-utils < 
> 1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
>   - cannot install the best update candidate for package 
> yum-utils-1.1.31-512.fc26.noarch
>   - cannot install the best update candidate for package 
> salt-2016.11.5-3.fc26.noarch
>  Problem 2: problem with installed package 
> yum-utils-1.1.31-512.fc26.noarch
>   - package dnf-utils-2.1.5-1.fc26.noarch conflicts with yum-utils < 
> 1.1.31-513 provided by yum-utils-1.1.31-512.fc26.noarch
>   - package salt-2017.7.2-1.fc26.noarch requires dnf-utils, but none of 
> the providers can be installed
>   - package dnf-utils-2.1.1-1.fc26.noarch requires dnf-plugins-core = 
> 2.1.1-1.fc26, but none of the providers can be installed
>   - package salt-ssh-2017.7.2-1.fc26.noarch requires salt = 
> 2017.7.2-1.fc26, but none of the providers can be installed
>   - cannot install both dnf-plugins-core-2.1.1-1.fc26.noarch and 
> dnf-plugins-core-2.1.5-1.fc26.noarch
>   - cannot install the best update candidate for package 
> salt-ssh-2016.11.5-3.fc26.noarch
>   - cannot install the best update candidate for package 
> dnf-plugins-core-2.1.5-1.fc26.noarch
> 
> 
>  PackageArch VersionRepository
>  Size
> 
> 
> Skipping packages with conflicts:
> (add '--best --allowerasing' to command line to force their upgrade):
>  dnf-plugins-core   noarch   2.1.1-1.fc26   fedora
>  49 k
>  dnf-utils  noarch   2.1.1-1.fc26   fedora
>  39 k
>  dnf-utils  noarch   2.1.5-1.fc26   updates   
>  40 k
> Skipping packages with broken dependencies:
>  salt   noarch   2017.7.2-1.fc26updates   
> 7.8 M
>  salt-ssh   noarch   2017.7.2-1.fc26updates   
>  21 k
> 
> Transaction Summary
> 
> 
> Skip  5 Packages
> 
> Nothing to do.
> Complete!
> [user@fedora-26 ~]$ 
> 

This is a known issue:

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

You can simply use `--best --allow-erasing`.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpSh5sACgkQ203TvDlQ
MDA/cxAAlpHOvQ055n+PN8JQoQy6mPuUN6lkV712E/bmGm/29RwEZV0QPU3Y2EdD
0GVqNC9hHz3VLzcPnXY0MfTDAeZEgASzTXsWFUNYxz1iTPnsSm13Nf6UTWXSMRkE
lz754rPrYaUXDNJSuw+O6Agyiek8Q4yYy+61rNFGoJrKNZ3cFUuTfedc1KtQXbl8
OtSWOnl4vqvntWHEibduB5F0Jvyaj0fafrzSiBUD1AIlwP1zfdkNjkbUc+0vMrIn
Rael/qWLxoMe9xckkYVYt1RAWDLgV8YCs8Ve5e9K1p67dGgynqu50QFrk3L9+C8l
EksfYwhYRI14TygBFG/guaMah4nHj4ho8qQvtB2vXYIT6WE0oTyfB3+twbs6U8hi
uxhPymZPfC9rzJPOYt9jqwY7hnZ/5bEh+lIJhLVW9bwYkoh8yZ2oofZFDEsq795e
NYCtcURE4G/Dm/A6YEDJcHDq0QYfvqaFFrBVi8XTNsbj1IlVz5RHDa2W4OWVUbHb
UFROOgxUVQFjH4rnVXzjFb+uhFEug+yILewcjPBWHCacgf16C4JhFBrfKVo11rtn
GIiOmwCEtJOo0toB2cJ6padcrcyp5FiukHL5eh/tZ3D2VPUqoqF5/Qo7cGiVeuJ9
9FKjr02qQmhT5HFCwZI5UkN7Q5X6FQtFjQzNlHN0CRA1yp7WszI=
=hIky
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users"

Re: [qubes-users] Re: qubes 4 qvm-trim not exist

2018-01-07 Thread 'Tom Zander' via qubes-users

On Sunday, 7 January 2018 19:40:27 GMT Yuraeitha wrote:
> But there are still some
> issues, i.e. no visual interface to show your overall disk space useage
> (the other month, you had to pull and combine several commands to make it
> show accurately). I'm not sure if this disk space useage reporting issue
> has been fixed today though.

* https://github.com/QubesOS/qubes-issues/issues/1872
(open) Implement UI Notifications for cases of a Qube disk full 

* https://github.com/QubesOS/qubes-issues/issues/1053
(open) Improve usability of VM disk space / increasing disk size

* https://github.com/QubesOS/qubes-issues/issues/3438
(open) Qubes storage pools of type LVM issues

This one is closed, but as I point out in the collection of issues (3438) 
this is not yet fixed;
https://github.com/QubesOS/qubes-issues/issues/2016
(closed) Create dom0 API to detect global disk space available

And, yeah, it also still needs  a user-interface.


The simplest way to get the space usage if you are using a LVM based pool 
(which requires completely manual setup at the moment) is
  sudo lvs
and you can read under the column "Data%" how much actual usage you reached.

-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


-- 
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/4269306.bpYcQdtx5U%40mail.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - Dell inspiron 13 7373

2018-01-07 Thread János Goromba

Hi!

I was able to test qubes R3.2 and R4.0-rc3.
Generally everything works fine, except the suspend when the network was
lost until reboot. It's most likely energy management 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/CAF%2BWpeZ1ZNA9%3DnCYEzvJGKdunBqRK%3DBXUOPEE4y6fjjmx%2B%3D6Vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Dell_Inc_-Inspiron_7373-20171231-031347.yml
Description: application/yaml

[qubes-users] how to get the update proxy working again

2018-01-07 Thread 'Tom Zander' via qubes-users

I needed space on my dom0  (Q4) drive, so I ended up using qvm-clone to copy 
my fedora25 template, my sys-net & sys-firewall to a different pool.
I naturally also copied the setup from the config dialog.

Everything seemed to work for a while, so I removed the sys-net /firewall 
originals.

Now I have a problem, updates in templates no longer work. The magic proxy 
fails me and I can't figure out how that thing actually was designed in order 
to make it work again.

My first thinking was to assign the original IP addresses to the cloned VMs, 
but qvm-prefs refuses to overwrite the qid property. :-(

The docs on the website talk about a service "qubes-yum-proxy" can't find 
that one, though. I guess its a 3.2 property.

Anyone here able to explain how this proxy works? Would make a nice doc on 
the website too!
I'd love some suggestions on how to fix this...

Thanks!
-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


-- 
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/4020213.iHnCjNg7BT%40mail.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] do i need to configure usb printer in disposalVM? to print from there

On Sun, January 7, 2018 10:31 pm, jerr...@disroot.org wrote:
> which vm do i attach it to (for example fedora-23 or debian-8) using the
> command qvm-usb so usb printer will dispay in disposablevm when right
> clicking a file and opening in dispVM

It doesn't work like that. If you want to print from a dispVM, you'd need
to qvm-usb attach the printer straight to the disposable VM, like "disp5"
or whatever.

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

Re: [qubes-users] hey, Please confirm we cannot install Qubes 4.0 on DVD, and the minimum on flash drive to install

On Mon, January 8, 2018 12:54 am, russlyatos...@gmail.com wrote:

> For #2 As I see Whonix OS within Qubes OS will not bring any additional
> benefits, more Cons than Pros? You would't recommend to install Whonix OS
> into Qubes OS? Don't we already have Whonix OS in Qubes OS? - I see in my
> Qubes right now "sys-whonix, whonix-gw, whonix-ws, anon-whonix which can
> run Tor Browser" ?

Yes, I recommended you use Whonix/Tor. You might also want to add a VPN
later, once you get a good understanding of the pros and cons.

>
> For #3 I'm not sure if I understood your answer, maybe I worded it wrong,
> I asked if I can run Tails on flash drive using Qubes OS installed on my
> PC? Is it possible? Will it bring additional layer or security and
> anonymity?

You can run Tails from inside Qubes (see
https://www.qubes-os.org/doc/tails/) but again, there are trade-offs to
that so it's a judgement call. Personally, I'd say use Qubes for
everything and boot Tails separately off the USB drive when you want to
use Tails. You might also want to check out Heads.

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

Re: [qubes-users] hey, Please confirm we cannot install Qubes 4.0 on DVD, and the minimum on flash drive to install

2018-01-07 Thread russlyatoslav

On Sunday, January 7, 2018 at 8:36:37 PM UTC-5, awokd wrote:
> On Mon, January 8, 2018 12:54 am, russlyatos...@gmail.com wrote:
> 
> > For #2 As I see Whonix OS within Qubes OS will not bring any additional
> > benefits, more Cons than Pros? You would't recommend to install Whonix OS
> > into Qubes OS? Don't we already have Whonix OS in Qubes OS? - I see in my
> > Qubes right now "sys-whonix, whonix-gw, whonix-ws, anon-whonix which can
> > run Tor Browser" ?
> 
> Yes, I recommended you use Whonix/Tor. You might also want to add a VPN
> later, once you get a good understanding of the pros and cons.
> 
> >
> > For #3 I'm not sure if I understood your answer, maybe I worded it wrong,
> > I asked if I can run Tails on flash drive using Qubes OS installed on my
> > PC? Is it possible? Will it bring additional layer or security and
> > anonymity?
> 
> You can run Tails from inside Qubes (see
> https://www.qubes-os.org/doc/tails/) but again, there are trade-offs to
> that so it's a judgement call. Personally, I'd say use Qubes for
> everything and boot Tails separately off the USB drive when you want to
> use Tails. You might also want to check out Heads.

#2 Don't we already have Whonix OS in Qubes OS? - I see in my Qubes right now 
"sys-whonix, whonix-gw, whonix-ws, anon-whonix" is it Whonix OS or something 
else? Can ou elaborate a bit?

#3 I see. Thanks! I will read more about Heads.

-- 
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/a89af1f9-5706-4533-89e0-2a3a81b06df9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes 4 qvm-trim not exist

2018-01-07 Thread Roy Bernat

On Sunday, 7 January 2018 22:30:39 UTC+2, Andrew David Wong  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2018-01-07 12:48, Roy Bernat wrote:
> > Hi All ,
> > 
> > What is the best practice to trim disk inside qubes 4 .
> > 
> > the qvm-trim-template dont exist anymore .
> > 
> > R
> > 
> 
> You can use the `fstrim` command in the TemplateVM:
> 
> $ sudo fstrim -v /
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpSg2AACgkQ203TvDlQ
> MDAlIQ//dJsCrtqcQ5iOWiZd2iDmhGv/SlE0R4omxq8W6d4kUGJfhZ2mLbedoRBs
> 9nz4AqnQhfdOy8HLoYtAKXosO8dbEkZDDkQO6lTua0nUnrEEOar9r8QBuNWq8Ihe
> VQ97sIFAvxJ0Q4LAwiTjfp+8ciFcyzAbDOePsf+z9wGGanQuNxtGAep8FZkE8EWl
> 7LnA+9Kl4F24BwdsYLEVIlKhtcitHoGmn3vVzE/yZ7Ouyuzt4tNj3jkwh1n6KNT6
> aqiBIVsD/bqfaDANwxZyQxOPtigW63gm4t4EZZeVarjWNo1OsmFyuRJk+s6gIB5b
> 4Zez8QZgKiVwi/isSNLxRejJ8qMEkPHEMWIblQPVa9eBlUTEP6SFok7MRJY14TmQ
> qR+L5I7WT6OAXAujIrvw1phiAwW/uY5t2WGNdLXELk+M2ycBme4te5dV6hhuG6Iy
> f8ayZXwWg/cUHYGbWSLlTNAhf1L40VQ9EfaRYDoujZdwBt64YSO1Q2I09SZKkW2Z
> yRP0tHXENebaYnCRqPYyp5xE40uKcvggfRdHDVqlNukgnH4aXkl7P3153Yo/j7bj
> aCulOGO1PjRsEKPNNx4oT4fKB1GAGqX5cuaITkhAcbFX9Hbicw6y3AVnqSIk9Fee
> 15Sd+D297E6SgZ5rQdIVqymWsAYjd65BmYST9+xMq3+hpznjvOA=
> =BJL6
> -END PGP SIGNATURE-

Hi 

fstrim: /: the discard operation is not supported

-- 
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/95a217b7-c391-4222-967e-68bad4545b12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes freezing (hangs) always in less than 1 hour

On Mon, January 8, 2018 12:59 am, Sameer Vao wrote:
>  If you havent already, try running sudo
> qubes-dom0-update as soon as you get in to Qubes.Thank
> you awokd. I did but havent solved it.Im thinking something
> limiting memory or CPU may be the way to solve it, but may be something
> else.Any other ideas anybody?After much search and trials last 5
> days, still found nothing online to solve this problem. Another notebook
> not an option for me at this time unfortunately.If I cant fix it I
> will have to install another linux distribution - but that would be sad.
> Anybody else have other ideas so I can keep qubes? Thank
> you

If I remember right, you only have 4GB of RAM in the laptop, right? Qubes
minimum is really more like 8GB, 16+ is even better. You might be hitting
this issue https://github.com/QubesOS/qubes-issues/issues/3079, but more
severely than most because you are essentially out of memory as soon as
you boot up.

Also, can you set your email client to Plain Text mode? Not sure what it's
doing but it makes your messages hard to read.

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

Re: [qubes-users] Re: qubes 4 qvm-trim not exist

On Sunday, January 7, 2018 at 9:48:51 PM UTC+1, Tom Zander wrote:
> On Sunday, 7 January 2018 19:40:27 GMT Yuraeitha wrote:
> > But there are still some
> > issues, i.e. no visual interface to show your overall disk space useage
> > (the other month, you had to pull and combine several commands to make it
> > show accurately). I'm not sure if this disk space useage reporting issue
> > has been fixed today though.
> 
> * https://github.com/QubesOS/qubes-issues/issues/1872
> (open) Implement UI Notifications for cases of a Qube disk full 
> 
> * https://github.com/QubesOS/qubes-issues/issues/1053
> (open) Improve usability of VM disk space / increasing disk size
> 
> * https://github.com/QubesOS/qubes-issues/issues/3438
> (open) Qubes storage pools of type LVM issues
> 
> This one is closed, but as I point out in the collection of issues (3438) 
> this is not yet fixed;
> https://github.com/QubesOS/qubes-issues/issues/2016
> (closed) Create dom0 API to detect global disk space available
> 
> And, yeah, it also still needs  a user-interface.
> 
> 
> The simplest way to get the space usage if you are using a LVM based pool 
> (which requires completely manual setup at the moment) is
>   sudo lvs
> and you can read under the column "Data%" how much actual usage you reached.
> 
> -- 
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel

Neat collection you put together here, gives a better understanding where we 
are at indeed. I suppose (partly guessing here) that "sudo lvs" works for both 
"LVM" and "LVM Thin" FS-formats? I can only check LVM atm as I'm currently not 
using "LVM Thin".

As for discard to be supported, I suppose it has to be enabled during the 
mounting process, such as in the fstab? Thinking more align the need to solve 
the issue the original posters response regarding lack of discard support, up 
above. Could a solution really be that simple as to put it into the fstab 
though, or is there more to it?

-- 
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/cf9cfc9b-1e20-417c-8d43-a6347bdeb0d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes 4 qvm-trim not exist

2018-01-07 Thread Marek Marczykowski-Górecki

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jan 07, 2018 at 12:45:58PM -0800, Roy Bernat wrote:
> On Sunday, 7 January 2018 22:30:39 UTC+2, Andrew David Wong  wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > On 2018-01-07 12:48, Roy Bernat wrote:
> > > Hi All ,
> > > 
> > > What is the best practice to trim disk inside qubes 4 .
> > > 
> > > the qvm-trim-template dont exist anymore .
> > > 
> > > R
> > > 
> > 
> > You can use the `fstrim` command in the TemplateVM:
> > 
> > $ sudo fstrim -v /
> 
> Hi 
> 
> fstrim: /: the discard operation is not supported

Strange, it should work. And on my system it works...

Anything special in your configuration? Have you chosen non standard
partitioning or such?
Maybe you don't have LVM thin based storage? You can check that for the
template using (adjust template name):

qvm-volume ls fedora-26

The storage pool used will be in the first column, for example:

POOL:VOLUME   VMNAME VOLUME_NAME  
REVERT_POSSIBLE
linux-kernel:4.9.56-21fedora-26  kernel   No
lvm:qubes_dom0/vm-fedora-26-private   fedora-26  private  No
lvm:qubes_dom0/vm-fedora-26-root  fedora-26  root No
lvm:qubes_dom0/vm-fedora-26-volatile  fedora-26  volatile No

Here you see "lvm" pool.

If you want, you can dig further: qvm-pool -i lvm 

name  lvm
driverlvm_thin
size  486585401344
thin_pool pool00
usage 347665269260
volume_group  qubes_dom0

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpSoNgACgkQ24/THMrX
1yzwzgf/Wl7+PDptZ0i9HN5viuSmQk0W5EeBawQ9CIJHseCGAqPLLvRToSRPBF9f
vRPZv7HHAf0xoY7TPnBygjUAgb+u30rbGdpFafBwDugyzy8ojDLZvOZXgxaOiegn
M27tjwX6i6Wpc83gh+HwIB4ARJua2gBOS0ULDXJBZZ4y1WoVN0fvr3RiDRGWhpYH
1QutmKGR4Cwz0D1KoEP1qhCiew9BQ2NS1SSCk4dgncZcAnnSCrLR+9WDmirZRl2U
2AbxMdFXMvFfsmXCiTyq/dw3H0N9c6Litq0KPcowkXxhXx24vQo7fjLJGKpFrOEv
KuN+RRcMchphkF87AoVASm+G0rTzLA==
=DGsq
-END PGP SIGNATURE-

-- 
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/20180107223608.GA12450%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] hey, Please confirm we cannot install Qubes 4.0 on DVD, and the minimum on flash drive to install