[qubes-users] Re: HCL - HP ProBook 6565b

2018-02-14 Thread tsdelude
On Saturday, January 13, 2018 at 11:15:20 PM UTC-6, tsde...@gmail.com wrote: > Type - Notebook > HVM - Yes > IOMMU - No > SLAT - Yes > TPM - Yes, present but untested > Brand - HP > Model - ProBook 6565b > BIOS - Tried 68LTU Ver F.22 and F.64 > CPU - AMD A4-3310MX > GPU - AMD Radeon HD 6480G >

[qubes-users] Re: Disk quota exceeded (when installing templates)

2018-02-14 Thread kveselnitskaya
On Saturday, February 4, 2017 at 11:51:08 AM UTC-5, john.david.r.smith wrote: > hi. > when using salt to install templates, i came across this error: > > Sending application list and icons to dom0 > Complete! > The downloaded packages were saved in cache until the next successful > transaction.

[qubes-users] R4 rc4 - Whonix System Time Error

2018-02-14 Thread 'sebuq' via qubes-users
The virgin whonix templates issue with official Qubes R4 rc4 downloads did not result in errors via whonixcheck. However after updating the whonix-gw template a get the following system time error: ERROR: Systemd Clock Check Result: Unexpected results by timedatectl. timedatectl_output_pretty:

Re: [qubes-users] Re: Win7, qvm-copy-to-vm, QubesIncoming location?

2018-02-14 Thread Ivan Mitev
On 02/13/2018 10:34 PM, brendan.h...@gmail.com wrote: On Tuesday, February 13, 2018 at 2:06:59 PM UTC-5, brenda...@gmail.com wrote: On Friday, March 3, 2017 at 1:36:35 PM UTC-5, Martin L. Fällman wrote: Does the issue still occur after You change the default Windows user in Qubes settings?

Re: [qubes-users] can't install fail2ban or sshguard

2018-02-14 Thread Matus
thank you for help. it was exactly as you said. i just installed only fail2ban server package and set it up and it works correctly with iptables. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving

Re: [qubes-users] If you get 'no authenticators available' with mutt

2018-02-14 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, Feb 10, 2018 at 01:33:53PM -, 'awokd' via qubes-users wrote: > On Fri, February 9, 2018 5:32 pm, Konstantin Ryabitsev wrote: > > If you are trying to use mutt with the default Fedora-26 template and > > can't figure out why authenticated

Re: [qubes-users] 4.0-rc3: sys-net not getting updated template OS image?

2018-02-14 Thread Steve Coleman
On 02/13/18 14:54, awokd wrote: On Tue, February 13, 2018 6:32 pm, Steve Coleman wrote: I have a strange situation where my sys-net's software template "fedora-26-net" (variant of fedora-minimal) does not appear to be providing updated OS images. My sys-net is the only vm using this specific

Re: [qubes-users] can't install fail2ban or sshguard

2018-02-14 Thread Ivan Mitev
On 02/14/2018 04:39 PM, Matus wrote: Hello, I'm using qubes os 3.2 with official template fedora 26 minimal. I tried installing fail2ban or sshguard but i get following error: dnf install fail2ban Failed to set locale, defaulting to C Fedora 26 - x86_64 - Updates

[qubes-users] can't install fail2ban or sshguard

2018-02-14 Thread Matus
Hello, I'm using qubes os 3.2 with official template fedora 26 minimal. I tried installing fail2ban or sshguard but i get following error: dnf install fail2ban Failed to set locale, defaulting to C Fedora 26 - x86_64 - Updates 10 MB/s |

Re: [qubes-users] 4.0-rc3: sys-net not getting updated template OS image?

2018-02-14 Thread Rusty Bird
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Steve Coleman: > I have a strange situation where my sys-net's software template > "fedora-26-net" (variant of fedora-minimal) does not appear to be providing > updated OS images. My sys-net is the only vm using this specific image. Assuming that

Re: [qubes-users] can't install fail2ban or sshguard

2018-02-14 Thread Ivan Mitev
On 02/14/2018 05:42 PM, Matus wrote: thank you for help. it was exactly as you said. i just installed only fail2ban server package and set it up and it works correctly with iptables. you're welcome - happy to read you worked it out. ivan -- You received this message because you are

[qubes-users] Re: Building Centos template conflict error?

2018-02-14 Thread fepitre
Le mercredi 14 février 2018 06:30:37 UTC+1, Tim W a écrit : > On Tuesday, February 13, 2018 at 5:07:32 PM UTC-5, Frédéric Pierret (fepitre) > wrote: > > Le mardi 13 février 2018 15:47:38 UTC+1, Tim W a écrit : > > > I was having issues building Centos template for 4.0 so I decided to > > > first

[qubes-users] Re: R4 rc4 - Whonix System Time Error

2018-02-14 Thread brendan . hoar
On Wednesday, February 14, 2018 at 5:33:03 AM UTC-5, sebuq wrote: > The virgin whonix templates issue with official Qubes R4 rc4 downloads > did not result in errors via whonixcheck. However after updating the > whonix-gw template a get the following system time error: > > ERROR: Systemd Clock

[qubes-users] Re: HCL - HP ProBook 6565b

2018-02-14 Thread tsdelude
I think this model can be safely marked as not supporting IOMMU and thus a No for Qubes 4.0, if that is indeed a hard requirement for 4.x. I'm not sure if there should be more Qubes 3.2 testing. -- You received this message because you are subscribed to the Google Groups "qubes-users" group.

Re: [qubes-users] Salt management questions

2018-02-14 Thread Johannes Graumann
On Mon, 2018-02-12 at 17:04 +0100, Johannes Graumann wrote: > On Wed, 2018-02-07 at 15:27 +0100, Johannes Graumann wrote: > > Gentlepeople, > > > > For a while I have been managing a qubes setup using a dedicated > > management VM and ansible via https://github.com/Rudd-O/ansible-qub > > es > > .

Re: [qubes-users] 4.0-rc3: sys-net not getting updated template OS image?

2018-02-14 Thread Rusty Bird
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Steve Coleman: > Here is the sys-net . I re-wraped the xml to make it a little > more readable in email: > > > pool="lvm" > revisions_to_keep="0" > size="21474836480" >

[qubes-users] Re: Building Centos template conflict error?

2018-02-14 Thread fepitre
Le mercredi 14 février 2018 06:30:37 UTC+1, Tim W a écrit : > On Tuesday, February 13, 2018 at 5:07:32 PM UTC-5, Frédéric Pierret (fepitre) > wrote: > > Le mardi 13 février 2018 15:47:38 UTC+1, Tim W a écrit : > > > I was having issues building Centos template for 4.0 so I decided to > > > first

Re: [qubes-users] Re: Setting up privateinternetaccess on qubes 3.2

2018-02-14 Thread Chris Laprise
On 02/13/2018 05:23 PM, vel...@tutamail.com wrote: Thanks Chris(and "tasket"!)took me a few tries but I managed to get it going, I tweaked the implementation a bit(scarey). I was not however able to get this command going from step #3 of the Github guide: sudo

Re: [qubes-users] Re: Win7, qvm-copy-to-vm, QubesIncoming location?

2018-02-14 Thread brendan . hoar
On Wednesday, February 14, 2018 at 3:32:18 AM UTC-5, Ivan Mitev wrote: > On 02/13/2018 10:34 PM, Brendan Hoar wrote: > > On Tuesday, February 13, 2018 at 2:06:59 PM UTC-5, brenda...@gmail.com > > wrote: > >> On Friday, March 3, 2017 at 1:36:35 PM UTC-5, Martin L. Fällman wrote: > Does the

Re: [qubes-users] Re: Setting up privateinternetaccess on qubes 3.2

2018-02-14 Thread velcro
Thank you Tasket\Chris... Thanks for the education on trust/veracity/trustworthiness with Github. You and the Qubes team are doing a good thing! I really appreciate all the help... Thank you! V -- You received this message because you are subscribed to the Google Groups "qubes-users"

[qubes-users] Re: Ubuntu templates

2018-02-14 Thread Bertrand Lec
Le jeudi 1 février 2018 00:56:29 UTC+1, Unman a écrit : > I'm just pushing up some PRs to remove zesty and institute build support > for artful (17.10). > If you cant wait there's a ready built 3.2 template you can try at: > http://qubes.3isec.org/Templates > > unman Thank you a lot for your

[qubes-users] q4rc4 very slow. VMs take 23 - 33 seconds to start

2018-02-14 Thread pixel fairy
[user@dom0 ~]$ time qvm-start personal real0m23.517s user0m0.182s sys 0m0.065s [user@dom0 ~]$ time qvm-start alpha real0m23.801s user0m0.191s sys 0m0.056s [user@dom0 ~]$ time qvm-start alphax real0m32.831s user0m0.193s sys 0m0.059s starting with debug turned

Re: [qubes-users] 4.0-rc3: sys-net not getting updated template OS image?

2018-02-14 Thread Steve Coleman
On 02/14/18 12:14, Rusty Bird wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Steve Coleman: I have a strange situation where my sys-net's software template "fedora-26-net" (variant of fedora-minimal) does not appear to be providing updated OS images. My sys-net is the only vm using

Re: [qubes-users] q4rc4 very slow. VMs take 23 - 33 seconds to start

2018-02-14 Thread Chris Laprise
On 02/14/2018 05:47 PM, pixel fairy wrote: [user@dom0 ~]$ time qvm-start personal real0m23.517s user0m0.182s sys 0m0.065s [user@dom0 ~]$ time qvm-start alpha real0m23.801s user0m0.191s sys 0m0.056s [user@dom0 ~]$ time qvm-start alphax real0m32.831s user0m0.193s

Re: [qubes-users] q4rc4 very slow. VMs take 23 - 33 seconds to start

2018-02-14 Thread pixel fairy
Fedora. just tried debian. 44.286s seconds. -- 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

Re: [qubes-users] q4rc4 very slow. VMs take 23 - 33 seconds to start

2018-02-14 Thread pixel fairy
On Wednesday, February 14, 2018 at 4:58:06 PM UTC-8, pixel fairy wrote: > Fedora. just tried debian. 44.286s seconds. Forgot the hardware. i7-6700, 64gigs ddr4, supermicro c7z170-sq, onboard intel graphics. -- You received this message because you are subscribed to the Google Groups

Re: [qubes-users] q4rc4 very slow. VMs take 23 - 33 seconds to start

2018-02-14 Thread WillyPillow
I also noticed similar slowdowns. I have no experience with rc3 (upgraded directly from 3.2), but your numbers seem to councide with my experience. Hardware is also pretty similar, namely Z170/6700K. --WillyPillow -- https://blog.nerde.pw/ PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154

[qubes-users] R4.0 rc4 Back-up Bug

2018-02-14 Thread 'sebuq' via qubes-users
Backups via the Control Panel fail with the message unable to find the directory. However using qvm-backup via Dom0 CLI works fine. Is it me, or is this bug on a list to be fixed at some point in the future? -- You received this message because you are subscribed to the Google Groups

Re: [qubes-users] q4rc4 very slow. VMs take 23 - 33 seconds to start

2018-02-14 Thread Chris Laprise
On 02/14/2018 08:00 PM, pixel fairy wrote: On Wednesday, February 14, 2018 at 4:58:06 PM UTC-8, pixel fairy wrote: Fedora. just tried debian. 44.286s seconds. Forgot the hardware. i7-6700, 64gigs ddr4, supermicro c7z170-sq, onboard intel graphics. What virt_mode is used? Default is pvh;

[qubes-users] Re: HCL - HP ProBook 6565b

2018-02-14 Thread tsdelude
Tried Qubes 4.0-rc4 VM's won't boot, likely due to lack of IOMMU. I could not change the Kernel or VT mode to PV from the GUI. I didn't try via terminal. = Qubes Release 4.0 (R4.0) Brand: Hewlett-Packard Model: HP ProBook 6565b BIOS: 68LTU Ver. F.22 Xen: 4.8.3 Kernel:

Re: [qubes-users] q4rc4 very slow. VMs take 23 - 33 seconds to start

2018-02-14 Thread David Hobach
On 02/15/2018 02:00 AM, pixel fairy wrote: On Wednesday, February 14, 2018 at 4:58:06 PM UTC-8, pixel fairy wrote: Fedora. just tried debian. 44.286s seconds. Forgot the hardware. i7-6700, 64gigs ddr4, supermicro c7z170-sq, onboard intel graphics. Got 13s with pvh on a laptop last built in

Re: [qubes-users] q4rc4 very slow. VMs take 23 - 33 seconds to start

2018-02-14 Thread pixel fairy
pvh. the hvm ones took even longer. looked at a couple systemd-analyze, one of them had 10s for dkms and 40 for qubes-update-check, even though that one only took 25s to boot, at least according to dom0. could whatever tells dom0 a guest is up have run before that? will play with this more and

[qubes-users] Re: Building Centos template conflict error?

2018-02-14 Thread Tim W
On Wednesday, February 14, 2018 at 11:46:32 AM UTC-5, Frédéric Pierret (fepitre) wrote: > Le mercredi 14 février 2018 06:30:37 UTC+1, Tim W a écrit : > > On Tuesday, February 13, 2018 at 5:07:32 PM UTC-5, Frédéric Pierret > > (fepitre) wrote: > > > Le mardi 13 février 2018 15:47:38 UTC+1, Tim W