Can't set VSwap size when creating new package in SolusVM It doesn't appear to be possible to define a vswap size when creating a new package in solusvm for openvz virtual machines and we have been manually creating a small vswap for each container after being automatically provisioned by the solusvmpro whmcs module. ++++++++++++++ If You want to buy cheap web hosting then visit http://Listfreetop.pw and select the cheapest hosting. it can be suitable for all your needs. Top 200 best traffic exchange sites http://Listfreetop.pw/surf list of top gpt sites list of top ptc sites list of top ptp sites list of top crypto currency Wallets sites Listfreetop.pw Listfreetop.pw Listfreetop.pw +++++++++++++++ Has anybody found a way to automate the creation of a vswap without making any modifications to solusvm? You can enable it on visiting the Node list -> Click on Edit the Node you would like to make change -> http://prntscr.com/lywyp1 After setting this option the vswap appears to be calculated from the amount of burst memory. If I specify 1024MB burstable RAM and 512MB dedicated RAM in the package template a 512 MB (1024MB - 512MB = 512MB) vswap is created. I'm not sure why it's calculated this way but it's working for now. The vSwap is calculated as the difference between the actual ram you assign to a container subtracted from the amount of burst memory you assign it. A positive number creates vSwap to account for the difference. As far as iopts on a physical drive as a result of virtual memory manipulation . The below calculation will help to understand clearly. Guaranteed memory = barrier of vmguarpages / 1024 * 4 Burstable memory = privvmpages / 1024 x 4 Current Memory Usage = physpages held value /1024 * 4 Current Usage (RAM + SWAP) = oomguarpages held value /1024 * 4 It doesn't appear to be possible to define a vswap size when creating a new package in solusvm for openvz virtual machines and we have been manually creating a small vswap for each container after being automatically provisioned by the solusvmpro whmcs module. Has anybody found a way to automate the creation of a vswap without making any modifications to solusvm? SolusVM KVM/OpenVZ templates have a tendency to not set up swap correctly. You have to enter by SSH and create the swap partition again. swapoff /dev/vda2 mkswap /dev/vda2 swapon /dev/vda2 You may have to change the size of your exchange with the GParted ISO available in SolusVM. digiproducts.com volcanohits.com echostage domain ownership history darmowy hosting forum mybb witcher 3 make money early domaine j laurens brut cyberhostpro.com domain realty rdr2 how to make money 6 ways to make money online homestay host forum wcex.co