[qubes-users] Someone should port this RDP Windows windower thing for Qubes

2020-11-30 Thread Guerlan

This project:
https://github.com/Fmstrat/winapps/ 

does what Qubes do to Linux and Windows 7, but to Windows 10 on KVM, by 
using RDP. Not the best approach but no one is working on the Windows 10 
port of the windowing thing. Maybe some people could work on porting this 
to Qubes, and maybe some prople from Qubes could direct funds to this. 
I even opened an issue about this:
https://github.com/Fmstrat/winapps/issues/112
I miss using Windows properly when I work on Qubes.
Would be nice if people from here could make some noise there to bring 
attention :)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/39bf30aa-dcbd-41b4-9ad8-233afff4c59an%40googlegroups.com.


Re: [qubes-users] ARM in Qubes OS

2020-11-20 Thread Guerlan
but Xen runs on ARM

On Wednesday, November 18, 2020 at 6:06:49 AM UTC-5 haa...@web.de wrote:

> On 11/16/20 3:55 PM, load...@gmail.com wrote:
> > *So, the question is the same: Are there plans to support ARM processors
> > in Qubes OS in the future?
>
> no woman, no cry - and no xen, no qubes :)
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e52f743a-0e0e-4937-a550-00b84c762960n%40googlegroups.com.


[qubes-users] How to recover files from a broken qubes pertition on ubuntu live CD?

2020-11-20 Thread Guerlan
My Qubes worked great but after a day it suddenly wouldn't boot and I got 
an error about qubes_dom0 root or something like that being not available. I

I mounted, on Ubuntu live CD, a LUKS partition that has these lvm 
containers from Qubes OS:


ubuntu@ubuntu:~$ sudo lvs
  LV VG Attr   
LSizePool   Origin Data%  
Meta%  Move Log Cpy%Sync Convert
  pool00 qubes_dom0 twi---tz-- 
<452.86g
 
 
  root   qubes_dom0 Vwi---tz-- 
<452.86g 
pool00  

 
  swap   qubes_dom0 
-wi-a-
8.96g   
  
 
  vm-anon-whonix-private qubes_dom0 
Vwi---tz--2.00g 
pool00  

 
  vm-bitpay-private  qubes_dom0 
Vwi---tz--2.00g pool00 
vm-bitpay-private-1604634684-back   
 
 
  vm-bitpay-private-1604634684-back  qubes_dom0 
Vwi---tz--2.00g 
pool00  

 
  vm-debian-10-private   qubes_dom0 
Vwi---tz--2.00g 
pool00  

 
  vm-debian-10-root  qubes_dom0 
Vwi---tz--   10.00g pool00 
vm-debian-10-root-1604634337-back   
 
 
  vm-debian-10-root-1604634337-back  qubes_dom0 
Vwi---tz--   10.00g 
pool00  

 
  vm-debian-sys-net-private  qubes_dom0 
Vwi---tz--2.00g pool00 
vm-debian-sys-net-private-1600569197-back   
 
 
  vm-debian-sys-net-private-1600569197-back  qubes_dom0 
Vwi---tz--2.00g 
pool00  

 
  vm-debian-temp-private qubes_dom0 
Vwi---tz--2.00g 
pool00  

 
  vm-debian10-coding-private qubes_dom0 
Vwi---tz--2.00g 
pool00  

 
  vm-debian10-coding-rootqubes_dom0 
Vwi---tz--   10.00g pool00 
vm-debian10-coding-root-1604634103-back 
 
 
  vm-debian10-coding-root-1604634103-backqubes_dom0 
Vwi---tz--   10.00g 
pool00  

 
  vm-default-mgmt-dvm-privatequbes_dom0 
Vwi---tz--2.00g 
pool00  

 
  vm-fedora-29-dvm-private   qubes_dom0 
Vwi---tz--2.00g 
pool00  

 
  vm-fedora-29-private   qubes_dom0 
Vwi---tz--2.00g 
pool00  

 
  vm-fedora-29-root  qubes_dom0 
Vwi---tz--   10.00g pool00 
vm-fedora-29-root-1599172317-back   
 
 
  vm-fedora-29-root-1599172317-back  qubes_dom0 
Vwi---tz--   10.00g 
pool00  

 
  vm-hacking-private qubes_dom0 
Vwi---tz--   20.00g pool00 
vm-hacking-private-1602069716-back  
 
 
  vm-hacking-private-1602069716-back qubes_dom0 
Vwi---tz--   20.00g 
pool00  

 
  vm-multipurpose-privatequbes_dom0 
Vwi---tz--   11.00g pool00 
vm-multipurpose-private-1589207893-back 
 
 
  vm-multipurpose-private-1589207893-backqubes_dom0 
Vwi---tz--   11.00g 
pool00  

 
  vm-orwell3-private qubes_dom0 Vwi---tz--  
137.00g pool00 
vm-orwell3-private-1602465727-back  

[qubes-users] Anyone has network problems when downloading fastly?

2020-11-20 Thread Guerlan

Whenever I download a file too fast, the network stops and I have to 
deactivate and activate again in the tray icon. Sometimes it even displays 
no network (with an x). I already tried moving from 4.0.1 to 4.0.3, tried 
creating a brand new sys-net based on debian 10 with the latest driver 
(same problem persists), and also tried something about setting a memory 
usage on the sys-net vm, don't remember exactly. 
Also I get lots of errors downloading files, I have to retry the download 
many times, probably a lot of corruption.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2fdbb75a-0e49-4e2b-b98b-4826ca6434bbn%40googlegroups.com.


[qubes-users] Android Studio 4.x unusable on Qubes due to qubes windowing system (maybe)

2020-07-24 Thread Guerlan
After moving from Android Studio 4.0.1, I noticed that all submenus open 
like you see in the image, with a little color between them. 

Looks like Android Studio/Intellij Idea opens them in a different way in 
this new version, so Qubes treats them differently, maybe considering them 
as little windows. 

Because of this, the autocomplete feature (very essential) isn't work.
Please see the video of the autocomplete/autoimport (alt enter) not working
https://drive.google.com/file/d/1t8fcEGdsDX1v5zEk2fHqRib9eQpeDLg0/view?usp=sharing

Anyone knows how to solve this? I cannot downgrade Android Studio

My qubes is Qubes 4.0.1 

Image of how it opens the submenus now: https://i.stack.imgur.com/spvc7.jpg 
(this submenu works, but the ones in the video do not)

There's an already open issue here:

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

but nothing about fixing 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7e577d5f-fa96-43ad-8860-c40343912887n%40googlegroups.com.


[qubes-users] Constant firefox crashes because of Qubes shared memory

2020-04-24 Thread Guerlan
I started having constant firefox crashes on my debian9 Qube. I sent the 
crash reports to firefox and the said that the problem occurs because of 
the shared memory configuration of Qubes, but he don't know how it's 
configured.

Can somebody help me fixing this? How can I enlarge the shared memory?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9a79daa0-7351-4ce0-b75f-b3f23ffe921a%40googlegroups.com.


[qubes-users] where is qubesd source?

2020-04-18 Thread Guerlan
I'm reading qubes-core-admin python source code and it opens a socket 
connection to qubesd. What is it? Where can I find its source?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/768141e2-99af-4095-97b4-e9662379b337%40googlegroups.com.


[qubes-users] How to disable or set the qrexec timeout for more than 60 seconds? getting halted because "cannot connect to qrexec agent for 60 seconds"

2020-04-16 Thread Guerlan
"Domain windows10 failed to start (after 60 seconds using it): cannot 
connect to qrexec agent for 60 seconds"


After installing qubes-windows-tools, it failed on moving the users folder 
to the D disk. I followed a guide: 
https://www.tenforums.com/tutorials/1964-move-users-folder-location-windows-10-a.html
 
but after doing it, it reboots. Upon startup, the windows keeps loding 
(possibly moving the folder, I don't know). Then, since it wont start in 
less than 60 seconds, Qubes closes it by saying 60 seconds has passed and 
it couldn't communicate with qrexec. Sometimes it happens even if the 
windows is up, I guess the windows qrexec fils to load sometimes.

Anyways, setting it to 0 by doing


qvm-features windows10 qrexec 0


has no effect

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8a66afb1-132f-415d-9642-e7114f8f397a%40googlegroups.com.


Re: [qubes-users] Which version of Xen does Qubes uses? Shouldn't it support OVMF already (HVM EFI boot)?

2020-04-13 Thread Guerlan


On Monday, April 13, 2020 at 8:13:18 PM UTC-3, awokd wrote:
>
> Guerlan: 
>
> > Can you tell me more about what is QEMU/stubdomain? Do you know of any 
> > reasons for them to not compile xen with efi boot support? 
>
> I meant to say libvirt (https://wiki.xen.org/wiki/Libvirt) more than 
> QEMU. Qubes uses libvirt calls to interact with Xen. Sometimes Xen 
> specific functionality (possibly OVMF as an example) aren't coded into 
> libvirt, so Qubes can't use that functionality without direct Xen calls. 
> I think they try to avoid those, in general. On top of that, the Qubes 
> utilities may not surface the option, even if it's available in Libvirt. 
> Different hard drive controllers are an example. It can be added, but 
> would take a programmer to add it to the layers. 
>
> -- 
> - don't top post 
> Mailing list etiquette: 
> - trim quoted reply to only relevant portions 
> - when possible, copy and paste text instead of screenshots 
>


Please take a look at: https://github.com/QubesOS/qubes-issues/issues/5767

I asked and somebody said there's support.

I activated it, it almost worked.

On Windows it booted to the Windows logo and then stayed that way forever 
(with high CPU usage)

On Linux it passed the "try ubuntu without installing" but then halted

If you know how to debug that, it'd be great

I'm trying to understand all of this out of curiosity but maybe I can make 
it work, who knows

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/59f51d2e-af11-4753-a7e4-ec70447e4689%40googlegroups.com.


[qubes-users] anyone can help debugging hidden EFI HVM boot option on Qubes?

2020-04-13 Thread Guerlan


I'm on a quest to make macOS run under Qubes. This repo: 
https://github.com/foxlet/macOS-Simple-KVM does this for KVM with minimal 
effort, using a python tool that downloads a macOS base image through 
python directly from apple servers. This base image is responsible for 
downloading and installing the rest of the macOS. Anyone can do it!

This post 
 
is the only one I found that teaches how to install macOS on Qubes, but 
it's for Qubes 3, requires too much effort, and we have to trust someone's 
else macOS image. The main problems he addresses to install Qubes are:

   - 
   
   Qubes 3 didn't have support for EFI boot (macOS only boots through EFI 
   now), so he does a hack that allows him to boot through USB in legacy mode.
   - 
   
   Xen had some bugs while running macOS, 2 patches were added
   - 
   
   There are some incompatibility problems with qemu-xen and qemu upstream 
   had to be used on some parts
   - 
   
   Some kexts are needed
   
Well, turns out Qubes now has support for EFI boot on HVM mode, as a 
developer told me here: 
https://github.com/QubesOS/qubes-issues/issues/5767#issuecomment-612551107

I enabled it and tried to boot Windows 10 and Ubuntu 18.

Windows 10 kinda boots: the Windows logo appears, but then the CPU gets 
high (like 90%) all the time and nothing more hapens.

Ubuntu 18 also kinda boots: I can select the "try ubuntu without 
installation", but after that, the VM halts.

I think that if we can solve this EFI boot problem, we can easily put the 
qcow2 image generated from the macOS-Simple-KVM repository to run under 
Qubes. They already have the kexts needed for Qemu, and we can try to make 
those 2 macOS xen patches land on Qubes Xen tree, or check if they didn't 
already land.

I'm learning about OVMF  in order to 
debug what happens when we try to boot into HVM EFI mode. Anyone have 
knowledge about this? If it boots but hangs or halts, then could it be that 
OVMF is working but something in Xen is broken?

I'm also reading Qemu source code. I can pass what I learned so far, and we 
can try to understand it better.


Please fell free to call me on github or comment things here about OVMF, 
Xen, Qemu, etc.

I have a macOS running under KVM rigth now on my other computer but I 
really wanted it to run Qubes. So why not try and learn a lot in the 
process?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8c33c835-e566-4471-88b4-7110c8b47ee7%40googlegroups.com.


[qubes-users] Where can I find the .cfg file for my VMs in qubes?

2020-04-11 Thread Guerlan
I found

/var/lib/qubes/appvms

has folders for each VM, but inside each folder there's only firewall.xml 
and icon.png

where can I find the .cfg file that xen uses? And how can I start these VMs 
using this .cfg? I want to do some xen tests

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/361d61bb-2b84-4bd9-a61a-91189b9bec0c%40googlegroups.com.


Re: [qubes-users] Domain win10 failed to start (after 60 seconds using it): cannot connect to qrexec agent for 60 seconds

2020-04-11 Thread Guerlan


On Friday, April 10, 2020 at 5:48:39 PM UTC-3, awokd wrote:
>
> Guerlan: 
> > 
> > 
> > My Qubes is closing my windows 10 VMs which are based on my Win10 
> template 
> > after 60 seconds, even though they are ok. It says 
> > 
> > 
> > Domain win10 failed to start: cannot connect to qrexec agent for 60 
> seconds 
> > 
> > 
> > even though it already had started and I was using it. 
> > 
> > 
> > It happened after I installed qubes-windows-tools 
> > 
> Sounds like they didn't install right. In dom0 terminal, check: 
> qvm-features win10 
> "Qrexec" is probably set to 1. Try removing with: 
> qvm-features win10 qrexec '' 
>
> -- 
> - don't top post 
> Mailing list etiquette: 
> - trim quoted reply to only relevant portions 
> - when possible, copy and paste text instead of screenshots 
>

Ok so I did

qvm-features win10 qrexec 0

and then 

qvm-features win10 

and it shows 0

but it still quits with the same error after 60 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/82fa4f68-5016-497b-9b3e-74ba9ec99e2e%40googlegroups.com.


Re: [qubes-users] Which version of Xen does Qubes uses? Shouldn't it support OVMF already (HVM EFI boot)?

2020-04-11 Thread Guerlan


On Friday, April 10, 2020 at 5:40:10 PM UTC-3, awokd wrote:
>
> Guerlan: 
> > Xen 4.4 has support for OVMF. Which version of Xen does Qubes uses? 
> > Shouldn't it already have this option? 
> > 
> "xl info" in dom0 will tell you exactly. Mine says 4.8.5-14. Xen might 
> be able to support it (although looks like it's not in the default 
> build), but not the Qubes or QEMU/stubdomain tooling on top of Xen. 
>
> -- 
> - don't top post 
> Mailing list etiquette: 
> - trim quoted reply to only relevant portions 
> - when possible, copy and paste text instead of screenshots 
>

Can you tell me more about what is QEMU/stubdomain? Do you know of any 
reasons for them to not compile xen with efi boot support?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fd4f68a4-4702-4ba2-8242-5c08b961074a%40googlegroups.com.


Re: [qubes-users] Domain win10 failed to start (after 60 seconds using it): cannot connect to qrexec agent for 60 seconds

2020-04-11 Thread Guerlan


On Friday, April 10, 2020 at 5:48:39 PM UTC-3, awokd wrote:
>
> Guerlan: 
> > 
> > 
> > My Qubes is closing my windows 10 VMs which are based on my Win10 
> template 
> > after 60 seconds, even though they are ok. It says 
> > 
> > 
> > Domain win10 failed to start: cannot connect to qrexec agent for 60 
> seconds 
> > 
> > 
> > even though it already had started and I was using it. 
> > 
> > 
> > It happened after I installed qubes-windows-tools 
> > 
> Sounds like they didn't install right. In dom0 terminal, check: 
> qvm-features win10 
> "Qrexec" is probably set to 1. Try removing with: 
> qvm-features win10 qrexec '' 
>
> -- 
> - don't top post 
> Mailing list etiquette: 
> - trim quoted reply to only relevant portions 
> - when possible, copy and paste text instead of screenshots 
>

this command of yours don't set it to 0, simply echoes the value 1 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0c8c5b5f-b3ac-4038-91f2-76a10d40ca46%40googlegroups.com.


[qubes-users] Which version of Xen does Qubes uses? Shouldn't it support OVMF already (HVM EFI boot)?

2020-04-10 Thread Guerlan
Xen 4.4 has support for OVMF. Which version of Xen does Qubes uses? 
Shouldn't it already have this option?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0eb2f1a0-bfc2-45a8-b2a5-695c2625c498%40googlegroups.com.


[qubes-users] Domain win10 failed to start (after 60 seconds using it): cannot connect to qrexec agent for 60 seconds

2020-04-09 Thread Guerlan


My Qubes is closing my windows 10 VMs which are based on my Win10 template 
after 60 seconds, even though they are ok. It says


Domain win10 failed to start: cannot connect to qrexec agent for 60 seconds


even though it already had started and I was using it.


It happened after I installed qubes-windows-tools

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ae80f54c-82b5-4126-a267-0ae812a84cb2%40googlegroups.com.


[qubes-users] Re: Cant format private Win10 disk as NTFS, only FAT and FAT32 works

2020-04-09 Thread Guerlan
everything ir working except for GUI (obviously wont and installer wont 
even install it) and filesystem.

Copy and paste, send and receive files, do work 

On Wednesday, April 8, 2020 at 11:41:19 PM UTC-3, Tech Chris wrote:
>
> Broken and abandoned, yeah thats a complicated problem
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5c405189-df96-4359-b837-9c3f3fa3ec24%40googlegroups.com.


[qubes-users] Re: Cant format private Win10 disk as NTFS, only FAT and FAT32 works

2020-04-07 Thread Guerlan
Windows tools work but some things migth break I guess

On Tuesday, April 7, 2020 at 3:49:53 PM UTC-3, Tech Chris wrote:
>
> I thought Windows tools was only for the old expired qubes 3.. I dont see 
> any new windows tools out i could be wrong.. I installed windows 10 HVM no 
> problem with internet access, but none of my audio of video Ethernet 
> connected equipment could communicate so I just got another ssd and 
> installed windows 10 on its own ssd boot menu from bios real easy... if u 
> do that, be sure to physically remove the qubes ssd or windows will screw 
> it up and vise versa. I had a few days in hell dealing with that fiasco.. 
>
> On Monday, April 6, 2020 at 10:38:38 PM UTC-7, Guerlan wrote:
>>
>> After creating my Win10 VM template and installing qubes-windows-tools I 
>> created a new VM based on this template. I then entered it and tried to 
>> format the private disk as NTFS, but it won't work: "Windows was unable to 
>> complete the format".
>>
>> FAt and FAT32 work!
>>
>> How can I format in NTFS? And which one should I use: NTFS, FAT or FAT32?
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/677cf3c2-c912-4400-93a5-bb47d18d535a%40googlegroups.com.


[qubes-users] Cant format private Win10 disk as NTFS, only FAT and FAT32 works

2020-04-06 Thread Guerlan
After creating my Win10 VM template and installing qubes-windows-tools I 
created a new VM based on this template. I then entered it and tried to 
format the private disk as NTFS, but it won't work: "Windows was unable to 
complete the format".

FAt and FAT32 work!

How can I format in NTFS? And which one should I use: NTFS, FAT or FAT32?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2c67f86f-b8a2-422c-a81e-552e3f10060e%40googlegroups.com.


[qubes-users] No internet on win10 after installing qubes-windows-tools

2020-04-06 Thread Guerlan
After installing qubes-windows-tools and restarting, I have no internet.
I tried setting up the netwrok settings from my qube settings on the 
windows 10 network manager, but when I click to save, I get a warning 
saying that gateway is not in the same subnet as the ip address. I give ok 
and apply the settings but they wont work

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cbb9f4da-ef97-47f9-9a88-e40676a68193%40googlegroups.com.


[qubes-users] Win10 VM won't start properly after installing qubes windows tools

2020-04-05 Thread Guerlan


After installing qubes-windows-tools on a Windows 10 VM, I used it for a 
while, everything worked. Now when I go to launch it again, instead of 
having simply "qubes settings" and "start" like before, I have all the 
windows apps to start. If I click on one of them, the VM starts but does 
not show any screen, it just shows up as started. There's also not a 
"start" option anymore


I opened a bug and one person related having the same problem


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


anyone knows how to solve 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8b25b047-d483-46df-9d51-55d04b30c916%40googlegroups.com.


[qubes-users] How to install qubes tools on Windows 10?

2020-03-15 Thread Guerlan
I bootem my machine with the .iso and started the .exe, but I get

"another version of this product is already installed"

somethig like that.

How to install on Windows 10?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b5624b0f-03d3-40ab-ab42-e50f26577d7a%40googlegroups.com.


[qubes-users] Re: Dom 0 latest update disabled my wireless device.

2020-03-11 Thread Guerlan
I know almost nothing about qubes internals but did you try to see if your 
pci card is mounted to sys-net as a PCI device? Does it appear there? Is it 
mounted in other qube?

On Wednesday, March 11, 2020 at 10:30:54 PM UTC-3, pc revival wrote:
>
> I have been using Qubes for a while now on my personal computers. With the 
> latest update to Dom 0 on Qubes 4.0.3 my wireless card has disappeared. I 
> still have the wired connection but no wireless device available. It was 
> working fine until I did this update and rebooted.
> I haven't seen anything else similar listed anywhere.
> My desktop is an HP 530 with an Intel 3168NGW wireless card.
> Any help or suggestions will be welcome.
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6c292160-a22c-4f4b-b037-604344855de4%40googlegroups.com.


[qubes-users] split-gpg, can't use keys from gpg VM

2020-03-09 Thread Guerlan
I can't use the keys from the same VM as the gpg VM. I know ideally I'd 
have a separate VM just for signing but due to my constrained RAM and due 
to the fact that I use a Yubikey, I'm using the 'social' VM (the one where 
I use social media only) to sign. The problem is that I also need to use 
the social VM sometimes to access things. But I can't select 'social' as 
destination when 'social' is also target in the qubes-gpg-split dialog box.

Also, which VM should I use for signing? I thougth of sys-usb but it does 
not have internet access for me to install qubes-gpg-split and I don't want 
to mess with its configurations just for that.

Is there any risks in what I'm doing?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7b20b8cf-ceff-419b-bf66-8c295cff6525%40googlegroups.com.


Re: [qubes-users] How Qubes / and /home/user mounting as different disks works?

2020-03-09 Thread Guerlan
so if I understood correctly, all the work is done inside the VM, not 
outside? I can imagine mounting the root disk as read only and then setting 
up my VM to 'write' to this disk using these pointers you mentioned. Is 
this how it work?

Which solution Qubes uses and do you know one for Ubuntu? I don't want to 
have lots of different VMs, Ubuntu is enough

On Thursday, March 5, 2020 at 1:56:39 AM UTC-3, Chris Laprise wrote:
>
> On 3/4/20 10:19 PM, Guerlan wrote: 
> > I'm curious about how Qubes does this: 
> > 
> > mounts /home/user and other user-related directories from disk B 
> > mounts the / from disk A, but when VM shutdowns, disk is discarded 
> > 
> > I'm curious on how it mounts disk A. I don't think it makes a copy of 
> > disk A to a temporary disk A', because that'd move lots of gigabytes on 
> > every VM startup. 
> > However, it also can't mount disk A as read-only, because I can write to 
> > it, it just gets discarded. 
> > How does this work? And is it exclusive of Xen? Couldn't I do the same 
> > in KVM? It's very useful 
>
> As to whether this can be done with KVM, yes you can. But Linux vendors 
> are very confused about which copy-on-write technologies to promote so 
> they tend to push the least common denominator, which is partitions or 
> VMDK files. OTOH, Qubes decided copy-on-write storage was too useful to 
> ignore and integrated it into VM management functions. 
>
> You could use LVM thin pools with KVM, but IIRC you would have to 
> automate snapshot handling yourself or find an additional package to do 
> it (if such exists). 
>
> -- 
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a67e7abc-4fda-4d87-bbca-a4c07b7835db%40googlegroups.com.


[qubes-users] Can split-pgp work with my yubikey?

2020-03-08 Thread Guerlan
I want to use my yubikey to ssh from all my Qube VMs to my server. To do 
that I need pgp to interact with my yubikey. It's almost like 
https://www.qubes-os.org/doc/split-gpg/ but with the yubikey inside a 
'trusted' AppVM instead of a private key inside a 'trusted' AppVM

Is it possible?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6bba6887-cf29-457a-9135-933f90c384f3%40googlegroups.com.


[qubes-users] How Qubes / and /home/user mounting as different disks works?

2020-03-04 Thread Guerlan
I'm curious about how Qubes does this:

mounts /home/user and other user-related directories from disk B
mounts the / from disk A, but when VM shutdowns, disk is discarded

I'm curious on how it mounts disk A. I don't think it makes a copy of disk 
A to a temporary disk A', because that'd move lots of gigabytes on every VM 
startup.
However, it also can't mount disk A as read-only, because I can write to 
it, it just gets discarded.
How does this work? And is it exclusive of Xen? Couldn't I do the same in 
KVM? It's very useful

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f07befc1-78bf-4892-ae7a-acf3dc10dc13%40googlegroups.com.


[qubes-users] VLC gets black when maximized

2020-02-09 Thread Guerlan
My VLC gets all black when maximized and the video wont start playing 
again, I have to close it. I'm trying on debian9. Did someone have this 
problem?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5b68ea3c-4e6d-4c76-89a4-757fb941d900%40googlegroups.com.


[qubes-users] How to install qrexec?

2020-01-27 Thread Guerlan
I want to install qrexec on Ubuntu in HVM mode and also Windows 10, but 
there's no information on how to install them in the Qubes pages.


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1e1ca2c1-64d2-4a2e-9ae5-9c19b0e2065e%40googlegroups.com.


[qubes-users] Is it possible to choose additional mount points for private volume?

2020-01-26 Thread Guerlan
I wanted my docker images to be kept in the machine after I turn it off. 
Unfortunately, since docker stores them in /var/lib/docker, this folder 
gets erased. Is there a way to speficy it to be kept?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/daec2f0e-b3b7-4267-929e-10d008550f6a%40googlegroups.com.


[qubes-users] How to redirect a pen drive as a usb device, not as a block device?

2020-01-26 Thread Guerlan
When I plug my pen drive these devices appear to be redirected:

sys-usb:sda
sys-usb:sda1
sys-usb:sda2

If I redirect sda, then I get sda1 and sda2 inside my VM, but I don't get 
/dev/sda, which is the device needed so I can dd a .img to the pen drive

How can I get the device inside?

If I do df -h inside the sys-usb, I don't even see the devices (when 
they're not redirected to VMs)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fde3ed49-be87-4923-b270-8efb830e640a%40googlegroups.com.


[qubes-users] A way to run android as in Android Studio VM manager

2020-01-23 Thread Guerlan
I know Xen supports nested virtualization but I don't want to weak my 
computer's security by compiling this version of Xen for my Qubes

Is there a way to run the images downloaded from Android VM manager in 
Qubes, even if outside the VM? Since adb (android debug bridge) works 
through TCP, it's just a matter of redirecting from my VM to the Android 
VM. Actually when I used KVM I used to run Android Studio inside the VM and 
android vm manager outside and redirect through TCP.

If someone knows another way of developing for Android on Qubes without 
plugging a USB phone, I'd love to hear.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c44dbc5a-e576-4c19-ad41-854935dc71c2%40googlegroups.com.


[qubes-users] Is hibernation supposed to work in HVM mode?

2020-01-19 Thread Guerlan
In PV, I tried installing hibernate in debian and it complains saying 
kernel does not support.

In HVM, I simply put my Kali linux to hibernate. When I started the VM 
again, it got stuck on "Resuming from hibernation"

Was hibernation supposed to work?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/997aa74f-e047-4a9a-bfdb-d2047ae93441%40googlegroups.com.


[qubes-users] No internet in Kali Linux (HVM)

2020-01-19 Thread Guerlan
I installed Kali Linux. It's in HVM mode. I have no internet. I tried to 
edit the network options, and choose eth0 as the adapter. 
ping google.com gives
temporary failure in name resolution

I tried adding 8.8.8.8 and 8.8.4.4 in the network options, but the error 
persists

Windows 10, also in HVM mode, has internet normally. 

Also, I tried running in PV mode, choosing the most recent kernel. It 
simply halts rigth after the boot. Why?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/37e7970a-e6ea-4f16-a148-ea1cc50fa8c0%40googlegroups.com.


Re: [qubes-users] Why Windows 10 is slow? Is it because of HVM?

2020-01-19 Thread Guerlan


On Sunday, January 19, 2020 at 8:36:26 AM UTC-3, Claudia wrote:
>
> January 19, 2020 6:34 AM, "Guerlan" > 
> wrote:
>
> > Windows 10 VM is considerably slower than my traditional PV VMs, the 
> ones that come with Qubes. In
> > fact no one would notice that my PV VMs are virtualized, they look just 
> like regular bare metal
> > machines.
> > However, Windows 10 has lags. Anyone would notice and think either the 
> computer is slow or the
> > system is badly virtualized. For example, when I press Win button, it 
> takes a while for the menu to
> > appear. I can only think that it's because Windows 10 is running in HVM 
> mode. Should I try running
> > it in PV mode? If so, how?
>
> You could try it in PV mode. I'm not sure if it's supported by Qubes but 
> you could probably make it work. 
> https://xenproject.org/windows-pv-drivers/
>
> Also consider that Windows might simply be slower than Linux, especially 
> in resource-constrained environments like a VM. Are your Linux HVMs also 
> slow/laggy? 
>

I have kali linux in HVM mode and it's as fast as the PV VMs. The probem 
seems to be related to windows. I'm gonna try to make Windows 10 PV anyway 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c0e25ff1-1e7f-4a65-b628-d6642485dc65%40googlegroups.com.


[qubes-users] Why Windows 10 is slow? Is it because of HVM?

2020-01-18 Thread Guerlan
Windows 10 VM is considerably slower than my traditional PV VMs, the ones 
that come with Qubes. In fact no one would notice that my PV VMs are 
virtualized, they look just like regular bare metal machines.

However, Windows 10 has lags. Anyone would notice and think either the 
computer is slow or the system is badly virtualized. For example, when I 
press Win button, it takes a while for the menu to appear. I can only think 
that it's because Windows 10 is running in HVM mode. Should I try running 
it in PV mode? If so, how?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/70ab1ac6-3f41-4e1c-913f-7a39551f2839%40googlegroups.com.


Re: [qubes-users] How different from bare metal linux is Qubes NVME interaction?

2020-01-18 Thread Guerlan


On Saturday, January 18, 2020 at 8:27:05 AM UTC-3, Claudia wrote:
>
> January 18, 2020 1:57 AM, "Guerlan" > 
> wrote:
>
> > I have a problem where any linux distro in my Razer Blade Stealth will 
> suffer from NVME corruption
> > (nvme enters in read only mode) many times a day. I tried the most 
> recent kernel, old ones, etc.
> > Tried opening a bug in canonical launchpad, got some help, some kernel 
> patches to try, but none
> > worked. I made two independent tests that prove it's not a problem in my 
> notebok or SSD: 1, I
> > bougth a brand new SSD, same problem. 2: neither Windows or Qubes will 
> give the error.
> > 
> > Actually, I installed Qubes just to see what would happen, because I 
> wanted to run something non
> > linux in my machine just to test. Turns out something in Qubes makes the 
> dom0 access the NVME
> > without any problems.
> > The way I think Xen/Qubes NVME interaction works is like this: xen has 
> pci front and back drivers.
> > Front is in xen, back is in dom0. dom0 then accesses the NVME through 
> PCI. The nvme driver in dom0
> > is the same as the nvme driver in my older bare metal linux 
> distributions which had the bug, so I
> > can only think the bug happens in the PCI level, because it's the only 
> thing different here.
> > 
> > Can someone with better understanding of Xen and Qubes give me a better 
> picture and maybe guess
> > what's happening and why I don't feel the bug at all in Qubes?
>
> Qubes doesn't use a storage domain, so the SATA controller (or in your 
> case, NVME) doesn't use pciback as far as I know. If not for that, I would 
> say it's probably because pciback blocks writes to read-only config space 
> of PCI devices. However storage devices in Qubes just use the normal driver 
> in dom0, just like any other Linux. You can check with `lspci -k`. 
> Unfortunately I don't know enough about NVME to be much help.
>
> Have you tried installing Xen in any other distro? See if the problem 
> occurs there. You can also test suspend/resume while you're at it. If you 
> find that it fixes the NVME problem and suspend works, you can continue 
> using that distro under Xen, even if you don't actually use any domUs. 
>

Thanks. Here's my lspci -k

[lz@dom0 ~]$ lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers (rev 02)
Subsystem: Razer USA Ltd. Device 6752
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 
02)
Subsystem: Razer USA Ltd. Device 6752
Kernel driver in use: i915
Kernel modules: i915
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
Subsystem: Razer USA Ltd. Device 6752
Kernel driver in use: pciback
Kernel modules: xhci_pci
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
Subsystem: Razer USA Ltd. Device 6752
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
Subsystem: Razer USA Ltd. Device 6752
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
Subsystem: Razer USA Ltd. Device 6752
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
Subsystem: Razer USA Ltd. Device 6752
Kernel driver in use: mei_me
Kernel modules: mei_me
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root 
Port #3 (rev f1)
Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root 
Port #9 (rev f1)
Kernel driver in use: pcieport
00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO UART Controller #0 (rev 21)
Subsystem: Razer USA Ltd. Device 6752
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 
21)
Subsystem: Razer USA Ltd. Device 6752
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
Subsystem: Razer USA Ltd. Device 6752
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
Subsystem: Razer USA Ltd. Device 6752
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
Subsystem: Razer USA Ltd. Device 6752
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 Network controller: Qualcomm Athero

Re: [qubes-users] Debugging a sleep/suspend problem on Razer Blade Stealth 2016 - Qubes

2020-01-17 Thread Guerlan


On Tuesday, January 14, 2020 at 7:58:11 AM UTC-3, Abel Luck wrote:
>
> Abel Luck: 
> > Hi there, 
> > 
> > I'm debugging similar resume issues, though on different hardware. 
> > Hopefully you don't mind if we share tips in this thread. 
> >   
> > 
> >>> I couldn't find anything related to those acpi devices. I thougth 
> first 
> >> that there was a driver for 
> >>> them, so I should just rmmod those drivers before sleep and insmod 
> when 
> >> wakeup, but couldn't find 
> >>> anything. There's this issue 
> >> https://ubuntuforums.org/archive/index.php/t-2393029.html which have 
> >>> those exact hash matches, but no answer. 
> >> 
> >> I don't know a lot about pm_trace, but it seems like there might be a 
> >> problem decoding the hash. 
> >> Normally it should show you a PCI address, /sys device name, driver 
> name, 
> >> or something more 
> >> specific (see example in link below). 
> >> 
> >> According to s2ram kernel documentation: 
> >> 
> >> If no device matches the hash (or any matches appear to be false 
> >> positives), the culprit may be a 
> >> device from a loadable kernel module that is not loaded until after the 
> >> hash is checked. You can 
> >> check the hash against the current devices again after more modules are 
> >> loaded using sysfs: 
> >> 
> >> cat /sys/power/pm_trace_dev_match 
> >> 
> >> 
> https://www.kernel.org/doc/html/latest/power/s2ram.html#using-trace-resume 
> >> 
> >> However, in qubes we may also have the opposite problem. Qubes takes 
> over 
> >> your network cards and 
> >> sometimes USB controllers in early userspace, so the drivers are not 
> >> available anytime. To disable 
> >> this behavior for USB controllers, remove rd.qubes.hide_all_usb from 
> the 
> >> kernel cmdline. For 
> >> network cards it's a little more complicated. 
> >> 
> >> You can try modifying the qubes initramfs hook. First, make sure there 
> are 
> >> no VMs configured to 
> >> start automatically at boot. Move 
> >> /usr/lib/dracut/modules.d/90qubes-pciback/ to your home 
> >> directory, or open the qubes-pciback.sh file and comment out the last 9 
> or 
> >> so lines (from "for dev 
> >> in $HIDEPCI"). Rebuild the initramfs. Then, do the pm_trace again as 
> you 
> >> did before. Then, try 
> >> pm_trace_dev_match as described in the link above. 
> >> 
> >> It might give you better information about the problem device, or it 
> might 
> >> just give you the same 
> >> info as before, but it's something to try. 
> >> 
> >> If it doesn't work, don't forget to put that file back how it was, and 
> >> rebuild initramfs again. 
> >> 
> > 
> > Thanks for this tip. Using this method I was able to get a "hash 
> matches" 
> > line in my dmesg whereas before I didn't get one. 
> > 
> > I am also debugging a suspend resume issue but with a Asus z390 I Aorus 
> Pro 
> > Wifi motherboard on a desktop (and an nvidia gpu unfortunately). 
> > 
> > Some interesting facts: 
> > 
> > 1) the pci device that matched was "INT34B9:00". I can't really find 
> > much info about what this device is, it doesn't correspond to anything 
> > under lspci. /sys/bus/acpi/devices/INT34B9:00/uid contains the value 
> > "SerialIoUart1" 
> > 
> > 2) suspend and resume works when I execute "echo mem > 
> /sys/power/state". 
> > However when I execute the suspend from xfce or run systemctl suspend, 
> the 
> > resume fails (with a black screen but the keyboard lights up). 
> >   
>
> >> Just some general tips: try kernel-latest, and Qubes R4.1, if you 
> haven't 
> >> yet. 
>
>
> Some interesting news, TL;DR is that I got suspend/resume working! 
> Here's how: 
>
>
> I updated dom0 to kernel-latest, booted again and with all vms off 
> tested suspend with this script: 
>
> ``` 
> #!/bin/sh 
>
> sync 
> echo 1 > /sys/power/pm_trace 
> echo mem > /sys/power/state 
> ``` 
>
> Resume worked. However as soon as I turned on sys-usb it failed to 
> resume again, with the monitor staying off but the keyboard lights 
> turning on. 
>
> At this point I went into my bios and disabled all the devices I could: 
> wlan adapter, ethernet adapter, graphics, etc. 
>
> Throughout this point I was constantly checking for the "hash matches" 
> devices in dmesg and looking at /sys/power/pm_trace_dev_match. Also I 
> had edited qubes-pciback.sh as described by Claudia. There was never a 
> clear smoking gun that revealed some particular device, and the values 
> seemed to change with every reboot or configuration. However at one 
> point I noticed 'drm' in  pm_trace_dev_match, and this would prove 
> useful later. 
>
> My motherboard has integrated intel graphics (igfx) but also a PCIe 
> nvidia card. Eventually I happened upon the bios configuration where I 
> enabled integrated graphics (I had no option to disable the nvidias card 
> aside from physically removing it). 
>
> Booting into Qubes using the igfx output, I noticed 'drm' in the 
> pm_trace_dev_match, which I know has something to do with the nouveau 
> driver.  So I disabled 

Re: [qubes-users] Debugging a sleep/suspend problem on Razer Blade Stealth 2016 - Qubes

2020-01-17 Thread Guerlan


On Saturday, January 11, 2020 at 4:37:17 PM UTC-3, Claudia wrote:
>
> January 9, 2020 1:55 AM, "Guerlan" > 
> wrote:
>
> > First of all, here's the HCL for my Razer Blade Stealth 2016 4K 
> touchscreen 16gb RAM 512gb SSD:
> > 
> https://groups.google.com/forum/#!searchin/qubes-users/razer$20blade|sort:date/qubes-users/PalZ-1inx
> > A/D3mQ4OI3CAAJ
> > 
> > When I close the lid and open again, keyboard wont ligth up, screen wont 
> turn on (it's LED so I can
> > see a brigth black when it turns on), and hitting keyboard or touchpad 
> does nothing. I have to
> > reboot. I don't know, however, if keyboard not ligthing when I open the 
> lid is because sys-usb,
> > which contains the keyboard, is not waken. Every other aspect of the 
> laptop seems to be working
> > perfectly.
>
> When you're testing, make sure there are no VMs set to start on boot, 
> especially not sys-net and
> sys-usb, and make sure rd.qubes.hide_all_usb is not set. You can try to 
> get that stuff working
> later on.
>
> Does pressing caps lock or num lock turn on/off their lights on the 
> keyboard? Does ctrl-alt-delete,
> or Alt-SysRq-B (you have to enable it first) cause it to reboot? If you 
> suspend with sound playing,
> can you hear it when you try to resume?
>
> > I followed Ubuntu's guide on kernel suspend bugs: 
> https://wiki.ubuntu.com/DebuggingKernelSuspend
> > 
> > Then, following what they suggest
> > 
> > `sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"`
> > 
> > and find the lines that says hash matches in dmesg rigth after reboot 
> (what does that mean?)
> > 
> > Well, I found two:
> > 
> > ```
> > [ 3.583591] ima: Allocated hash algorithm: sha1
> > [ 3.593050] input: AT Raw Set 2 keyboard as 
> /devices/platform/i8042/serio0/input/input4
> > [ 3.638808] Magic number: 0:929:176
> > [ 3.638867] acpi device:39: hash matches
> > [ 3.638893] acpi device:0c: hash matches
> > [ 3.639073] rtc_cmos 00:01: setting system clock to 2016-01-01 12:09:51 
> UTC (1451650191)
> > ```
> > 
> > I couldn't find anything related to those acpi devices. I thougth first 
> that there was a driver for
> > them, so I should just rmmod those drivers before sleep and insmod when 
> wakeup, but couldn't find
> > anything. There's this issue 
> https://ubuntuforums.org/archive/index.php/t-2393029.html which have
> > those exact hash matches, but no answer.
>
> I don't know a lot about pm_trace, but it seems like there might be a 
> problem decoding the hash.
> Normally it should show you a PCI address, /sys device name, driver name, 
> or something more
> specific (see example in link below).
>
> According to s2ram kernel documentation:
>
> If no device matches the hash (or any matches appear to be false 
> positives), the culprit may be a
> device from a loadable kernel module that is not loaded until after the 
> hash is checked. You can
> check the hash against the current devices again after more modules are 
> loaded using sysfs:
>
> cat /sys/power/pm_trace_dev_match
>
> https://www.kernel.org/doc/html/latest/power/s2ram.html#using-trace-resume
>
> However, in qubes we may also have the opposite problem. Qubes takes over 
> your network cards and
> sometimes USB controllers in early userspace, so the drivers are not 
> available anytime. To disable
> this behavior for USB controllers, remove rd.qubes.hide_all_usb from the 
> kernel cmdline. For
> network cards it's a little more complicated.
>
> You can try modifying the qubes initramfs hook. First, make sure there are 
> no VMs configured to
> start automatically at boot. Move 
> /usr/lib/dracut/modules.d/90qubes-pciback/ to your home
> directory, or open the qubes-pciback.sh file and comment out the last 9 or 
> so lines (from "for dev
> in $HIDEPCI"). Rebuild the initramfs. Then, do the pm_trace again as you 
> did before. Then, try
> pm_trace_dev_match as described in the link above.
>
> It might give you better information about the problem device, or it might 
> just give you the same
> info as before, but it's something to try.
>
> If it doesn't work, don't forget to put that file back how it was, and 
> rebuild initramfs again.
>
> > Then I asked for help on a forum and they found this problematic line on 
> my dmesg:
> > 
> > `[ 2.543596] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM`
> > 
> > seems like ASPM is disabled on my Qubes. I don't know why. Should this 
> be considered a bug? Is
> > there anything I can do to get it working? This looks promisin

[qubes-users] How different from bare metal linux is Qubes NVME interaction?

2020-01-17 Thread Guerlan
I have a problem where any linux distro in my Razer Blade Stealth will 
suffer from NVME corruption (nvme enters in read only mode) many times a 
day. I tried the most recent kernel, old ones, etc. Tried opening a bug in 
canonical launchpad, got some help, some kernel patches to try, but none 
worked. I made two independent tests that prove it's not a problem in my 
notebok or SSD: 1, I bougth a brand new SSD, same problem. 2: neither 
Windows or Qubes will give the error.

Actually, I installed Qubes just to see what would happen, because I wanted 
to run something non linux in my machine just to test. Turns out something 
in Qubes makes the dom0 access the NVME without any problems. 

The way I think Xen/Qubes NVME interaction works is like this: xen has pci 
front and back drivers. Front is in xen, back is in dom0. dom0 then 
accesses the NVME through PCI. The nvme driver in dom0 is the same as the 
nvme driver in my older bare metal linux distributions which had the bug, 
so I can only think the bug happens in the PCI level, because it's the only 
thing different here.

Can someone with better understanding of Xen and Qubes give me a better 
picture and maybe guess what's happening and why I don't feel the bug at 
all in Qubes?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e77b4739-f44e-4265-b267-09a08ca45aa3%40googlegroups.com.


[qubes-users] My bluetooth device appears in sys-usb but its module (wifi) is in sys-net

2020-01-09 Thread Guerlan
I'm trying to understand something. My bluetooth device is a PCI device 
that is also a wifi device. The wifi PCI device is mounted to sys-net, so 
bluetooth should appear there as well. However:

[user@sys-usb ~]$ hcitool dev
Devices:
hci09C:86:C0:1D:41:E1

[user@sys-net ~]$ hcitool dev
Devices:

Even though sys-usb has a bluetooth device scanning returns nothing, so I 
don't know if it really is a bluetooth device. However sys-net should have 
it. 

Here are lspci for both VMs:

[user@sys-usb ~]$ lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton 
II]
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 
01)
00:03.0 VGA compatible controller: Device 1234: (rev 02)
00:04.0 USB controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 
EHCI Controller (rev 10)
00:06.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)

[user@sys-net ~]$ lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton 
II]
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 
01)
00:03.0 VGA compatible controller: Device 1234: (rev 02)
00:04.0 USB controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 
EHCI Controller (rev 10)
00:06.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32) <<< controller that has bluetooth

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c359061f-4039-4afe-94f6-212bc48e97bd%40googlegroups.com.


Re: [qubes-users] Re: No Suspend/Resume on Dell Latitude 7400 (i5-8365U) with 4.0.2rc3

2020-01-08 Thread Guerlan


On Wednesday, January 8, 2020 at 8:28:12 AM UTC-3, Claudia wrote:
>
> January 8, 2020 12:10 AM, "Guerlan" > 
> wrote:
>
> > On Tuesday, January 7, 2020 at 8:41:31 PM UTC-3, Claudia wrote:
> > 
> >> January 7, 2020 6:08 PM, "Guerlan"  wrote:> On 
> Monday, January 6, 2020 at
> >> 12:43:40 AM UTC-3, Claudia wrote:
> >>> 
> >>>> January 6, 2020 3:14 AM, dmoe...@gmail.com wrote:> On Sunday, 
> January 5, 2020 at 9:49:42 PM
> >> UTC-5,
> >>>> Guerlan wrote:
> >>>>>> can you tell me how you figured this out? I've been trying to fix a 
> suspend bug in mine and
> >> It'd
> >>>> be
> >>>>>> helpful to know how you debugged things
> >>>>> 
> >>>>> Mostly trial and error, trying all the things listed above. Two 
> little tricks to use:
> >>>>> 
> >>>>> 1. Look at the end of journalctl right before it tries to suspend. 
> This is where I saw that it
> >>>> was
> >>>>> going into s2idle, which then brought me to this thread:
> >>>>> 
> >>>> 
> >> 
> https://groups.google.com/forum/#!msg/qubes-users/TmGDlkluJgM/1BFsQZWNDAAJ;context-place=forum/qubes
> >>>>> users This Dell did not have the lack of S3 that the new Thinkpads 
> have, but it did still try
> >> to
> >>>>> use s2idle.
> >>>> 
> >>>> /sys/power/mem_sleep will list supported modes, with the default in 
> brackets. You can echo to it
> >> to
> >>>> set the default at runtime, or use the boot parameter.
> >>> 
> >>> [lz@dom0 ~]$ cat /sys/power/mem_sleep
> >>> s2idle [deep]
> >>> 
> >>> What does this mean? It means that it detected only s2idle or that my 
> system does not support
> >>> suspend to RAM? I've used Ubuntu and Fedora and lid closing always 
> worked, I just don't know if
> >> it
> >>> was idle or to ram or other thing.
> >> 
> >> This means that s2idle mode and deep mode are the two modes supported 
> by your machine, and that
> >> deep is the mode that will be used for sleep when no specific mode is 
> specified, such as using the
> >> lid switch or the logout menu or systemctl suspend for example. In OP's 
> case, deep is manually set
> >> as default using the kernel parameter mem_sleep_default=deep. Generally 
> the kernel chooses the
> >> deepest mode supported (s2idle -> shallow -> deep) to be the default, 
> but on some machines the
> >> kernel will choose s2idle as the default even if deep is supported.
> >> 
> >> 
> https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html#basic-sysfs-interfaces-for-sy
> >> tem-suspend-and-hibernation
> > 
> > Thanks! I now understand how it works. I've checked and indeed my system 
> defaults to deep. I tried
> > s2idle by doing echo freeze > /sys/power/state and the screen turns off 
> but they keyboard keeps
> > with lights on. Pressing buttons does nothing. Pressing touchpad, 
> nothing. Pressing power rapidly,
> > nothing. Had to reboot by long pressing power. Shouldn't s2idle always 
> work since it's software
> > based?
>
> I don't know much about s2idle, but yes, in theory it should be the most 
> reliable of the sleep states. It could be a graphics driver issue. However, 
> from your log it looks like it's still entering deep sleep. 
>
> > I have no other ideas. If someone know a little more on how to debug, 
> I'd be glad. Remember that I
> > found this error in ACPI 
> https://github.com/QubesOS/qubes-issues/issues/ on dmesg. It indicates
> > that ASPM does not work. Maybe this is crucial?
>
> Debugging suspend is a long and complicated process. I don't want to get 
> any more off-topic in this thread. Please start a new thread for your 
> machine detailing everything you've tried so far, including logs and any 
> other relevant information, so it's all in one place. 
>


Ok thanks, here's the new thread 
https://groups.google.com/forum/#!topic/qubes-users/eMWxHSy9h7c 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/4e10bb5b-ac36-49ce-a613-457b6b80013a%40googlegroups.com.


[qubes-users] Debugging a sleep/suspend problem on Razer Blade Stealth 2016 - Qubes

2020-01-08 Thread Guerlan
First of all, here's the HCL for my Razer Blade Stealth 2016 4K touchscreen 
16gb RAM 512gb SSD: 
https://groups.google.com/forum/#!searchin/qubes-users/razer$20blade%7Csort:date/qubes-users/PalZ-1inxnA/D3mQ4OI3CAAJ

When I close the lid and open again, keyboard wont ligth up, screen wont 
turn on (it's LED so I can see a brigth black when it turns on), and 
hitting keyboard or touchpad does nothing. I have to reboot. I don't know, 
however, if keyboard not ligthing when I open the lid is because sys-usb, 
which contains the keyboard, is not waken. Every other aspect of the laptop 
seems to be working perfectly.

I followed Ubuntu's guide on kernel suspend bugs: 
https://wiki.ubuntu.com/DebuggingKernelSuspend

Then, following what they suggest

`sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"`

and find the lines that says hash matches in dmesg rigth after reboot (what 
does that mean?)

Well, I found two:

```
[3.583591] ima: Allocated hash algorithm: sha1
[3.593050] input: AT Raw Set 2 keyboard as 
/devices/platform/i8042/serio0/input/input4
[3.638808]   Magic number: 0:929:176
[3.638867] acpi device:39: hash matches
[3.638893] acpi device:0c: hash matches
[3.639073] rtc_cmos 00:01: setting system clock to 2016-01-01 12:09:51 
UTC (1451650191)
```

I couldn't find anything related to those acpi devices. I thougth first 
that there was a driver for them, so I should just rmmod those drivers 
before sleep and insmod when wakeup, but couldn't find anything. There's 
this issue https://ubuntuforums.org/archive/index.php/t-2393029.html which 
have those exact hash matches, but no answer. 

Then I asked for help on a forum and they found this problematic line on my 
dmesg:

`[2.543596] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM`

seems like ASPM is disabled on my Qubes. I don't know why. Should this be 
considered a bug? Is there anything I can do to get it working? *This looks 
promising.*

It's worth noting that on Ubuntu 18, 19, Fedora 30, Linux Mint, etc, *all 
these systems work like a charm with the sleep process*. I can close the 
lid and open and it works. So the problem seems to be **related to Qubes**. 
I even tried qubes most recent dom0 kernel, based on 5.x linux kernel, but 
the problem persists.

I also tried `pcie_aspm=force` on `/boot/efi/EFI/qubes/xen.cfg` (is this 
where I put kernel parameters?) like this:

`kernel=vmlinuz-4.14.74-1.pvops.qubes.x86_64 
root=/dev/mapper/qubes_dom0-root 
rd.luks.uuid=luks-39fc83eb-9829-43b7-86e8-08068bd81087 
rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 
pcie_aspm=force rhgb quiet plymouth.ignore-serial-consoles`

but it didn't help.

I pratically *need* to run Qubes on this notebook because any Linux 
distribution with any kernel will have a problem that corrupts my SSD many 
times a day. No one could solve it, and on Qubes it never happens. I tried 
Qubes just to see if it'd solve and it does! I'm loving it, not going back 
even on other notebooks. However, closing the lid/putting the system to 
sleep is essential for a notebook.

```
[lz@dom0 ~]$ cat /sys/power/mem_sleep 
s2idle [deep]
```

as you see, the suspend default is deep mode.

I tried s2idle by doing `echo freeze > /sys/power/state` and the screen 
turns off but they keyboard keeps with lights on. Pressing buttons does 
nothing. Pressing touchpad, nothing. Pressing power rapidly, nothing. Had 
to reboot by long pressing power. I thougth s2idle should always work since 
it's software based. 

Here's my journalctl of the moment when I go to suspend by closing the lid 
(that is, suspending in deep mode):

```
Jan 07 20:56:24 dom0 systemd-logind[1925]: Lid closed.
Jan 07 20:56:24 dom0 systemd-logind[1925]: Suspending...
Jan 07 20:56:24 dom0 systemd[1]: Starting Qubes suspend hooks...
Jan 07 20:56:25 dom0 qmemman.daemon.algo[1921]: balance_when_enough_memory(
xen_free_memory=8172072647, total_mem_pref=2493652659.2, 
total_available_memory=13171544083.8)
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: dom '5' 
act=3198156800 pref=963591782.4 last_target=3198156800
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: dom '0' 
act=4294967296 pref=1530060876.8 last_target=4294967296
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: xenfree=8224501447 
memset_reqs=[('5', 3198156800), ('0', 4294967296)]
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: mem-set domain 5 to 
3198156800
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: mem-set domain 0 to 
4294967296
Jan 07 20:56:25 dom0 qrexec[3884]: qubes.GetDate: social -> @default: 
allowed to dom0
Jan 07 20:56:25 dom0 qmemman.daemon.algo[1921]: 
balance_when_enough_memory(xen_free_memory=8172072647, 
total_mem_pref=2450575027.2, total_available_memory=13214621715.8)
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: dom '5' 
act=3198156800 pref=920514150.4 last_target=3198156800
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: dom '0' 
act=4294967296 

Re: [qubes-users] Re: No Suspend/Resume on Dell Latitude 7400 (i5-8365U) with 4.0.2rc3

2020-01-07 Thread Guerlan


On Tuesday, January 7, 2020 at 8:41:31 PM UTC-3, Claudia wrote:
>
> January 7, 2020 6:08 PM, "Guerlan" > 
> wrote:
>
> > On Monday, January 6, 2020 at 12:43:40 AM UTC-3, Claudia wrote:
> > 
> >> January 6, 2020 3:14 AM, dmoe...@gmail.com wrote:> On Sunday, January 
> 5, 2020 at 9:49:42 PM UTC-5,
> >> Guerlan wrote:
> >>>> can you tell me how you figured this out? I've been trying to fix a 
> suspend bug in mine and It'd
> >> be
> >>>> helpful to know how you debugged things
> >>> 
> >>> Mostly trial and error, trying all the things listed above. Two little 
> tricks to use:
> >>> 
> >>> 1. Look at the end of journalctl right before it tries to suspend. 
> This is where I saw that it
> >> was
> >>> going into s2idle, which then brought me to this thread:
> >>> 
> >> 
> https://groups.google.com/forum/#!msg/qubes-users/TmGDlkluJgM/1BFsQZWNDAAJ;context-place=forum/qubes
> >>> users This Dell did not have the lack of S3 that the new Thinkpads 
> have, but it did still try to
> >>> use s2idle.
> >> 
> >> /sys/power/mem_sleep will list supported modes, with the default in 
> brackets. You can echo to it to
> >> set the default at runtime, or use the boot parameter.
> > 
> > [lz@dom0 ~]$ cat /sys/power/mem_sleep
> > s2idle [deep]
> > 
> > What does this mean? It means that it detected only s2idle or that my 
> system does not support
> > suspend to RAM? I've used Ubuntu and Fedora and lid closing always 
> worked, I just don't know if it
> > was idle or to ram or other thing.
>
> This means that s2idle mode and deep mode are the two modes supported by 
> your machine, and that deep is the mode that will be used for sleep when no 
> specific mode is specified, such as using the lid switch or the logout menu 
> or systemctl suspend for example. In OP's case, deep is manually set as 
> default using the kernel parameter mem_sleep_default=deep. Generally the 
> kernel chooses the deepest mode supported (s2idle -> shallow -> deep) to be 
> the default, but on some machines the kernel will choose s2idle as the 
> default even if deep is supported. 
>
>
> https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html#basic-sysfs-interfaces-for-system-suspend-and-hibernation
>


Thanks! I now understand how it works. I've checked and indeed my system 
defaults to deep. I tried s2idle by doing echo freeze > /sys/power/state 
and the screen turns off but they keyboard keeps with lights on. Pressing 
buttons does nothing. Pressing touchpad, nothing. Pressing power rapidly, 
nothing. Had to reboot by long pressing power. Shouldn't s2idle always work 
since it's software based?

I also followed the dmoe...@gmail.com tip of viewing journalctl just before 
suspend:

Jan 07 20:56:24 dom0 systemd-logind[1925]: Lid closed.
Jan 07 20:56:24 dom0 systemd-logind[1925]: Suspending...
Jan 07 20:56:24 dom0 systemd[1]: Starting Qubes suspend hooks...
Jan 07 20:56:25 dom0 qmemman.daemon.algo[1921]: 
balance_when_enough_memory(xen_free_memory=8172072647, 
total_mem_pref=2493652659.2, total_available_memory=13171544083.8)
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: dom '5' 
act=3198156800 pref=963591782.4 last_target=3198156800
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: dom '0' 
act=4294967296 pref=1530060876.8 last_target=4294967296
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: xenfree=8224501447 
memset_reqs=[('5', 3198156800), ('0', 4294967296)]
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: mem-set domain 5 to 
3198156800
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: mem-set domain 0 to 
4294967296
Jan 07 20:56:25 dom0 qrexec[3884]: qubes.GetDate: social -> @default: 
allowed to dom0
Jan 07 20:56:25 dom0 qmemman.daemon.algo[1921]: 
balance_when_enough_memory(xen_free_memory=8172072647, 
total_mem_pref=2450575027.2, total_available_memory=13214621715.8)
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: dom '5' 
act=3198156800 pref=920514150.4 last_target=3198156800
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: dom '0' 
act=4294967296 pref=1530060876.8 last_target=4294967296
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: stat: xenfree=8224501447 
memset_reqs=[('5', 3198156800), ('0', 4294967296)]
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: mem-set domain 5 to 
3198156800
Jan 07 20:56:25 dom0 qmemman.systemstate[1921]: mem-set domain 0 to 
4294967296
Jan 07 20:56:26 dom0 qmemman.daemon.algo[1921]: 
balance_when_enough_memory(xen_free_memory=8172072647, 
total_mem_pref=2398557056.0, total_available_memory=13266639687.0)
Jan 07 20:56:26 dom0 qmemman.systemstate[1921]: stat: dom '5' 
act=3198156800 pref=920514150.4 last_target=319

[qubes-users] How to use QEMU with Qubes?

2020-01-07 Thread Guerlan
I undrstand that HVM uses QEMU to emulate some devices and BIOS. However, 
what if I want to have total control of QEMU?

What if there's an OS for which there's a QEMU tutorial and I want to do 
exact what is in the tutorial but in Qubes?

Do I need Qemu on dom0? dom0 has qemu-img-xen and qemu-nbd-xen. What are 
they for?

Or does QEMU runs inside xen, not in 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/aca54b73-0562-4451-8b26-ef4831aba79d%40googlegroups.com.


Re: [qubes-users] Re: No Suspend/Resume on Dell Latitude 7400 (i5-8365U) with 4.0.2rc3

2020-01-07 Thread Guerlan


On Monday, January 6, 2020 at 12:43:40 AM UTC-3, Claudia wrote:
>
> January 6, 2020 3:14 AM, dmoe...@gmail.com  wrote:
>
> > On Sunday, January 5, 2020 at 9:49:42 PM UTC-5, Guerlan wrote:
> >> can you tell me how you figured this out? I've been trying to fix a 
> suspend bug in mine and It'd be
> >> helpful to know how you debugged things
> > 
> > Mostly trial and error, trying all the things listed above. Two little 
> tricks to use:
> > 
> > 1. Look at the end of journalctl right before it tries to suspend. This 
> is where I saw that it was
> > going into s2idle, which then brought me to this thread:
> > 
> https://groups.google.com/forum/#!msg/qubes-users/TmGDlkluJgM/1BFsQZWNDAAJ;context-place=forum/qubes
> > users This Dell did not have the lack of S3 that the new Thinkpads have, 
> but it did still try to
> > use s2idle.
>
> /sys/power/mem_sleep will list supported modes, with the default in 
> brackets. You can echo to it to set the default at runtime, or use the boot 
> parameter. 
>


 [lz@dom0 ~]$ cat /sys/power/mem_sleep 
s2idle [deep]

What does this mean? It means that it *detected* only s2idle or that my 
system does not support suspend to RAM? I've used Ubuntu and Fedora and lid 
closing always worked, I just don't know if it was idle or to ram or other 
thing. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/bc364066-1824-413d-afd1-e3c148ad7a53%40googlegroups.com.


[qubes-users] Re: No Suspend/Resume on Dell Latitude 7400 (i5-8365U) with 4.0.2rc3

2020-01-05 Thread Guerlan


On Saturday, January 4, 2020 at 7:00:54 PM UTC-3, dmoe...@gmail.com wrote:
>
> The suspending problem was s2idle. Adding mem_sleep_default=deep to the 
> kernel= line of /boot/efi/EFI/qubes/xen.cfg fixes the suspend problem.
>
> Installing kernel-latest (5.3.11-1) fixes the last two problems with 
> completing shutdown and with a lack of a bootsplash.
>
> I'll post an HCL in a moment. Everything now works flawlessly.
>
> Daniel
>


can you tell me how you figured this out? I've been trying to fix a suspend 
bug in mine and It'd be helpful to know how you debugged 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/601cf502-8ac2-4749-9709-fbc534109508%40googlegroups.com.


[qubes-users] Re: Recommended laptop?

2020-01-02 Thread Guerlan


On Tuesday, December 24, 2019 at 7:43:08 AM UTC-2, Ondřej Šulák wrote:
>
> Hello pals,
> for the last release of Qubes, what laptop would you recommend? Is there 
> any cheaper option which does have HW compatibility with latest Qubes 
> (ideally with shipping from EU), than this one:
>
> https://insurgo.ca/produit/qubesos-certified-privacybeast_x230-reasonably-secured-laptop/
>  
> ?
>
> Thanks for any tips!
>
> Ondrej
>


Im running on a Razer Blade Steatlh 4k + touchscreen 2016 16gb RAM 512gb 
SSD i7 ultra thin. *Everything* works wxcept for the lid closing and 
opening but I'm trying to find a solution. Qubes runs very good on this 
laptop, I'm very happy!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/da6966c6-c4d8-4465-85a6-dc9a27cb4206%40googlegroups.com.


[qubes-users] Which Qemu does Qubes have and how to use?

2020-01-02 Thread Guerlan
I'm trying to install macOS on Qubes. For it, it needs Qemu. There are two 
qemu-* in dom0:

qemu-img-xen and qemu-nbd-xen

I can't find options to see which versions of qemu they are. Where's the 
simple `qemu` command? And is it rigth to run it in 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8637c8de-9110-430b-aa03-5be541fc6d90%40googlegroups.com.


[qubes-users] Debugging kernel suspend on Qubes - does Qubes run fsck on boot?

2019-12-26 Thread Guerlan
I'm following https://wiki.ubuntu.com/DebuggingKernelSuspend to debug a 
kernel suspend bug on my computer. Since there's no nvme available during 
suspend, I must rely on the motherboard clock for logging.

The problem is that when I use the clock for logging, it loses its clock 
time and then the system thinks it's time to run fsck. But if the fsck 
takes too much time, the clock loses the logging file.

To avoid the fsck, I must run tune2fs -i 0 partition, where partition is 
the qubes partition, which I THINK is /dev/mapper/qubes_dom0-root. The 
problem is that this partition already has the value 0. However when I 
suspend I THINK that a fsck happens, because after I input the LUKS 
password, the progress bar takes about an hour to complete. Since qubes 
shows no logging, I guess it is fsck running.

So how should I prevent qubes from running fsck after doing suspend?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9df60785-ffbc-4ec2-84a3-9ad774d735a7%40googlegroups.com.


[qubes-users] how to install or use pm-suspend similar command on Qubes

2019-12-26 Thread Guerlan
I'm following https://wiki.ubuntu.com/DebuggingKernelSuspend to debug 
kernel suspend problems. However, on dom0 there's no pm-suspend command.

How can I install SECURELY this command or how to substitute for another 
one? 

This is the command:

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

Which command does xfce use when I click the suspend button?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2af6661d-b7fd-4a3b-9fb8-6dc6ba2d6f7a%40googlegroups.com.


Re: [qubes-users] equivalent of grub kernel parameters on qubes?

2019-12-19 Thread Guerlan


On Wednesday, October 30, 2019 at 9:53:47 AM UTC-3, unman wrote:
>
> On Mon, Oct 28, 2019 at 09:36:50AM -0700, Guerlan wrote: 
> > I scrolled and couldn't find what you suggested. 
> > 
> > The contents of /boot/efi/EFI is a qubes folder which has qubes kernels 
> and 
> > xen.cfg, xen.efi 
> > 
> > On Monday, October 28, 2019 at 11:35:06 AM UTC-3, unman wrote: 
> > > 
> > > On Sun, Oct 27, 2019 at 10:07:25PM -0700, Guerlan wrote: 
> > > > I tried to locate that file on dom0 but I couldn't find. Was it 
> supposed 
> > > to 
> > > > be elsewhere? (yes, I installed with UEFI) 
> > > > 
> > > > On Sunday, October 27, 2019 at 11:59:05 AM UTC-3, unman wrote: 
> > > > > 
> > > > > On Fri, Oct 25, 2019 at 05:41:37PM -0700, Guerlan wrote: 
> > > > > > There's a quirk for laptop suspend problem that I want to try on 
> > > Qubes 
> > > > > that 
> > > > > > is the following on Ubuntu: 
> > > > > > 
> > > > > > sudo nano /etc/default/grub 
> > > > > > GRUB_CMDLINE_LINUX_DEFAULT="button.lid_init_state=open" 
> > > > > > 
> > > > > > However dom0 does not have such file. How do I pass kernel 
> > > parameters to 
> > > > > Qubes? 
> > > > > > 
> > > > > 
> > > > > I have that file but I use standard(legacy) boot. Did you install 
> with 
> > > > > UEFI? 
> > > > > If you are using UEFI, I believe you can install a EFI shell and 
> boot 
> > > > > into it to test change parameters. Or you can edit the file at 
> > > > > /boot/efi/EFI/qubes/xen.cfg to add your parameters. 
> > > > > 
> > > > > NB I dont like UEFI and dont use it, but I think that pointer is 
> > > right. 
> > > > > As always, back up any system files before you start changing 
> them. 
> > > > > 
> > > > > unman 
> > > > > 
> > > 
> > > The convention on these lists is to post at the bottom of the message, 
> > > so that a new reader can follow the sense by reading downwards. Can 
> you 
> > > try to do that? All you have to do is scroll to the bottom and 
> > > start typing. Thanks. 
> > > 
> > > So do you have /boot/efi/EFI? 
> > > What are contents? 
> > > 
> > 
> I'm starting to think you are ideologically wedded to top-posting. 
> Believe me, once you've tried bottom posting you will never understand 
> why you did this. 
> I guess your mail software outs the cursor at the top of the message 
> when you h=it "Reply". Ignore this broken piece of garbage.Take 
> control. Scroll to the bottom of the message, deleting any 
> unnecessary stuff on the way, and start typing. This will take you 
> seconds, 
> compared to the minutes, perhaps hours, that other users will spend 
> flipping between top and bottom of the message, trying to understand 
> what's going on. 
> Try it. 
>
> e in hand - look at the contents of the (*flip to top of message, 
> sighs*) xen.cfg and xen.efi files. Is one of those the one you are 
> booting from? 
> (Not being a UEFI person - is there really no grub screen?) 
>
> unman 
>


Am I doing things rigth now?

So, xen.cfg contains things like

default=4.19.71-1.pvops.qubes.x86_64

[4.14.74-1.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx 
ucode=scan smt=off
kernel=vmlinuz-4.14.74-1.pvops.qubes.x86_64 
root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-39... 
rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 
rhgb quiet plymouth.ignore-serial-consoles
ramdisk=initramfs-4.14.74-1.pvops.qubes.x86_64.img
[4.19.71-1.pvops.qubes.x86_64]

which seem to be configuratioons to xen. Xen.efi gives me giant text with 
things like this:

ativesalloc_host_save_areastartup_cpu_idle_loopacpi_tb_create_local_fadt__trampoline_rel_startget_free_pirqcore2_no_vpmu_opsinject_vmceio_apic_read_remap_rteamd_iommu_setup_ioapic_remappinghpet_deinitvtd_ops_preamble_quirkvioapic_initsvm_vmexit_do_stgifree_domheap_pagesprocess_pending_softirqsnsvm_hap_walk_L1_p2mrangeset_domain_printkmcheck_initsetup_ept_dumpmapcache_vcpu_initmachine_to_phys_mapping_validautogen_entrypointsapic_versionpirq_shared__stop_bug_frames_0vcpu_restore_fpu_lazypaging_domain_initp2m_get_p2mpage_unlockdo_hvm_opdomain_pausecpufreq_gov_userspace__update_guest_eiplowmem_kbcontext_savedsvm_asid_initarch_do_vcpu_opcontinue_hypercall_on_cpuiommu_pt_cleanup_listinit_guest_l4_tablehvm_get_tsc_scaling_rationode_online_mapvmx_pin_based_exec_controlmemguard_guard_rangehvm_x2apic_msr_writevideo_flagsacpi_initialize_tablesserial_endbootsimple_strtoulldomain_unpause_by_systemcontrollercpupool_get_by_idcmci_supportmcequirk

There's no grub screen as far as I know. It boots to a log screen with very 
small resolution and them qubes password input appears

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fefe2ffc-e7c3-4e3f-a29c-d8e2994f50c1%40googlegroups.com.


[qubes-users] default dispvm template has a different networking setting than this qube

2019-12-05 Thread Guerlan
I installed Kali Linux (as a non template vm) and in the qubes setting for 
this Kali it says:

default dispvm template has a different networking setting than this qube, 
unexpected network access may occur

what should I do in Kali for it to work?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0d2e6664-8e01-43ea-b272-dd5f1cc961d4%40googlegroups.com.


Re: [qubes-users] equivalent of grub kernel parameters on qubes?

2019-10-28 Thread Guerlan
I scrolled and couldn't find what you suggested.

The contents of /boot/efi/EFI is a qubes folder which has qubes kernels and 
xen.cfg, xen.efi

On Monday, October 28, 2019 at 11:35:06 AM UTC-3, unman wrote:
>
> On Sun, Oct 27, 2019 at 10:07:25PM -0700, Guerlan wrote: 
> > I tried to locate that file on dom0 but I couldn't find. Was it supposed 
> to 
> > be elsewhere? (yes, I installed with UEFI) 
> > 
> > On Sunday, October 27, 2019 at 11:59:05 AM UTC-3, unman wrote: 
> > > 
> > > On Fri, Oct 25, 2019 at 05:41:37PM -0700, Guerlan wrote: 
> > > > There's a quirk for laptop suspend problem that I want to try on 
> Qubes 
> > > that 
> > > > is the following on Ubuntu: 
> > > > 
> > > > sudo nano /etc/default/grub 
> > > > GRUB_CMDLINE_LINUX_DEFAULT="button.lid_init_state=open" 
> > > > 
> > > > However dom0 does not have such file. How do I pass kernel 
> parameters to 
> > > Qubes? 
> > > > 
> > > 
> > > I have that file but I use standard(legacy) boot. Did you install with 
> > > UEFI? 
> > > If you are using UEFI, I believe you can install a EFI shell and boot 
> > > into it to test change parameters. Or you can edit the file at 
> > > /boot/efi/EFI/qubes/xen.cfg to add your parameters. 
> > > 
> > > NB I dont like UEFI and dont use it, but I think that pointer is 
> right. 
> > > As always, back up any system files before you start changing them. 
> > > 
> > > unman 
> > > 
>
> The convention on these lists is to post at the bottom of the message, 
> so that a new reader can follow the sense by reading downwards. Can you 
> try to do that? All you have to do is scroll to the bottom and 
> start typing. Thanks. 
>
> So do you have /boot/efi/EFI? 
> What are contents? 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/beb02368-906c-4778-8afa-5e65099d4e86%40googlegroups.com.


Re: [qubes-users] equivalent of grub kernel parameters on qubes?

2019-10-27 Thread Guerlan
I tried to locate that file on dom0 but I couldn't find. Was it supposed to 
be elsewhere? (yes, I installed with UEFI)

On Sunday, October 27, 2019 at 11:59:05 AM UTC-3, unman wrote:
>
> On Fri, Oct 25, 2019 at 05:41:37PM -0700, Guerlan wrote: 
> > There's a quirk for laptop suspend problem that I want to try on Qubes 
> that 
> > is the following on Ubuntu: 
> > 
> > sudo nano /etc/default/grub 
> > GRUB_CMDLINE_LINUX_DEFAULT="button.lid_init_state=open" 
> > 
> > However dom0 does not have such file. How do I pass kernel parameters to 
> Qubes? 
> > 
>
> I have that file but I use standard(legacy) boot. Did you install with 
> UEFI? 
> If you are using UEFI, I believe you can install a EFI shell and boot 
> into it to test change parameters. Or you can edit the file at 
> /boot/efi/EFI/qubes/xen.cfg to add your parameters. 
>
> NB I dont like UEFI and dont use it, but I think that pointer is right. 
> As always, back up any system files before you start changing them. 
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/dc579d4e-ff18-49e4-ba3e-c55dd6d7fc36%40googlegroups.com.


[qubes-users] equivalent of grub kernel parameters on qubes?

2019-10-25 Thread Guerlan
There's a quirk for laptop suspend problem that I want to try on Qubes that 
is the following on Ubuntu:

sudo nano /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="button.lid_init_state=open"

However dom0 does not have such file. How do I pass kernel parameters to Qubes?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2a5feb78-fabb-48af-9d80-29c20dab5d0c%40googlegroups.com.


[qubes-users] Why is there no option to save VM state?

2019-10-22 Thread Guerlan
In KVM with Qemu I used a lot of VM state saving, where I could save the 
entire VM to disk and restore that. Since my SSD is very fast that only 
took 5 seconds in average, so it was very useful. Specially, since I cannot 
put my laptop to sleep and hibernate wont work either, my only option was 
to be able to save VM state, but I don't see any way of doing it.

Is it possible or is it a feature to be implemented?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/356d3ac5-cc1f-4df1-bdf5-7f8d496825ae%40googlegroups.com.


[qubes-users] Was hibernate supposed to work?

2019-10-22 Thread Guerlan
When I press hibernate, nothing happens. Was it supposed to work? If so, 
how can I debug what's happening?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d032f977-a646-4566-98d6-8c2e36114b70%40googlegroups.com.


[qubes-users] Easy way to copy files from dom0 to VM?

2019-10-18 Thread Guerlan
Currently when I take a screenshot I need to open dom0's terminal and use 
qvm-copy-to-vm which is painful. Isn't there a way to use Nautilus in dom0 
to easily copy to a VM? Os better, isn't there a way to save screenshots 
directly to a VM? Maybe by mounting this VM to dom0 (not a security risk I 
guess, because dom0 already has access to everything)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b30209f2-2c3c-4a71-bdae-8f77125b1be5%40googlegroups.com.


[qubes-users] Re: Creating App Shortcut for a Single AppVM Doesn't Work

2019-10-11 Thread Guerlan
I uses gnome shortcut editor to create the desktop file (optional) and 
saved to desktop. Then I double clicked it in the file manager and opened 
the program one time. Then I think I rebooted (I don't remember) but it was 
there in the qubes settings->applications

hope it helps

On Friday, October 11, 2019 at 10:03:34 PM UTC-3, pudding wrote:
>
> Hi, 
>
> I downloaded the AppImage version of KeePassXC, moved it to an Debian 
> 10-based AppVM "kpxc", and wanted to create a dom0 startmenu entry for 
> it. I followed the "If you only want to create a shortcut for a single 
> AppVM..." part of the guide here: 
> https://www.qubes-os.org/doc/managing-appvm-shortcuts/ , but after 
> completing the steps and rebooting, there is still no entry of KeePassXC 
> under kpxc in the startmenu, and I couldn't figure out why. Here's the 
> content of ~/.local/share/applications/kpxc-KeePassXC.desktop which I 
> wrote: 
>
> Version=1.0 
>
> Type=Application 
>
> Terminal=false 
>
> Name=kpxc: KeePassXC 
>
> GenericName=kpxc: Password Manager 
>
> Comment=Manage Passwords 
>
> Exec=qvm-run kpxc '~/Desktop/KeePassXC.AppImage' 
>
>
> Both dom0 and Debian template are updated to the lastest stable. 
>
> Any help would be appreciated! 
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/afdb2a7f-cfdf-44f6-b169-991a458b59b6%40googlegroups.com.


Re: [qubes-users] Does installing things with sudo affect my template and therefore all VMs that use this template?

2019-10-11 Thread Guerlan
thanks, that explains why I needed to install gnome-disks every time I 
plugged a disk. I wondered why it didn t stay

On Friday, October 11, 2019 at 7:37:44 PM UTC-3, Claudia wrote:
>
> Guerlan: 
> > I installed some drivers on a sys-net-2 VM. Does that men they are 
> > installed on the template then? 
>
> No. Probably not. The root directory is shared, but only for reading. 
> Any changes are visible only within that VM, and are lost on reboot. 
> Exceptions are anything mapped to /rw (e.g. /home/user and /usr/local). 
>
> If you want to install something permanently, without affecting other 
> VMs, the simplest way is to create a StandaloneVM. Alternatively, you 
> can clone the TemplateVM and install your package in it, then create an 
> AppVM using the new TemplateVM. 
>
> https://www.qubes-os.org/doc/software-update-domu/ 
>
> - 
> This free account was provided by VFEmail.net - report spam to 
> ab...@vfemail.net  
>   
> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of 
> the NSA's hands! 
> $24.95 ONETIME Lifetime accounts with Privacy Features!   
> 15GB disk! No bandwidth quotas! 
> Commercial and Bulk Mail Options!   
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e4f58228-c80b-46c6-9679-081824273175%40googlegroups.com.


Re: [qubes-users] Does installing things with sudo affect my template and therefore all VMs that use this template?

2019-10-11 Thread Guerlan
I installed some drivers on a sys-net-2 VM. Does that men they are 
installed on the template then?



On Friday, October 11, 2019 at 6:04:15 PM UTC-3, steve.coleman wrote:
>
> On 2019-10-11 14:16, Guerlan wrote: 
> > The root folder is shared, only the /home is unique for each VM. Does 
> > that mean that is I instal anything with sudo in one VM, it will affect 
> > the template and therefore all other VMs? 
>
> When you install software in /usr or /opt in the template VM it will be 
> visible in all the user VM's that use that template. The settings to 
> automatically launch daemon processes may need to be enabled for each 
> AppVM depending on both yours and the particular software package 
> requirements. You may not necessarily need a cron job or a daemon to run 
> in every AppVM instance, for example. 
>
> If you instead install software in the AppVM's /home/user/* or 
> /usr/local/* (basically any directory automatically remapped from the 
> private volume /rw/* ), then the software will be available only within 
> that single AppVM. 
>
> Where it makes sense to install a particular third-party software 
> package depends highly on what that specific software needs in order to 
> function properly. If the software is installed locally in /usr/local 
> but then still wants its configuration files to be in /etc, or needs 
> cron, then you may need to work around that specific problem with either 
> copying the configuration file separately into the template VM /etc, or 
> else using some magic scripting during the AppVM startup to copy the 
> config file into the right location before the software that needs it is 
> actually started. There is usually a workaround that will get the job 
> done, but you may need to learn a bit more about how each software 
> package works than you normally would on some other less secure system. 
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6c7e94cf-62fe-488c-9cc2-403a789f6762%40googlegroups.com.


[qubes-users] qubes-builder error: target not found: linux

2019-10-11 Thread Guerlan
I've ran qubes-builder by selecting ubuntu, debian, arch and kali. However 
I always end up in this error after running make qubes-vm:

(11/11) Rebuilding certificate stores...
  --> Removing non-required linux kernel (can be added manually through a 
package)...
error: target not found: linux
make[1]: *** 
[/home/user/qubes-builder/qubes-src/builder-archlinux/Makefile.archlinux:104: 
/home/user/qubes-builder/chroot-vm-archlinux/home/user/.prepared_base] 
Error 1
make: *** [Makefile:226: vmm-xen-vm] Error 1

there's no issues in the github project so I can't talk directly to them

anyone knows what  is happening?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3636bbac-4bfc-4094-92f5-fdd48fdc89f2%40googlegroups.com.


[qubes-users] Wifi card adapter wont appear inside VM

2019-10-11 Thread Guerlan
I have a MediaTek card adapter. I redirected it to the VM. When I run lsusb 
inside the VM, it won't appear.

How do I troubleshoot this?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a7d96c4f-38c5-4e71-b914-646c9a5d06cc%40googlegroups.com.


[qubes-users] Does installing things with sudo affect my template and therefore all VMs that use this template?

2019-10-11 Thread Guerlan
The root folder is shared, only the /home is unique for each VM. Does that 
mean that is I instal anything with sudo in one VM, it will affect the 
template and therefore all other VMs?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6cd98a22-adcc-45c3-bc7c-3c179b75f49e%40googlegroups.com.


Re: [qubes-users] Any virtualizer / emulator working in Qubes OS?

2019-10-11 Thread Guerlan
nested virtualization would be very useful for android development but I 
only found unconclusive posts about how to do it

On Friday, October 11, 2019 at 4:01:18 AM UTC-3, Jean-Philippe Ouellet 
wrote:
>
> Currently: anything that doesn't require nested virt, meaning anything 
> that actually emulates instead of trying to use vmx (via kvm, etc.). 
>
> Examples include qemu using its tcg backend instead of kvm, and bochs. 
>
> On Thu, Sep 19, 2019 at 11:58 AM Patrick Schleizer 
> > wrote: 
> > 
> > Is there any virtualizer / emulator working inside Qubes OS AppVMs? 
> > 
> > -- 
> > 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...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/2d7d4f20-b255-ed3b-30ef-7b98bfd44e69%40whonix.org.
>  
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f5733f2b-7660-45f0-b910-b9ff44fa1df7%40googlegroups.com.


[qubes-users] Re: Easiest way to redirect USB to a VM?

2019-10-10 Thread Guerlan
after reading carefully I found the option to automatically add the 
keyboard and create the sys-usb vm

On Monday, October 7, 2019 at 2:04:05 AM UTC-3, Guerlan wrote:
>
> I tried to create sys-usb, and my keyboard stopped working. I then 
> rebooted and couldn t use keyboard to put my LUKS password. I had to 
> reinstall qubes entirely.
>
> Is there an easier way to pass USB from dom0 to a VM? I don' t want to 
> create a sys-usb and I don' t care too much about security in this level. I 
> just need to have my Android phone inside the virtual machine.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ff51ed42-3a71-4acc-86ce-32253570c8e9%40googlegroups.com.


[qubes-users] Is there a fix for constantly failing wifi?

2019-10-10 Thread Guerlan
I have a Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)

It constantly goes off. I tried the rmmod and insert from the qubes wifi 
page and it didn't work. I then discovered that simply turning it off and 
on in the tray icon works. However I have to do it every 15 mintutes, and 
if I download something huge (that is, I use a lot of wifi) it goess off 
and I have to restart it every 30 seconds, itś  very annoying!

Is there a way to fix 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/46b024fe-41f0-4e27-b5be-92352e58d0ac%40googlegroups.com.


Re: [qubes-users] laptop screen wont appear after closing lid

2019-10-10 Thread Guerlan
I did the HCL report and sent.

I tried the manual sleep and it wont work, the same thing happens as when I 
close the lid: the keyboard goes off and the screen goes blank and nothing 
returns when I open. I tried pressing the power button but also didn't work.

The workaround isn't good for me because my notebook has very limited 
battery, so I need for it to sleep while closed.

I tried Fedora 30 and sleep worked perfectly. I just closed the lid and 
reopened and it worked.

On Tuesday, October 8, 2019 at 7:52:03 PM UTC-3, Claudia wrote:
>
> Guerlan: 
> > Whenever I close the lid of the notebook, when I open again, I see the 
> > keyboard light lightning up but the screen never lights and I have to 
> > reboot. 
> > 
> > Is there a fix for it? 
> > 
>
> It sounds like suspend/resume isn't working correctly on your laptop 
> under Qubes. Does the same thing happen when you click suspend from the 
> logout menu? 
>
> As a workaround, open the Xfce Power Manager (Start -> System Tools -> 
> Power Manager) and change the lid switch to "do nothing." This way it 
> won't go into suspend when you close the lid, but it'll at least turn 
> off the screen. 
>
> Something else to try: download Fedora 30 and boot into a live CD/USB, 
> and try suspend/resume (by closing the lid) from there, and see if the 
> screen comes back on. If it does, it probably means Qubes' dom0 (F25) is 
> too old for your hardware. 
>
> Also it would help to know the make and model of your laptop. Ideally, 
> you can submit an HCL report: https://www.qubes-os.org/doc/hcl/ 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3a901720-bb25-44b1-ac81-d0f0085c66b7%40googlegroups.com.


Re: [qubes-users] Easiest way to redirect USB to a VM?

2019-10-08 Thread Guerlan
I installed android-tools and it didn't work.

Are you sure I don't need a sys-usb VM?

On Tuesday, October 8, 2019 at 6:44:22 PM UTC-3, steve.coleman wrote:
>
> On 2019-10-08 17:35, Guerlan wrote: 
> > On Ubuntu it always worked out of th ebox,I only had to choose the rigth 
> > USB option in Android. 
> > 
> > How can I install things in dom0? Is it posible? 
>
> To search what is available: 
>
> dom0$ sudo qubes-dom0-update --action=search  
>
> then: 
>
> dom0$ sudo qubes-dom0-update  
>
> Be careful not to install any dangerous software that you don't actually 
> need in dom0. Its best to leave that to the VM's that will be mounting 
> the phone USB. 
>
>
> > I tried all USB modes on 2 phones and I get nothing on both qvm-usb and 
> > qvm-block 
> > 
> > I also plugged an Yubikey and it appears in lsusb (the phones appear 
> > too) but they don't appear in the devices tray icon. 
> > 
> > On Tuesday, October 8, 2019 at 6:14:39 PM UTC-3, steve.coleman wrote: 
> > 
> > On 2019-10-08 16:44, Guerlan wrote: 
> >  > I tried that too, but when I run qvm-usb I get an empty list of 
> usb 
> >  > devices. Running lsusb obviously gives me a lot of usb devices 
> (on 
> >  > dom0). So I thought sys-usb is needed for USB to work. What am I 
> > doing 
> >  > wrong? 
> > 
> > I think the trick is to: 
> > 
> > 1) Make sure your Android device presents itself as a USB drive, so 
> > that 
> > you can copy/move files between the device and the VM. 
> > 
> > Q: Have you used the phone with any other Linux/Windows machine such 
> > that you know it is configured to present the USB drive interface? 
> I'm 
> > pretty sure you need to configure that on the phone first. 
> > 
> > 2) Then Dom0 needs to have the proper tools/drivers to see that USB 
> > device as a drive, so that it can be passed/attached via the command 
> > line tools or the toolbar applet. I know that fedora-25 has a 
> > "android-tools" package that might be needed for this. 
> > 
> > Once you can see it in dom0 using qvm-usb/qvm-block you should be 
> able 
> > to pass it through to your VM with the toolbar applet or qvm-block 
> > attach. 
> > 
> > Its been a long while since I have done this, and I have not yet 
> > done it 
> > with either Qubes4.x nor my current Android phone, so your mileage 
> may 
> > vary greatly. 
> > 
> > 
> > 
> > 
> > -- 
> > 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...@googlegroups.com  
> > <mailto:qubes-users+unsubscr...@googlegroups.com >. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/qubes-users/cbbed5fa-400a-44e6-8efc-832a5157af76%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/qubes-users/cbbed5fa-400a-44e6-8efc-832a5157af76%40googlegroups.com?utm_medium=email_source=footer>.
>  
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b21af873-2217-4550-9c16-d88b89ee0eea%40googlegroups.com.


Re: [qubes-users] Easiest way to redirect USB to a VM?

2019-10-08 Thread Guerlan
On Ubuntu it always worked out of th ebox,I only had to choose the rigth 
USB option in Android.

How can I install things in dom0? Is it posible?

I tried all USB modes on 2 phones and I get nothing on both qvm-usb and 
qvm-block

I also plugged an Yubikey and it appears in lsusb (the phones appear too) 
but they don't appear in the devices tray icon.

On Tuesday, October 8, 2019 at 6:14:39 PM UTC-3, steve.coleman wrote:
>
> On 2019-10-08 16:44, Guerlan wrote: 
> > I tried that too, but when I run qvm-usb I get an empty list of usb 
> > devices. Running lsusb obviously gives me a lot of usb devices (on 
> > dom0). So I thought sys-usb is needed for USB to work. What am I doing 
> > wrong? 
>
> I think the trick is to: 
>
> 1) Make sure your Android device presents itself as a USB drive, so that 
> you can copy/move files between the device and the VM. 
>
> Q: Have you used the phone with any other Linux/Windows machine such 
> that you know it is configured to present the USB drive interface? I'm 
> pretty sure you need to configure that on the phone first. 
>
> 2) Then Dom0 needs to have the proper tools/drivers to see that USB 
> device as a drive, so that it can be passed/attached via the command 
> line tools or the toolbar applet. I know that fedora-25 has a 
> "android-tools" package that might be needed for this. 
>
> Once you can see it in dom0 using qvm-usb/qvm-block you should be able 
> to pass it through to your VM with the toolbar applet or qvm-block attach. 
>
> Its been a long while since I have done this, and I have not yet done it 
> with either Qubes4.x nor my current Android phone, so your mileage may 
> vary greatly. 
>
>
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cbbed5fa-400a-44e6-8efc-832a5157af76%40googlegroups.com.


Re: [qubes-users] Easiest way to redirect USB to a VM?

2019-10-08 Thread Guerlan
I tried that too, but when I run qvm-usb I get an empty list of usb 
devices. Running lsusb obviously gives me a lot of usb devices (on dom0). 
So I thought sys-usb is needed for USB to work. What am I doing wrong?

On Tuesday, October 8, 2019 at 5:39:35 PM UTC-3, Mike Keehan wrote:
>
> On Tue, 8 Oct 2019 11:40:23 -0700 (PDT) 
> Guerlan > wrote: 
>
> > Yes, I followed that topic and when I created the sys-usb VM mey 
> > keyboard and mouse got disabled and I couldn't do anything else. 
> > 
> > That's why I asked if there's an easier (possibly less secure) way to 
> > redirect the USB from dom0 directly to another VM. I can't create a 
> > sys-usb because I will be left without keyboard 
> > 
> > On Monday, October 7, 2019 at 9:06:50 AM UTC-3, Mike Keehan wrote: 
> > > 
> > > On Sun, 6 Oct 2019 22:04:05 -0700 (PDT) 
> > > Guerlan > wrote: 
> > >   
> > > > I tried to create sys-usb, and my keyboard stopped working. I 
> > > > then rebooted and couldn t use keyboard to put my LUKS password. 
> > > > I had to reinstall qubes entirely. 
> > > > 
> > > > Is there an easier way to pass USB from dom0 to a VM? I don' t 
> > > > want to create a sys-usb and I don' t care too much about 
> > > > security in this level. I just need to have my Android phone 
> > > > inside the virtual machine. 
> > > >   
>
> > > 
> > > Have you read the docs?  https://www.qubes-os.org/doc/usb-devices/ 
> > >   
> > 
>
> In the link above, the section titled "With The Command Line Tool" shows 
> how to use qvm-usb in dom0 to attach usb devices to a VM. 
>
> (I think you have been reading the usb-qubes page, and not that in the 
> link given above!). 
>
> Mike. 
>
> ps - mailing list etiquette is to post replies below the email, not 
> above. 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7bd940e7-1987-4a71-aa3d-adfa12eee894%40googlegroups.com.


Re: [qubes-users] Easiest way to redirect USB to a VM?

2019-10-08 Thread Guerlan
Yes, I followed that topic and when I created the sys-usb VM mey keyboard 
and mouse got disabled and I couldn't do anything else.

That's why I asked if there's an easier (possibly less secure) way to 
redirect the USB from dom0 directly to another VM. I can't create a sys-usb 
because I will be left without keyboard

On Monday, October 7, 2019 at 9:06:50 AM UTC-3, Mike Keehan wrote:
>
> On Sun, 6 Oct 2019 22:04:05 -0700 (PDT) 
> Guerlan > wrote: 
>
> > I tried to create sys-usb, and my keyboard stopped working. I then 
> > rebooted and couldn t use keyboard to put my LUKS password. I had to 
> > reinstall qubes entirely. 
> > 
> > Is there an easier way to pass USB from dom0 to a VM? I don' t want 
> > to create a sys-usb and I don' t care too much about security in this 
> > level. I just need to have my Android phone inside the virtual 
> > machine. 
> > 
>
> Have you read the docs?  https://www.qubes-os.org/doc/usb-devices/ 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c6aa536e-12fd-4046-af68-ce0c0e91a9a0%40googlegroups.com.


[qubes-users] laptop screen wont appear after closing lid

2019-10-08 Thread Guerlan
Whenever I close the lid of the notebook, when I open again, I see the 
keyboard light lightning up but the screen never lights and I have to 
reboot.

Is there a fix for 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ed421d19-6ac1-4e06-8f2e-102823274ead%40googlegroups.com.


[qubes-users] Easiest way to redirect USB to a VM?

2019-10-06 Thread Guerlan
I tried to create sys-usb, and my keyboard stopped working. I then rebooted 
and couldn t use keyboard to put my LUKS password. I had to reinstall qubes 
entirely.

Is there an easier way to pass USB from dom0 to a VM? I don' t want to 
create a sys-usb and I don' t care too much about security in this level. I 
just need to have my Android phone inside the virtual machine.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/687e3ce2-19b9-43e4-bc12-2305750b985c%40googlegroups.com.


[qubes-users] Is it possible to PCI passthrough my only GPU temporary to a VM?

2019-10-05 Thread Guerlan
I only have one GPU, which is an Intel UDH graphics. Obviously Qubes uses 
it to display graphics. However, I think it's theoretically possible to 
disable my GPU from dom0 and do a PCI passthrough to another VM, which will 
then appear as fullscreen (I will not be able to use Qubes meanwhile). Then 
when I need Qubes again I can simply reattach the GPU to dom0.

Is it really possible, and if so, could someone guide me into how to 
achieve this? 

I mainly want this because my laptop don't have a dedicated GPU and I'm 
developing an application which decodes video and sometimes I need to test 
GPU decoding. It'd be also fun to play some video games.


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/260544e4-59af-4a9d-9622-3be63bc7b77b%40googlegroups.com.


Re: [qubes-users] Re: Installing in UEFI without reefind (razer blade stealth 16gb ram 2016)

2017-12-09 Thread Guerlan
On Saturday, December 9, 2017 at 5:39:32 PM UTC-2, Matteo wrote:
> >> update: I doscovered that Legacy Mode is called CSM on some 
> >> BIOS(https://github.com/QubesOS/qubes-issues/issues/2838#issuecomment-349234545
> >>  ), so I found that my system actually supports it. However, when I boot 
> >> into legacy mode, I only see an empty black screen, forever. Here's my CSM 
> >> menu:
> >>
> >> https://photos.app.goo.gl/Qbv7OBnXquEcHkTF3
> > 
> > I'd however prefer to install it in uefi mode, if possible. Could somebody 
> > discover what is going on?
> > 
> 
> i'm not expert but from the photo there is launch video option rom [uefi
> only]
> to me it seems "use video card only in uefi mode"
> so this could explain why you see nothing if you boot legacy.
> 
> try enable everything in that meny also for legacy/csm (but not pxe, is
> not needed. it is network boot you don't need it).
> 
> try again legacy, it's easier to have it working.

yes, it worked with that video thing, but graphical installation won't launch, 
and text installation is buggy in 3.2. Anyways, I moved to 4.0rc3 and I'm 
having these problems now: 
https://groups.google.com/forum/#!topic/qubes-users/drw9j_EuPPk

Anyways, the UEFI problem is still not fixed in 4.0rc3. Does somebody know what 
to do?

-- 
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/6797aa4e-f6ca-4cde-bf41-d726cedd741b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Qubes 4 rc3 unpacking errors durint installation

2017-12-09 Thread Guerlan
First of all, I tried installing 3.2, but graphical installation won't launch, 
and text installation has a bug which prevents me from installing. Also, UEFI 
still has all that old bugs, so I had to install with legacy mode. In 4.0rc3 
graphical installation launches. I verified the pen drive checksum with dd 
before booting, and also launched 'test and install'. At some time on the 
installation, I got

https://photos.google.com/share/AF1QipMXz9KLUxsmw3OPK4ufYmw3xeyj7frOSwu3RV_zMKDtSxPeQtxYeg0g27OyCggVSw/photo/AF1QipPGKbVHkH4erY53Nkq63b0ahMoZ_Vcj-GDPjVkt?key=N0V3YloyRlZIa1BkbDVQcEd6WWJZVTY2bjlES093


after that, I did everything again with another pen drive, and got this error:

https://photos.google.com/share/AF1QipMXz9KLUxsmw3OPK4ufYmw3xeyj7frOSwu3RV_zMKDtSxPeQtxYeg0g27OyCggVSw/photo/AF1QipMOgKd9Us6k5MnZyq9KmjIEExHQwG90PHBfklmK?key=N0V3YloyRlZIa1BkbDVQcEd6WWJZVTY2bjlES093

what is happening?

-- 
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/e8bed3d0-6502-4cf6-bd95-80f8000812c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Installation "Couldn't obtain the File System Protocol Interface."

2017-12-09 Thread Guerlan
On Saturday, September 23, 2017 at 9:53:09 PM UTC-3, janchristop...@gmail.com 
wrote:
> Hey folks,
> 
> currently trying to install QubesOS 3.2 from USB which I created using rufus.
> After booting the installation medium, I get the message "Couldn't obtain the 
> File System Protocol Interface." 
> Then I am returned to the Menu of the installation medium, after which 
> selecting any option just refreshes the menu.
> 
> Using a MSI B250M Mortar, set the boot option to "UEFI + Legacy" (the only 
> other option being "UEFI").
> 
> Anyone with similar struggles or suggestions?
> 
> Cheers

same here :(

-- 
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/acd3e645-b30d-4e6d-beda-65435e94dd27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Installing in UEFI without reefind (razer blade stealth 16gb ram 2016)

2017-12-08 Thread Guerlan
On Saturday, December 9, 2017 at 4:32:08 AM UTC-2, Guerlan wrote:
> On Saturday, December 9, 2017 at 4:17:21 AM UTC-2, Guerlan wrote:
> > I'm trying to install Qubes on my Razer Blade Stealth (4k 2016 16gb ram). 
> > It has no legacy mode, so I need to install in UEFI mode. Also, I don't 
> > want to trust reefind. 
> > 
> > Here's the problem I'm having. First, in the installaiton menu, anything I 
> > click leads me to this fast message that appears in the screen:
> > 
> > https://photos.google.com/share/AF1QipOUP-zk0Km0KnofmVDFVeKU01CElFTLqe94eH05H41B9PTkcQorHsvOYAbF87uIWA/photo/AF1QipNGHHM_QYgu_r_umhMC3hjfZZZqmsK5ZT3xiVJK?key=emxGYk1GM3A5Y0RrUmZOTzlFMzZsanBiaDN2MVVR
> > 
> > I followed https://www.qubes-os.org/doc/uefi-troubleshooting/
> > 
> > First step says
> > 
> > In GRUB menu1, select “Troubleshoot”, then “Boot from device”, then press e.
> > 
> > There's no "Troubleshoot" option alone, instead, there is 
> > 
> > "Troubleshoot - verbose boot and install Qubes 3.2", so there is no “Boot 
> > from device” option to choose, because when I click this, I get the fast 
> > message and then return to the same screen. Anyways, I pressed 'e' and 
> > edited the line by adding /mapbs /noexitboot at the end of it, then gave 
> > control-x. It displays a fast message again and returns to the edited text
> > 
> > https://photos.google.com/share/AF1QipOUP-zk0Km0KnofmVDFVeKU01CElFTLqe94eH05H41B9PTkcQorHsvOYAbF87uIWA/photo/AF1QipPWg5qiTSs8dpiKIu-QLdJzFuu5p-AFqMDbOnSf?key=emxGYk1GM3A5Y0RrUmZOTzlFMzZsanBiaDN2MVVR
> > 
> > 
> > 
> > Anybody knows what am I doing wrong?
> 
> update: I doscovered that Legacy Mode is called CSM on some 
> BIOS(https://github.com/QubesOS/qubes-issues/issues/2838#issuecomment-349234545
>  ), so I found that my system actually supports it. However, when I boot into 
> legacy mode, I only see an empty black screen, forever. Here's my CSM menu:
> 
> https://photos.app.goo.gl/Qbv7OBnXquEcHkTF3

I'd however prefer to install it in uefi mode, if possible. Could somebody 
discover what is going on?

-- 
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/bc284afd-fb79-4011-88c4-de2fcf047043%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Installing in UEFI without reefind (razer blade stealth 16gb ram 2016)

2017-12-08 Thread Guerlan
On Saturday, December 9, 2017 at 4:17:21 AM UTC-2, Guerlan wrote:
> I'm trying to install Qubes on my Razer Blade Stealth (4k 2016 16gb ram). It 
> has no legacy mode, so I need to install in UEFI mode. Also, I don't want to 
> trust reefind. 
> 
> Here's the problem I'm having. First, in the installaiton menu, anything I 
> click leads me to this fast message that appears in the screen:
> 
> https://photos.google.com/share/AF1QipOUP-zk0Km0KnofmVDFVeKU01CElFTLqe94eH05H41B9PTkcQorHsvOYAbF87uIWA/photo/AF1QipNGHHM_QYgu_r_umhMC3hjfZZZqmsK5ZT3xiVJK?key=emxGYk1GM3A5Y0RrUmZOTzlFMzZsanBiaDN2MVVR
> 
> I followed https://www.qubes-os.org/doc/uefi-troubleshooting/
> 
> First step says
> 
> In GRUB menu1, select “Troubleshoot”, then “Boot from device”, then press e.
> 
> There's no "Troubleshoot" option alone, instead, there is 
> 
> "Troubleshoot - verbose boot and install Qubes 3.2", so there is no “Boot 
> from device” option to choose, because when I click this, I get the fast 
> message and then return to the same screen. Anyways, I pressed 'e' and edited 
> the line by adding /mapbs /noexitboot at the end of it, then gave control-x. 
> It displays a fast message again and returns to the edited text
> 
> https://photos.google.com/share/AF1QipOUP-zk0Km0KnofmVDFVeKU01CElFTLqe94eH05H41B9PTkcQorHsvOYAbF87uIWA/photo/AF1QipPWg5qiTSs8dpiKIu-QLdJzFuu5p-AFqMDbOnSf?key=emxGYk1GM3A5Y0RrUmZOTzlFMzZsanBiaDN2MVVR
> 
> 
> 
> Anybody knows what am I doing wrong?

update: I doscovered that Legacy Mode is called CSM on some 
BIOS(https://github.com/QubesOS/qubes-issues/issues/2838#issuecomment-349234545 
), so I found that my system actually supports it. However, when I boot into 
legacy mode, I only see an empty black screen, forever. Here's my CSM menu:

https://photos.app.goo.gl/Qbv7OBnXquEcHkTF3

-- 
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/aa16cb02-4c90-4556-a5e4-01816840ea8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Installing in UEFI without reefind (razer blade stealth 16gb ram 2016)

2017-12-08 Thread Guerlan
I'm trying to install Qubes on my Razer Blade Stealth (4k 2016 16gb ram). It 
has no legacy mode, so I need to install in UEFI mode. Also, I don't want to 
trust reefind. 

Here's the problem I'm having. First, in the installaiton menu, anything I 
click leads me to this fast message that appears in the screen:

https://photos.google.com/share/AF1QipOUP-zk0Km0KnofmVDFVeKU01CElFTLqe94eH05H41B9PTkcQorHsvOYAbF87uIWA/photo/AF1QipNGHHM_QYgu_r_umhMC3hjfZZZqmsK5ZT3xiVJK?key=emxGYk1GM3A5Y0RrUmZOTzlFMzZsanBiaDN2MVVR

I followed https://www.qubes-os.org/doc/uefi-troubleshooting/

First step says

In GRUB menu1, select “Troubleshoot”, then “Boot from device”, then press e.

There's no "Troubleshoot" option alone, instead, there is 

"Troubleshoot - verbose boot and install Qubes 3.2", so there is no “Boot from 
device” option to choose, because when I click this, I get the fast message and 
then return to the same screen. Anyways, I pressed 'e' and edited the line by 
adding /mapbs /noexitboot at the end of it, then gave control-x. It displays a 
fast message again and returns to the edited text

https://photos.google.com/share/AF1QipOUP-zk0Km0KnofmVDFVeKU01CElFTLqe94eH05H41B9PTkcQorHsvOYAbF87uIWA/photo/AF1QipPWg5qiTSs8dpiKIu-QLdJzFuu5p-AFqMDbOnSf?key=emxGYk1GM3A5Y0RrUmZOTzlFMzZsanBiaDN2MVVR



Anybody knows what am I doing wrong?

-- 
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/feba843e-7686-4a17-8d53-0de4e69b5171%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - Razer Blade Stealth (Late 2016 Model)

2017-11-16 Thread Guerlan
How did you install in UEFI mode? Mine will show a terminal with some text for 
less than 1 second and turn back to the installation menu. Secure boot is 
disabled. The far I get is the first menu that appears

-- 
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/ba2a8b81-2a58-4b22-aa44-ad4ae478adab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Is there a way to use secure boot with qubes?

2017-11-09 Thread Guerlan
On Thursday, November 9, 2017 at 9:27:01 AM UTC-2, blacklight wrote:
> On Wednesday, 8 November 2017 20:52:14 UTC, Guerlan  wrote:
> > My computer complains about bad signature when I try to install qubes. Is 
> > there a way to install it without disabling secure boot? Does qubes support 
> > secure boot? Is there a way to install qubes keys on the BIOS? Why did it 
> > reject the keys?
> 
> the question is more that if secureboot supports qubes, rather than the 
> otherway around.  to be supported by secureboot, one would need to buy a very 
> expensive license from microsoft, something qubes is not able afford atm.

thanks, now I understand. I thought qubes had a signature but it was failing in 
my computer. I'm gonna try to install without secure boot then :)

-- 
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/890e05a1-407a-42d1-a0ab-572d12298c18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Is there a way to use secure boot with qubes?

2017-11-08 Thread Guerlan
On Thursday, November 9, 2017 at 2:06:28 AM UTC-2, tai...@gmx.com wrote:
> On 11/08/2017 03:52 PM, Guerlan wrote:
> 
> > My computer complains about bad signature when I try to install qubes. Is 
> > there a way to install it without disabling secure boot? Does qubes support 
> > secure boot? Is there a way to install qubes keys on the BIOS? Why did it 
> > reject the keys?
> >
> If you can't turn off "secure" boot then return your computer and buy 
> one for real (as of now it is simply a lease if you can't install 
> whatever OS and bootloader you want).
> Owner controllability is very important, I suggest a lenovo g505s with 
> coreboot (this laptop has open source init unlike many others and it has 
> no ME/PSP or hardware code signing enforcement)

I can turn it off, its a simple BIOS switch, but I wanted to know if it's 
possible to install with secure boot, so I don't need to trust my pen drive for 
example. 

-- 
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/b0ee29fe-afad-40f9-9e3f-edbbcd9b9a74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Is there a way to use secure boot with qubes?

2017-11-08 Thread Guerlan
My computer complains about bad signature when I try to install qubes. Is there 
a way to install it without disabling secure boot? Does qubes support secure 
boot? Is there a way to install qubes keys on the BIOS? Why did it reject the 
keys?

-- 
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/e7b1a882-02d4-4b2c-ac9a-2907577497ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Is there a way to use secure boot with qubes?

2017-11-08 Thread Guerlan
On Wednesday, November 8, 2017 at 6:52:14 PM UTC-2, Guerlan wrote:
> My computer complains about bad signature when I try to install qubes. Is 
> there a way to install it without disabling secure boot? Does qubes support 
> secure boot? Is there a way to install qubes keys on the BIOS? Why did it 
> reject the keys?

its a razer blade stealth 2016 or 2017 model

-- 
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/dcc9a87a-eee0-4663-b598-d15aa48150fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Why Qubes won't UEFI boot on Macbook Air and why it isn't fixed?

2017-09-04 Thread Guerlan
But it does support UEFI, as I already installed arch linux in uefi mode. So if 
it supports, why it won't boot qubes?

-- 
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/5e32f4ac-327f-43d7-88a3-cd62c5179c3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Why Qubes won't UEFI boot on Macbook Air and why it isn't fixed?

2017-09-04 Thread Guerlan
Its a macbook air 2011. So old it doesn't have secure boot :(

-- 
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/fea6528d-a716-4fd6-9f6e-18e075a71493%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Why Qubes won't UEFI boot on Macbook Air and why it isn't fixed?

2017-09-03 Thread Guerlan
but why it won't work? I was intersted in the reason behind this, and why it 
wasn't fixed. Also, did you install rEFInd before?

-- 
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/5a39bdd4-8c17-44b4-bd88-3bb7100e7e34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Why Qubes won't UEFI boot on Macbook Air and why it isn't fixed?

2017-09-02 Thread Guerlan
I've just found how to install Qubes on my Macbook Air 2011. It requires me to 
activate BIOS booting. Why Qubes won't UEFI boot on my mac? Why it wasn't fixed 
in the update?

This is just a question to learn more about booting, I'm interested :)

-- 
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/0d5abc6e-eb5f-4656-99bd-ff3ca0db23c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.