Re: [qubes-users] pgp smart card for luks keyfile

2018-10-01 Thread 'awokd' via qubes-users
hron wrote on 9/28/18 10:47 AM: Hi, I am wondering if it is possible to use a LUKS key file during boot of qubes. In other distros I encrypted that key file with a pgp smart card an could decrypt it during boot by just plugging in the smart card and typing in my PIN code. Does anybody know if

Re: [qubes-users] Re: No Bootable Device after installing Qubes 4.0, Updating VMs and dom0, and rebooting

2018-10-01 Thread 'awokd' via qubes-users
Zelda wrote on 9/29/18 12:10 PM: Does anyone have any insight/ideas as to why the OS is only booting with the backup drive present? During typical use, I don't usually keep the backup drive connected when using the operating system. I'm guessing your system's EFI partition is on the backup

Re: [qubes-users] Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread 'awokd' via qubes-users
'Setherson' via qubes-users wrote on 9/30/18 2:12 AM: I am using Qubes 3.2. All TemplateVMs and dom0 have been updated sometime within the past week. Since about the same time, my Workstation TemplateVM and every AppVM based on it has been unable to connect to the internet. The Whonix

Re: [qubes-users] Installing qr-exec on HVM

2018-10-01 Thread 'awokd' via qubes-users
Will Dizon wrote on 9/28/18 10:04 PM: I am currently working on trying to make a TemplateVM out of a Linux from Scratch installation (or more accurately, BLFS). Progress has been immense, but I've run into a roadblock I'm not sure how to diagnose. For starters, I've gone through and

Re: [qubes-users] ERROR: PCI device does not exist

2018-10-01 Thread 'awokd' via qubes-users
Eric wrote on 9/30/18 10:35 PM: awokd, is there anything else you want me to do before I wipe Qubes off this box? I put up a Centos7.4/Xen4.6 Dom0 (Kernel 4.9.127 which is way earlier than qubes 4.14.67) and everything seems to be running OK, which does seem a bit odd. Since this is a

Re: [qubes-users] Timezone issues after update to Template

2018-10-01 Thread 'awokd' via qubes-users
brandonmaytha...@gmail.com wrote on 9/30/18 11:18 AM: Updated my Fedora Template from Fedora 25 to Fedora 28 as well as Whonix I am running Qubes 4.0 When ever I boot up I get the following from sys-whonix: ERROR: Systemd Clock Check Result: Unexpected results by timedatectl.

Re: [qubes-users] Re: Screen recorder for Qubes..?

2018-10-01 Thread daktak
On Friday, 22 June 2018 22:18:38 UTC+10, ar...@ethereum.org wrote: > > > > The trickiest points (for me) were to compile and install v4l2loopback as a > > kernel module on the template-vm > > > yup. that's where I'm failing. https://gist.github.com/daktak/a3a1025cd9e4ce6e31b5209044877570

[qubes-users] Installation, no AMD-vi, interrupt mapping, etc.

2018-10-01 Thread naasking
My first attempt at installing Qubes brought up a dialog indicating AMD-Vi and interrupt remapping wasn't available. I know my hardware supports the necessary virtualization extensions (AMD FX-8120 on a 990FX mobo), so further investigation suggested that the bios was probably buggy. I updated

Re: [qubes-users] Installation, no AMD-vi, interrupt mapping, etc.

2018-10-01 Thread Jonathan Seefelder
maybe a dump Question, but did you check if its enabled in the BIOS ? ;) cheers On 10/1/18 11:46 AM, naask...@gmail.com wrote: > My first attempt at installing Qubes brought up a dialog indicating AMD-Vi > and interrupt remapping wasn't available. I know my hardware supports the > necessary

Re: [qubes-users] ERROR: PCI device does not exist

2018-10-01 Thread Eric
On 01/10/18 21:36, 'awokd' via qubes-users wrote: Eric wrote on 10/1/18 10:29 AM: When running Centos, does lspci -vvv give the same unusual output for that problem device? Don't know what else to suggest; I have a

Re: [qubes-users] nftables vs iptables

2018-10-01 Thread Chris Laprise
On 10/01/2018 05:48 PM, mfreemon wrote: On 1/11/18 3:01 PM, Chris Laprise wrote: > On 01/10/2018 03:47 PM, Connor Page wrote: >> The official templates use nftables so shouldn’t be mixed with iptables. I didn’t have time to learn about nftables, so just removed nftables package from debian 9

[qubes-users] Re: Installation, no AMD-vi, interrupt mapping, etc.

2018-10-01 Thread Sergio Matta
Em segunda-feira, 1 de outubro de 2018 16:04:34 UTC-3, naas...@gmail.com escreveu: > Installation went fine except for a libxenlight config error of some kind. I > still can't enable IOMMU using either of the approaches described in that > Ubuntu thread, even though it successfully worked with

Re: [qubes-users] ERROR: PCI device does not exist

2018-10-01 Thread 'awokd' via qubes-users
Eric wrote on 10/1/18 10:29 AM: When running Centos, does lspci -vvv give the same unusual output for that problem device? Don't know what else to suggest; I have a Realtek dual port RTL8111/8168/8411 PCI Express card in one of my systems and it works fine under Qubes 4.0. No "lspci -vvv"

Re: [qubes-users] ERROR: PCI device does not exist

2018-10-01 Thread Eric
When running Centos, does lspci -vvv give the same unusual output for that problem device? Don't know what else to suggest; I have a Realtek dual port RTL8111/8168/8411 PCI Express card in one of my systems and it works fine under Qubes 4.0.

Re: [qubes-users] Installation, no AMD-vi, interrupt mapping, etc.

2018-10-01 Thread naasking
Yes, SVM and IOMMU are enabled and show as enabled when booting raw Linux when I pass in explicit ivrs_ioapic parameters at boot. I just tried again passing in iommu=debug and loglvl=all as described at [1], and xl dmesg just reports: (Xen) IVHD Error: Invalid IO-APIC 0 (Xen) AMD-Vi: Error

[qubes-users] Re: Installation, no AMD-vi, interrupt mapping, etc.

2018-10-01 Thread Sergio Matta
> I updated the bios but still no luck, so I tried a manual procedure as > described at [1]: I ran a recent live linux distro from a USB key and > confirmed that interrupt remapping was disabled by default due to this BIOS > bug. I then figured out the IOMMU and SMBus addresses using the

[qubes-users] Re: Installation, no AMD-vi, interrupt mapping, etc.

2018-10-01 Thread naasking
Yes, I read that thread as well. The last post in that thread did not enable IOMMU on Linux, the second to last did and it's the same procedure I linked in my first post on superuser.com. However, adding these parameters while booting the Qubes installer doesn't seem to have an effect. Are you

[qubes-users] Re: Installation, no AMD-vi, interrupt mapping, etc.

2018-10-01 Thread Sergio Matta
Are you suggesting I just proceed with the installation regardless and try to set these parameters in the grub booting config after I get up and running? > > Sandro > Yes! And even if iommu does not works, you will be able to use Qubes 4 VM as PV. Networking will need to set up by hand and

Re: [qubes-users] pgp smart card for luks keyfile

2018-10-01 Thread ron
On Mon, 1 Oct 2018 07:07:58 + "'awokd' via qubes-users" wrote: > hron wrote on 9/28/18 10:47 AM: > > Hi, > > I am wondering if it is possible to use a LUKS key file during boot of > > qubes. In other distros I encrypted that key file with a pgp smart card an > > could decrypt it during

[qubes-users] Re: Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread John S.Recdep
On 9/30/18 10:18 PM, 'awokd' via qubes-users wrote: > 'Setherson' via qubes-users wrote on 9/30/18 2:12 AM: >> I am using Qubes 3.2. All TemplateVMs and dom0 have been updated >> sometime within the past week. >> >> Since about the same time, my Workstation TemplateVM and every AppVM >> based on

[qubes-users] The log entries in sys-net are filled with a bunch of messages

2018-10-01 Thread gdrub51
Hi, I created a new sys-net (sys-net2) as network VM to use a wireless USB adapter. The sys-net2 dmesg logs (guest-sys-net2.log) are filled with a bunch of messages (4878 lines) like the following: ---%<-- First lines ---%<-- [0.00] Linux version 4.14.57-2.pvops.qubes.x86_64

[qubes-users] /dev/mapper/qubes_dom0-root does not exist

2018-10-01 Thread Micah Lee
I recently installed Qubes 4.0 on a laptop, installed updates in dom0 and my templates, restored a backup, and did a bunch of custom configuration. And then when I rebooted, Qubes wouldn't boot up due to a partitioning error. (It looks like it's the same problem described here [1]). During

Re: [qubes-users] Re: Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread 'Setherson' via qubes-users
> On Oct 1, 2018, at 3:06 PM, John S.Recdep wrote: > > On 9/30/18 10:18 PM, 'awokd' via qubes-users wrote: > >> 'Setherson' via qubes-users wrote on 9/30/18 2:12 AM: >> >>> I am using Qubes 3.2. All TemplateVMs and dom0 have been updated >>> sometime within the past week. >>> >>> Since about the

Re: [qubes-users] Re: Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread john s.
On 10/1/18 10:17 AM, Setherson wrote: >> On Oct 1, 2018, at 3:06 PM, John S.Recdep wrote: >> >> On 9/30/18 10:18 PM, 'awokd' via qubes-users wrote: >> >>> 'Setherson' via qubes-users wrote on 9/30/18 2:12 AM: >>> I am using Qubes 3.2. All TemplateVMs and dom0 have been updated sometime

Re: [qubes-users] Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread 'Setherson' via qubes-users
> I should have said in my previous email that I got the same error you just > pasted. What I did was comment out the onion server in > /etc/apt/sources.list.d/whonix.list as well. > > That fixed the problem for me. > > -- > You received this message because you are subscribed to the Google

Re: [qubes-users] Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread 'Setherson' via qubes-users
> On Oct 1, 2018, at 3:18 AM, 'awokd' via qubes-users > wrote: > > 'Setherson' via qubes-users wrote on 9/30/18 2:12 AM: > >> I am using Qubes 3.2. All TemplateVMs and dom0 have been updated sometime >> within the past week. >> >> Since about the same time, my Workstation TemplateVM and every

Re: [qubes-users] Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread john s.
On 10/1/18 10:23 AM, Setherson wrote: >> I should have said in my previous email that I got the same error you just >> pasted. What I did was comment out the onion server in >> /etc/apt/sources.list.d/whonix.list as well. >> >> That fixed the problem for me. >> >> -- >> You received this message

[qubes-users] Re: Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread John S.Recdep
On 10/1/18 10:13 AM, 'Setherson' via qubes-users wrote: >> On Oct 1, 2018, at 3:18 AM, 'awokd' via qubes-users >> wrote: >> >> 'Setherson' via qubes-users wrote on 9/30/18 2:12 AM: >> >>> I am using Qubes 3.2. All TemplateVMs and dom0 have been updated sometime >>> within the past week. >>> >>>

[qubes-users] Re: Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread John S.Recdep
On 9/29/18 4:12 PM, 'Setherson' via qubes-users wrote: > I am using Qubes 3.2. All TemplateVMs and dom0 have been updated sometime > within the past week. > > Since about the same time, my Workstation TemplateVM and every AppVM based on > it has been unable to connect to the internet. > > The

[qubes-users] Re: Installation, no AMD-vi, interrupt mapping, etc.

2018-10-01 Thread naasking
I meant qemu-kvm not VirtualBox. I now see this table [1] that claims that Xen doesn't support IOMMU on rev.1 of our mobo have, but does on rev.2. I'll probably go with the alternative I have in mind then since, unless someone else has any ideas. If not, thanks for the suggestions everyone!

[qubes-users] Re: Installation, no AMD-vi, interrupt mapping, etc.

2018-10-01 Thread naasking
Installation went fine except for a libxenlight config error of some kind. I still can't enable IOMMU using either of the approaches described in that Ubuntu thread, even though it successfully worked with raw Linux. What boot parameters did you add? I have the earlier rev.1 Sabertooth 990FX

Re: [qubes-users] /dev/mapper/qubes_dom0-root does not exist

2018-10-01 Thread Chris Laprise
On 10/01/2018 02:50 PM, Micah Lee wrote: I recently installed Qubes 4.0 on a laptop, installed updates in dom0 and my templates, restored a backup, and did a bunch of custom configuration. And then when I rebooted, Qubes wouldn't boot up due to a partitioning error. (It looks like it's the

Re: [qubes-users] /dev/mapper/qubes_dom0-root does not exist

2018-10-01 Thread Chris Laprise
On 10/01/2018 05:24 PM, Chris Laprise wrote: On 10/01/2018 02:50 PM, Micah Lee wrote: I recently installed Qubes 4.0 on a laptop, installed updates in dom0 and my templates, restored a backup, and did a bunch of custom configuration. And then when I rebooted, Qubes wouldn't boot up due to a

[qubes-users] nftables vs iptables

2018-10-01 Thread mfreemon
On 1/11/18 3:01 PM, Chris Laprise wrote: > On 01/10/2018 03:47 PM, Connor Page wrote: >> The official templates use nftables so shouldn’t be mixed with iptables. I didn’t have time to learn about nftables, so just removed nftables package from debian 9 template. YMMV. >> > > Hmmm, I was just