New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qmemman doesn't distribute free memory after VM shutdown #246

Closed
marmarek opened this Issue Mar 8, 2015 · 7 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by marmarek on 26 Jun 2011 20:12 UTC
After VM shutdown memory left as xen free. It should be distributed to VMs instantly...
Now qmemman waits for any other event: VM meminfo update or memory request from qvm-start.

I've tried to fix it, but unfortunately without success:
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=bd447308fe03240d781eecb856153b1ac5461dc4

Migrated-From: https://wiki.qubes-os.org/ticket/246

@marmarek marmarek added this to the Release 1 Beta 3 milestone Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 10 Sep 2011 08:16 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 10 Sep 2011 08:16 UTC

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 12 Sep 2011 07:51 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 12 Sep 2011 07:51 UTC

@marmarek marmarek added P: major and removed P: minor labels Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 13 Sep 2011 13:56 UTC
The impact is minor as memory will be balanced upon first request for it (starting new VM or need for memory from already running VM).

The next try can be "@releaseDomain" xenstore watch (see xen-4.0.1/source/docs/misc/xenstore.txt#185).

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 13 Sep 2011 13:56 UTC
The impact is minor as memory will be balanced upon first request for it (starting new VM or need for memory from already running VM).

The next try can be "@releaseDomain" xenstore watch (see xen-4.0.1/source/docs/misc/xenstore.txt#185).

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 13 Sep 2011 17:01 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 13 Sep 2011 17:01 UTC

@marmarek marmarek added P: minor and removed P: major labels Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 25 Sep 2011 11:14 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 25 Sep 2011 11:14 UTC

@marmarek marmarek added P: major and removed P: minor labels Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by marmarek on 30 Sep 2011 11:17 UTC

Member

marmarek commented Mar 8, 2015

Modified by marmarek on 30 Sep 2011 11:17 UTC

@marmarek marmarek assigned marmarek and unassigned rootkovska Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment