[qubes-users] Re: Start failed: 'qubes.devices.UnknownDevice object' has no attribute 'device_node'

2017-12-14 Thread jordylc1998 
On Thursday, November 30, 2017 at 1:30:28 AM UTC-8, quenti...@gmail.com wrote:
> Trying to create an HVM for tails 3.3 in 4.0-rc3 (upgraded from rc2).
> 
> Fails on the `qvm-start HVM_tails-3_3 
> --cdrom=untrusted1:/home/user/Downloads/tails.iso` step in the 
> https://www.qubes-os.org/doc/tails/ write up.
> 
> The  throws the error.
> 
> This comes from a vm.devices.block.assignments(True) call in xen.xml.

I have the same exact issue but with win7

-- 
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/d87e0501-58f8-4cd9-9365-f4db3dc7c0e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-12-14 Thread pub08goog 
OK, here is (I hope) a *public* version of said screen shot:
https://photos.google.com/share/AF1QipMRlHUC5EOV-PQD5kfWWfCp9BDroAHDXGAFdWcq_SrmJhfhnHHOF6ZvYU7-JenLOA?key=MlJxWFRyZm1OTHBnWXpHd1pfUXNVYzJjMmJsTlRR

(Just learning Google Photo, Google+, gmail, etc., for purposes of this post.  
Until now I've been able to avoid them :-/ )

  - Eric

-- 
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/f44e144a-c45e-43a0-84f0-1ca61905bce8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-12-14 Thread Eric Siegerman 
Here's a screenshot of the above-described boot error:
https://photos.google.com/photo/AF1QipMO-vL-kcyiORVEZ5P4ydjpdBJwwzzTZ00JuNm1

On Thu, Dec 14, 2017 at 10:04 PM,  wrote:

> > Does anyone have an idea what the difference livecd-iso-to-disk make,
> > compared to isohybrid? If possible, we'd like to installation iso work
> > out of the box on UEFI systems, including new ones...
>
> No, but I have what seems like another data point.  On my Lenovo
> T520 under UEFI, trying to boot the 4.0rc3 installer produces
> similar symptoms: whichever option I choose from the grub menu,
> the screen goes blank briefly (I didn't measure, but probably
> <2sec), then comes back to the grub menu.  Repeat ad nauseam.
>
> But if I try the same thing from EFI Shell (version 1, because my
> UEFI firmware's too old to support version 2), I get this:
> Read failed for initrd.img: Device error
> fs1:\EFI\BOOT># i.e. it comes right back to the shell prompt
>
> And sure enough, when I try again from grub, I can *sometimes*
> see a very brief flash of purple before the grub menu returns.  I
> suspect that Qubes/Xen is displaying the same message, but then
> grub is clearing the screen too quickly for me to read it.
>
> Details:
>   - Hardware: Lenovo T520, model 4239-CTO (this laptop was bought
> in 2012, and has been happily running Ubuntu in UEFI mode
> ever since)
>
>   - BIOS: 8AET56WW (1.36 ) 12/06/2011
>   - I think the UEFI version is 2.0, but not totally sure
>
>   - TPM *disabled* (one thing at a time, y'know?)
>
>   - I'm not using USB, but rather a real DVD+R, burned directly
> from the (signature-verified) .iso
>
>   - I've verified the DVD media against the original .iso image
> *after* seeing these symptoms, which suggests it isn't an
> actual media error
>
> So, two things:
>   - If this is helpful (and it's a solvable problem), awesome!
>
>   - I'd suggest adding a "Hit  to continue" (perhaps with
> timeout) after a failed boot attempt, to keep any error
> message on screen for a while
>
> > I wonder if Fedora netinst iso (_not_ Live iso) boot on such new
> > hardware, after directly dd-ing it to USB stick. Can you check that?
>
> I already have :-)  Fedora 27 netinst (again, signature-verified
> and burned to optical media) boots successfully.  I aborted the
> installer at its first (language) prompt.  I was't sure which
> Fedora version 4.0rc3 contains, so picked the newest; if you'd
> like me to test an older one, please let me know -- or if you
> need more information (including a reboot to verify the UEFI
> version).
>
>   - Eric
>
> --
> 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/TEmVIozLJh0/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/c0576e3b-9a58-458f-92fb-3dda8540033f%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/CABRujHQiUkBQ0pGWJh9GGk5PTNNiYYPGFsT3rQ4-adzN2efUFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-12-14 Thread pub08goog 
> Does anyone have an idea what the difference livecd-iso-to-disk make,
> compared to isohybrid? If possible, we'd like to installation iso work
> out of the box on UEFI systems, including new ones...

No, but I have what seems like another data point.  On my Lenovo
T520 under UEFI, trying to boot the 4.0rc3 installer produces
similar symptoms: whichever option I choose from the grub menu,
the screen goes blank briefly (I didn't measure, but probably
<2sec), then comes back to the grub menu.  Repeat ad nauseam.

But if I try the same thing from EFI Shell (version 1, because my
UEFI firmware's too old to support version 2), I get this:
Read failed for initrd.img: Device error
fs1:\EFI\BOOT># i.e. it comes right back to the shell prompt

And sure enough, when I try again from grub, I can *sometimes*
see a very brief flash of purple before the grub menu returns.  I
suspect that Qubes/Xen is displaying the same message, but then
grub is clearing the screen too quickly for me to read it.

Details:
  - Hardware: Lenovo T520, model 4239-CTO (this laptop was bought
in 2012, and has been happily running Ubuntu in UEFI mode
ever since)

  - BIOS: 8AET56WW (1.36 ) 12/06/2011
  - I think the UEFI version is 2.0, but not totally sure

  - TPM *disabled* (one thing at a time, y'know?)

  - I'm not using USB, but rather a real DVD+R, burned directly
from the (signature-verified) .iso

  - I've verified the DVD media against the original .iso image
*after* seeing these symptoms, which suggests it isn't an
actual media error

So, two things:
  - If this is helpful (and it's a solvable problem), awesome!

  - I'd suggest adding a "Hit  to continue" (perhaps with
timeout) after a failed boot attempt, to keep any error
message on screen for a while

> I wonder if Fedora netinst iso (_not_ Live iso) boot on such new
> hardware, after directly dd-ing it to USB stick. Can you check that?

I already have :-)  Fedora 27 netinst (again, signature-verified
and burned to optical media) boots successfully.  I aborted the
installer at its first (language) prompt.  I was't sure which
Fedora version 4.0rc3 contains, so picked the newest; if you'd
like me to test an older one, please let me know -- or if you
need more information (including a reboot to verify the UEFI
version).

  - Eric

-- 
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/c0576e3b-9a58-458f-92fb-3dda8540033f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] USB Mouse not detected after last upgrade on 3.2

2017-12-14 Thread Adrian Rocha 
I found the problem.
When I updated the template I uninstalled Thunderbird, and the qubes-usb-proxy 
and other related tools are considered unused dependencies. I think that this 
is a bug in the template. I solved the issue installing the necessary packages.

$ sudo dnf remove thunderbird
Dependencies resolved.
==
 Package  Arch   Version Repository 
 Size
==
Removing:
 thunderbird  x86_64 52.4.0-2.fc26   @updates   
157 M
Removing dependent packages:
 python-backports-ssl_match_hostname
  noarch 3.5.0.1-4.fc26  @fedora
 18 k
 python2-crypto   x86_64 2.6.1-14.fc26   @fedora
2.2 M
 python2-cryptography x86_64 2.0.2-2.fc26@updates   
2.6 M
 python2-jinja2   noarch 2.9.6-1.fc26@fedora
3.6 M
 python2-pyOpenSSLnoarch 16.2.0-6.fc26   @updates   
523 k
 python2-requests noarch 2.13.0-1.fc26   @fedora
409 k
 python2-tornado  x86_64 4.4.2-3.fc26@fedora
3.9 M
 python2-urllib3  noarch 1.20-1.fc26 @fedora
536 k
 python2-zmq  x86_64 16.0.2-3.fc26   @fedora
1.6 M
 qubes-mgmt-salt-vm-connector
  noarch 3.2.5-1.fc26
@qubes-builder-vm-r3.2-current-testing 4.7 k
 qubes-vm-recommended noarch 3.2.3-1.fc26
@qubes-builder-vm-r3.2-current-testing   0  
 salt noarch 2017.7.2-1.fc26 @updates   
 36 M
 salt-ssh noarch 2017.7.2-1.fc26 @updates   
3.0 k
 thunderbird-qubesx86_64 1.2.9-1.fc26
@qubes-builder-vm-r3.2-current-testing  11 k
 zeromq   x86_64 4.1.6-3.fc26@fedora
671 k
Removing unused dependencies:
 PyYAML   x86_64 3.12-3.fc26 @fedora
646 k
 dnf-utilsnoarch 2.1.5-1.fc26@updates   
3.8 k
 libtomcrypt  x86_64 1.17-31.20160123git912eff4.fc26
 @updates   
824 k
 libtommath   x86_64 1.0-8.fc26  @updates   
106 k
 libyaml  x86_64 0.1.7-2.fc26@fedora
121 k
 openpgm  x86_64 5.2.122-8.fc26  @fedora
317 k
 python-backports x86_64 1.0-9.fc26  @fedora
638  
 python-chardet   noarch 2.3.0-3.fc26@fedora
1.1 M
 python-enum34noarch 1.1.6-1.fc26@fedora
232 k
 python-ipaddress noarch 1.0.16-4.fc26   @fedora
227 k
 python2-asn1crypto   noarch 0.23.0-1.fc26   @updates   
924 k
 python2-babelnoarch 2.3.4-5.fc26@fedora
 20 M
 python2-backports_abcnoarch 0.5-3.fc26  @fedora
 30 k
 python2-futures  noarch 3.1.1-1.fc26@fedora
 91 k
 python2-idna noarch 2.5-1.fc26  @fedora
563 k
 python2-markupsafe   x86_64 0.23-13.fc26@fedora
 83 k
 python2-msgpack  x86_64 0.4.8-3.fc26@fedora
272 k
 python2-pysocks  noarch 1.6.7-1.fc26@updates   
 79 k
 python2-singledispatch   noarch 3.4.0.3-7.fc26  @fedora
 46 k
 python2-systemd  x86_64 234-1.fc26  @fedora
262 k
 pytz noarch 2016.10-4.fc26  @fedora
185 k
 qubes-core-vm-docnoarch 3.2.20-1
@qubes-builder-vm-r3.2-current-testing 2.2 k
 qubes-gpg-split  x86_64 2.0.26-1.fc26   
@qubes-builder-vm-r3.2-current-testing  59 k
 qubes-img-converter  x86_64 1.2.3-1.fc26
@qubes-builder-vm-r3.2-current-testing 6.5 k
 qubes-input-proxy-sender x86_64 1.0.10-1.fc26   
@qubes-builder-vm-r3.2-current-testing  18 k
 qubes-pdf-converter  x86_64 2.1.2-1.fc26
@qubes-builder-vm-r3.2-current-testing  15 k
 qubes-usb-proxy  noarch 1.0.11-1.fc26   
@qubes-builder-vm-r3.2-current-testing 7.7 k

Transaction Summary

[qubes-users] Re: Fedora25 fails updates unless I reboot the machine 9.13.17

2017-12-14 Thread Gustavo Lapido Loureiro 
On Wednesday, September 13, 2017 at 7:49:35 PM UTC-3, qubester wrote:
> Fedora25 fails updates unless I reboot the machine 9.13.17
> 
> 2 or 3 times now, are others having this problem?  is there some 
> particular remedy or  just  let it go?
> 
> "failed to syncronize cache"

I confirme the issue too.
Running Qubes 3.2 on a Dell N4050

-- 
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/7191b317-87b1-487e-80e6-b6fa6623ed54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Ethernet-to-USB Adapter

2017-12-14 Thread Sven Semmler 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 12/12/2017 05:27 AM, taii...@gmx.com wrote:
> You can simply assign disable sys-usb then assign the USB
> controllers to sys-net via the VM manager. Please note that any non
> PCI-e network interface is going to be have terrible performance
> and high CPU usage.

This did the trick! I needed it only once for an initial run of
qubes-dom0-update ... now all my networking hardware works.

Thank you!

I will post a detailed description of all steps I had to follow and a
HCL soon.

/Sven

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJaMva7AAoJENpuFnuPVB+2tPoP/AgTdpVs3wGky0KHQ+ZRNcbe
1SF7onbrTQCLVKe9utlNXXoV/lphhrJVxK3BFGtzpDItOQdXaiangVgw/O/URKhR
OXFOLp01A8i0gHXb6PwCniqPVdJHzx18+EAjougXpVjZP2KCvA1uMxCGs4fSG9EM
9Y+0To9LtbUjklCXxWLzhogGmocbcSYhGTvufR3g5NUAzTVIxeV7fDaTLGOUtJ5b
GbvRQ7qsXY1BcTJqAMibXs85+FvvNRHscD72wL6g38bM1Bg9RTPr4DLPFCFRihpu
H+/pVgXLBDdvjVFJhApiXRqR1854MUHBToJxXOgCr6Q6tHzTfijT+BclK8hSRVJN
ZYN73x3oU6RIx97GGoIip5XwBtuFFlIx6qTweU6xyLw5g9Rkx1h3zRgKqSizfwUa
LC1SCyZRWIK5MI8dopqNYocSwxsz6Y5QZ0BwEzfYNZhdQU5LbsArRP5l21BT17kZ
W/DRdhZdauVnVNlZHDxhLeCN3CL1PWFFzSpyJoq3f/mHtJR9Zrt0ituaAYHlC/kV
7tabfsn5utPUGgOCOzH9fpf8TmGLTivin4p1OSMQsM51PquYoONaZuW53FNPbkMf
OlAzXhsFt0J+qN8r5FL+rvfEr0mJB/7Ef3KS8SdEsUrSnucy0eOuiHDEkKQvMM2H
zibG4jnjH+epGnRA79et
=zJ88
-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/cd30b827-2683-7a25-3c53-9c974c142012%40SvenSemmler.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] USB Mouse not detected after last upgrade on 3.2

2017-12-14 Thread Adrian Rocha 
> That's a wireless mouse isn't it and what you see there is the USB
> receiver? You may be right that it isn't triggering the input proxy.
> 
> When you say "upgrade" do you mean that or simply "update"? I mean are
> you still running 3.2?
> What template are you using for the sys-usb? What were you using before?
> 
> unman

Right, it is a wireless Mouse. I see the receiver

Sorry, it was just an update. I am using fedora-26 template. Using this same 
template was working fine before the dom0 & template update.
The rest of usb devices like usb drives or network adapter are working fine and 
recognized by the Qubes manager.

-- 
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/dc16e217-ddc8-478b-abce-9de03f1f07c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Unable to start VM after renaming in Qubes Manager

2017-12-14 Thread Unman 
On Thu, Dec 14, 2017 at 08:59:06PM -, joonas.lehto...@openmailbox.org wrote:
> Hello,
> 
> it looks like I got hit by a severe problem that prevents me from starting an 
> appvm
> 
> 
> I searched the bugtracker and it looks like:
> 
> https://github.com/QubesOS/qubes-issues/issues/2054
> 
> I also renamed a VM and it no longer starts.
> 
> The folder under 
> /var/lib/qubes/appvms/oldname 
> is still present.
> 
> What is the easiest way to get access to the data stored in that VM?
> 
> thanks!
> Joonas

The data is stored in the private.img file in that folder.

You can either create a new qube, and then attach the file:
qvm-block -A  dom0:/var/lib/qubes/appvms/oldname /private.img
then mount /dev/xvdi in , and extract the data from
/mnt/home/user
OR: mount the private.img file in dom0 and qvm-copy the data files to some qube.
OR: create a new qube, and copy the private.img file to 
/var/lib/qubes/appvms/new

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

[qubes-users] Unable to start VM after renaming in Qubes Manager

2017-12-14 Thread joonas . lehtonen 
Hello,

it looks like I got hit by a severe problem that prevents me from starting an 
appvm


I searched the bugtracker and it looks like:

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

I also renamed a VM and it no longer starts.

The folder under 
/var/lib/qubes/appvms/oldname 
is still present.

What is the easiest way to get access to the data stored in that VM?

thanks!
Joonas

-- 
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/20171214205906.22D684E772C%40mta-1.openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: What are the disadvantages of NOT having vt-d?

2017-12-14 Thread Matteo 
> I see.. But currently I am using Qubes 3.2 and 4.0 last time I tried was
> VERY unpolished, I am not sure I am going to look at it before support
> for 3.2 expires...

Same here, and my pc doesn't have vt-d nor slat (second level addres
tranlation); both required for Qubes 4

> It's not like I would not have the money to buy a 7700k, but I want to
> avoid spending money if not necessary that is why I want to get a clear
> picture...

As far as i know, you can't just replace the cpu to get vt-d (IOMMU);
also the chipset and the bios must have proper support so changing the
cpu only might be a waste of money.
There was a discussion about finding a notebook with proper support
https://groups.google.com/forum/#!topic/qubes-users/Sz0Nuhi4N0o

vt-d protect from dma (direct memory access) attacks.
for a demo take a look at "inception" that works via firmware interface.
i have personally tested against a windows xp and worked (from what i
have read, newer os are protected against this *specific* attack).
it protect you from bad/exploited dma devices like network card.
net vm is used for both ethernet and wifi.

for your use case (almost anyone use case) you don't need vt-d but we
are starting to see succesful attacks against network interfaces, and
thanks to the hard work of Qubes OS team and that genius person Joanna
Rutkovska we have that extra protection for free.

-- 
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/3e5c2e86-63ad-74bd-c8e3-44bd6974dec9%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Q4R3 - debian-stable

2017-12-14 Thread Unman 
On Thu, Dec 14, 2017 at 09:56:23AM +0100, Johannes Graumann wrote:
> On Thu, 2017-12-14 at 01:51 -0500, haaber wrote:
> > Thank you both for comments. That must be a *very* slow boot, it is
> > up
> > for 12h now, and still no xterm available, neither via qubes-menu,
> > nor
> > via qvm-run in dom0 :)) Anyhow, it seems better to download the
> > template.
> > 
> > How to you get the template name? I could not find any helpful doc on
> > it, so  I tried guessing the names by browsing deb.qubes-os.org for
> > the
> > debian branch or yum.qubes-os.org, but this did not help either.
> > 
> > I ask because I'd like to get a fedora-x-minimal or a debian-9-
> > minimal
> > as strating point for sys-net or sys-usb with minimized attack
> > surface.
> > Bernhard
> > 
> > 
> > 
> > On 12/13/2017 02:00 PM, Chris Laprise wrote:
> > > On 12/13/2017 11:02 AM, Westley Argentum Hennigh-Palermo wrote:
> > > > On Tuesday, December 12, 2017 at 3:14:17 PM UTC-5, haaber wrote:
> > > > > Hello,
> > > > > I cloned the out-of-the-box debian-8 and brought it to debian-9 
> > > > > with
> > > > > apt-get distupgrade. I halted it. After reboot no way to get a
> > > > > shell, or
> > > > > anything else (not by qvm-run within dom0 either). Is there a
> > > > > way to get
> > > > > error messages somewhere?  Thank you, Bernhard
> > > > 
> > > > Hey, I'd also be interested to know more about getting detailed
> > > > debugging info, maybe someone can comment on that... but things I
> > > > do
> > > > know that might be helpful:
> > > > 
> > > > - You can get a debian 9 template by running: `sudo qubes-dom0-
> > > > update
> > > > qubes-template-debian-9` (see docs here:
> > > > https://www.qubes-os.org/doc/templates/debian/)
> > > > 
> > > > - There are some vm logs available at `/var/log/qubes/`
> > > > 
> > > 
> > > There is issue #2913 about very long boot delay for debian-9. This
> > > means
> > > you have to wait about 2min. before starting programs. A fix is in
> > > the
> > > works, and a workaround is deleting an @service link like so:
> > > 
> > > sudo rm /etc/systemd/system/multi-
> > > user.target.wants/wpa_supplicant@.service
> > > 
> > 
> > 
> 
> Have a look at https://ftp.qubes-os.org/repo/yum/r4.0/templates-itl/rpm
> /
> 
> Sincerely, Joh
> 

Or in dom0 run:
sudo qubes-dom-update --action="list available qubes*"

or even more particularly:
sudo qubes-dom-update --action="list available qubes-template*"


Using --action allows you to pass in other dnf commands, rather than
just using for update/install.

You'll see there are a number of Fedora minimal templates, but no
Debian.
The absence of a Debian-minimal is a long standing issue, and you will
have to roll your own for now.

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

Re: [qubes-users] install of 4.0 rc3 failing on XPS 15 (9560)

2017-12-14 Thread Mike Keehan 
On Mon, 11 Dec 2017 02:45:23 -0800 (PST)
Piers Saye  wrote:

> Dell XPS 15 (9560) 1TB 32GB HiRes Touchscreen
> 
> 3.2 running fine with the previously documented fixes.
> 
> 
> When I try and install 4.0 rc3 the installer hangs often prior to
> getting to the GUI installer with a soft lock on CPU #7
> 
> 
> When it does proceed further I am able to get through the various
> screens to the point of actual installation however it gets to action
> (797/1018) qubes-mgmt-salt-base-topd.noarch and then hangs with
> system freeze.
> 
> Any thoughts or anyone that has experienced the same or ideas?
> 

Hi Piers,

I had the same problems with my XPS 9560.

I managed to get Qubes 4.0-rc3 installed by adding the option
"modprobe.blacklist=nouveau" to the installer's boot command line.

It is all running fine now.

Mike.

-- 
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/20171214170029.12f0a423.mike%40keehan.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] USB Mouse not detected after last upgrade on 3.2

2017-12-14 Thread Adrian Rocha 
Hi,

After the last upgrade of Qubes + QubesVMs my usb mouse is not working.
If I run lsusb in sys-usb I can see the device, but apparently is not detected 
as a mouse, I think.

[user@sys-usb ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 8087:8000 Intel Corp. 
...
Bus 002 Device 009: ID 04f2:0976 Chicony Electronics Co., Ltd 
...


The dom0 file /etc/qubes-rpc/policy/qubes.InputMouse has the line for the 
device:
sys-usb dom0 allow,user=root

I restarted the VM and the host machine but the problem persists.

Which could be the reason?

-- 
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/4c079309-4dd9-4e73-896f-740e327fd629%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AW: Re: [qubes-users] Qubes 4rc3 :: 50% reduced battery runtime compared to Qubes 3.2 on Lenovo X230

2017-12-14 Thread 'MirrorWay' via qubes-users 
Another partial workaround, you can change virt_mode from hvm back to pv for 
trustworthy VMs, like vault, etc...

The bug: https://github.com/QubesOS/qubes-issues/issues/2849

For me it amounts to an overhead of 10% x cpu core per hvm, according to xentop.

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

Re: AW: Re: [qubes-users] Qubes 4rc3 :: 50% reduced battery runtime compared to Qubes 3.2 on Lenovo X230

2017-12-14 Thread donoban 

On 12/13/2017 07:30 PM, '[799]' via qubes-users wrote:

Hello Chris,

 Original-Nachricht 
An 13. Dez. 2017, 19:15, Chris Laprise schrieb

 > Increased CPU usage is a known issue.
 > You can see it in the 'xentop' listing.
 > This may be one of the core tradeoffs
 > when moving to R4.0

I'll run the test on Q4rc3 and Q3.2 which will hopefully help 
investigating this problem.


On which level is the increased CPU generated? If this is happening on 
the AppVM level. This would mean that I should get a better runtime when 
running only dom0, correct?

Of course this is only meant for investigating this issue.


Try playing with xenpm

Using: 'xenpm set-scaling-governor powersave' I win between 20min and 1h 
depending on the CPU load (with an average runtime of 3-4h)


--
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/9bca29b7-6896-7bae-0135-ee719f10e758%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes OS and latest hardware (8700K)

2017-12-14 Thread 'Chris' via qubes-users 
Hi,

will Qubes OS 3.2 work with the 8700K desktop CPU that was just released? I've 
heard conflicting reports. If not, will 4.0 support it? I read that you need 
Kernel 4.12 (I believe) but even Qubes 4.0 seems to be stuck with 4.8...

Is this just a matter of "perfect" support or are they talking about not even 
running on 8700K with a lower kernel version?

The same question popped up for the new DELL XPS, which runs then 8th gen 
mobile CPUs. I guess the support question is similar here?!

Thanks!

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