Change settings gives quota-error when unlimited container created

[GoogleCodeExporter]

Steps to reproduce:
1. create new virtual server using the unlimited template
2. after creation try to change settings
3. an error is shown, as the vzctl set command fails with a quota error

Actual result:
An error is shown due to vzctl set command failing due to missing quota 
(unlimited = no quota)

Expected result:
Settings like nameserver etc. should be updateable even if no quota is used 
and/or unlimited is chosen (maybe differentiate vzctl set switches?)

Version of the product:
2.1

Server OS:
CentOS 6.3 x86_64 (have tried with Fedora also) with:
kernel 2.6.32-042stab057.1
vzctl version 3.3
Vzquota version 2.5.0 (I have tried with the newer version also, it does not 
matter as it looks like a syntax/switch error)

Browser:
Chrome, Firefox (doe not matter)

Additional information:
This should be fixable by modifying the vzctl set switches used.

Original issue reported on code.google.com by bill...@incubatec.com on 17 Jul 2012 at 9:01

[GoogleCodeExporter]

I've been having the same issue.  Most of my containers run on dedicated 
partitions, with quota disabled.  Setting the value to a size larger than the 
dedicated partition is a possible workaround, but only if the container is 
stopped before trying to make the changes.

Original comment by dball...@gmail.com on 8 Aug 2013 at 12:13