Closed GoogleCodeExporter closed 9 years ago
Nice. Please include in next version.
Original comment by cod...@iscgr.de
on 8 Jan 2012 at 12:42
Issue 390 has been merged into this issue.
Original comment by sibprogrammer
on 30 Jan 2012 at 2:52
physpages parameter doesn't changed when editing VM config values at RHEL6
based openvz.
Original comment by anton.ka...@gmail.com
on 19 Feb 2012 at 11:54
Original comment by sibprogrammer
on 13 Mar 2012 at 12:53
has this already been included in the source by any chance ?
Original comment by norm...@gmail.com
on 24 Mar 2012 at 11:28
I guess there should be some autodetection of vzctl version... To keep
compatibility with systems where is no vSwap. Or maybe the configuration of
containers will not interferre as SWAPSPACE will only show fake swap in
containers on older hosts... I am not sure about memory... Maybe it remains
same...
Original comment by Harvi...@gmail.com
on 28 May 2012 at 2:10
Anyway... this started to be real spliner in ass for me after upgrade as i
can't let anybody to change memory using ovz-web-panel as it would screw up the
vSwap settings... :(
Original comment by Harvi...@gmail.com
on 3 Jun 2012 at 2:07
A couple of helpful hints
(1) Hardware node supports vswap if /proc/vz/vswap file exists.
(2) CT config is considered vswap-enabled, if physpages.limit is NOT set to
unlimited.
(3) Newer vzlist (as of today's git, will be available in vzctl-3.4) have a new
vswap field which shows yes (CT config is vswap-enabled) or no (config is old
fashioned UBC config) for a container.
(4) In vswap mode, one can still use other beancounters, they just become
optional. The only non-optional ones are PHYSPAGES (aka --ram) and SWAPPAGES
(aka --swap).
Original comment by kolysh...@gmail.com
on 13 Jun 2012 at 6:38
Hello,
I made a tiny patch to support modifying RAM setting on a vswap enabled VE
I started to put some SWAP support but it requires more work on the API part.
It now shows correctly the RAM assigned to the VE, in VE listing, and let you
change it without messing up your vswap config.
-O.
Original comment by oliver.m...@gmail.com
on 20 Jun 2012 at 12:55
Attachments:
Oliver: thx for your effort. I've tried your patch with OWP 2.1, but it seems
to behave bit strange...
I've got following container:
# RAM
PHYSPAGES="0:512M"
# Swap
SWAPPAGES="0:1G"
And panel now says it's 2 MB Ram and unlimited swap...
Original comment by Harvi...@gmail.com
on 18 Aug 2012 at 4:30
(before patch it said that it's unlimited ram and did't known what swap is)
Original comment by Harvi...@gmail.com
on 18 Aug 2012 at 4:39
Issue 127 has been merged into this issue.
Original comment by sibprogrammer
on 2 Feb 2013 at 9:46
Original comment by sibprogrammer
on 2 Feb 2013 at 9:46
Support for vSwap was added. See
https://github.com/sibprogrammer/owp/commit/2bb1f15c58cd860e7ae38d016b2f430c2152
2406
Original comment by sibprogrammer
on 2 Feb 2013 at 9:50
Awesome!!! Thank you very much :-)
There's only single thing that i like to change...
If i specify size (doesn't matter if swap, ram or disk) in config as eg.:
5G:5.5G
Web panel shows it to mi in MB, but when i save it it's in Bytes which is quite
annoying as it prevents humans from reading/editing the config manualy.
And this is why i think that your panel is the best of all OpenVZ panels -
because i can decide if i want to use SSH or Web (so helpdesk staff can edit
settings while i can still use native configuration in critical situations).
Original comment by Harvi...@gmail.com
on 2 Feb 2013 at 5:09
Original issue reported on code.google.com by
scr4tchy...@gmail.com
on 7 Jan 2012 at 12:13