How do I change the DispVM generation time out limit?

[Reg Tiangha]

I run Qubes on a laptop with a regular hard drive, and I've noticed that
as my drive fills up and I assume fragmentation hits, it takes longer
and longer for VMs to start up as they get moved around by
qvm-trim-template and what not.

It comes with the territory so I've just learned to live with it until I
get an SSD in this thing, but it's gotten to the point (about 100GB free
on a 750GB drive) that either generating a DispVM or updating its save
file after the main template has been updated takes about a minute and a
half or so for the DispVM file to completely boot, but the
qvm-create-default-dvm script times out with a "ERROR: Cannot start
qubes-guid!" error.

Sometimes I can work around it by trimming the DispVM template or
running e4defrag on it or even just copying it somewhere and deleting
the old one just to get the VM to move to another part of the disk, but
that's getting harder and harder to do now as (I assume) enough
contiguous free space on my disk becomes less and less as time goes by.

Is there any way that I can change the time out the DVM generation
script waits in order to connect to qubes-guid? I think I may need to
double or triple it, but the machine does start up eventually; it's just
the DVM generation script that gives up too soon.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Currently it's hardcoded to 45 seconds. But should be trivial to add
an option for this.
https://github.com/QubesOS/qubes-issues/issues/2759

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJY9mMtAAoJENuP0xzK19csEsUH/RE9u0Qjui+FYvlXWGxZdwUi
a7FqWCMomIAHaIFsCw010qwYsi4i0j5q9ilVbc1TXPXiibPIudoHLz4ahpjo0HI1
Cu30Y0G2Gj8TzuXbZ4Mg8/0LnnrhBBorJV5dWHkUcbq/H13X3uPhX7HfJZBUhn6t
b42Y/elgwkZMaFczntcTyspUy1yMnXUC8RddNYCHtfM9DMLJaN7IKBdtxTf57aIh
I31pYfUU1IQpiWt/CSGGKnhw9+IDfvfMiTUQpnrSivR5lDibynxTXumUgaKcvcLZ
GJzD3dOu0ho8XkDWN5x0SAkbfg8nIE9GdVGQRVG6CBtLNrL3wklHNQunAmiZtbE=
=piF1
-----END PGP SIGNATURE-----

[Reg Tiangha]

On 04/18/2017 01:04 PM, Marek Marczykowski-Górecki wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256

> Currently it's hardcoded to 45 seconds. But should be trivial to add
> an option for this.
> https://github.com/QubesOS/qubes-issues/issues/2759
>
> - --
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJY9mMtAAoJENuP0xzK19csEsUH/RE9u0Qjui+FYvlXWGxZdwUi
> a7FqWCMomIAHaIFsCw010qwYsi4i0j5q9ilVbc1TXPXiibPIudoHLz4ahpjo0HI1
> Cu30Y0G2Gj8TzuXbZ4Mg8/0LnnrhBBorJV5dWHkUcbq/H13X3uPhX7HfJZBUhn6t
> b42Y/elgwkZMaFczntcTyspUy1yMnXUC8RddNYCHtfM9DMLJaN7IKBdtxTf57aIh
> I31pYfUU1IQpiWt/CSGGKnhw9+IDfvfMiTUQpnrSivR5lDibynxTXumUgaKcvcLZ
> GJzD3dOu0ho8XkDWN5x0SAkbfg8nIE9GdVGQRVG6CBtLNrL3wklHNQunAmiZtbE=
> =piF1
> -----END PGP SIGNATURE-----
>

Is that in a script I can edit in the meantime as a workaround, or is it
compiled in? I tried to trace through the generation script, but I
couldn't find what threw the "Connecting to VM's GUI agent......time
out" message. The start up of the VM takes just over a minute, so that
45 second limit is definitely the issue then and upping it might fix
things not just for me, but for anyone else who's been having
unexplained DispVM generation issues lately or in the past.