Re: [qubes-devel] Re: Memory balancing issue resurfaced

2018-04-04 Thread Elias Mårtenson
On Saturday, 24 March 2018 21:14:10 UTC+8, Marek Marczykowski-Górecki  wrote:

> I haven't seen this for a while (since closing that issue). Check
> `journalctl` for qmemman related entries when it happens. Especially
> there are reports about each VM needs and how much memory was really
> assigned + some details about state of qmemman.

I just had the problem again. Restarting qubes-qmemman fixed it, as expected. 
Before I restarted it, I had lots of messages like the following. Would you be 
able to draw any conclusions from it?



Apr 04 20:55:48 dom0 qmemman.daemon.algo[19150]: left_memory=79834729 
acceptors_count=5
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: dom 16 is below pref, allowing 
balance
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '0' act=7797228211 
pref=1940720102.4 last_target=7797228211
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '16' act=401645568 
pref=606883430.4 last_target=401604608
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '11' act=1594164013 
pref=385653964.8 last_target=1594164013
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '5' act=943718400 
pref=292608409.6 last_target=943718400
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '13' act=1529529771 
pref=369450598.4004 last_target=1529529771
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '7' act=2125299035 
pref=518805913.6 last_target=2125299035
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: xenfree=66575070 
memset_reqs=[('0', 6804649009), ('13', 1308300424), ('11', 1364980293), ('7', 
1830749866), ('5'
, 943718400), ('16', 2138847702)]
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 0 to 6804649009
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 13 to 1308300424
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 11 to 1364980293
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 7 to 1830749866
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 5 to 943718400
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: dom '11' still hold more 
memory than have assigned (1512398848 > 1364980293)
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 16 to 2021704585
Apr 04 20:55:48 dom0 qmemman.daemon.algo[19150]: 
balance_when_enough_memory(xen_free_memory=-2950780, 
total_mem_pref=4845036416.01, total_available_memory=99929653
59.98)
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: dom 18 is below pref, allowing 
balance
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '0' act=6804649009 
pref=1940720102.4 last_target=6804649009
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '18' act=419431424 
pref=730913996.801 last_target=419431424
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '16' act=2021704585 
pref=606883430.4 last_target=2021704585
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '11' act=1512398848 
pref=385653964.8 last_target=1364980293 slow_memset_react
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '5' act=943718400 
pref=292608409.6 last_target=943718400
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '13' act=1308300424 
pref=369450598.4004 last_target=1308300424
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: dom '7' act=1830749866 
pref=518805913.6 last_target=1830749866
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: stat: xenfree=49478020 
memset_reqs=[('13', 1130316938), ('0', 5937542971), ('5', 895221832), ('11', 
1179890384), ('7',
 1587262584), ('16', 1856731654), ('18', 2236197408)]
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 13 to 1130316938
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 0 to 5937542971
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 5 to 895221832
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 11 to 1179890384
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 7 to 1587262584
Apr 04 20:55:48 dom0 qmemman.systemstate[19150]: mem-set domain 16 to 1856731654
Apr 04 20:55:49 dom0 qmemman.systemstate[19150]: dom '11' didnt react to memory 
request (holds 1512398848, requested balloon down to 1179890384)
Apr 04 20:55:49 dom0 qmemman.systemstate[19150]: dom '7' still hold more memory 
than have assigned (1605578752 > 1587262584)
Apr 04 20:55:49 dom0 qmemman.systemstate[19150]: mem-set domain 18 to 1903107387
Apr 04 20:55:49 dom0 qmemman.daemon.algo[19150]: 
balance_when_enough_memory(xen_free_memory=805899, total_mem_pref=5152096332.8, 
total_available_memory=8588960524.1999
99)
Apr 04 20:55:49 dom0 qmemman.systemstate[19150]: dom 19 is below pref, allowing 
balance
Apr 04 20:55:49 dom0 qmemman.systemstate[19150]: stat: dom '0' act=5937542971 
pref=1940720102.4 last_target=5937542971
Apr 04 20:55:49 dom0 qmemman.systemstate[19150]: stat: dom '19' act=419431424 
pref=692713881.6 last_target=419431424
Apr 04 20:55:49 dom0 qmemman.systemstate[19150]: 

Re: [qubes-devel] Re: Memory balancing issue resurfaced

2018-03-24 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Mar 23, 2018 at 07:56:00AM -0700, Elias Mårtenson wrote:
> On Tuesday, 20 March 2018 11:41:54 UTC+8, Elias Mårtenson  wrote:
> 
> > If this happens again, are there any logs or anything like that that I can 
> > collect in order to make it easier to debug this issue?
> 
> I just had the bug again, and this time I decided to restart qubes.qmemman 
> and sure enough, that seemed to have fixed the problem.
> 
> Clearly this issue is still around, but does anyone else see this?

I haven't seen this for a while (since closing that issue). Check
`journalctl` for qmemman related entries when it happens. Especially
there are reports about each VM needs and how much memory was really
assigned + some details about state of qmemman.

- -- 
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-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqtyGUACgkQ24/THMrX
1yzL7Qf7BiswgKcwaNu3k8TjqBun09eXC/pwjxOIokIuULmdJpZe/PgYdL9omVXE
7BOweVkGJ/bX6+jHmxQoMxkF83kD8hZBvNijpZkogMB+yLCnXZ62pbqMHa2YV8xZ
F5cSqoYZgikBKhUk6e3YU+ZrEdhA+ytlA6Z3G3RMeyTR9Ac1+wSQ2NkeYWJVsOh1
/u7ZXJJyck4wUOFA5XijN5SKDiwiMlaS7HwI2/wX/wlx2GnuIxeObxGZS/0Ghwmw
CyBoJq5jKNE1TrrzSAeVy5tvv8eOlZIwk8Vt+ZBj0die+B2UWuNn4/I5TGyOVG1A
u5XDklJ5otG6r19y1pVUQW1RGwJGmw==
=3br4
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/20180324131402.GJ8343%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


[qubes-devel] Re: Memory balancing issue resurfaced

2018-03-23 Thread Elias Mårtenson
On Tuesday, 20 March 2018 11:41:54 UTC+8, Elias Mårtenson  wrote:

> If this happens again, are there any logs or anything like that that I can 
> collect in order to make it easier to debug this issue?

I just had the bug again, and this time I decided to restart qubes.qmemman and 
sure enough, that seemed to have fixed the problem.

Clearly this issue is still around, but does anyone else see this?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/96058068-155c-4e36-959b-d7a952e29361%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.