[qubes-users] Announcement: Recommended Fedora 25 TemplateVM Upgrade for Qubes 3.2

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Qubes Users,

Fedora 24, one of the supported TemplateVM versions in Qubes 3.2, is
scheduled to reach EOL (end of life) approximately one month after the
release of Fedora 26, which was on 2017-07-11. This places the
expected EOL date for Fedora 24 somewhere in the second week of August.

Options for migrating to Fedora 25 are now available for Qubes 3.2. If
you're currently using Fedora 24 (or older) TemplateVMs or
StandaloneVMs, we strongly recommend upgrading them to Fedora 25
before then. We provide step-by-step instructions for upgrading your
existing TemplateVMs and StandaloneVMs in-place here:

https://www.qubes-os.org/doc/template/fedora/upgrade-24-to-25/

We also provide fresh Fedora 25 TemplateVM packages through the official
Qubes repositories, which you can get with the following commands (in
dom0).

Standard Fedora 25 TemplateVM:

$ sudo qubes-dom0-update qubes-template-fedora-25

Minimal Fedora 25 TemplateVM:

$ sudo qubes-dom0-update qubes-template-fedora-25-minimal

After upgrading to a Fedora 25 TemplateVM, please remember to set all
qubes that were using the old template to use the new one. This can be
done in dom0 either with the Qubes VM Manager or with the `qvm-prefs`
command-line tool.

Please note that no user action is required regarding the OS version in
dom0. If you're using Qubes 3.2, there is no dom0 OS upgrade available,
since none is currently required. For details, please see here:

https://www.qubes-os.org/doc/supported-versions/#dom0

If you're using an older version of Qubes, we strongly recommend that
you upgrade to 3.2, as older versions are no longer supported.

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

iQIcBAEBCgAGBQJZfUNvAAoJENtN07w5UDAw04kQAL6Y1o3jn6QHyMYfVzR+E8rr
xA0Vi2xC26S6hcTXISG34O3QFwMzP6S36tDolUKNhnc4vllj3eqOrYF2SQK2Mzi4
T6EYteCot/l0EwDt3jWGmNm4cJay6n/WVrViH+8RCXWFpjEc9UsLEqCg0tLDm6dZ
CbhNWOpmiYTNNM1SRVqwS30gNjux45Z0eLK1Sp8A0YP+OrcVFCT5i34sSDFVJCOm
IeOIf6Kwg+IrlP9dVV5ZJcrvwcwgzFxUhA430j93W5RQ9K2h8eBrJXx7Tw7W4/tR
GebOhNfye+uODWeXanfMluvPTXAVP26hwAsz+mC1LVic1ITuQ4tJ0K4xeKfagF9J
1ZujpeYKZWbD1dyxy6bVge4WGow5lAto0CguVrP0ksxawquAHtONMOFvaAkIFWS1
Q3I4yNAzUZGs3epd3u+gKGhXxo42EkKKy9/eP0niOkW99zBPFO6FxKUJM3z2/Lzy
4zJIjdy8arXkRvKo2RbYLOrhDnXE6u3bfKwPVAo5yMU+vfNcOTqYzJE7So99uUsw
J8cKhFuwzaK2EsTE+Riksl7EzS89e5fv7sUHRBX/2K8GxhpdotXYN/slE0Jrz2Sc
ZXlbLNZAQy7Vo9syxxj0noLI1UG/LzwY7f5q1bH8SrCTukipebRHiHD1czoXFFJj
L0nZd4QKopnMPsMag3n/
=RuQT
-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/aebc9f9a-7baf-50e2-f298-74b9c759469f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes OS 3.2 NUC7i7BNH network driver issue

[Unman]

On Sat, Jul 29, 2017 at 01:42:50PM -0700, wannabeiron...@gmail.com wrote:
> On Thursday, July 13, 2017 at 4:14:54 PM UTC-4, Grzesiek Chodzicki wrote:
> > W dniu czwartek, 13 lipca 2017 20:34:15 UTC+2 użytkownik 
> > wannabe...@gmail.com napisał:
> > > NUC7i7BNH 32GB RAM 500GB M2
> > > 
> > > I was able to load Qubes 3.2 using a efi bootloader.
> > > 
> > > I am assuming with bleeding edge hardware that issues may pop-up here and 
> > > there.
> > > 
> > > My current issue is the ethernet driver in sys-net. 
> > > 
> > > lspci drivers are there and firmware version 
> > > 20160609-66.gita4bbc811.fc23.noarch.
> > > 
> > > "Dom0" dmesg output:
> > > 
> > > pciback: driver tried to write to read-only configuration space. (bolded, 
> > > not in red) See permissive attributes in sysfs.
> > > 
> > > At the moment I am not able to use sys-net when I assign a static or dhcp 
> > > IP.
> > > 
> > > Any help would be much appreciated.
> > 
> > https://www.qubes-os.org/doc/assigning-devices/
> > Go to possible issues and tr both fixes.
> 
> Tried both fixes with no luck.
> 
> kernelopts : nopat iommu=soft swiotlb=8192 (default)
> 
> pciback :XX:XX.X: enabling permissive mode configuration space accesses!
> permissive mode is potential unsafe!
> 
> xen_pciback: vpci: :XX:XX.X: assign to virtual slot 0
> 
> Still no wired network connection. 
> 

Intel only assert that Windows is supported.
There are no customer reports of Linux working on the NUC7i7BNH, but
there are reviews indicating success with Ubuntu 16.10 -  specifically ,
wifi and network working.
You don't say which Templates you have tried - I'm sure the base one
installed wont cut it. Try stretch or Fed25, or maybe build a zesty
from source - and you'll need a recent kernel - there's an ongoing
thread about this on the list

Good Luck

unman

-- 
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/20170729230116.euoqhwkgyj3ukknk%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes OS 3.2 NUC7i7BNH network driver issue

[wannabeironman]

On Thursday, July 13, 2017 at 4:14:54 PM UTC-4, Grzesiek Chodzicki wrote:
> W dniu czwartek, 13 lipca 2017 20:34:15 UTC+2 użytkownik wannabe...@gmail.com 
> napisał:
> > NUC7i7BNH 32GB RAM 500GB M2
> > 
> > I was able to load Qubes 3.2 using a efi bootloader.
> > 
> > I am assuming with bleeding edge hardware that issues may pop-up here and 
> > there.
> > 
> > My current issue is the ethernet driver in sys-net. 
> > 
> > lspci drivers are there and firmware version 
> > 20160609-66.gita4bbc811.fc23.noarch.
> > 
> > "Dom0" dmesg output:
> > 
> > pciback: driver tried to write to read-only configuration space. (bolded, 
> > not in red) See permissive attributes in sysfs.
> > 
> > At the moment I am not able to use sys-net when I assign a static or dhcp 
> > IP.
> > 
> > Any help would be much appreciated.
> 
> https://www.qubes-os.org/doc/assigning-devices/
> Go to possible issues and tr both fixes.

Tried both fixes with no luck.

kernelopts : nopat iommu=soft swiotlb=8192 (default)

pciback :XX:XX.X: enabling permissive mode configuration space accesses!
permissive mode is potential unsafe!

xen_pciback: vpci: :XX:XX.X: assign to virtual slot 0

Still no wired network connection. 

-- 
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/afbe4058-4148-4c8f-b907-8b6a0df8146c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] After Windows 10 Install, Qubes don´t Start/Boot

[pencilfight]

I stand corrected.  Windows 10 is mentioned in the documentation. I would give 
it a shot. Then no more dual booting and you can have an Win10 HVM template as 
well. 

https://www.qubes-os.org/doc/hvm

29. Jul 2017 09:37 by darkstrange...@gmail.com:


> Now i've installed qubes after, but now starts only qubes and i can't finde 
> win 10
>
> Am Samstag, 29. Juli 2017 schrieb pencilfight :
>
>>   >> I can certainly relate to the headache from dealing with 
>> something similar. >> I eventually came to the conclusion I had to decide 
>> which OS I truly was going to be using the most and did not dual boot.  This 
>> is great from a security standpoint and both OS's can be installed on a USB 
>> drive for the times you need your secondary OS. Hopefully HVM support for 
>> Win 10 comes soon. I'm quite impressed with my Win7 running in an HVM.  Best 
>> of luck!
>>
>>
>> 29. Jul 2017 07:46 by >> trip...@hackingthe.net>> :
>>
>>
>>>
>>> On 07/29/2017 04:40 AM, Franz wrote:
 On Fri, Jul 28, 2017 at 8:53 PM, < darkstrange...@gmail.com > 
 wrote:

> First i installed Qubes OS than Win 10, now is the Problem that Win starts
> but i cant start qubes os. Can anyone help me please?
>>>
>>> Your Qubes partitions might still be there...
>>> At least the boot loader was likely removed by Windows though, i.e. you'll 
>>> have to fix that using your favorite Live CD.
>>> For fresh installs Franz's solution below would work best.
>>>
 Well I do not know win 10, but previous Windows versions did not have any
 respect what is already installed and delete everything. If you want dual
 boot you need to install windows first and Qubes second, so Qubes will
 install Grub that will perform the OS election.

>>>
>>> -- 
>>> 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/e72a6d2d-8362-4a01-6fad-2021942b908d%40hackingthe.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/KqDkFBe--3-0%40tutanota.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Recommandations for storage configuration

[1sd2fec2oyiar77231ydf4bhwd46s99ykc01g2x155yxn9583mq6v52qx24fb58f]

So i have a 30~GB ssd and a 750GB hdd. Right now i am using the ssd as root and 
hdd as /home with luks on lvm for both. I only use DispVMs and a personal vm so 
I only have the DispVM template, personal vm and a debian-8 template on the ssd 
and others on the hdd I have about 7~GB space left on the ssd I decided to do 
some tests and these are the results:
(I did 3 tests for each and took the average all of the times are in seconds 
and DispVM template is debian-8 with no customizations and don't worry DispVM 
template was updated as well lastly I stopped the timer while I entered the 
luks password.)

 HDD    SSD
shutdown (with no vms running)--20~ 
--20~
start (no vms will start)--53~ 
--30~
dispvm start (time for a firefox to open)--40~ 
--8~
So the result seems that ssd greatly reduces vm startup times but it really 
doesn't help the os other than the start. Is that the case so I should install 
the root to hdd and just move frequently used vms to ssd? or is there a case 
that having the root on the ssd.
Oh and i don't really care about the faster start or shutdown times and a HCL 
report for my machine is coming I just need to test hdmi and some other things.

-- 
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/KqDdYAN--3-0%40tutanota.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] After Windows 10 Install, Qubes don´t Start/Boot

[David Hobach]

On 07/29/2017 04:40 AM, Franz wrote:

On Fri, Jul 28, 2017 at 8:53 PM,  wrote:


First i installed Qubes OS than Win 10, now is the Problem that Win starts
but i cant start qubes os. Can anyone help me please?


Your Qubes partitions might still be there...
At least the boot loader was likely removed by Windows though, i.e. 
you'll have to fix that using your favorite Live CD.

For fresh installs Franz's solution below would work best.


Well I do not know win 10, but previous Windows versions did not have any
respect what is already installed and delete everything. If you want dual
boot you need to install windows first and Qubes second, so Qubes will
install Grub that will perform the OS election.



--
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/e72a6d2d-8362-4a01-6fad-2021942b908d%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [qubes-users] Bootloader not installed on USB

[Nero]

Thank you!
But I already quit Qubes installation program and "chrooot /mnt/sysimage" do 
nothing. And I can not find files like "/boot/efi/EFI/qubes/xen.cfg" to edit on 
my installation USB. Actually when mounted under OSX it contains only one file: 
"/Volumes/Linux HFS+ ESP/EFI/qubes/xen-4.6.1.efi"

Do I have to run installation again or there is a way to fix bootloader on my 
USB without running installation?
I'm pretty new to UNIX systems so exact command would be helpfull, thank you!

> On Fri, Jul 28, 2017 at 6:48 AM, Nero  wrote:
> > I'm installing Qubes on Macbook Air.
> > I partitioned (EFI, Macos journalled) my SSD but Qubes installer do not see 
> > any partitions on SSD but see my 32GB USB stick.
> > 1. Why I can not install on SSD?
> >
> > Ok, trying to install on USB goes ok until message like "boot loader can 
> > not be written" at the end of installation.
> > Trying to boot with this installations get me to "grub>" only.
> >
> > Can I fix my USB somehow? Maybe I can write bootloader manually?
> 
> In case you haven't seen it already, have you read through the MacBook
> troubleshooting page [1], particularly the sections "4. Fix GRUB
> configuration", and "5. Fix bootloader"?
> 
> [1]: https://www.qubes-os.org/doc/macbook-troubleshooting/
> 
> Regards,
> Jean-Philippe

-- 
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/83256940-0bb0-43e3-b607-d5cdd13fa00e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Bootloader not installed on USB

[Nero]

Thank you!
But I already quit Qubes installation program and "chrooot /mnt/sysimage" do 
nothing. And I can not find files like "/boot/efi/EFI/qubes/xen.cfg" to edit on 
my installation USB. Actually when mounted it contains only one file: 
"/Volumes/Linux HFS+ ESP/EFI/qubes/xen-4.6.1.efi"

Do I have to run installation again or there is a way to fix bootloader on my 
USB without running installation?


> On Fri, Jul 28, 2017 at 6:48 AM, Nero  wrote:
> > I'm installing Qubes on Macbook Air.
> > I partitioned (EFI, Macos journalled) my SSD but Qubes installer do not see 
> > any partitions on SSD but see my 32GB USB stick.
> > 1. Why I can not install on SSD?
> >
> > Ok, trying to install on USB goes ok until message like "boot loader can 
> > not be written" at the end of installation.
> > Trying to boot with this installations get me to "grub>" only.
> >
> > Can I fix my USB somehow? Maybe I can write bootloader manually?
> 
> In case you haven't seen it already, have you read through the MacBook
> troubleshooting page [1], particularly the sections "4. Fix GRUB
> configuration", and "5. Fix bootloader"?
> 
> [1]: https://www.qubes-os.org/doc/macbook-troubleshooting/
> 
> Regards,
> Jean-Philippe

-- 
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/a8bd069c-b541-41b8-9eef-180e2b500a82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: After Windows 10 Install, Qubes don´t Start/Boot

[Foppe de Haan]

On Saturday, July 29, 2017 at 1:53:10 AM UTC+2, darkstr...@gmail.com wrote:
> First i installed Qubes OS than Win 10, now is the Problem that Win starts 
> but i cant start qubes os. Can anyone help me please?

I've not had this problem myself, but if you google for grub bootloader windows 
guide, I'm sure you'll find other people who have had the same issue -- windows 
overwriting it, and their having to restore 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/53af28cf-8a93-4df5-b65b-5d9d6476b9a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: *REQ* INVITE CODE RISEUP.NET

[qubester]

On 07/28/2017 03:54 AM, little help wrote:

You can email me on backtracesec[@]mail.com and I will give you one. I dont 
want to post it on public forum.


Here are terms and conditions:
 Trust: Give invite codes only to people you know.
 Privacy: We retain a list of whom you have invited, but only for a limited 
time.
 Abuse: We will close your account if you give an invite code to someone 
who sends Spam or Phishing emails.



Correct me if I'm wrong this ISN'T qubes related,  so   should not be 
posted to the Qubes forum .


--
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/50c4e236-b1bc-5539-715b-500d158d66c2%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] After Windows 10 Install, Qubes don´t Start/Boot

[qubester]

On 07/28/2017 04:40 PM, Franz wrote:

On Fri, Jul 28, 2017 at 8:53 PM, 
 wrote:


First i installed Qubes OS than Win 10, now is the Problem that Win starts
but i cant start qubes os. Can anyone help me please?



Well I do not know win 10, but previous Windows versions did not have any
respect what is already installed and delete everything. If you want dual
boot you need to install windows first and Qubes second, so Qubes will
install Grub that will perform the OS election.



Did you see the dual boot section in the Docs, assuming that is what you 
are saying is the problem???


Did you have windows set up to boot off UEFI  or  "legacy boot", if 
UEFI, which may be likely,  then  my understanding is the dual boot 
won't work,  maybe windows10 needs to be booting in legacy mode, but 
make an effort to read the Docs section, if you haven't,   and maybe be 
bit more effusive .:P


--
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/87ea5a22-d85d-9733-93f5-f4a1bd3caf65%40riseup.net.
For more options, visit https://groups.google.com/d/optout.