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
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
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
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
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.
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
> > [@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.
>
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
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?
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
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/
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
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
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
>> 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
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
> 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
17 matches
Mail list logo
