On Sunday, March 25, 2018 at 7:20:29 AM UTC-4, awokd wrote: > On Sun, March 25, 2018 3:07 am, sevas wrote:
> > I had qubes installed without it. I wanted to install android. Android > > didnt recognize the virtual machines. So, I plugged in a 2nd disk. I was > > able to qvm-pci attach my SSD. Android recognized it and was able to > > install. > > I'm surprised this actually worked without trouble! lol! > The options I see for you are: > > A) Go back to 3.2 with the emulated disk controller Android can detect > (see https://github.com/QubesOS/qubes-issues/issues/3651). Not a chance! > B) Wait for someone to add a feature to 4.0/4.1 to change the emulated > disk controller type per VM (or find out if there is a more direct means > to change it). This would let you add both your drives to the same LVM > pool and encryption, and use regular drive images for your HVM. > > C) Dedicate and passthrough the single SSD only for your Android HVM > without encryption etc. Im now thinking about doing this with an SD card. Do you think that would work? Well, Im going to test it tomorrow. > I'm not exactly sure I follow what you've done to this point, so that > might be the safest approach. Fdisk the SSD (assuming there's nothing you > need to keep on it), shutdown your computer, physically disconnect/remove > the SSD, power on and reinstall Qubes if needed. Then power back down and > reattach it. You can then use it with one of the above options. If option > B, suggest manually setting up cryptsetup on it with the same password and > then a separate LVM pool. I could encrypt it from within qubes and decrypt it before use with VM, right? Qubes manages encryption and android is none the wiser. -With Qubes on 2 drives: --Ive tried trimfs and --allow-discard on root and luks --shrinking the pool= no info on google about this --qvm-create BIGVM && dd if=/dev/random of=/BIGFILE.img count=250GB && qvm-remove BIGVM >>shrink pool ----no cigar >>I'm not exactly sure I follow what you've done to this point, PVcreate: Qubes installation with one m.2 only. Added SSD later. $ sudo pvcreate /dev/sdb #Error device not found (or ignored by filtering) Am I supposed to use $ sudo pvcreate /dev/sdb1 ? I wanted to PV the entire device and not just the partition(s). $ nano /etc/lvm/lvm.conf >#global-filtering = [devices] #No change. >global-filtering = [sdb] #did not fix. >global-filtering = [devices] #did not fix, of course. 'devices' is just >generic for 'add your device here'. But I un-commented it anyway. And >restarted. Im pretty sure Im just misunderstanding the pvcreate tool. I will read up on the correct methods tomorrow too. But some people were using 'global-filtering=sdb' and they could suddenly 'pvcreate sdb' device without partition without errors. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/67cfe244-23b4-414d-97c6-e0d494f27887%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
