Re: [qubes-users] Re: Qubes 4.0 without IOMMU/VT-d/AMD-Vi or Interrupt Remapping
On Tue, Feb 6, 2018 at 2:01 PM, Utility Panel wrote: > Meanwhile, the machines I'm currently replacing are both server workstations > with 96 gigs of EEC RAM. I'm looking to upgrade to something comparable, and > I'm pretty certain at this point that I'll start building with either the > KCMA-D8 or KGPE-D16. I've got one year after the release of 4.0 to make the > transition, so I've got time to collect all the bits before 3.2 reaches > end-of-life. > Did you consider Dell workstations? I am also looking for some high-end workstation and I was considering HP Z8 - thanks for the warning! So maybe Dell T7820? The plus is that you can request them with Linux - so at least some of the compatibility problems go away. I am not so eager to build something - as you can get into the same compatibility issues with any part be it mother board, video etc. - and then the issue just gets more complex (and also the recommended KGPE-D16 looks old). -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUu-1NwYrmzBJ%3Dx5KDTRowaM3ioPckxZUAu%3DqCiGWubuUQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0 without IOMMU/VT-d/AMD-Vi or Interrupt Remapping
On Mon, Feb 26, 2018 at 6:53 AM, Utility Panel wrote: ... > So, I've decided to build with the KGPE-D16. Thus far, I've got the > motherboard and two 6386SE CPUs with air coolers. I buy the other components > when the pricing is favorable. > > Later, when I've got the machine built, I'll figure out how to flash the > BIOS. I know it isn't difficult, and I think I've got some good instructions > bookmarked. I just haven't done that before, so it will be a learning > experience. > > Like you, I am a tad concerned about how old the KGPE-D16 is, but it and the > 6386SE are both a bit spiffier than the kit in my Z800s, and I was planning > on riding them into obsolescence. So, my "new" build should have a bit more > life in it than the Z800s, it will support Qubes 4.0, and I will gain the > privacy and security benefits from using coreboot. Apparently there are some problems with the 63xx series Opterons and coreboot: https://www.coreboot.org/Board:asus/kgpe-d16#CPUs_recommended_by_users I was also thinking about using a PCIe drive - but it looks like that would not work on KGPE-D16 (or maybe require another adapter + complications). Z. -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUvDmdOZn-YbOiTgJ_aKL%3Dvbd54TThN6fj5K-%3Dwq1bsttg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Cannot copy installation image to USB
I tried two usb sticks with 16GB and 64GB and on both I was getting this: user@personal:~/Downloads$ sudo dd if=Qubes-R4.0-rc5-x86_64.iso of=/dev/xdvi && sync dd: writing to ‘/dev/xdvi’: No space left on device 2891865+0 records in 2891864+0 records out 1480634368 bytes (1.5 GB) copied, 13.1412 s, 113 MB/s That was on a debian VM. I solved that problem for me by using my ubuntu machine - but reporting just in case. -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUuE67D6aD3Q2HztOMXOdFrmcQtgdeGg_QehYFaBtj1RYA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] user behavioral analytics
Is it possible to control one VM form another one enough to do a User Behavioral Analysis (one that would include not just net usage but also data internal to the anlyzed vm)? I guess this should be possible - so further questions - is anyone working on this? Are there any plans for tools doing this? -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/ -- 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/CAGL_UUshxg%2BscQh7ONEDpmRc3sF8_aO7ioaBVKUSM92f7NqTpA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Resize dom0
There are instructions how to resize a VM at https://www.qubes-os.org/doc/resize-root-disk-image/ - but this cannot apply to dom0 - because it requires stopping the VM and then running commands in dom0. What would be the procedure for resizing dom0 root partition? -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/ -- 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/CAGL_UUvH1mT_LP57dS6DO5ksNDEf%3DZWA0XiruH7rzM455GHkdg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Resize dom0
Thanks for the instructions. Unfortunately I have no space after the partition - and I did not want to have two passwords - so I created a new partition with enough space. I tried copying (with dd) the old partition into the new one and then proceeding with the instructions - but that failed with duplicate UUIDS (and it seems I am lucky I did not corrupt the system completely with that). So I am back here asking how can I clone the QubesOS system into the bigger partition? I don't want to corrupt the system. Additional question is that apparently I don't have encryption on the physical partition level - but rather at the logical volume level: [root@dom0 zby]# lvdisplay --- Logical volume --- LV Path/dev/qubes_dom0/01 LV Name01 VG Namequbes_dom0 ... [root@dom0 zby]# cryptsetup luksDump /dev/qubes_dom0/00 LUKS header information for /dev/qubes_dom0/00 Version: 1 Cipher name: aes Cipher mode: xts-plain64 Hash spec: sha256 Payload offset:4096 MK bits: 512 ... Is that normal? This was my first QubesOS installation so I don't think I tried anything non-standard then. It is also set on the other lv /dev/qubes_dom0/01 - but I still enter just one password. I guess this would change the instructions sequence. Z. On Sat, Feb 18, 2017 at 7:45 AM, tezeb wrote: > On 02/18/17 11:23, Zbigniew Łukasiak wrote: >> There are instructions how to resize a VM at >> https://www.qubes-os.org/doc/resize-root-disk-image/ - but this cannot >> apply to dom0 - because it requires stopping the VM and then running >> commands in dom0. What would be the procedure for resizing dom0 root >> partition? >> > > It's just a linux, and by default dom0 root fs is ext4, which can be > grown while mounted, so 'standard' resizing procedure should do. Please > take into account that there is ext4 on LVM on LUKS and each have to be > grown separately. All commands run as root from dom0(do backups and be > carefull!!!). > Thanks to LVM there are two alternative solutions. > > First one, if you have space after LUKS partition on your HDD/SSD: > 0. grow physical partition using fdisk or gparted. > 1. grow LUKS container using "cryptsetup resize". > 2. grow (LVM) physical volume using "pvresize". > 3. grow (LVM) logical volume(default name: root) using "lvextend". > 4. grow ext4 filesystem using "resize2fs". > > Alternatively you can extend root by extending LVM, but this will > require providing two(or more) passwords while booting(because each part > of LVM will need to be decrypted before "merging" it into root partition). > 0. Create new partition using fdisk/gparted. > 1. Create new encrypted luks container using "cryptsetup luksFormat". > 2. Mount newly created luks container. > 3. Initialize (LVM) physical volume on newly created luks container > using pvcreate. > 4. Add newly created physical volume to LVM volume group (by default > named: qubes_dom0) using "vgextend". > 5. grow (LVM) logical volume using "lvextend". > 6. grow ext4 filesystem using "resize2fs". > 7. remember to recreate initramfs including both LUKS containers and new > lvm settings > > As always with filesystem changing operations, backup everything before > proceding and be extremly carefull. I'm also not providing full > commands(it's hard to do from the top of my head), so RTFM to get better > understanding of each of above-mentioned commands. > > To analyze current state of LVM useful commands are: pvdisplay, > vgdisplay and lvdisplay. Additionally all used devices shall be visible > in /dev/mapper. > > Regards, > tezeb > -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/ -- 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/CAGL_UUvz_Sy7WzOdOBFVkgTNkAkuvtRvxdMOrWKyXF-MCETd5Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Resize dom0
My current plan is to install a new QubesOS system into the big free partition - and then move stuff there. I don't have anything valuable in dom0 - so it is about moving the VMs. Is there a clean way to do that? Would it work if I just copy /var/lib/qubes into the new system? Cheers, Zbigniew -- 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/CAGL_UUtud%3DfWfcS%3DKmuG9f7joF0DoexW7sia%3DLOpzmBO6p8crA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Backup error - where is the log?
I am getting an error message when trying to restore a VM backup: "unable to extract the qubes backup. Check the extracting process errors." Where should I look for the extracting process error log? I don't see anything relevant in /var/log - but maybe I missed something. More info: I made a bacup using the 'System' -> 'Bacup VMs' menu entry in the Qubes VM Manager and then I tried to restore it with the 'System' -> 'Restore VMs from backup' menu entry. I tried both just veryfying the integrity and restoring it entirely - with the same result. My root filesystem if full - and I noticed that the backup verification process tried to write to /var/tmp . This was failing - so I tried symlinking that directory to another filesystem and mounting another partition over it. This worked at the start and it did create a 'restore_*' directory with some files in /var/tmp - but then failed with the message I described above. I would like to look into the error message - to understand what is failing. -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/ -- 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/CAGL_UUsszNem5qZuNcQNDtQWpW6c%3DB-kS0UBR%2B-%2BZHeoroSB7A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup error - where is the log?
ora-23 fedora-23-dvm personal python-anaconda sys-firewall sys-net sys-whonix untrusted vault whonix-gw whonix-ws work ERROR: Please shutdown all VMs before proceeding. On Thu, Feb 23, 2017 at 3:42 AM, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, Feb 22, 2017 at 12:38:48PM -0500, Zbigniew Łukasiak wrote: >> I am getting an error message when trying to restore a VM backup: >> "unable to extract the qubes backup. Check the extracting process errors." >> >> Where should I look for the extracting process error log? >> I don't see anything relevant in /var/log - but maybe I missed something. > > If you launched the backup from Qubes Manager, check ~/.xsession-errors. > >> More info: >> >> I made a bacup using the 'System' -> 'Bacup VMs' menu entry in the >> Qubes VM Manager and then I tried to restore it with the 'System' -> >> 'Restore VMs from backup' menu entry. I tried both just veryfying the >> integrity and restoring it entirely - with the same result. >> >> My root filesystem if full - and I noticed that the backup >> verification process tried to write to /var/tmp . This was failing - >> so I tried symlinking that directory to another filesystem and >> mounting another partition over it. This worked at the start and it >> did create a 'restore_*' directory with some files in /var/tmp - >> but then failed with the message I described above. I would like to >> look into the error message - to understand what is failing. > > Out of disk space is most likely the reason. But if it isn't the case > after symlinking /var/tmp, check messages in ~/.xsession-errors. If > still nothing interesting, you can launch restoring (or verification) > from command line (qvm-backup-restore), with --debug switch. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJYrqCOAAoJENuP0xzK19csQXYH/2j89aAzUg1LAemETRfxOMcy > T4oM+/ps2qlR1kgA1/LLKx6LdbW2cu5rMR9uAQhr5yHeLp15j5JXF4Ef/pFp1fXr > TrvSMl4x9z+OAUKt+6uZncyl81J7UhMzJ0ixwE58B1vxUzP76aBXz7N8BwhdCLTw > ydi0mg4Pd2iIMRV8wYCX4qxjT0M9OmYf4ClQpOcDUc8+68rEX2vwrD7vOuC0RIfu > MUjutenc3jkLEnAEr0W9cXjwCR360R4ZU5r3SaOPXXo6P4JpBwHkdYdan1uv+cPT > dGtKHMoQlgb6Gq3KPIobaMLhi+8WPv0RkThgjxodirUOHfiZ9GlVfpChtrd8Hjc= > =pEg5 > -END PGP SIGNATURE- -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/ -- 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/CAGL_UUsueQJ%3DANg9QSrBMakWEKSc8ypxjLbCuP3puitp0yDkTg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup error - where is the log?
I removed some templates - and now there is no error about no disk space - but when restoring I still get the same error. It might be indeed about the path fed to tar - because when creating the archive I also get errors when I try to archive to a file in the current dir without giving the full path - it looks like the variable base_backup_dir does not get initialized, see below for the output. Backing up worked when I gave it a full path - still failing at restoring time. Z. == [zby@dom0 ~]$ qvm-backup -x dom0 -x anon-whonix -x sys-net -x sys-firewall -x sys-whonix -x python-anaconda backup --+--+--+ VM | type | size | --+--+--+ untrusted |AppVM | 16.0 KiB | personal |AppVM |0 | myovm |AppVM | 5.0 GiB | my-new-vm |AppVM | 9.9 GiB | exch |AppVM |315.8 MiB | --+--+--+ Total size: |15.1 GiB | --+--+--+ VMs not selected for backup: anon-whonix debian-8 debian-8-python dom0 fedora-23 fedora-23-dvm python-anaconda sys-firewall sys-net sys-whonix whonix-gw whonix-ws Traceback (most recent call last): File "/usr/bin/qvm-backup", line 218, in main() File "/usr/bin/qvm-backup", line 141, in main stat = os.statvfs(os.path.dirname(base_backup_dir)) OSError: [Errno 2] No such file or directory: '' On Fri, Feb 24, 2017 at 9:27 AM, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Fri, Feb 24, 2017 at 08:23:00AM -0500, Zbigniew Łukasiak wrote: >> Ok - I tried the command line version - the output is below. The same >> error I see in ~/.xsession-errors. It looks to work correctly with the >> symlinked tmp - but still fails somehow - maybe the archive is >> corrupted. >> >> I tried to re-make the bacup from commandline, and this reports >> "qvm-backup: export error: [Errno 28] No space left on device" - even >> though I have enough space on both the /home and the /var/tmp >> partitions. See below for details - I mounted quite a big partition on >> /var/tmp. Maybe it somehow still uses the root partition. I did not >> see that error when running backup from Qubes Manager - but maybe the >> problem was still there and it was corrupting the backup. >> >> >> >> >> [zby@dom0 ~]$ qvm-backup-restore qubes-2017-02-22T111605 --verify-only >> --debug >> Please enter the passphrase to verify and (if encrypted) decrypt the backup: >> Checking backup content... >> Working in temporary dir:/var/tmp/restore_RxbZ1b >> Extracting data: 1.0 MiB to restore >> Run command[u'tar', u'-ixvf', 'qubes-2017-02-22T111605', u'-C', >> u'/var/tmp/restore_RxbZ1b', u'backup-header', u'backup-header.hmac', >> u'qubes.xml.000', u'qubes.xml.000.hmac'] >> Got backup header and hmac: backup-header, backup-header.hmac >> Verifying file /var/tmp/restore_RxbZ1b/backup-header >> Loading hmac for file /var/tmp/restore_RxbZ1b/backup-header >> File verification OK -> Sending file /var/tmp/restore_RxbZ1b/backup-header >> Creating pipe in: /var/tmp/restore_RxbZ1b/restore_pipe >> Getting new file:qubes.xml.000 >> Getting hmac:qubes.xml.000.hmac >> Verifying file /var/tmp/restore_RxbZ1b/qubes.xml.000 >> Started sending thread >> Moving to dir /var/tmp/restore_RxbZ1b >> Loading hmac for file /var/tmp/restore_RxbZ1b/qubes.xml.000 >> File verification OK -> Sending file /var/tmp/restore_RxbZ1b/qubes.xml.000 >> Getting new file: >> Waiting for the extraction process to finish...Extracting file >> /var/tmp/restore_RxbZ1b/qubes.xml.000 >> >> Running command [u'tar', u'-xkv', >> u'../../../../var/tmp/restore_RxbZ1b/qubes.xml'] > > This path looks strange. AFAIR it's calculated as "path to > /var/tmp/restore_RxbZ1b/qubes.xml, relative to /var/tmp/restore_RxbZ1b". > Have you actually mounted something on /var/tmp, or used a symlink? You > can use mount --bind if you don't want to mount the whole device there. > And be sure do to it before launching qvm-backup-restore, not during it. > >> === >> >> >> [zby@dom0 ~]$ df >> Filesystem 1K-blocks Used Available Use% Mounted on >> devtmpfs 2002988 0 2002988 0% /dev >>
Re: [qubes-users] Backup error - where is the log?
If I install a second Qubes system on a different partition - is there any way to copy the VMs from the first one? Because that was my goal with the backups. It is possible that the lack of space somehow corrupted the system - and that is the reason for the problems with backups - so maybe there is any other way to do that? Z. -- 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/CAGL_UUvMPW%3D6LteSw_gA3C%2B3jVyNbruc8BvuCRinfjy6c-77BQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Help adding documentation to Qubes Repository
This is something I am also struggling with - but shouldn't there be a sign-off line in all the commit comments as described in https://www.qubes-os.org/doc/license/ ? And by the way - shouldn't that be somehow linked (or maybe moved into) from https://github.com/QubesOS/qubes-doc/blob/master/CONTRIBUTING.md ? Cheers, Zbigniew On Fri, May 12, 2017 at 3:49 AM, Zrubi wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 05/12/2017 09:39 AM, Zrubi wrote: >> On 05/11/2017 11:51 PM, 'PR' via qubes-users wrote: >>> Hello, >> >>> I need some help understanding how the collaborative >>> documentation with GitHub works. >> >> https://www.qubes-os.org/doc/doc-guidelines/ >> >> TL;DR: you only missed the create a pull request part. >> >> > > Or if it is your pull request: > https://github.com/QubesOS/qubes-doc/pull/418 > > Then you made it right. > Now you just have to wait for someone to review and accept it into the > official doc's > > > - -- > Zrubi > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQIcBAEBCAAGBQJZFWkXAAoJEH7adOMCkunmdnsP/RDMnkUZLHsYt1FfEOK9tFDM > 7yhrqJzszYd99zWjJesdvne1ojUUekCA8hcyAfYYz2MbUhVvhGLX95P7Qv/TEgzI > gREkt3+dAJDgOM/FdW2Jw8PFb60ufQOdnTGyGmP4U0NS6Su1ir2HFKYRkub8lfiw > SOBgzZ2HDE2whcP9f4HS/JHaoBPjuDpR6VMAjLf2/Rrmx8oupGpGOr4BR9VFDZVG > ITzdcUBmEZYsAKRnpKW4xAXwxTMZlYmViS4OrDIafYxJJJ1xCUTpEfyKr64JIpMM > Fdn4MqEcC3bu9FoDxQBQxxlzCpeC+uqXwMKkws/J64Oe9e6o2eol2cPYvBgW0uvs > 4uBaKz9EvVgkKpVBgiodHTduUVB1c+rsHZ6HiRmOxPxVT0gwOqMk5ymS6h1iPa8Z > fBW8VZpmWvO7wE8k9VUKF4RUyde8/q5tOkL+cpwblNJ9uxYKmyG+UZd1p8DX97K6 > zLuyvOH4T3GxVZ/CCIT536LE6ArErJ/d2k22lJogIwNec/2iv+P0Z+nhWbrNq1u7 > s6c7Gh9X3/WzltsGC2Ws91BU+FYKxKYBpXq57q6oVQh6WnXa2pq9lLyiIrn9/wxr > ndPLFHLKO/tI17Dpql4IFV9xdVY8G4SSZFrIe4zjvSgYyabDC1frJieA8u2i83pT > wN9jb3AwifHWw72J/8f6 > =+nLj > -END PGP SIGNATURE- > > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users+unsubscr...@googlegroups.com. > To post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/4eca89c0-b10c-3787-f6ca-6dabfd9d6b32%40zrubi.hu. > For more options, visit https://groups.google.com/d/optout. -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/ -- 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/CAGL_UUtCozfq%2BOte33h1gPpO-%2BN-xaCkHO09r3%2B%2BK7Jq2AfxeQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Best Desktop for Qubes
A companion to the Best Laptop for Qubes thread :) Most of the HCL is filled with laptops - very few desktops are there, especially on the high end. Currently I have a Dell Inspiron - works but 16GB RAM is max there (and it is a non-ECC so most probably more than that does not make much sense), and 16BG is not enough for me (browsers seem to eat unbelievable amounts of RAM). Is there a recommended desktop system for Qubes with over 16GB RAM? -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/ -- 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/CAGL_UUtUq2LsrKrLxgS7G6hhNqpkSRA4vw%3Dy1c3Ary%3DcJ%2BcYWQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: [qubes-devel] Re: Announcement: Qubes OS Begins Commercialization and Community Funding Efforts
On Friday, December 2, 2016 at 6:13:35 PM UTC-5, Andrew David Wong wrote: > > So that's what I'm thinking, maybe it would be good for the > > "evangelization" of Qubes to make some very simple, brief, and to-the-point > > videos and howto's? > > > > Yes, certainly. Would you be willing to help us with that? :) I am new to Qubes - just installed it on my computer. I can note the problems that I encounter. Where to send this? Z. -- 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/5efd008f-27de-4d6c-9c57-919664342fa1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Newbie surprises
Here is a list of stuff that I got into trouble trying out Qubes. I am a long time Linux user (since 1993) - so I know a bit about the Linux environment - but I never liked administration stuff. This is just a list - I guess I did a lot of silly things, and I don't suggest that the system should make it impossible to do that. But I hope that it might inspire someone to make it a little bit less probably that newbies get lost :) 1. Immediately after installation I wanted to add USB headphones to the personal vm and I went into Devices configuration of that vm and I added all lines with USB to the vm. I don't remember if it froze immediately or maybe after a reboot of the vm - but I've got completely cut off from the top level Qubes system. Fortunately a hard reboot fixed the problem. 2. The suspend button activates a popup that says: "Do you want to suspend to RAM?" This is a bit confusing - I thought that suspension saves the RAM onto the disk, not in the opposite direction. 3. Initially I did not understand how can I change the templates. I thought that to have additional software or to make any special configuration in a template I need to create a new template and I started reading the documentation at https://www.qubes-os.org/doc/qubes-builder/ - that was really confusing. There are also additional questions that the docs don't answer, like if the changes in the template will be visible in a vm based on it and if yes - then when? 4. I still don't really understand how the keyboard configuration works. What worked for me to have Polish letters in a vm was to set it up both in the top level environment (System Tools > Settings Manager > Keyboard) and in the vm (setxkbmap pl). Initially I spent a lot of time in trying to do it only in the vm - but it failed in mysterious ways. -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/ -- 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/CAGL_UUvk%2BfDxHotQ%3Db9fcky4JBY85n9WBqmskPBaMnLSJ%2Brhxw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Newbie surprises
Two more surprises from me: 1. I have USB headphones. So fare I have not yet found a way to make them work under Qubes - but I found some headphones with the old audio jack - and this works. 2. Once I detached an USB memory device from a VM, before unmounting the device inside the VM. Then I could not unmount it anymore and I rebooted the VM. Maybe detaching should check if the device is used? Cheers, Z. -- 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/CAGL_UUtLbgw-zb9%2BjXS1J28y2PQXHDRuB7GrU4qSzMUaKUqztA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Constant firefox crashes because of Qubes shared memory
I am running fedora-30 in an App-VM (not disposable) and I also experience the crashes. Not only Firefox, Opera also crashes, while Slack app and Thunderbird which also run all the time don't. I thought this is because of not enough RAM - but out of frustration I assigned 23GB to that machine and it did not help, also top reports 10GB free memory now. In the past I also used Debian and I had those crashes too. -- ZŁ On Mon, Apr 27, 2020 at 1:44 PM donoban wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 2020-04-25 03:00, Guerlan wrote: > > 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? > > > > I am running fedora-30 and never had this kind of crash with firefox. > My AppVms mostly have default 400MB/4000MB and some even less max > limit. Maybe is it related to debian-9? Could you test debian-10? > -BEGIN PGP SIGNATURE- > > iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAl6mxaUACgkQFBMQ2OPt > CKWONg/8DxzS1fwOIBIbCarULt8buq7tAtFa5pl6gUF2sL9hn6Uboz53TJsf1e8g > N75pqb5JjFRaZTf2gGwYkTeAo/HFyWxdEZWRprmWcW/0iLHaB86KzxDRXDaREmEs > AWtZTbH7u6lTBx2U3YhPlW3YvBArMeqvdVY3SRIEk3Dl8c/snzMlQ0BQRwAazhmH > IoRy2jeSAEvG0U0CXbEdxRmqt5ck9mFCndPZTfCxPoBup02B1QhwjfMZmCh14F0/ > zHaUZrHszUtVq5iAj6qe2x/PjY5NsAa15cOlM8I1h672vMxEJdv0WzWEYSdwhzEb > i6p/NwtsoeI35DJInedbAk+Z7gTypanqSU23dS9Y77ox7OY+MPuSd+OMNRm+RSl7 > 7EVJo+ABg2SoUiX1ESb8Py4zH1jF0EFFOraPbr/N9QppgWVblVBXkW8hAbgwJk6t > UoZJo0lHGbDHMj7TTfaU1nhvfwOmoYfiq/oTbs/+mamztUwYjI+jryOOBH+3JgXv > MreOm0YH0jsLTMwjVfmxv4zmaSoA7mTwt6gCOpoamq4j9P3onVNgMmo0xcvmTxV0 > ReT5BPB1bASPH0vC7Kw+lfZndK/gYrptWAYjuw2Fo/jsh8z4zMUv9ppGe6TFu5kO > mnVCBrjP5/ljNtGSYvxUNdzI7L7f3Wn3kOJTcfQfilTyzcdosGk= > =+tb9 > -END PGP SIGNATURE- > > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/1670d4bb-ea5b-0ea3-f72e-4284eff9b521%40riseup.net. -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUvU9LDpdLS222TRGTxtFu9czi8s%2B1qy8P9UP0W6D5YWmg%40mail.gmail.com.
Re: [qubes-users] Constant firefox crashes because of Qubes shared memory
marmarek advised me on irc to add more shared memory: mount /dev/shm -o remount,size=10G and it seems to work. 10G is close to half of that VM's RAM. Qubes was assigning only 1G previously. Cheers, Zbigniew On Mon, Apr 27, 2020 at 9:19 PM Zbigniew Łukasiak wrote: > > I am running fedora-30 in an App-VM (not disposable) and I also > experience the crashes. Not only Firefox, Opera also crashes, while > Slack app and Thunderbird which also run all the time don't. I > thought this is because of not enough RAM - but out of frustration I > assigned 23GB to that machine and it did not help, also top reports > 10GB free memory now. > > In the past I also used Debian and I had those crashes too. > > -- > ZŁ > > > On Mon, Apr 27, 2020 at 1:44 PM donoban wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > On 2020-04-25 03:00, Guerlan wrote: > > > 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? > > > > > > > I am running fedora-30 and never had this kind of crash with firefox. > > My AppVms mostly have default 400MB/4000MB and some even less max > > limit. Maybe is it related to debian-9? Could you test debian-10? > > -BEGIN PGP SIGNATURE- > > > > iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAl6mxaUACgkQFBMQ2OPt > > CKWONg/8DxzS1fwOIBIbCarULt8buq7tAtFa5pl6gUF2sL9hn6Uboz53TJsf1e8g > > N75pqb5JjFRaZTf2gGwYkTeAo/HFyWxdEZWRprmWcW/0iLHaB86KzxDRXDaREmEs > > AWtZTbH7u6lTBx2U3YhPlW3YvBArMeqvdVY3SRIEk3Dl8c/snzMlQ0BQRwAazhmH > > IoRy2jeSAEvG0U0CXbEdxRmqt5ck9mFCndPZTfCxPoBup02B1QhwjfMZmCh14F0/ > > zHaUZrHszUtVq5iAj6qe2x/PjY5NsAa15cOlM8I1h672vMxEJdv0WzWEYSdwhzEb > > i6p/NwtsoeI35DJInedbAk+Z7gTypanqSU23dS9Y77ox7OY+MPuSd+OMNRm+RSl7 > > 7EVJo+ABg2SoUiX1ESb8Py4zH1jF0EFFOraPbr/N9QppgWVblVBXkW8hAbgwJk6t > > UoZJo0lHGbDHMj7TTfaU1nhvfwOmoYfiq/oTbs/+mamztUwYjI+jryOOBH+3JgXv > > MreOm0YH0jsLTMwjVfmxv4zmaSoA7mTwt6gCOpoamq4j9P3onVNgMmo0xcvmTxV0 > > ReT5BPB1bASPH0vC7Kw+lfZndK/gYrptWAYjuw2Fo/jsh8z4zMUv9ppGe6TFu5kO > > mnVCBrjP5/ljNtGSYvxUNdzI7L7f3Wn3kOJTcfQfilTyzcdosGk= > > =+tb9 > > -END PGP SIGNATURE- > > > > -- > > You received this message because you are subscribed to the Google Groups > > "qubes-users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to qubes-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/qubes-users/1670d4bb-ea5b-0ea3-f72e-4284eff9b521%40riseup.net. > > > > -- > Zbigniew Lukasiak > https://medium.com/@zby > http://brudnopis.blogspot.com/ -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUtUxkCeqF2xj8Fud5Fwj7dfT5GanOYhxmRx6ESonBy3FA%40mail.gmail.com.
[qubes-users] Updating sys-usb template
My sys-usb uses a very old template. I tried some googling - but failed to find any advice about update it without locking me out of the system. I guess I could remove it - there is a description on how to do that in https://www.qubes-os.org/doc/usb-qubes/ - and then add it again with a new template. But it is kind of complicated and looks dangerous. -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUtLXaNv%2Bs3L738sdSsA_eKv4cW15_2HvQhNugUHLT3Fag%40mail.gmail.com.
Re: [qubes-users] Updating sys-usb template
On Sat, May 30, 2020 at 12:02 AM wrote: > > > > disable sys-usb autostart. > > > maybe "lock out" refers to a USB keyboard ? > > yes, that is how i read it, and that is what my suggestions for > dealing with the update are about. Yes - I have an USB keyboard. So just to be sure - when I checkout "start qube automatically on boot" in the sys-usb Qube Settings and reboot - then the system will use my USB keyboard directly without any problems? -- ZŁ -- 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/CAGL_UUtzC9KncM3Zz2oDkBFNRmsJ_E1Q4k9QpD%2BqX8H3VdAaNA%40mail.gmail.com.
[qubes-users] Thunderbird hangs when sending email.
I fixed it by restarting the vm - but now it is back. It looks qubes related because: user@personal:~$ ps xa | grep thunder 9461 ?Sl 0:00 /usr/bin/python2 /usr/bin/qubes-desktop-run /usr/share/applications/mozilla-thunderbird.desktop 9485 ?S 0:00 /usr/bin/sh -l /usr/lib/qubes/qubes-rpc-multiplexer qubes.StartApp+mozilla-thunderbird dom0 9486 ?S 0:00 /usr/bin/sh -l /usr/lib/qubes/qubes-rpc-multiplexer qubes.StartApp+mozilla-thunderbird dom0 9489 ?S 0:00 logger -t qubes.StartApp+mozilla-thunderbird-dom0 9501 ?Sl 0:20 /usr/lib64/thunderbird/thunderbird 11702 pts/0S+ 0:00 grep thunder -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUv90e5HaKUEP7sfjnQm80U6831fspjgSrtEFkP3hss9Uw%40mail.gmail.com.
[qubes-users] qvm-usb does not list device, but lsusb does
I try to attach my Android phone (Samsung Galaxy S7) via USB cable to transfer files to my QubesOS box. From googling around figured out a plan to attach the USB device to another qube, install the MPT library there - and use Nautilius to mount the drive there. Unfortunately qvm-usb does not list any devices: [zby@dom0 ~]$ qvm-usb l BACKEND:DEVID DESCRIPTION USED BY [zby@dom0 ~]$ lsusb Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. Bus 001 Device 011: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP) Bus 001 Device 006: ID 03f0:0641 Hewlett-Packard Bus 001 Device 003: ID 413c:2111 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUs%3DjT7xojGWf2aEhJV%2B7tuK6c1uZ7-sJ968CMZJj832TA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qvm-usb not functioning
On Friday, December 1, 2017 at 12:58:59 PM UTC+1, awokd wrote: > On Fri, December 1, 2017 05:50, Drew White wrote: > > On Tuesday, 21 November 2017 06:45:02 UTC+11, awokd wrote: > >> On Mon, November 20, 2017 02:32, Drew White wrote: > >> > Hi folks, sys-usb still isn't functioning and allowing me to attach a > >> > device. > >> > > >> > help please? > > Let's start over. Describe your Qubes version, the USB device you are > trying to attach, which USB controllers you have assigned to sys-usb or > dom0, and the output of commands you use when attaching. I have a similar problem - qvm-usb retuns an empty list. [root@dom0 zby]# qvm-usb BACKEND:DEVID DESCRIPTION USED BY [root@dom0 zby]# lsusb Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. Bus 001 Device 011: ID 148f:761a Ralink Technology, Corp. Bus 001 Device 004: ID 03f0:0641 Hewlett-Packard Bus 001 Device 003: ID 413c:2111 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub This is Qubes 4.0 I tried the recoding suggestion - I added "ID_SERIAL=`echo ${ID_SERIAL} | iconv -t ASCII//TRANSLIT`" in /usr/lib/qubes/udev-usb-add-change and then removed and put back the device - but that did not change the result. Cheers, Zbigniew -- 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/9732cf6a-6916-4223-86ab-dbb58425ef73%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qvm-usb not functioning
On Sat, Mar 23, 2019 at 3:23 AM unman wrote: > > On Fri, Mar 22, 2019 at 06:32:07AM -0700, Zbigniew Łukasiak wrote: > > On Friday, December 1, 2017 at 12:58:59 PM UTC+1, awokd wrote: > > > On Fri, December 1, 2017 05:50, Drew White wrote: > > > > On Tuesday, 21 November 2017 06:45:02 UTC+11, awokd wrote: > > > >> On Mon, November 20, 2017 02:32, Drew White wrote: > > > >> > Hi folks, sys-usb still isn't functioning and allowing me to attach a > > > >> > device. > > > >> > > > > >> > help please? > > > > > > Let's start over. Describe your Qubes version, the USB device you are > > > trying to attach, which USB controllers you have assigned to sys-usb or > > > dom0, and the output of commands you use when attaching. > > > > I have a similar problem - qvm-usb retuns an empty list. > > > > [root@dom0 zby]# qvm-usb > > BACKEND:DEVID DESCRIPTION USED BY > > [root@dom0 zby]# lsusb > > Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. > > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. > > Bus 001 Device 011: ID 148f:761a Ralink Technology, Corp. > > Bus 001 Device 004: ID 03f0:0641 Hewlett-Packard > > Bus 001 Device 003: ID 413c:2111 Dell Computer Corp. > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > > > This is Qubes 4.0 > > > > I tried the recoding suggestion - I added "ID_SERIAL=`echo ${ID_SERIAL} | > > iconv -t ASCII//TRANSLIT`" in /usr/lib/qubes/udev-usb-add-change and then > > removed and put back the device - but that did not change the result. > > > > > > > > Cheers, > > Zbigniew > > > > What's the USB device you are trying to attach? This time I needed the wifi card (Ralink) - but this is not the first time I had this problem. > I'm assuming you chose not to create a sys-usb. Yes - and after someone on irc advised me to create it - that fixed the problem. Maybe this is a documentation problem - apparently sys-usb is kind of obligatory now. Cheers, Zbigniew -- 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/CAGL_UUvou106_6-7MWksmRXNrH577c4msL-PwNKLX4FGsgQMEw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Compiling kernel modules
Hi there, I am trying to connect my qubes box via wifi - but I cannot compile any kernel module for my wifi cards (on both fedora 26 and 29). The compilation fails at the first object file: [user@sys-usb rtl8821AU]$ make make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.14.103-1.pvops.qubes.x86_64/build M=/home/user/rtl8821AU modules make[1]: Entering directory '/usr/lib/modules/4.14.103-1.pvops.qubes.x86_64/build' make[2]: *** No rule to make target '/home/user/rtl8821AU/core/rtw_cmd.o', needed by '/home/user/rtl8821AU/8821au.o'. Stop. make[1]: *** [Makefile:1535: _module_/home/user/rtl8821AU] Error 2 make[1]: Leaving directory '/usr/lib/modules/4.14.103-1.pvops.qubes.x86_64/build' make: *** [Makefile:2003: modules] Error 2 but the source file for that object file is there: [user@sys-usb rtl8821AU]$ ls /home/user/rtl8821AU/core/rtw_cmd.c /home/user/rtl8821AU/core/rtw_cmd.c I have installed the headers: sudo dnf install make automake gcc gcc-c++ kernel-devel This looks like it must be something silly - but I really cannot find anything. I have installed the I have also tried the kernel modules that are already in the system for the two cards that I have bought (tp-link AC600 Archer T2UH and Edimax EW-7811UTC) - but no result, i.e. /proc/net/dev does not show anything, I am doing it in sys-usb - so that the access to the device is a sure thing. The Edimax one explicitly lists Linux as supported but the instructions still require compiling a kernel module. -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUtNizZdziLdrpJ7HhpPn5_NoRyH9SCOdKV1gaQhTPXBPg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Compiling kernel modules
OK - so it looks that it does not work like that in QubesOS - i.e. by default the modules directory is read only. I found some instructions on installing custom kernels in: www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm. I don't really need a new kernel - I just want to be able to compile the modules - but this looks like a possible way out for me. So I did cloned the fedora-29 template and: qvm-prefs virt_mode hvm qvm-prefs kernel '' unfortunately now the cloned template does not start - so I cannot continue with the instructions at the doc linked above. When I change the kernel back to '4.14.103-1' it works fine. -- ZL -- 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/CAGL_UUvA65K__3Kg1mNexjdMidvOJEsT%2BOYDyJUzBH7aR3AayQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HVM + Kernel: None = distorted graphics
How did you set the kernel? I have tried: [zby@dom0 ~]$ qvm-prefs -s netvm-fedora-29-template kernel 'none' qvm-prefs: error: Kernel 'none' not installed [zby@dom0 ~]$ qvm-prefs -s netvm-fedora-29-template kernel none qvm-prefs: error: Kernel 'none' not installed [zby@dom0 ~]$ qvm-prefs -s netvm-fedora-29-template kernel '(none)' qvm-prefs: error: Kernel '(none)' not installed [zby@dom0 ~]$ qvm-prefs -s netvm-fedora-29-template kernel '' The last one worked - but then the vm does not start anymore. I get an error that it did not start for 60 seconds. Maybe I should try running grub before changing the kernel - but that does not work either: bash-4.4# grub2-install /dev/xvda3 Installing for i386-pc platform. grub2-install: warning: File system `ext2' doesn't support embedding. grub2-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. grub2-install: error: will not proceed with blocklists. I don't quite understand that error - because it should be ext4: /dev/xvda3 on / type ext4 (rw,noatime,discard,data=ordered) ZŁ On Wed, Mar 27, 2019 at 5:30 AM wrote: > > Hi, > > I've been trying to get Wireguard up and running following the instructions > referenced from this issue: > > https://github.com/QubesOS/qubes-issues/issues/3591 > > I've tried installation in both Fedora 29 and Debian 9-based templates. The > problem is, I can switch to HVM mode, but as soon as I set the kernel to > "(none)" in either template, any attempt to bring up a terminal gives me a > window with distorted graphics inside. My impression is that kernel has to be > none for the kernel modules to be loaded properly? > > I'm not really sure why this is happening. Dom0 has a different DPI setting > than the baseline templates, although that doesn't seem to cause problems > usually. I would appreciate any help. > > -- > 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/90695bc3-2297-44af-90cc-4f04a4d7e315%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUvMC-aHRXa6yBnYnAU-AioSz0Dwhwo1G5QxM1QdjVaKrA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HVM + Kernel: None = distorted graphics
On Wed, Mar 27, 2019 at 8:28 AM Zbigniew Łukasiak wrote: > > How did you set the kernel? I have tried: > [zby@dom0 ~]$ qvm-prefs -s netvm-fedora-29-template kernel 'none' > qvm-prefs: error: Kernel 'none' not installed > [zby@dom0 ~]$ qvm-prefs -s netvm-fedora-29-template kernel none > qvm-prefs: error: Kernel 'none' not installed > [zby@dom0 ~]$ qvm-prefs -s netvm-fedora-29-template kernel '(none)' > qvm-prefs: error: Kernel '(none)' not installed > [zby@dom0 ~]$ qvm-prefs -s netvm-fedora-29-template kernel '' > > The last one worked - but then the vm does not start anymore. I get an > error that it did not start for 60 seconds. > > Maybe I should try running grub before changing the kernel - but that > does not work either: > bash-4.4# grub2-install /dev/xvda3 > Installing for i386-pc platform. > grub2-install: warning: File system `ext2' doesn't support embedding. > grub2-install: warning: Embedding is not possible. GRUB can only be > installed in this setup by using blocklists. However, blocklists are > UNRELIABLE and their use is discouraged.. > grub2-install: error: will not proceed with blocklists. > > I don't quite understand that error - because it should be ext4: > /dev/xvda3 on / type ext4 (rw,noatime,discard,data=ordered) > > > ZŁ > > On Wed, Mar 27, 2019 at 5:30 AM wrote: > > > > Hi, > > > > I've been trying to get Wireguard up and running following the instructions > > referenced from this issue: > > > > https://github.com/QubesOS/qubes-issues/issues/3591 > > > > I've tried installation in both Fedora 29 and Debian 9-based templates. The > > problem is, I can switch to HVM mode, but as soon as I set the kernel to > > "(none)" in either template, any attempt to bring up a terminal gives me a > > window with distorted graphics inside. My impression is that kernel has to > > be none for the kernel modules to be loaded properly? > > > > I'm not really sure why this is happening. Dom0 has a different DPI setting > > than the baseline templates, although that doesn't seem to cause problems > > usually. I would appreciate any help. > > > > -- > > 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/90695bc3-2297-44af-90cc-4f04a4d7e315%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > I should add that /var/log/xen/console/guest-netvm-fedora-29-template.log file is empty. The grub install worked after I tried it on /dev/xvda instead of /dev/xvda3 - but still it did not change anything. ZŁ -- 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/CAGL_UUtUU1m4beQJWELjhMPVXsKj2sYzZGOQN1Ga3O9QJSaZfA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Compiling kernel modules
On Wed, Mar 27, 2019 at 12:50 AM 'awokd' via qubes-users wrote: > > Zbigniew Łukasiak wrote on 3/24/19 4:22 PM: > > OK - so it looks that it does not work like that in QubesOS - i.e. by > > default the modules directory is read only. I found some instructions > > on installing custom kernels in: > > www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm. > > I don't really need a new kernel - I just want to be able to compile > > the modules - but this looks like a possible way out for me. So I did > > cloned the fedora-29 template and: > > > > qvm-prefs virt_mode hvm > > qvm-prefs kernel '' > > > > unfortunately now the cloned template does not start - so I cannot > > continue with the instructions at the doc linked above. When I change > > the kernel back to '4.14.103-1' it works fine. > > That should be all you have to do. Might be an issue with fedora-29. > Does it work with 28? With 28 the same thing. It does not start - /var/log/xen/console/guest-fedora-28-netvm-template.log is empty. In /var/log/xen/console/guest-fedora-28-netvm-template-dm.log there are entries - last lines are: + target=40 + device_model=device-model/40 + true + xenstore-watch -n 2 device-model/40/command device-model/40/command -device 'scsi-hd,bus=scsi0.0,drive=disk1,wwn=0x3525400051756266' -drive 'file=/dev/xvdc,if=none,id=disk2,format=host_device,cache=writeback,readonly=off' -device 'scsi-hd,bus=scsi0.0,drive=disk2,wwn=0x3525400051756267' + set +x random: qemu: uninitialized urandom read (16 bytes read) {"QMP": {"version": {"qemu": {"micro": 0, "minor": 0, "major": 3}, "package": ""}, "capabilities": []}} {"execute": "qmp_capabilities"} qubes_gui/init: 592 qubes_gui/init: 607 qubes_gui/init: 609 qubes_gui/init[639]: version sent, waiting for xorg conf {"return": {}} qemu: pin_memory_cacheattr failed: Operation not permitted clocksource: tsc: mask: 0x max_cycles: 0x39c700f5c78, max_idle_ns: 440795340708 ns random: crng init done ZŁ -- 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/CAGL_UUtnPUVEMT9TD0j9UUsz-9_P%2BjEHRfaT7Oh%3DyX18uFKxaQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Compiling kernel modules
Thanks - it worked! I hope a fix gets into the core system as I still have some problems with the modem and I am not sure what I am doing wrong. Z. On Sat, Mar 30, 2019 at 5:07 PM awokd wrote: > > Zbigniew Łukasiak wrote on 3/27/19 8:22 AM: > > On Wed, Mar 27, 2019 at 12:50 AM 'awokd' via qubes-users > > wrote: > >> > >> Zbigniew Łukasiak wrote on 3/24/19 4:22 PM: > >>> OK - so it looks that it does not work like that in QubesOS - i.e. by > >>> default the modules directory is read only. I found some instructions > >>> on installing custom kernels in: > >>> www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm. > >>> I don't really need a new kernel - I just want to be able to compile > >>> the modules - but this looks like a possible way out for me. So I did > >>> cloned the fedora-29 template and: > >>> > >>> qvm-prefs virt_mode hvm > >>> qvm-prefs kernel '' > >>> > >>> unfortunately now the cloned template does not start - so I cannot > >>> continue with the instructions at the doc linked above. When I change > >>> the kernel back to '4.14.103-1' it works fine. > >> > >> That should be all you have to do. Might be an issue with fedora-29. > >> Does it work with 28? > > > > With 28 the same thing. It does not start - > > /var/log/xen/console/guest-fedora-28-netvm-template.log is empty. > > > > This worked for me with Debian-9: > > - create Standalone based from template, or clone existing template > - leave PVH and kernel set, start terminal > - sudo dkms autoinstall -k 4.9.0-8-amd64 [without this step I got either > gibberish or no terminal window] > - powerdown, set to HVM and kernel to none > - start terminal > > I had the same problem you described while trying Fedora-28. I'm not > sure how to run dkms in there because it complains about a missing > dkms.conf. See also https://github.com/QubesOS/qubes-issues/issues/4920. > > -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUvgadzPhpjTdQ8yODQf%3D-3B4eFXaZJ8WYH9ZvRUPRyV_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HP Sure Start
Is this compatible with Qubes? http://h10032.www1.hp.com/ctg/Manual/c05163901 -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUv4B-u%2BwmB%3DR2mwYRBLU%2Bem_eGKQGqpTmcQEO_3BR62Vg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Problems with split PGP (QUBES_GPG_DOMAIN) in 4.0 + fedora 28
1. QUBES_GPG_DOMAIN env variable somehow gets cleared between the shell and the Enigmail process. I set it in the shell before starting thunderbird: user@personal:~$ export QUBES_GPG_DOMAIN=work-gpg user@personal:~$ echo $QUBES_GPG_DOMAIN work-gpg user@personal:~$ thunderbird & But when I look at the Enigmail debug console I get this error: enigmail> /usr/bin/qubes-gpg-client-wrapper --charset utf-8 --display-charset utf-8 --no-auto-check-trustdb --batch --no-tty --no-verbose --status-fd 2 --fixed-list-mode --with-colons --list-config ERROR: Destination domain not defined! Set it with QUBES_GPG_DOMAIN env variable. 2. Enigmail somehow refuses to accept /usr/bin/qubes-gpg-client-wrapper as correct setting even if it apparently uses it (see above). I keep getting this erro message: Enigmail: Error in accessing Enigmail service In order to use Enigmail, GnuPG is required. If you did not install GnuPG yet, the easiest way to do this is using the "Setup Wizard" button below. And then when I set it up in the wizard I keep getting: "The file you specified is not a GnuPG executable. Please specify a different file." Thunderbird data: Name Thunderbird Version 60.0 Build ID 20180829122858 Update History User Agent Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 OS Linux 4.14.67-1.pvops.qubes.x86_64 -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUtAouD-ZYzUbNOh6QvGGQwXWp-JH0iURsVwK6%3DpoW%3Duig%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How can I add networking to a minimal template VM?
I am trying to setup a printer AppVM as described in https://www.qubes-os.org/doc/network-printer/ - i.e. first I am trying to create a template VM and configure printing there. I cloned fedora-28-minimal for the template VM. I tried to configure the printing without networking - that should be possible, but I failed at it and I think it is still useful to be able to switch on networking temporarily in a template VM. Then in "Qube Settings" I changed Networking from "default (none)" to "sys-net (current)" (I tried also "sys-firewall"). Unfortunately it boots without networking - so I tried to set it up manually: bash-4.4# ip addr add 10.137.0.27/32 dev eth0 bash-4.4# ip route add default via 10.137.0.6 dev eth0 Error: Nexthop has invalid gateway. At one point that worked, but now it stopped with the above error message. -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.com/ -- 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/CAGL_UUsA3RWa7VAqUfH5CJQY2WSACOVdfQAGDuSq8MDRhvQLZw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How can I add networking to a minimal template VM?
On Thu, Oct 18, 2018 at 1:40 PM unman wrote: > > On Thu, Oct 18, 2018 at 04:36:00AM +0200, Zbigniew Łukasiak wrote: > > I am trying to setup a printer AppVM as described in > > https://www.qubes-os.org/doc/network-printer/ - i.e. first I am trying > > to create a template VM and configure printing there. > > > > I cloned fedora-28-minimal for the template VM. > > > > I tried to configure the printing without networking - that should be > > possible, but I failed at it and I think it is still useful to be able > > to switch on networking temporarily in a template VM. > > > > Then in "Qube Settings" I changed Networking from "default (none)" to > > "sys-net (current)" (I tried also "sys-firewall"). > > > > Unfortunately it boots without networking - so I tried to set it up > > manually: > > > > bash-4.4# ip addr add 10.137.0.27/32 dev eth0 > > bash-4.4# ip route add default via 10.137.0.6 dev eth0 > > Error: Nexthop has invalid gateway. > > > > At one point that worked, but now it stopped with the above error message. > > > > -- > > Zbigniew Lukasiak > > https://medium.com/@zby > > http://brudnopis.blogspot.com/ > > > > have you read www.qubes-os.org/doc/templates/fedora-minimal ? Yeah - somehow I missed this one. Later I found it - but thanks :) Eventually I went with the normal fedora template - I need it for the printer vm and there I need all the packages to display stuff - so I guess the difference would not be that dramatic anyway. > > Your ip command does not work because you dent have a route to the IP your > are setting as default. I don't quite get that - because 10.137.0.27 and 10.137.0.6 are in the same subnet (and I tried /24 as well). But whatever. > If you install the relevant qubes-core-agent-networking etc then you > should get IP set up automatically. > Cheers, Zbigniew -- 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/CAGL_UUuS78pS%2Bnb_WTmDzR76L9bWbtSqsGtQKvBimNGAG8P3Wg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.