Re: [qubes-devel] More regular point releases schedule?

2019-02-06 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/02/2019 1.54 PM, Marek Marczykowski-Górecki wrote: > On Wed, Feb 06, 2019 at 08:50:19PM +0100, Zrubi wrote: >> On 2/6/19 5:54 PM, Marek Marczykowski-Górecki wrote: > >>> I'm not sure what such schedule should look like, every 3 >>> months? 6 m

Re: [qubes-devel] More regular point releases schedule?

2019-02-06 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Feb 06, 2019 at 08:50:19PM +0100, Zrubi wrote: > On 2/6/19 5:54 PM, Marek Marczykowski-Górecki wrote: > > > I'm not sure what such schedule should look like, every 3 months? > > 6 months? > > I would synchronize this with the most used gues

Re: [qubes-devel] More regular point releases schedule?

2019-02-06 Thread Zrubi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2/6/19 5:54 PM, Marek Marczykowski-Górecki wrote: > I'm not sure what such schedule should look like, every 3 months? > 6 months? I would synchronize this with the most used guest templates: the Fedora and the Debian releases. Means it should no

Re: [qubes-devel] Allocating(too fast)fails and triggers OOM-killer before MemTotal reaches AppVM's set Max memory

2019-02-06 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Feb 06, 2019 at 02:17:17PM -0500, Chris Laprise wrote: > On 2/6/19 1:07 PM, Marek Marczykowski-Górecki wrote: > > (*) Actually there are two parts of this: first detecting that qube > > needs more RAM - it is reported with 10Hz frequency, as

Re: [qubes-devel] More regular point releases schedule?

2019-02-06 Thread Chris Laprise
On 2/6/19 11:54 AM, Marek Marczykowski-Górecki wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, It may be a good idea to introduce regular schedule for stable [point releases[1]. It would minimize the need to download a lot of updates just after installation. This is even more sig

Re: [qubes-devel] Allocating(too fast)fails and triggers OOM-killer before MemTotal reaches AppVM's set Max memory

2019-02-06 Thread Chris Laprise
On 2/6/19 1:07 PM, Marek Marczykowski-Górecki wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Feb 06, 2019 at 06:29:22PM +0100, Dupéron Georges wrote: This would work for dom0 in Qubes, but I don't know how you would trigger it in a VM. There is `xl sysrq` which you can use to

[qubes-devel] Re: More regular point releases schedule?

2019-02-06 Thread Foppe de Haan
On Wednesday, February 6, 2019 at 5:54:37 PM UTC+1, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi all, > > It may be a good idea to introduce regular schedule for stable [point > releases[1]. It would minimize the need to download a lot of updates >

Re: [qubes-devel] Allocating(too fast)fails and triggers OOM-killer before MemTotal reaches AppVM's set Max memory

2019-02-06 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Feb 06, 2019 at 06:29:22PM +0100, Dupéron Georges wrote: > This would work for dom0 in Qubes, but I don't know how you would trigger > it in a VM. There is `xl sysrq` which you can use to inject sysrq to a VM. - -- Best Regards, Marek Marc

Re: [qubes-devel] Allocating(too fast)fails and triggers OOM-killer before MemTotal reaches AppVM's set Max memory

2019-02-06 Thread Dupéron Georges
On a non-Qubes system, I used to press "alt+sysrq f" to manually invoke the OOM killer when the disk would start thrashing. Worked like a charm, but the OOM picks a random process so it can kill e.g. Xorg if you're unlucky. This would work for dom0 in Qubes, but I don't know how you would trigger

Re: [qubes-devel] More regular point releases schedule?

2019-02-06 Thread Holger Levsen
On Wed, Feb 06, 2019 at 05:54:29PM +0100, Marek Marczykowski-Górecki wrote: > It may be a good idea to introduce regular schedule for stable [point > releases[1]. It would minimize the need to download a lot of updates > just after installation. This is even more significant, if some updates > may

[qubes-devel] More regular point releases schedule?

2019-02-06 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, It may be a good idea to introduce regular schedule for stable [point releases[1]. It would minimize the need to download a lot of updates just after installation. This is even more significant, if some updates may require non-standard updat

Re: [qubes-devel] Allocating(too fast)fails and triggers OOM-killer before MemTotal reaches AppVM's set Max memory

2019-02-06 Thread Marcus Linsner
On Wed, Feb 6, 2019 at 4:46 PM Marek Marczykowski-Górecki wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, Feb 06, 2019 at 07:38:19AM -0800, Marcus Linsner wrote: > > I have an AppVM with > > Initial Memory: 2400 MB > > Max memory 24000 MB > > [v] Include in memory balancin

Re: [qubes-devel] Allocating(too fast)fails and triggers OOM-killer before MemTotal reaches AppVM's set Max memory

2019-02-06 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Feb 06, 2019 at 07:38:19AM -0800, Marcus Linsner wrote: > I have an AppVM with > Initial Memory: 2400 MB > Max memory 24000 MB > [v] Include in memory balancing > > has no swap enabled (swapon reports nothing) and uses an official kernel(eg.

[qubes-devel] Allocating(too fast)fails and triggers OOM-killer before MemTotal reaches AppVM's set Max memory

2019-02-06 Thread Marcus Linsner
I have an AppVM with Initial Memory: 2400 MB Max memory 24000 MB [v] Include in memory balancing has no swap enabled (swapon reports nothing) and uses an official kernel(eg. not compiled by me): Linux dev01-w-s-f-fdr28 4.19.12-3.pvops.qubes.x86_64 #1 SMP Wed Dec 26 22:31:51 UTC 2018 x86_64 x86_6

[qubes-devel] Re: Qubes as a GSoC voucher for Whonix

2019-02-06 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > Dear Qubes Developers, > > Whonix is applying to be a Google Summer of Code organization this year. > I am writing on behalf of Whonix to ask if Qubes could be a voucher for > Whonix. Specifically, in the application form, it asks: > > > If you a