Re: [EXT] [qubes-users] How to attach private storage from one AppVM to another AppVM (LVM)?
Thank you all for describing the various approaches, this is great feedback and all sound feasible. I'll start testing soon. Ultimately I'll probably move all the files over to some network location if it proves fast enough. The BIG VM so far caused nothing but problems anyway. But currently it is there so I have to cope with it. On Friday, December 11, 2020 at 5:28:12 AM UTC+1 Stuart Perkins wrote: > > > On Thu, 10 Dec 2020 20:43:27 +0100 > Ulrich Windl wrote: > > >On 12/7/20 3:56 PM, 'heinrich...@googlemail.com' via qubes-users wrote: > >> From one AppVM I need to temporarily access a large amount of files > >> from another AppVM. Can this be done without copying the files around? > >> > >> _Background: _ > >> I have a large amount of files stored in AppVM "BIG". That's hundreds > of > >> GB in a separate pool on a spinning HDD. > >> I also have a small AppVM "SMALL" running a program that needs to > access > >> files from "BIG". This AppVM resides on a small SSD. > >> > >> In the past I copied files from BIG to SMALL. But this takes time and I > >> need to sort the files beforehand because there is not enough space on > >> the SSD. I don't want to do that anymore. It would be okay to allow > >> AppVM "SMALL" to access files from "BIG"'s private storage directly. > >> > >> Googling around tells me to mount "private.img", but I'm using LVM so > >> that's not an option. But how can this be done? Can it be done? (Or is > >> there even a better "file sharing" approach for this amount of data > >> without having to revert to a NAS?) > >> > >> Any tips are appreciated. > > > >Actually I have not done it, but it feels like you should have an NFS > >server on BIG with a network only accessible from inside qubes, and > >specifically from SMALL. Still it will have to transfer the file > >contents, but you benefit from any application that only reads parts of > >the files. > > > >When not wanting to copy I guess you'll have to mount a snapshot of > >BIG's data as the LV should be mounted only once (AFAIK). > > > What I have done is... > > created a large disk image (600g or so) on the mail dom0 drive space > > written a script in dom0 to attach the image to whichever machine I want > to access it from. > > This script.. > attaches the image to a loop device > mounts the image to the machine I desire > added /etc/hosts entries to each app vm to mount to a dedicated directory > when doing "sudo mount -a" by uuid > script ends with an execution of "sudo mount -a" on the target vm > > there is also a corresponding unmount script, so if it is mounted to > "mail" I can easily unmount it and mount it to "money". > > > This lets me treat the 600g.img file like a removable media which can be > attached to any app vm. I also back that drive image up on my network > server. > > Stuart > -- 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/2197e4ca-903a-41b6-b5e5-bb2cd1bbd878n%40googlegroups.com.
[qubes-users] Screenreader - accessibility
Hello, I am wondering if anyone has any ideas as to how I could run a screen reader in Qubes. I use Orca with Debian-based systems, would it be possible to do the same thing? I do realize that blind people that want privacy or an extremely small minority. However, I think that people that are blind or that have became blind such as myself deserve the same right to privacy. :) Thank you all very much in advance, -Reece -- 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/D9ECF348-8D98-4C4C-AA5C-7ABF4814672B%40icloud.com.
[qubes-users] camera not connected after sys-usb switch
Hi! I've switched my sys-usb to a minimal template and a dvm setup (according to this manual: https://www.qubes-os.org/doc/disposablevm-customization/). Everything works fine except the built-in camera. The camera is being detected during sys-usb-dvm startup, but when I try to connect it to another AppVM, I receive the message "Attaching device MyDevice to AppVm failed. Error: QubesException - Device attach failed: No device info received, connection failed, check backend side for details." Am I missing some packages in the minimal template which are not listed here: https://www.qubes-os.org/doc/templates/minimal/#distro-specific-notes? Best, P -- 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/e6849cd2-e5e2-ebaf-b2e7-50da39506e60%40gmx.de.
[qubes-users] Re: HCL - DELL Precission M6800 A26
A26 BIOS?! Are you sure? A16 is more plausible. Cheers, Ludwig On Thursday, December 10, 2020 at 2:29:37 PM UTC Sergey Bezugliy wrote: > -- 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/ecd26d2a-fea0-4ed8-be65-65db74f47fden%40googlegroups.com.
[qubes-users] Screenreader - accessibility
Hello, I am wondering if anyone has any ideas as to how I could run a screen reader in Qubes. I use Orca with Debian-based systems, would it be possible to do the same thing? I do realize that bond people that want privacy or an extremely small minority. However, I think that people that are blind or that have became blind such as myself deserve the same right to privacy. :) Thank you all very much in advance, -Reece -- 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/5C4F2434-2B52-4ECF-B712-754CA9A7BCD7%40icloud.com.
[qubes-users] qubes-os // stand-alone reactos fails
Hi I am trying to install reactos 0.4.13 as stand alone with 16G system and 16g private. I know, way too much. Reactos fails with blue screen and red print: "Setup could not find a harddisk" Enter = Reboot computer. So why there is no harddisk in the vm? Is there an editor to configure more options to the vm? So I would like to see if the devices are there. BTW: If someone could contribute a reactos template with common tools like peazip and sumatrapdf it would be nice for all to play with some old windows stuff. Regards Ludwig -- 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/0f9d5f99-b470-425f-a65a-8396f034a23en%40googlegroups.com.
[qubes-users] Show kali desktop menu
How can I access the kali linux desktop menu I get when running kali as a standalone OS, within a kali appvm? -- 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/bP0lsVqpK87E7GBipVqVc0ht2iBtwqu_G0zZ0DOsORktcmS6Lm2fFA_27SI-9iz4KWzdLG3VunxLsHiTNHSXyyjdTYmvKR4RXF3GhE1voeo%3D%40protonmail.com.
Re: [qubes-users] Show kali desktop menu
On Sun, Dec 13, 2020 at 11:31:25PM +, 'keyandthegate' via qubes-users wrote: > How can I access the kali linux desktop menu I get when running kali as a > standalone OS, within a kali appvm? > A (template based) Kali appvm does not have a desktop per se, so you cant access the desktop menu, unless you can find a command which will make it appear, and map that to a desktop or keyboard shortcut in dom0. You could try copying the menu from a standalone system and create a copy in dom0, editing the links to call "qvm-run ..", which would give you a desktop menu in dom0. If you wanted to be very fancy you could edit the dom0 desktop menu to include the kali appvm menu. -- 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/20201214010557.GB19004%40thirdeyesecurity.org.
Re: [qubes-users] Re: btrfs for template/appvm
On 12/12/20 11:14 AM, unman wrote: On Sat, Dec 12, 2020 at 07:32:13AM +, 'keyandthegate' via qubes-users wrote: I have btrfs set up for dom0 and I'm using the refilnk driver, but my appvms themselves seem to be ext4? Where would I even set this? I don't see an option on the pool or on qvm-create. ? Original Message ? On Saturday, December 12, 2020 12:36 AM, keyandthegate wrote: I want to use btrfs for the snapshots feature in my appvms. I know Qubes supports btrfs for dom0: https://github.com/QubesOS/qubes-issues/issues/2340 Does Qubes support using btrfs in individual appvms? If not is there some other way I can get snapshots? It would make me less afraid to make a mistake while using my computer. I *think* you would have to custom build templates using btrfs, but I have no idea if that would work - I'll try and report back. When I'm making significant changes then I make liberal use of qvm-clone: then I may archive off, but more usually just throw away the clone if I'm happy. (On the rare occasions that I work with Windows qubes I do this a lot.) Yes. If you have Btrfs in dom0 then you already have those features at the VM level at least. And I would recommend against putting Btrfs on top of Btrfs, as its more CPU intensive. For those who have the default LVM in dom0, Btrfs in appVMs is a better prospect. But since LVM also has snapshots, to me the only two overriding reasons to use Btrfs this way is for compression (Btrfs has Zstandard now!) of things like databases and email archives; and also for its integrity checking. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a7f06577-40d9-00e9-6035-8e79765ec553%40posteo.net.
Re: [qubes-users] Screenreader - accessibility
On 12/13/20 4:17 PM, 'Reece O'Bryan' via qubes-users wrote: I am wondering if anyone has any ideas as to how I could run a screen reader in Qubes. I use Orca with Debian-based systems, would it be possible to do the same thing? I am afraid that's going to be a though one. The way I understand how screen readers work is that they interrogate the UI and then provide some form of output be it audio or haptic. In Qubes a lot of energy went into preventing exactly this scenario. My high level understanding is that each VM renders their windows onto a virtual screen. The areas of these windows are then sent securely as a bitmap to dom0 where those bitmaps then get rendered onto the screen. The entire point being that no VM can see or interrogate any of the output of the other VMs and dom0 cannot be compromised because it is only dealing with bitmaps. There might be a way to get Orca or similar tools to work on a per VM basis, which might be OK with audio output -- I don't know. But things like system wide focus management would require a Qubes specific screen reader implementation in dom0 with stubs in each VM. With the upcoming version of Qubes GUI management will be removed from dom0 and instead happen in a dedicated GUI VM, which is even more secure and is meant to also make it easier to support different environments like GNOME, KDE etc. My hope would be that in this new architecture there would be an easier way to support 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/c27a79b5-f261-c414-913c-72b01988bc3d%40SvenSemmler.org. OpenPGP_signature Description: OpenPGP digital signature
Re: [qubes-users] qubes-os // stand-alone reactos fails
On Sun, Dec 13, 2020 at 03:07:06PM -0800, ludwig...@gmail.com wrote: > Hi I am trying to install reactos 0.4.13 as stand alone with 16G system and > 16g private. > I know, way too much. > Reactos fails with blue screen and red print: "Setup could not find a > harddisk" > Enter = Reboot computer. > > So why there is no harddisk in the vm? > Is there an editor to configure more options to the vm? So I would like > to see if the devices are there. > > BTW: If someone could contribute a reactos template with common > tools like peazip and sumatrapdf it would be nice for all to play with some > old windows stuff. > > Regards > > Ludwig > This has come up a number of times on the list, both for ReactOS and Android installs. The issue is that ReactOS *has* to see a disk at /dev/sda or /dev/hda, whereas Qubes presents disks at /dev/xvda etc. Take a look at https://github.com/unman/notes/blob/master/disks_in_Qubes If you look at https://github.com/unman/change_disk you'll see a possible solution: how to use those files is explained at https://github.com/unman/notes/blob/master/InstallingAndroid.md Basically, you redefine the disks so that they are presented as disks that ReactOS will accept. Then you can just install to /dev/sda If you need help, just ask. -- 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/20201214005453.GA19004%40thirdeyesecurity.org.
