Re: Re: [qubes-users] Q4rc4 :: qvm-prefs-screenshot-to-clipboard - 1st attempt

2018-02-18 Thread Yuraeitha
On Sunday, February 18, 2018 at 11:32:16 PM UTC+1, awokd wrote:
> On Sun, February 18, 2018 10:24 pm, Yuraeitha wrote:
> 
> > hmm, thinking about it, did you try awokd's approach?
> 
> He had but it wasn't working so I was just suggesting trying out a
> different command line option for xclip. Could be because it was in a
> different session or something, like you're saying.

@awokd 
Most likely yes, I haven't seen a command that can't be run from dom0 yet, it 
just need a little spanki'... Ahem, love. 

I haven't yet fully grasped why some commands behave different as they do when 
from dom0, compared to when same command is executed inside the AppVM. For 
example the bash example above. But I imagine, grasping this difference, one 
can probably execute anything from 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/d5e105c6-8007-48c7-9a60-303bdf4c5453%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Re: [qubes-users] Q4rc4 :: qvm-prefs-screenshot-to-clipboard - 1st attempt

2018-02-18 Thread 'awokd' via qubes-users
On Sun, February 18, 2018 10:24 pm, Yuraeitha wrote:

> hmm, thinking about it, did you try awokd's approach?

He had but it wasn't working so I was just suggesting trying out a
different command line option for xclip. Could be because it was in a
different session or something, like you're saying.


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


Re: Re: [qubes-users] Q4rc4 :: qvm-prefs-screenshot-to-clipboard - 1st attempt

2018-02-18 Thread Yuraeitha
On Sunday, February 18, 2018 at 1:11:58 AM UTC+1, [799] wrote:
> Hello awokd,
> 
>  Original-Nachricht 
> An 17. Feb. 2018, 23:41, 'awokd' via qubes-users schrieb:
> 
> > Can't really find a man page for xclip. What
> > happens when you run this in dom0? 
> 
> xclip doesn't have to be present in dom0 as the command is only used in the 
> AppVM.
> As such you might need to install it in your template VM.
> 
> In dom0 you are only using gnome-screenshot to make the screenshot.
> If it is not available in dom0 you can install it via qubes-dom0-update 
> gnome-screenshot or use any other existing sxreenshot-app which is available 
> in your dom0 and offers the option to safe screenshots directly to file.
> 
> Question regarding security:
> As far as I can tell I don't think that the suggested solution to transfer 
> screenshots to an AppVM offers a great security risk as the data is only 
> flowing from (!) dom0 to your AppVM and the graphic file is creating in dom0.
> But as I am far away from being a security expert, I'd like to hear a more 
> qualified feedback if working with this script might be a bad idea.
> 
> Regards
> 
> [799]

hmm, thinking about it, did you try awokd's approach? I do something very 
similar for my QubesTV setup that I'm working on polishing, which works on 
scripts too, like we're doing here. The command may have to be adjusted a bit, 
but in general, it should work, even without xclip in dom0. 

Actually, I'd go as far as to say it should most definitely work for xclip, 
while my scripts here are different, I've done it enough to tell it can work if 
modified correctly.

Either way, try awokd's command out, it will definitely work in one variant or 
different. The question is if require a bit of modification. For example, maybe 
use "qvm-run AppVM bash 'command to execute inside AppVM -o etc. lalala'" 
instead of say, "qvm-run AppVM gnome-terminal -e 'command to execute inside 
AppVM -o etc. lalala'". 

For example I've seen a case where one when executed inside the AppVM, will 
open the executed QubesTV streaming link in the same browser, same tab, while 
the very same command inserted into the AppVM from dom0, would open up a whole 
new instance of Firefox, and thereby open a new window. Which, needless to say, 
doesn't work. The solution was to use bash for already running firefox, so that 
it won't start a new firefox instance. Hopefully you can use any of this to 
make qvm-run appvm "command" work.

In terms of security, I'm in the same boat, I can't say for sure. But I agree 
with the notion, that it "probably"? is secure due to the one direction flow of 
data.

-- 
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/8bc85072-ac09-4ccc-8915-331ea300a33f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


AW: Re: [qubes-users] Q4rc4 :: qvm-prefs-screenshot-to-clipboard - 1st attempt

2018-02-17 Thread '[799]' via qubes-users
Hello awokd,

 Original-Nachricht 
An 17. Feb. 2018, 23:41, 'awokd' via qubes-users schrieb:

> Can't really find a man page for xclip. What
> happens when you run this in dom0?

xclip doesn't have to be present in dom0 as the command is only used in the 
AppVM.
As such you might need to install it in your template VM.

In dom0 you are only using gnome-screenshot to make the screenshot.
If it is not available in dom0 you can install it via qubes-dom0-update 
gnome-screenshot or use any other existing sxreenshot-app which is available in 
your dom0 and offers the option to safe screenshots directly to file.

Question regarding security:
As far as I can tell I don't think that the suggested solution to transfer 
screenshots to an AppVM offers a great security risk as the data is only 
flowing from (!) dom0 to your AppVM and the graphic file is creating in dom0.
But as I am far away from being a security expert, I'd like to hear a more 
qualified feedback if working with this script might be a bad idea.

Regards

[799]

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


[qubes-users] Q4rc4 :: SUCCESS qvm-screenshot-to-clipboard - 1st working version 0.1

2018-02-17 Thread '[799]' via qubes-users
Hello,

after some troubleshooting I can now present a working alpha-solution for copy 
& paste screenshots between dom0 and AppVMs.

You might have to install 2 packages:
xclip in your AppVM
gnome-screenshot in dom0

I had to tweak the xclip command a bit and now the script does exactly what it 
should do.

You also don't need to have a helper script within the AppVMs, just copy the 
script to dom0 and launch it with:

qvm-screenshot-to-clipboard

Then choose the area you want to screenshot and switch to your AppVM and paste 
it. There is an effect that the xclip command will wait until you pasted the 
image before the script continues.

But this is a nice thing as you can get two notification:

1) Screenshot is available in AppVMs Clipboard
2) Screennshot has been pasted from AppVMs clipboard.

Attention:

This script has mainly be made to provide a quick workarround and to get 
inter-VM screenshots working.

There is much improvement for error detection and also mabye usability 
improvements that the script can be launched without a command line argument, 
presenting a popup after the screenshot to which AppVM the screenshot should be 
placed.

Feel free to improve this, I'll upload the code to GitHub.

regards

[799]

 the script follows here ---

#!/bin/bash
# qvm-screenshot-to-clipboard
# Creates a dom0 screenshot and copy it to the Clipboard of an AppVM

# Define Variables
MyAppVM=$1
MyScreenshot=qvm-screenshot-to-clipboard.png

# Take screenshot in dom0 by selecting an area and adding border+shadow
gnome-screenshot --area --include-border --border-effect=shadow 
--file=/tmp/$MyScreenshot

# Copy screenhot to AppVM
qvm-move-to-vm $MyAppVM /tmp/$MyScreenshot

# Create a helper-Script in the AppVM to copy screenshot file to clipboard
echo "xclip -selection clipboard -l 1 -t image/png 
/home/user/QubesIncoming/dom0/$MyScreenshot" > /tmp/file2clipboard.sh
chmod +x /tmp/file2clipboard.sh
qvm-move-to-vm $MyAppVM /tmp/file2clipboard.sh
# Send notification for 5sec when Screenshot has been pasted into (!) AppVM
notify-send --urgency low --icon image --expire-time=5000 
"qvm-screenshot-to-clipboard" "Screenshot available in $MyAppVM's clipboard"
# Run the helper script in the AppVM
qvm-run $MyAppVM /home/user/QubesIncoming/dom0/file2clipboard.sh

### The last command will remain active until the pasting has been done in the 
AppVM

# Send notification for 5sec after Screenshot has been pasted from (!) AppVM
notify-send --urgency low --icon image --expire-time=5000 
"qvm-screenshot-to-clipboard" "Screenshot pasted from $MyAppVM's clipboard"

# Remove helper script and screenshot file in AppVM
qvm-run $MyAppVM "rm -f /home/user/QubesIncoming/dom0/file2clipboard.sh 
/home/user/QubesIncoming/dom0/$MyScreenshot"

--
Qubes 4rc3 > Lenovo X230
Qubes 4rc4 > Lenovo W540

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


qvm-screenshot-to-clipboard.sh
Description: Binary data


Re: [qubes-users] Q4rc4 :: qvm-prefs-screenshot-to-clipboard - 1st attempt

2018-02-17 Thread 'awokd' via qubes-users
On Sat, February 17, 2018 10:11 pm, '[799]' via qubes-users wrote:

> xclip -selection clipboard -t image/png
> /home/user/QubesIncoming/dom0/qvm-screenshot-to-clipboard.png

Can't really find a man page for xclip. What happens when you run this in
dom0?

qvm-run $MyAppVM 'xclip -t image/png
/home/user/QubesIncoming/dom0/qvm-screenshot-to-clipboard.png'


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


[qubes-users] Q4rc4 :: qvm-prefs-screenshot-to-clipboard - 1st attempt

2018-02-17 Thread '[799]' via qubes-users
Hello,

having the idea of a qvm-screenshot-to-clipboard script I was eager to try 
writting a script.
The solution I had in mind could work but I am struggling with a small issue 
and would like to get some help.
The script takes a screenshot in dom0, store it to a file and qvm-copy the file 
to the target appvm (one and only command line argument for the script).
Then within the AppVM it is using xclip to copy the graphic to clipboard and 
removes all temporary files in the AppVM and dom0
All pieces are working, except the xclip command when launced from dom0.

When I launch the command within the AppVM it is working.
But I need to start the xclip command from an external script and when I do so, 
the same command is not working.
It seems that I am missing something when using xclip via script which is run 
in a new terminal session (from dom0 but also within the App)

Any ideas how to fix this?
It feels so frustrating that I nearly have a working solution but I am missing 
the last few meters.

How to use the script:

1) in dom0: launch script

2) make the screenshot by selection the area

as the xclip is not working in the AppVM as supposed:

3) switch to the AppVM where the screenshot should be used

4) launch the "helper script" in the AppVM which is running the following 
command

xclip -selection clipboard -t image/png 
/home/user/QubesIncoming/dom0/qvm-screenshot-to-clipboard.png

My qvm-screenshot-to-clipboard script which has to be placed and run from dom0:

--- BEGIN of script ---

#!/bin/bash
# qvm-screenshot-to-clipboard
# Creates a dom0 screenshot and copy it to the Clipboard of an AppVM

MyAppVM=$1
MyScreenshot=qvm-screenshot-to-clipboard.png

# Take screenshot in dom0 by selecting an area and adding border+shadow
gnome-screenshot --area --include-border --border-effect=shadow 
--file=/tmp/$MyScreenshot

# Copy screenhot to AppVM command line argument / delete existing file

qvm-run $MyAppVM 'rm -f /home/user/QubesIncoming/dom0/$MyScreenshot'

qvm-copy-to-vm $MyAppVM /tmp/$MyScreenshot

###FIXME begin

# I would like to just invoke the following
# command via qvm-run in the AppVM
# but the clipboard is just empty when using
# this approach.
# running the same command
# xclip -selection clipboard -t image/png 
/home/user/QubesIncoming/dom0/qvm-screenshot-to-clipboard.png
# therof I have put the command into a helper
# script in my AppVM:
# qvm-run $MyAppVM /home/user/qvm-screenshot-to-clipboard-appvm.sh
# the script is working when it is launched from
# an already opened gnome-terminal window
# but it will not work when the script is invoked
# from dom0 via qvm-run or through an own
# strangely it is also not working when I start
# the script from within the appvm
# 'xterm -e

-- 
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/83oC6xNoYAsoP38eTDzM6CjCNyJlG0OG5UFNufeW4ID0bW0heejkX6oCffPAmI_LIKMVbelsQLxzboiwv3Rt-SM3Htd-rLsGgXSSi8jomnE%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Q4rc4 :: qvm-screenshot-to-clipboard (Was: Q4rc4 :: AppVM Screenshot-Tool only generates black window)

2018-02-17 Thread '[799]' via qubes-users
Hello,

I have made some research and it seems that it is not possible to make 
screenshots within one AppVM but only from dom0.

Having a short walk in our forest I came up with a great idea (at I think it is 
:-) which I would like to share to hear your opinions.

I know that there are some screenshot tools for Qubes like the 
qvm-screenshot-tool, which are trying to make the screenshot workflow easier 
when taking screenshots from dom0.

https://github.com/evadogstar/qvm-screenshot-tool/blob/master/README.md

I would like to have a tool, which makes a screenshot on dom0 (select area 
which should be screenshoted) then save this to a file, which gets qvm-copied 
to the AppVM I need the screenshot on and then copy the graphic file into the 
clipboard and delete the file afterwards.

This would make the workflow working with screenshots much easier.
It seems that something like "copy graphic file to clipboard" can be done:

https://askubuntu.com/questions/759651/how-to-copy-an-image-to-the-clipboard-from-a-file-using-command-line

xclip -selection clipboard -t image/png -i example.png

Can someone build a script in dom0 to do this?

qvm-screenshot-to-appvm-clip

- start

1) command to open a screenshot tool in dom0 with the possibility to select an 
area of the screen and make a screenshot.

2) after the taking the screenshot the screenshot is saved to a file on dom0 
(/tmp/screenshot-.PNG

3) qvm-copy-to-appvm  /tmp/screenshot-.PNG

4) qvm-run  "copy-picture-to-clipboard.sh screenshot-.PNG"

5) copy-picture-to-clipboard.sh is a script in the AppVM which copy the file 
from the Qubes-Incoming/dom0 directory into the clipboard
Maybe something like xclip mentioned here:
https://askubuntu.com/questions/759651/how-to-copy-an-image-to-the-clipboard-from-a-file-using-command-line

6) delete the screenshot in the AppVm

7) delete the screenshot in dom0

- end

What do you think? Wouldn't this feature be a great enhancement for working 
with Qubes?

[799]

--
Qubes 4rc3 > Lenovo X230
Qubes 4rc4 > Lenovo W540

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


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

2018-02-17 Thread David Hobach

On 02/17/2018 05:26 AM, WillyPillow wrote:

I did some timing, and for PVH, my Fedora 26 VMs take about 30s, while Debian 9 
takes about 45s. For HVM, qrexec usually times out (did not bother to adjust 
the timeout).


P.S.: I recall I had similar issues with HVM in 4.0rc1, cf. 
https://github.com/QubesOS/qubes-issues/issues/3149


So I think only your pvh timings are strange.

--
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/3ae83ff4-a174-9bc2-d6bd-ea6493a44308%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature


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

2018-02-16 Thread WillyPillow
 Original Message 
On 2018年2月17日 10:30, pixel fairy wrote:
On Friday, February 16, 2018 at 4:07:10 PM UTC-8, Marek Marczykowski-Górecki 
wrote:
> Yes, there is "xpti=false" option for Xen command line (xen.gz option in
> grub, or options= line in xen.cfg for UEFI).
tried that by editing the multiboot /xen-4.8.3.gz line while booting. no 
change. maybe its a different change between rc3 and rc4. seems like a stretch, 
but one that only affects supermicro c7z motherboards?

I did some timing, and for PVH, my Fedora 26 VMs take about 30s, while Debian 9 
takes about 45s. For HVM, qrexec usually times out (did not bother to adjust 
the timeout).

Just to clarify, my mobo is an ASRock Z170, not a Supermicro one.

--WillyPillow
--
https://blog.nerde.pw/
PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154  217F 1C16 C70E E7C3 1C8
--

-- 
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/feIj1otJTWDwda2aJVKqIsscwlqCmyDknsPVwOrKhcRXKZidQ0J6gyKrycBdVTYxQuOOUTF4KzOO8PnhdStxTn9CEbAASNZtxOCETNOchV8%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.


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

2018-02-16 Thread 'awokd' via qubes-users
On Sat, February 17, 2018 2:30 am, pixel fairy wrote:
> On Friday, February 16, 2018 at 4:07:10 PM UTC-8, Marek
> Marczykowski-Górecki wrote:
>
>
>> Yes, there is "xpti=false" option for Xen command line (xen.gz option
>> in grub, or options= line in xen.cfg for UEFI).
>
> tried that by editing the multiboot /xen-4.8.3.gz line while booting. no
> change. maybe its a different change between rc3 and rc4. seems like a
> stretch, but one that only affects supermicro c7z motherboards?

Try the Linux equivalent to disable mitigations in your template kernel
options too maybe?


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


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

2018-02-16 Thread pixel fairy
On Friday, February 16, 2018 at 4:07:10 PM UTC-8, Marek Marczykowski-Górecki 
wrote:

> Yes, there is "xpti=false" option for Xen command line (xen.gz option in
> grub, or options= line in xen.cfg for UEFI).

tried that by editing the multiboot /xen-4.8.3.gz line while booting. no 
change. maybe its a different change between rc3 and rc4. seems like a stretch, 
but one that only affects supermicro c7z motherboards?

-- 
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/8f3f5438-a930-4abb-9435-06adf92359e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2018-02-16 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Feb 16, 2018 at 11:37:46AM -, 'awokd' via qubes-users wrote:
> On Thu, February 15, 2018 2:24 am, pixel fairy wrote:
> 
> > at first i thought it was just the
> > performance hit from mitigating speculation vulnerabilities, but others
> > were reporting better performance in rc4 than rc3.
> 
> Maybe they are on AMD. :)
> 
> To rule out mitigations, I know Linux has an option to turn it off. Does
> Xen have something similar? Try that and see if it restores your
> performance.

Yes, there is "xpti=false" option for Xen command line (xen.gz option in
grub, or options= line in xen.cfg for UEFI).

- -- 
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/THMrX1ywFAlqHcg4ACgkQ24/THMrX
1ywm/gf/TBoqkz8zMaJS+oEvq3ezpydA9vc+NZVvxv+qYr4OKDq+BNIbhwRRV90Y
kPrEsBTLPhBhjA39RB37gjv3tkLj1pUMg/mZRFENbS6/QU3zIuOgylBdwLIGdTQf
sz56zdU9ypAYJfFGZhpj68c7PGyukG7pCdvG5c0kezwG30Xls1Cn221Nwxsc1zt1
kuIUehQuSKcv+v5upX6WS0rPii0Q6pUF734QtHaT41hLsFmdnXPc9bvMK9sEzwH7
EV4eiLzv3l3XiHlpB7y4I6THQnQSbjTdpU8eXN5LY7XLxrHqUUlfxQdXDgprKAFA
Tu/KTSFt9B9GFbv+uz+sGE5MiUmY5A==
=96W1
-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/20180217000646.GB8969%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


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

2018-02-16 Thread 'awokd' via qubes-users
On Thu, February 15, 2018 2:24 am, pixel fairy wrote:

> at first i thought it was just the
> performance hit from mitigating speculation vulnerabilities, but others
> were reporting better performance in rc4 than rc3.

Maybe they are on AMD. :)

To rule out mitigations, I know Linux has an option to turn it off. Does
Xen have something similar? Try that and see if it restores your
performance.

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


[qubes-users] Q4rc4 :: Fedora AppVM Screenshot-Tool only generates black window

2018-02-15 Thread '[799]' via qubes-users
Hello,

I am migrating most of my work tasks to Qubes but found out, that I can't use 
the screenshot tool in the Fedora based AppVM.

When I launch the screenshot tool, I can launch a screenshot, which covers 
another window are part of the screen with a window from the same AppVM, but 
the screenshot only result in a black copy, the content is not shown.

I am using a Fedora 26 AppVM based on the default Fedora template which comes 
with Qubes 4rc4.
I have updated the template to the latest version.

Can someone verify if this is a really a bug or what I need to do to get 
screenshots working.
Most of my work involved creating screenshots for troubleshooting and 
documentation.

Regards

[799]

--
Qubes 4rc4 > Lenovo X230 + Lenovo W540

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


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 2012 or so, i.e. your timings 
are rather odd indeed...


--
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/db5c1c2b-132f-bd76-7533-2aea051f430a%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature


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  217F 1C16 C70E E7C3 1C8
--

-- 
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/_u34bjS6AXj5CHBS0GgzGXhvql6dmV8Qa5ABa-NOi-JKjSal18usCoqxPpf01YSQp6FQ0vnvgGNIKUbKiyOrl_gjIrlgsRBW4K8iZGM7Lcc%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.


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 get back to you.

turns out the qvm-pref debug doesnt matter in boot time. its hvm that takes 
around 40 seconds, and pvh that takes around 25.

a standalone hvm with no os installed took 16 seconds to "start"

this started happening after installing 4.0rc4 over 4.0rc3. had to qvm-prefs 
the restored vms to pvh. at first i thought it was just the performance hit 
from mitigating speculation vulnerabilities, but others were reporting better 
performance in rc4 than rc3.

-- 
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/e15ed300-e888-4cbc-99a7-5ecc82323d8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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; Try switching the mode to hvm 
(and this let you use debug mode). Then there are logs in dom0 
/var/log/qubes for each VM.


On the VM side you can try 'systemd-analyze blame' for start timings, 
also 'journalctl' and 'dmesg'.



--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

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


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 
"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/7cc90ae0-f905-4f99-beef-90c3fc4dbc09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a025ca67-8aa1-4097-a096-372ec3e41fe3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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
sys 0m0.059s

starting with debug turned on takes 46 seconds. it shows a console window with

SeaBIOS
Machine UUID
Booting from ROM...
Probing EDD...

15 seconds for the console window to come up, with the first 3 lines
8 seconds later for Probing EDD to come up
23 seconds after that for the VM to start and the console window to go blank.



Is this Debian or Fedora? If the latter, can you try Fedora?

--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1e54cfd9-47a3-084a-7b3a-68d47b5e7bf3%40posteo.net.
For more options, visit https://groups.google.com/d/optout.


[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 on takes 46 seconds. it shows a console window with

SeaBIOS
Machine UUID
Booting from ROM...
Probing EDD...

15 seconds for the console window to come up, with the first 3 lines
8 seconds later for Probing EDD to come up
23 seconds after that for the VM to start and the console window to go blank.

-- 
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/a49c3481-a3c1-4147-8efe-47277079974e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Q4RC4

2018-02-02 Thread Shashank
Hi

I am trying to install qubes 4 on my xps 15 9560. I am getting this error where 
the installation stops, with error

Watchdog: BUG: soft lockup - cpu stuck for 22s[xorg:1325]

This goes on and on. Need help installing it. 

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/3bef4705-333d-4340-924e-c3fa222c56c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.