Re: [qubes-users] Move To a Larger Disk
On Thu, Jun 25, 2020 at 10:29:33PM +, 'Matt Drez' via qubes-users wrote: > How to safely raise it to the maximum size (1TB ) and not just an > arbitrary number that's close enough? which "it"? if you bought a "1TB disk", that usualy means 931GiB. the pvresize dance means the pv is now as big as the partition/luks. > VG #PV #LV #SN Attr VSize VFree > qubes_dom0 1 141 0 wz--n- 929.32g 556.51g so 929.32g sounds about right, thats the size of your disk minus the boot partition minus some headers. > pool00 qubes_dom0 twi-aotz-- 897.98g 33.45 14.82 you can probably grow that pool some more. check "vgs" again, the VFree is now something like 6.5g? so run "lvresize -L +6g qubes_dom0/pool00" i would NOT assign the last few megabytes to a device, but keep them "free" in case i need to dig myself out of a "oops, metadata is full because i have too many snapshots" situation. -- 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/20200625224532.GJ137863%40priv-mua.
Re: [qubes-users] Move To a Larger Disk
This worked (see below). Thank you so much. You rock! Only one question remained: How to safely raise it to the maximum size (1TB ) and not just an arbitrary number that's close enough? [@dom0 ~]$ sudo pvresize --setphysicalvolumesize 900g /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 WARNING: Device /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 has size of 1948924598 sectors which is smaller than corresponding PV size of 1949320573 sectors. Was device resized? One or more devices used as PVs in VG qubes_dom0 have changed sizes. Physical volume "/dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576" changed 1 physical volume(s) resized / 0 physical volume(s) not resized [@dom0 ~]$ sudo pvresize /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 Physical volume "/dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576" changed 1 physical volume(s) resized / 0 physical volume(s) not resized [@dom0 ~]$ sudo pvs PVVG Fmt Attr PSize PFree /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 qubes_dom0 lvm2 a-- 929.32g 556.51g [Abraham@dom0 ~]$ sudo vgs VG #PV #LV #SN Attr VSize VFree qubes_dom0 1 141 0 wz--n- 929.32g 556.51g [@dom0 ~]$ sudo lvresize -L +550G qubes_dom0/pool00 WARNING: Sum of all thin volume sizes (3.34 TiB) exceeds the size of thin pools and the size of whole volume group (929.32 GiB)! For thin pool auto extension activation/thin_pool_autoextend_threshold should be below 100. Size of logical volume qubes_dom0/pool00_tdata changed from 347.98 GiB (89083 extents) to 897.98 GiB (229883 extents). Logical volume qubes_dom0/pool00_tdata successfully resized. [@dom0 ~]$ sudo lvs qubes_dom0/pool00 LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert pool00 qubes_dom0 twi-aotz-- 897.98g 33.45 14.82 -- 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/MkGm7nh38pBsMKc1EErmyFdomARbWOKze0yli6OOWpN2Y1L_U2iix57O2DN_Ue6IQkJiPuVtQdd83j1xToY4tnNd2AV3oYHR0AUJB8yT4W4%3D%40pm.me. publickey - mattdrez@pm.me - 0x8196D0F4.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Move To a Larger Disk
On Thu, Jun 25, 2020 at 08:54:51PM +, Matt Drez wrote: > This is where I am at now (below). What would be the best course of > action. What would you if this was your mess to clean up? :) > WARNING: Device > /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 has size of > 1948924598 sectors which is smaller than corresponding PV size of > 1949320573 sectors. Was device resized? this is a bit worrying and i am not sure how you ended up with that. to clean this up, i would try ... pvresize --setphysicalvolumesize 900g /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 pvresize /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 then check that the warning is gone (pvs or vgs). AFTER resolving the PV size problem, i would grow the thin pool. > VG #PV #LV #SN Attr VSize VFree > qubes_dom0 1 141 0 wz--n- 929.51g 556.70g > [@dom0 ~]$ sudo lvs qubes_dom0/pool00 > LV VG Attr LSize Pool Origin Data% Meta% Move Log > Cpy%Sync Convert > pool00 qubes_dom0 twi-aotz-- 347.98g 86.33 14.67 this suggests you resized the poolmetadata already? if you did NOT: lvresize --poolmetadatasize +1G qubes_dom0/pool00 then resize the pool itself: lvresize -L +550G qubes_dom0/pool00 then check it worked by running "lvs qubes_dom0/pool00" again, the new LSize should be 900g, and the Meta% should still be a lot smaller than the Data%. > [@dom0 ~]$ sudo df -h / > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/qubes_dom0-root 1.1T 9.7G 1.1T 1% / this is unfortunate, but not critical. if you really want to shrink the FS again, look up how to shrink a ext4 FS. basicly you will have to boot from some rescue disk or live image, open the luks container + lvm, fsck and resize2fs the fs, then shrink the LV, then grow the fs again to fit. if it were my system, i wouldnt bother with that. -- 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/20200625214028.GI137863%40priv-mua.
Re: [qubes-users] Move To a Larger Disk
This is where I am at now (below). What would be the best course of action. What would you if this was your mess to clean up? :) [@dom0 ~]$ sudo pvs WARNING: Device /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 has size of 1948924598 sectors which is smaller than corresponding PV size of 1949320573 sectors. Was device resized? One or more devices used as PVs in VG qubes_dom0 have changed sizes. PVVG Fmt Attr PSize PFree /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 qubes_dom0 lvm2 a-- 929.51g 556.70g [@dom0 ~]$ sudo vgs WARNING: Device /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 has size of 1948924598 sectors which is smaller than corresponding PV size of 1949320573 sectors. Was device resized? One or more devices used as PVs in VG qubes_dom0 have changed sizes. VG #PV #LV #SN Attr VSize VFree qubes_dom0 1 141 0 wz--n- 929.51g 556.70g [@dom0 ~]$ sudo lvs qubes_dom0/pool00 WARNING: Device /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 has size of 1948924598 sectors which is smaller than corresponding PV size of 1949320573 sectors. Was device resized? One or more devices used as PVs in VG qubes_dom0 have changed sizes. LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert pool00 qubes_dom0 twi-aotz-- 347.98g 86.33 14.67 [@dom0 ~]$ sudo lsblk -d /dev/mapper/qubes_dom0-root NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT qubes_dom0-root 253:40 1.1T 0 lvm / [@dom0 ~]$ sudo df -h / Filesystem Size Used Avail Use% Mounted on /dev/mapper/qubes_dom0-root 1.1T 9.7G 1.1T 1% / -- 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/lBEPHNJUXqgIorBVpRV55mrLeGAmBhZuD3U50kizqhdmxuBNhc7n9KEms0VTp6lrwhW8AYUfJW7TksEi6D-W4n6v4WoGhdY-GuB4tiXmRUU%3D%40pm.me. publickey - mattdrez@pm.me - 0x8196D0F4.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Move To a Larger Disk
On Thu, Jun 25, 2020 at 08:05:11PM +, Matt Drez wrote: > That makes total sense. Well, I'm glad I didn't screw everything up > but now how do I reverse what I have done so I could achieve my goal? > How can I "take away" the 100% free space I assigned to root and give > it to the whole system? i am not sure you have to do anything. check with "vgs", does it still report 500+ VFree? then you can just go ahead with the "resizing pool00 meta+data" parts. if you really want to clean up the qubes_dom0-root situation... check with "lsblk -d /dev/mapper/qubes_dom0-root". does it say 500something GB? all good, nothing to do. does it say 1TB? meh, continue. check with "df -h /", does it report 500something GB total? good! IF the df-total is 500something GB, you can just lvresize qubes_dom0-root back down to something like 600GB. pick something that is 10% or so bigger than your old disk and the df-total. DO NOT try to hit the exact size! DO NOT try this if df says 1TB total! -- 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/20200625204225.GH137863%40priv-mua.
Re: [qubes-users] Move To a Larger Disk
> > [@dom0 ~]$ sudo lvs qubes_dom0/pool00 > > LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert > > pool00 qubes_dom0 twi-aotz-- 347.98g 87.01 58.34 > > if you want to enlarge logical volume qubes_dom0/pool00, you > should enlarge qubes_dom0/pool00, not random other devices. > > and it is important you enlarge the metadata volume first. > something like: > lvresize --poolmetadatasize +1G qubes_dom0/pool00 That makes total sense. Well, I'm glad I didn't screw everything up but now how do I reverse what I have done so I could achieve my goal? How can I "take away" the 100% free space I assigned to root and give it to the whole system? Thanks for all your help and your patience with me. -- 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/XyY4ZVGeaKnYWLiUV-oxi_Lx4OcX-KKkgUT1fLFGB_U9N5Sz-QHGs_sADzyoaGqieV8A88459kMuvWceLKgDlqmTCeHngfGiz25Jx4oV-l4%3D%40pm.me. publickey - mattdrez@pm.me - 0x8196D0F4.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Quebes for noobs (Installation)
On 6/25/20 3:41 PM, Bostongeorge wrote: Should I try to load an ISO file, (I have created the usb bootable with rufus) Did you use the correct options when creating the bootable USB? The installation guide gives very specific instructions. https://www.qubes-os.org/doc/installation-guide/ -- 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/56270031-6407-89a8-440a-9ba14449db66%40ak47.co.za.
Re: [qubes-users] Move To a Larger Disk
On Wed, Jun 24, 2020 at 07:49:56PM +, Matt Drez wrote: > [@dom0 ~]$ sudo lvextend -l +100%FREE /dev/mapper/qubes_dom0-root this means you resized your dom0 root volume. that is probably not what you were trying to do. you can check if that worked with "df -h /" or "lsblk -d /dev/mapper/qubes_dom0-root" in dom0. > [@dom0 ~]$ sudo lvextend -l +100%FREE > /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 it is dangerous to press random buttons when dealing with diskspace. > [@dom0 ~]$ sudo lvs qubes_dom0/pool00 > LV VG Attr LSize Pool Origin Data% Meta% Move Log > Cpy%Sync Convert > pool00 qubes_dom0 twi-aotz-- 347.98g 87.01 58.34 if you want to enlarge logical volume qubes_dom0/pool00, you should enlarge qubes_dom0/pool00, not random other devices. and it is important you enlarge the metadata volume first. something like: lvresize --poolmetadatasize +1G qubes_dom0/pool00 -- 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/20200625181841.GG137863%40priv-mua.
Re: [qubes-users] Updating Linux and Whonix
On Thu, Jun 25, 2020 at 11:03:19AM -0700, E. Foster wrote: > I finally got latest version of Qubes installed. thanks for the what version is that? > version displayed did not change. From reading the documentation, The > updater should have updated to Whonix 16, and Fedora 35 or 36 as indicated what documentation is that? there is no "fedora 35 or 36" yet. those are versions that will be released in 1-2 years. > Fedora 30. Would any of you have some suggestions as to how to build a fedora 30 is unsupported. you should install fedora 31 or 32 first. https://www.qubes-os.org/news/2020/04/30/fedora-31-template-available/ -- 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/20200625181157.GF137863%40priv-mua.
[qubes-users] Updating Linux and Whonix
Greetings, I finally got latest version of Qubes installed. thanks for the suggestions. Yet, I ran through a few updates for Debian, Dom() and Whonix however the version displayed did not change. From reading the documentation, The updater should have updated to Whonix 16, and Fedora 35 or 36 as indicated in the version table. It didn't. What I am trying to figure out were the updates needed or suggested, because, I noticed a setting for whonix (safest) was downgraded (to standard). In essence, I'd like to know how to either remove the updates/revert or upgrade to the versions suggested in the table? Is there also a way to set the ethernet/wifi to off, so that I must physically turn it on before any connections take place. I suppose the default is ON, however I was just asking. Also, I've tried to set up a VM for Zoom with Whonix but the settings manager for the VM displays a caution symbol. I didn't know you couldn't use Whonix for the connection. The settings manager does allow sys-firewall. Furthermore, I am having difficulty installing Zoom on Fedora 30. Would any of you have some suggestions as to how to build a Zoom VM or a work around for installing the rpm file. My background is Windows and somehow Fedora is a slight leap of faith. Thanks, -- 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/da966cbc-07fd-4865-bf7a-d8cc290bddf5o%40googlegroups.com.
Re: [qubes-users] Updates Broken After Today's Update
On 6/25/20 6:30 PM, Qubes wrote: My Qubes system was fully patched before today but today I received a notification in the system tray that there is a new update available for dom0 which I have installed. After installing this update I can no longer install new software in any of my TemplateVMs. This is quite unexpected. Is anybody on this list experiencing the same issue? Ok scrap that it looks like it was only a temporary issue. -- 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/4485c919-bc48-00a1-9e50-eb05ace610a8%40ak47.co.za.
[qubes-users] Updates Broken After Today's Update
My Qubes system was fully patched before today but today I received a notification in the system tray that there is a new update available for dom0 which I have installed. After installing this update I can no longer install new software in any of my TemplateVMs. This is quite unexpected. Is anybody on this list experiencing the same issue? -- 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/d7d9b984-2c97-cf79-8231-c4450bf72244%40ak47.co.za.
Re: [qubes-users] How to split into two gateways
> Try just doing the passthrough first. If you can get the NICS to show up > in `lspci` in the two sys-nets and configure networking so you can ping > out. > > Command to attach the NIC: `qvm-pci attach sys-net2 dom0:`. > > PCI-address can be found in the output of `qvm-pci`. Those are the exact steps I tried but no luck. I have no problem passing the NIC to the gw and it shows up with lspci but it won't acquire an IP. The "funny" thing is that as soon as the sys-net starts the green light goes out on the the NIC. If I issue an `ip addr` command I cannot even see its MAC. I even tried connecting the second NIC to a completely different network and router but made no difference. -- 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/JEL2UbOm3FnbcPLHorIHVP3vjTkyHGCmPE1H2Pm9lQEUVz2PPLKNrv3_1E7OStfcir2xiApqztw0YRcswVugy5RBcjKzqQTCyDvWkmHGc5w%3D%40pm.me. publickey - mattdrez@pm.me - 0x8196D0F4.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [qubes-users] New Qubes User here: Need guidance in safely & securely installing to DomUs/Fedora TemplateVM
That really should be your assumption of all software unless you have > written or audited and compiled it yourself. And even then ... why do > you trust your compiler? It's not like that hasn't been done yet. > > One of the many things I appreciate in the Qubes philosophy is that > you dramatically minimize the things you have to trust implicitly: the > XEN hypervisor, the HW virtualization and the Qubes team. > > You should setup your qubes thinking that you are already thoroughly > compromised. How would you minimize damage then? A really sound and honest advice for those who are really badly targeted is: Just don’t bother. Privacy and security are no longer for you. Learn to live without them completely. Regards, Anil Eklavya -- अनिल एकलव्य (Anil Eklavya) -- 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/CAAPfsu8-u-%2BHHaxvD4XNopZbb1HSxVn07zykPPtE7Ng2Jh9Hbw%40mail.gmail.com.
Re: [qubes-users] Quebes for noobs (Installation)
>> I get an error at once i start the installation. > Is that something i need ot change in the bios? Exactly this. The machine you posted should support the features listed, but they may not be enabled by default. Boot into BIOS/UEFI and ensure SVM and IOMMU are enabled. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/00086443-7463-9ba3-31ea-8b5ffa02d0c9%40undef.tools.
Re: [qubes-users] Quebes for noobs (Installation)
On 6/24/20 9:52 PM, Bostongeorge wrote: I am new to this OS, wondering if its possible to install this with this specs on a desktop i just made: In terms of specifications your machine would certainly be able to handle Qubes. If I was you I would just stick in Qubes installation media and start an install. If your BIOS default is set to UEFI and you are looking at a blank screen after booting from the Qubes installation media, please note the following from the documentation, "Note : On UEFI install, there is no boot menu on Qubes OS 4.0 by design. It goes straight to the installer. The boot menu will be back in Qubes OS 4.1." https://www.qubes-os.org/doc/installation-guide/ Please let us know if everything installs and works as expected. -- 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/a1184513-c138-d160-e96a-1d30a74a047c%40ak47.co.za.
[qubes-users] Switch focus on Qubes.OpenURL
Is there a programmatic way to switch window focus between VMs? -- 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/0ecc6c16-bda9-2e8b-d189-430c7dca557f%40gmail.com.
