-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Steve Coleman:
> I seem to have an intermittent problem when my backup scripts are running
> late at night.
>
> My qubesd is apparently being shutdown (sent a sigterm signal) by systemd
> during my long running backup sessions which then causes an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Oleg Artemiev:
> I've slow disk on my qubes PC. Sometimes when I start VMs it tells
> that it can't connect to qrexec & fails to start automatically - I've
> to start again manually & then on the second time the disk reads
> faster due to cache & it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Crsi:
> However, I made sure no VM was running (my host system
> crashed previously anyways). That means there's a difference between
> powering down a VM (e.g. qvm-shutdown) and having a powered down VM due to
> crash / power loss? Am I right that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
unman:
> On Wed, Dec 28, 2022 at 11:00:18AM +0100, Ulrich Windl wrote:
> > Am I the only one that sees extra shutdown delays?
> > It seems that everything is unmounted, but still thing hang; unsure what
> > that is. See attachment.
> > What
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
449f09c92:
> had to edit the relevant code to disable CoW when volatile.img is
> created
file-reflink doesn't inherently do CoW for volatile volumes, it just
defaults to whatever the underlying location on the filesystem does.
For Btrfs, to get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Rusty Bird:
> Disabling CoW and hence checksums (besides being specific to Btrfs -
> file-reflink is filesystem agnostic)
Although for volatile volumes in particular it might be possible to
get away with (optionally, configured per-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> The line "10.1.1.1 myhost.example.com" is appended to
> /etc/hosts. But when I open a disposable terminal and type 'host
> myhost.example.com', I get the DNS address, not 10.1.1.1.
'host' isn't suitable for testing this, because it never looks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Qubes:
> I am sure I have read this somewhere here on the list or in the
> [documentation](https://www.qubes-os.org/doc/) that it is possible to inject
> configuration files into an appVM when it gets created. Can someone maybe
> remind me how to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Boryeu Mao:
> of ``some-dom: command failed with code: 137``, which I have been ignoring
> since the job with ``some-pid`` did get killed. What could be the meaning
> of the code 137 and its significance?
137 == 128 + (signal) 9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Qubes:
> However, when I use the Qubes backup tool it shows the size of the dom0
> backup is going to be 7.1 GB, but other than about 20 MB of screenshots in
> `/home/Pictures/` I don't have anything in `/home/`.
It's a bug in the GUI backup tool's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Boryeu Mao:
> > For R4.1.2 I had some RPC calls with + and - characters in the file
> > name. These are considered as invalid characters to be part of service
> > names in the new qrexec policy format (e.g. in
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Boryeu Mao:
> An attempt to shutdown `sys-firewall` in `Qube Manager` receive a warning
> about running processes in the qube; similarly on command line
> `qvm-shutdown sys-firewall` fails with an error. Is it possible to
> designate an appVM to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rusty Bird:
> Boryeu Mao:
> > An attempt to shutdown `sys-firewall` in `Qube Manager` receive a warning
> > about running processes in the qube; similarly on command line
> > `qvm-shutdown sys-firewall` fails with an e
101 - 113 of 113 matches
Mail list logo
