[qubes-users] Re: Install Qubes in Odroid H2,

2020-04-02 Thread Foppe de Haan
what he means is install Qubes the same way you installed Ubuntu Mate, on 
its own drive.
That said, did you check in the bios if IOMMU and VT-X and VT-D support 
were all enabled?

-- 
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/122b22a1-3aaa-4fb7-8ac5-7973f34175fc%40googlegroups.com.


[qubes-users] Re: How many CPU threads is recommended for Qubes OS ?

2020-04-02 Thread Tech Chris
No, 4 may be enough, but it wont be enough.. I use the ryzen with the 8 
double core and 32ghz ddr4 clocked at 2666 ram SSD 1tb and a Fata1ty 350 
board... I can boot windows 10 from a second ssd in about 8 seconds from 
power up, but qubes takes about 15 seconds, but once up and running, works 
out great..

On Friday, November 8, 2019 at 10:46:17 PM UTC-8, M wrote:
>
> How many CPU threads is recommended for Qubes OS ? 
>
> Is 4 enough, or should I go for 8 or more... ? 
>
> I have bought the Ryzen 3 3200G, but I could change it for another one 
> with more threads (for example the Ryzen 3400G), if it is recommended as I 
> haven’t unpacked it yet.

-- 
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/0e0d5db1-2e68-4d83-bd6e-99440e75cb21%40googlegroups.com.


[qubes-users] Re: Install Qubes in Odroid H2,

2020-04-02 Thread eloybb
Es lo que hecho, pero el .iso lo cargo con KVM.

Me has nombrado baremetal, no he encontrado nada al respecto, parecen ser 
servidores de IBM.


El jueves, 2 de abril de 2020, 14:02:50 (UTC+2), Yethal escribió:
>
>
>
> W dniu środa, 1 kwietnia 2020 13:16:28 UTC+2 użytkownik elo...@gmail.com 
> napisał:
>>
>>
>>
>> El martes, 31 de marzo de 2020, 15:29:50 (UTC+2), Yethal escribió:
>>>
>>> In order for Qubes to work inside KVM your CPU would need to support 
>>> nested virtualization. Either switch your hardware or install baremetal
>>>
>>> W dniu sobota, 28 marca 2020 22:40:03 UTC+1 użytkownik elo...@gmail.com 
>>> napisał:

 I install Ubuntu mate 18.04.4LTS Bionic in x86_64bits, in mate 1.20.1 
 in Personal computer Odroid H2, my computer have a CPU J4105 Intel 
 celeron. 
 I install the libraries for the virtualization of the QEMU virtual 
 machine manager, creating a KVM, QEMU supports Xen type hypervisors. 

 The creation of the virtual machine has the following configuration.

 Considering that my personal computer has 8 GB of RAM and 4 TB of disk 
 space, I have allocated 2 CPUs, 4 GB of ram and 100 gigabytes of storage 
 space, the iso image that I downloaded from the official website is Qubes 
 4.0.3 x86_64 bits.iso, is loaded from the hard disk to start 
 virtualization. The virtual network interface is assigned to the device 
 model of the network card, but I can also choose, virtio.

 The installation has no failures, except the warning that my hardware 
 does not support supports IOMMU / VT-d / AMD-Vi.

 When I start Qubes, the last line fails.
 Failed to start Qubes VM sys-net. But the system loads equally, I start 
 Qubes manager.

 When I try to start whonix -ws, the warning becomes apparent, / usr / 
 bin / qvm-start, sys-firewall failed: stdout:
 stderr: failed to start and HVM qube with PCI devices assigned-hardware 
 does not support IOMMU / VT-d / AMD-Vi

 I try to configure the devices, adding network cards, but I get the 
 same results.* In the Bios I have the VT-d display enabled*, I don't 
 know what else to do, in which I have the PVH mode enabled by default, and 
 I have also tried the HVM mode.

 and tried to update sys-whonix, in terminal, and it shows me the same 
 Qube HVM boot failure message.

 Other collateral errors are, Start failed: invalid argument: could not 
 find capabilities for arch = x86_64, see 
 /var/log/libvirt/libxl/libx-driver.log for details.

 The sys-firewall qube is network connected to sys-net, which does not 
 support firewall.

 You may edit the sys-firewall qube firewall rules, but these will not 
 take any effect until you connect it to a working firewall qube.

 Other comments like PVH, mode is hidden since it doesn't support PCI 
 passthrough.

 [image: 20200320_023124.jpg]

 [image: 20200320_024218.jpg]


 I just need to know how to make the HVM mode work, and know how I can 
 transfer files from my USB, since the recognition of USB devices also 
 fails, everything else works perfectly. I have noticed that my Qubes 
 is something different, I give an example.

 In the following video 
 https://www.youtube.com/watch?v=yrDo0q9qSXs=937s, at minute 37:54, 
 in the option Domain: anon-whonix many options appear, while I only see 
 one. Only 
 Qube settings.
  
 Thanks, and for the culture, I must not stop trying.

>>>
>>  
>>
>>
>> *Where can I download baremetal?*
>>
>>  Download the Qubes ISO and install it like a regular operating 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/c6e67bba-34e4-4dae-a53a-22086ebb1d90%40googlegroups.com.


[qubes-users] Re: Unable to complete Step 3

2020-04-02 Thread 'Ben' via qubes-users
Hi,  I downloaded the iso file and the signing key. Wehn i click to download 
the signature it takes me to a new tab with this on there.

-BEGIN PGP SIGNATURE-

iQIzBAABCAAdFiEEWBekOyg95akYGlIuGEh5L54nlekFAl4lBUYACgkQGEh5L54n
lemMFQ//SlK43KO9RvW+kpvW2CqAyUHZdRLjBymCXx5KED+BxDTE9cPeDDhAarV4
4vw90qX4LJBqndMA8v8UUY1WnfRbOic3dmoez10dZcJGDKI2+2rxbxBh3e4rpkbY
JzcCL7EB/jGDZ+lUr7mhInlCqkGAKfcN+gBMV5wv4et76AgBjzlx4LEovbERy3Rl
5V86QxsT/FsakOu5pxolHbDcFpeOwEXNIBMut4egIm2YXO3aMa9/fVFgLDSzRWsV
6OkH6tio+G8fuij9pG4OJFWfSaud8lrVsHZz0eu5ZfuXcWGN/ieOJBfhwI3uUhfH
4stJFJ6VcVlOdQon0xstKIxJH1O6xoNpOlpT5mAT3EydKrOPaWp65kUHazCWUahO
dSXSxTvFN/OqZ6WkOEe++qLK25MP1wxQHd1lsZR25gATxTPrDvWc/tPwNvwiXxPw
0ywopvXyuL887aSB1jNjucKHml9vwCshF0DKweTSQBQAEIb6r97wQLoLgn1XltVY
NMuAtECtTxe2nRLSD4ujbQQKs8O4M6kBcaK/kIL4EaQX2kgSdYKtTTSJVhliB2TJ
UwvKCtM/zP1mGRrQKnv0U12mY32eV4zW4D1Mkiis5MqFkvQKukmApks9OJuhXml3
Gpnj1j6Bn9pjAdz39eHO9/MBl9KhStSrnvyr8lwy4F3hFtDX5Uk=
=+KxG
-END PGP SIGNATURE-

Best
Ben

‐‐‐ Original Message ‐‐‐
On Thursday, 2 April 2020 08:53, WillyPillow  wrote:

> On Wednesday, April 1, 2020 8:32 AM, Ben  
> wrote:
>
>> Hello, thank you for the help with the second step. it worked as you said 
>> when i changed the X to 4.
>>
>> here's what i get when i try to verify the iso file on the 3rd step.
>>
>> gpg2 -v --verify Qubes-RX-x86_64.iso.asc Qubes-RX-x86_64.iso
>> gpg: can't open 'Qubes-RX-x86_64.iso.asc': No such file or directory
>> gpg: verify signatures failed: No such file or directory
>>
>> I also tried to change the X to a 4 but this also did not work this time.
>>
>> Best
>> Ben
>
> Hi.
>
> (I presume the context was 
> https://groups.google.com/d/msg/qubes-devel/BdjHoVhKs7I/1b5z24StBgAJ)
>
> Not entirely sure why you are sending this (only) to me instead of the ML, so 
> forwarded.
>
> Did you forget to download the signature file from the downloads page by any 
> chance?
>
> --WillyPillow
>
>> https://blog.nerde.pw/
>>
>> PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154 217F 1C16 C70E E7C3 1C84
>>
>> Protonmail PGP = D02D CEFF ACE5 5A7B FF5D 871E 4004 1CB1 F52B 127E

-- 
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/tp28SwX3iOEh7QG4YDkIEvlH3EUro5_ekNT-IOSOplZ4c34C_3nIEnS3sSSLzptFYwnC64cAF23uDe1B2YoStrnpl28fDMK8EvD-YOc2Zzs%3D%40protonmail.com.


[qubes-users] Re: Can't start apps from VM

2020-04-02 Thread Günter Zöchbauer
It looks like it was some code for keyring I added to `~/.profile`  that 
asked for a password.
I commented out that line and now it's working again.

On Thursday, April 2, 2020 at 2:59:07 PM UTC+2, Günter Zöchbauer wrote:
>
> My development VM became quite slow because some kswapd0 (if I remember 
> correctly) running at 100% all the time.
>
> I have my machine usually running 24/7, but I decided to restart to see if 
> this helps (after increasing assigned memory).
>
> After I restarted the machine I wasn't able to start any app for this VM.
> I modified the template quite a lot since I restarted last time, so I 
> wasn't too surprised.
>
> I tried creating a new VM based on the same debian-10 template and all 
> went fine.
>
> Then I went away and when I came back my PC showed the lock screen and was 
> frozen (I had this a few times in the past already).
> So I had to restart again.
>
> After this I couldn't start any application in the new VM as well.
> I tried to start Gnome Terminal from dom0:terminal but nothing happens. No 
> error. The command just hangs until Ctrl-c.
>
> I couldn't find any log file with hints about possible causes.
>
> I can run the VM in debug mode and access the data from the tiny terminal 
> window.
>
> Any ideas how to debug?
>

-- 
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/8a75181e-a1db-4f74-98af-80fce544472f%40googlegroups.com.


[qubes-users] Can't start apps from VM

2020-04-02 Thread Günter Zöchbauer
My development VM became quite slow because some kswapd0 (if I remember 
correctly) running at 100% all the time.

I have my machine usually running 24/7, but I decided to restart to see if 
this helps (after increasing assigned memory).

After I restarted the machine I wasn't able to start any app for this VM.
I modified the template quite a lot since I restarted last time, so I 
wasn't too surprised.

I tried creating a new VM based on the same debian-10 template and all went 
fine.

Then I went away and when I came back my PC showed the lock screen and was 
frozen (I had this a few times in the past already).
So I had to restart again.

After this I couldn't start any application in the new VM as well.
I tried to start Gnome Terminal from dom0:terminal but nothing happens. No 
error. The command just hangs until Ctrl-c.

I couldn't find any log file with hints about possible causes.

I can run the VM in debug mode and access the data from the tiny terminal 
window.

Any ideas how to debug?

-- 
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/c360d75a-8e92-41ec-9765-682b3272d66d%40googlegroups.com.


[qubes-users] Switching desktops causes stuck ctrl key

2020-04-02 Thread Andrew Todd
For the last month or so, I've been having a problem -- intermittently, 
when I switch desktops using Ctrl+Alt+arrow key, I find that on the new 
desktop all applications behave as if the Ctrl key is stuck, constantly 
pressed down. For instance, if I start scrolling the mouse in Firefox, I 
will start zooming in and out on the page.

Experimentally, I can usually clear the stuck key by switching back and 
forth to another desktop a few more times.

Has anyone else encountered 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/ebd447c1-5997-4782-a19b-3b6a7e5b2cfa%40googlegroups.com.


[qubes-users] Re: Unable to complete Step 3

2020-04-02 Thread WillyPillow
On Wednesday, April 1, 2020 8:32 AM, Ben  
wrote:

> Hello, thank you for the help with the second step. it worked as you said 
> when i changed the X to 4.
> 

> here's what i get when i try to verify the iso file on the 3rd step.
> 

> gpg2 -v --verify Qubes-RX-x86_64.iso.asc Qubes-RX-x86_64.iso
> gpg: can't open 'Qubes-RX-x86_64.iso.asc': No such file or directory
> gpg: verify signatures failed: No such file or directory
> 

> I also tried to change the X to a 4 but this also did not work this time.
> 

> Best
> Ben

Hi.

(I presume the context was 
https://groups.google.com/d/msg/qubes-devel/BdjHoVhKs7I/1b5z24StBgAJ)

Not entirely sure why you are sending this (only) to me instead of the ML, so 
forwarded.

Did you forget to download the signature file from the downloads page by any 
chance?

--WillyPillow

> https://blog.nerde.pw/
>
> PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154 217F 1C16 C70E E7C3 1C84
>
> Protonmail PGP = D02D CEFF ACE5 5A7B FF5D 871E 4004 1CB1 F52B 127E

-- 
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/QRukAYbeGN8pGMBDt8e7KGJKNYwW6NVkkQrrFpl4beDFpqrofI98qOWdn9QRKfzZSL9p7kR_6BFTsTWsRS-QVkAMZ5OqjrzDcxvX_4Wd7M8%3D%40nerde.pw.


publickey - wp@nerde.pw - 0xD02DCEFF.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


[qubes-users] Re: Install Qubes in Odroid H2,

2020-04-02 Thread Yethal


W dniu środa, 1 kwietnia 2020 13:16:28 UTC+2 użytkownik elo...@gmail.com 
napisał:
>
>
>
> El martes, 31 de marzo de 2020, 15:29:50 (UTC+2), Yethal escribió:
>>
>> In order for Qubes to work inside KVM your CPU would need to support 
>> nested virtualization. Either switch your hardware or install baremetal
>>
>> W dniu sobota, 28 marca 2020 22:40:03 UTC+1 użytkownik elo...@gmail.com 
>> napisał:
>>>
>>> I install Ubuntu mate 18.04.4LTS Bionic in x86_64bits, in mate 1.20.1 in 
>>> Personal computer Odroid H2, my computer have a CPU J4105 Intel celeron. I 
>>> install the libraries for the virtualization of the QEMU virtual machine 
>>> manager, creating a KVM, QEMU supports Xen type hypervisors. 
>>>
>>> The creation of the virtual machine has the following configuration.
>>>
>>> Considering that my personal computer has 8 GB of RAM and 4 TB of disk 
>>> space, I have allocated 2 CPUs, 4 GB of ram and 100 gigabytes of storage 
>>> space, the iso image that I downloaded from the official website is Qubes 
>>> 4.0.3 x86_64 bits.iso, is loaded from the hard disk to start 
>>> virtualization. The virtual network interface is assigned to the device 
>>> model of the network card, but I can also choose, virtio.
>>>
>>> The installation has no failures, except the warning that my hardware 
>>> does not support supports IOMMU / VT-d / AMD-Vi.
>>>
>>> When I start Qubes, the last line fails.
>>> Failed to start Qubes VM sys-net. But the system loads equally, I start 
>>> Qubes manager.
>>>
>>> When I try to start whonix -ws, the warning becomes apparent, / usr / 
>>> bin / qvm-start, sys-firewall failed: stdout:
>>> stderr: failed to start and HVM qube with PCI devices assigned-hardware 
>>> does not support IOMMU / VT-d / AMD-Vi
>>>
>>> I try to configure the devices, adding network cards, but I get the same 
>>> results.* In the Bios I have the VT-d display enabled*, I don't know 
>>> what else to do, in which I have the PVH mode enabled by default, and I 
>>> have also tried the HVM mode.
>>>
>>> and tried to update sys-whonix, in terminal, and it shows me the same 
>>> Qube HVM boot failure message.
>>>
>>> Other collateral errors are, Start failed: invalid argument: could not 
>>> find capabilities for arch = x86_64, see 
>>> /var/log/libvirt/libxl/libx-driver.log for details.
>>>
>>> The sys-firewall qube is network connected to sys-net, which does not 
>>> support firewall.
>>>
>>> You may edit the sys-firewall qube firewall rules, but these will not 
>>> take any effect until you connect it to a working firewall qube.
>>>
>>> Other comments like PVH, mode is hidden since it doesn't support PCI 
>>> passthrough.
>>>
>>> [image: 20200320_023124.jpg]
>>>
>>> [image: 20200320_024218.jpg]
>>>
>>>
>>> I just need to know how to make the HVM mode work, and know how I can 
>>> transfer files from my USB, since the recognition of USB devices also 
>>> fails, everything else works perfectly. I have noticed that my Qubes is 
>>> something different, I give an example.
>>>
>>> In the following video 
>>> https://www.youtube.com/watch?v=yrDo0q9qSXs=937s, at minute 37:54, in 
>>> the option Domain: anon-whonix many options appear, while I only see one. 
>>> Only 
>>> Qube settings.
>>>  
>>> Thanks, and for the culture, I must not stop trying.
>>>
>>
>  
>
>
> *Where can I download baremetal?*
>
>  Download the Qubes ISO and install it like a regular operating 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/3d540e16-678c-4e0d-a8e0-a3f3fb9e6bf1%40googlegroups.com.