I decided to go back and get the "support" file, attached.
I also noticed the recent thread on qubes-users about the kernel 5.4.
However, when I tried this kernel, Qubes OS was completely unusable:
starting from the point where the OS-level boot log would normally
appear ("Starting service
My employer recently issued me a Dell Precision 7550, which came with a
Ubuntu installation with some OEM customizations. I hoped to use Qubes
OS to protect my employee records and communications from all the
software I'll be running as part of my development work.
Unfortunately, my assessment
On Wed, 2020-11-18 at 22:49 -0800, Andrew David Wong wrote:
> On 11/18/20 5:54 AM, Matt McCutchen wrote:
> > I assumed the update process was the same for a TemplateVM or a
> > StandaloneVM (though I've never tried the latter),
>
> It mostly is, but I personally find
On Wed, 2020-11-18 at 14:34 +, unman wrote:
> On Wed, Nov 18, 2020 at 08:54:23AM -0500, Matt McCutchen wrote:
> > The problem is when I change the main TemplateVM and want to apply the
> > change to all existing system volumes. For example, recently I've
> > migrat
I have the honor of a response from Andrew! :)
On Tue, 2020-11-17 at 20:57 -0800, Andrew David Wong wrote:
> For me, the advantage of TemplateVMs over StandaloneVMs (even if there's
> only one TemplateBasedVM based on the TemplateVM) is that it's easier to
> update the TemplateVM and back up
Hi Steve,
Thanks for your thoughtful response!
On Sun, 2020-11-15 at 16:31 -0500, Steve Coleman wrote:
> My way of dealing with it is to just clone your pristine fedora-32
> template and add the required packages to that template clone, then
> create an AppVM that uses that template. This way
Hi qubes-users,
I have a bunch of VMs based on one Fedora TemplateVM. In most cases,
I'm willing to install any Fedora package needed by any of the VMs in
the TemplateVM. However, due to security concerns, I have one VM that
runs Zoom, one that runs Skype, one that runs Google Chrome, and one
To the original point of this thread (figuring out /why/ the measured
boot isn't working):
The way I found to do this is to configure tboot to log to the screen
by setting (for example) "logging=vga vga_delay=10" on the "multiboot
/tboot.gz" line in grub.cfg. The Qubes default setting is
On Thu, 2017-01-12 at 13:42 +0100, Marek Marczykowski-Górecki wrote:
> On Thu, Dec 01, 2016 at 04:32:50PM +0100, Swâmi Petaramesh wrote:
> > Hi Rusty Bird, and thanks for your help,
> >
> > Please see below.
> >
> > >
> > > Is the SINIT module working? Run the "find" command from step 2b of
> >
