On March 10, 2018 1:02 AM, 799 wrote:
> On 10 March 2018 at 01:48, 'MirrorWay' via qubes-users
> wrote:
>
>> Unlike regular dispvms, the lifetime of a named dispVMs is not tied to an
>> app, you have to shutdown manually. Like regular
@Mirrorway
On Saturday, March 10, 2018 at 1:48:12 AM UTC+1, MirrorWay wrote:
> Unlike regular dispvms, the lifetime of a named dispVMs is not tied to an
> app, you have to shutdown manually. Like regular dispvms, named dispVMs
> forget all changes to private storage after shutdown.
>
>
>
> To
On 10 March 2018 at 01:48, 'MirrorWay' via qubes-users <
qubes-users@googlegroups.com> wrote:
> Unlike regular dispvms, the lifetime of a named dispVMs is not tied to an
> app, you have to shutdown manually. Like regular dispvms, named dispVMs
> forget all changes to private storage after
On Saturday, March 10, 2018 at 1:49:55 AM UTC+1, Unman wrote:
> On Sat, Mar 10, 2018 at 01:21:22AM +0100, 799 wrote:
> > Hello,
> >
> > Am 10.03.2018 1:10 vorm. schrieb "'MirrorWay' via qubes-users" <
> > qubes-users@googlegroups.com>:
> >
> > You can reduce the start time to almost zero by
On Sat, Mar 10, 2018 at 01:21:22AM +0100, 799 wrote:
> Hello,
>
> Am 10.03.2018 1:10 vorm. schrieb "'MirrorWay' via qubes-users" <
> qubes-users@googlegroups.com>:
>
> You can reduce the start time to almost zero by using an already-running,
> named DIspVM, see marmarek's post in
Unlike regular dispvms, the lifetime of a named dispVMs is not tied to an app,
you have to shutdown manually. Like regular dispvms, named dispVMs forget all
changes to private storage after shutdown.
To create a named dispVM called "disp-untrusted" that is based on the
"untrusted" VM:
$
On Saturday, March 10, 2018 at 1:21:25 AM UTC+1, [ 799 ] wrote:
> Hello,
>
>
>
> Am 10.03.2018 1:10 vorm. schrieb "'MirrorWay' via qubes-users"
> :
>
> You can reduce the start time to almost zero by using an already-running,
> named DIspVM, see marmarek's post in
Hello,
Am 10.03.2018 1:10 vorm. schrieb "'MirrorWay' via qubes-users" <
qubes-users@googlegroups.com>:
You can reduce the start time to almost zero by using an already-running,
named DIspVM, see marmarek's post in https://github.com/QubesOS/
qubes-issues/issues/2801.
That sounds very
You can reduce the start time to almost zero by using an already-running, named
DIspVM, see marmarek's post in
https://github.com/QubesOS/qubes-issues/issues/2801.
You can set a cron job that ensures they shutdown at least once per day.
--
You received this message because you are subscribed
Hello,
I am just wondering if there is a way to speed up the start of disposable
VMs.
On my W540 with an Intel Core i7-4900MQ with 4 Cores @ 2.8GHz / 32 GB RAM /
512GB SSD and having only sys-net / sys-firewall running the first boot of
a disposable VM takes 18sec, later starts take 15sec.
There
10 matches
Mail list logo