Re: [qubes-devel] Where does Qubes 4 store the VM images?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Nov 08, 2017 at 03:12:29AM -0800, Elias Mårtenson wrote: > In 3.2, the images were stored as sparse files in > /var/lib/qubes/appvms/VMNAME. In Qubes 4, these directories are practically > empty, so where is the data stored? > > Also, the

Re: [qubes-devel] dispvms in qubes 4.0

On Wednesday, November 8, 2017 at 9:01:44 PM UTC-8, Marek Marczykowski-Górecki wrote: > > > > Hmm, what exactly to do you want to achieve? The above "qvm-create > > > > > > > make a customized dvm with menus that show up in the top left. Ideally, > > this > > would behave like the

[qubes-devel] dispvms in qubes 4.0

Ive tried creating them with qvm-create --class DispVM --template fedora25 --label red mydvm app: Error creating VM: Got empty response from qubesd. See Journalctl in dom0 for details. the last line of that was AttributeError: 'TemplateVM' object has no attribute 'template_for_dispvms' so

Re: [qubes-devel] dispvms in qubes 4.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Nov 08, 2017 at 07:12:24PM -0800, pixel fairy wrote: > Ive tried creating them with > > qvm-create --class DispVM --template fedora25 --label red mydvm > app: Error creating VM: Got empty response from qubesd. See Journalctl in > dom0 for

[qubes-devel] Re: (trying to avoid) unpacking before checking signatures

On Wed, Nov 8, 2017 at 10:51 PM, Jean-Philippe Ouellet wrote: > Hello, > > The way some things are distributed on kernel.org (e.g. util-linux > [1], cryptsetup [2], etc.) is such that the authors upload .tar and > .tar.sign files, and then the kernel.org infrastructure compresses >

[qubes-devel] (trying to avoid) unpacking before checking signatures

Hello, The way some things are distributed on kernel.org (e.g. util-linux [1], cryptsetup [2], etc.) is such that the authors upload .tar and .tar.sign files, and then the kernel.org infrastructure compresses those (creating .tar.gz & .tar.xz) and signs all resulting files (creating

Re: [qubes-devel] dispvms in qubes 4.0

> > > > Template for DispVM needs to be an AppVM. So, first create AppVM (or use > fedora-25-dvm provided for this purpose), then set > template_for_dispvms=True and use that AppVM for your DispVM. > Still confused. The second thing i tried above was make an appvm, then set

Re: [qubes-devel] dispvms in qubes 4.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Nov 08, 2017 at 07:59:24PM -0800, pixel fairy wrote: > > > > > > > > > Template for DispVM needs to be an AppVM. So, first create AppVM (or use > > fedora-25-dvm provided for this purpose), then set > > template_for_dispvms=True and use

Re: [qubes-devel] dispvms in qubes 4.0

On Wed, Nov 8, 2017 at 8:08 PM Marek Marczykowski-Górecki < marma...@invisiblethingslab.com> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, Nov 08, 2017 at 07:59:24PM -0800, pixel fairy wrote: > > > > > > > > > > > > > > Template for DispVM needs to be an AppVM. So, first

Re: [qubes-devel] dispvms in qubes 4.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, Nov 09, 2017 at 04:32:38AM +, pixelfairy wrote: > On Wed, Nov 8, 2017 at 8:08 PM Marek Marczykowski-Górecki < > marma...@invisiblethingslab.com> wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > On Wed, Nov 08,