[GH-ISSUE #407] Prevent hard-coded memory limits #304

Closed
opened 2026-02-27 16:38:47 +03:00 by kerem · 1 comment
Owner

Originally created by @michelkaeser on GitHub (Aug 30, 2014).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/407

In https://github.com/retspen/webvirtmgr/blob/master/instance/views.py#L458 the memory limits are hard-coded and there is no way to manually set other values.

Suggestions:

  • Allow setting a custom value
  • Use conn.get_max_memory() to get the node's memory limit and then do a while loop with increment 1024 to add possible values. That way - on a 32GB server - one can set for example 24GB.
Originally created by @michelkaeser on GitHub (Aug 30, 2014). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/407 In https://github.com/retspen/webvirtmgr/blob/master/instance/views.py#L458 the memory limits are hard-coded and there is no way to manually set other values. Suggestions: - Allow setting a custom value - Use `conn.get_max_memory()` to get the node's memory limit and then do a while loop with increment 1024 to add possible values. That way - on a 32GB server - one can set for example 24GB.
kerem closed this issue 2026-02-27 16:38:48 +03:00
Author
Owner

@lub commented on GitHub (Sep 3, 2014):

Maybe it would be enough when you could choose a custom memory limit (in GB * 1024).
Then you could quickly select a common limit and specify a more or less uncommon for your use case.

<!-- gh-comment-id:54256682 --> @lub commented on GitHub (Sep 3, 2014): Maybe it would be enough when you could choose a custom memory limit (in GB \* 1024). Then you could quickly select a common limit and specify a more or less uncommon for your use case.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/webvirtmgr#304
No description provided.