Editing VSwap
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 72: | Line 72: | ||
If you have an existing container with usual UBC parameters set, and you want to convert this one into VSwap enabled config, here's what you need to do. | If you have an existing container with usual UBC parameters set, and you want to convert this one into VSwap enabled config, here's what you need to do. | ||
− | # Decide on how much RAM and swap you want this CT to have. | + | # Decide on how much RAM and swap you want this CT to have. FIXME how to convert from UBC. |
# Manually remove all UBC parameters from config. '''This is optional''', you can still have UBC limits applied if you want. | # Manually remove all UBC parameters from config. '''This is optional''', you can still have UBC limits applied if you want. | ||
− | + | 2. Add PHYSPAGES and SWAPPAGES parameters to config. Easiest way is to use <code>vzctl set $CTID --ram N --swap M --save</code> | |
Now your config is vswap enabled, and when you (re)start it (or use <code>--reset_ub</code>), vswap mechanism will be used by the kernel for this CT. | Now your config is vswap enabled, and when you (re)start it (or use <code>--reset_ub</code>), vswap mechanism will be used by the kernel for this CT. |