VE-Reconfig

The <ve-reconfig> element is used to specify which server configuration parameters can be modified in various scenarios.

    <ve-reconfig>
        <VM>
            <linux>
                <ram can-decrease-when-started="true" can-increase-when-started="true"/>
                <cpu-number can-change-when-started="true"/>
                <cpu-freq can-change-when-started="true"/>
                <bandwidth can-change-when-started="true"/>
                <disk-size can-change-when-started="false"/>
                <disk-type can-change-when-started="false"/>
                <node can-change-when-started="true"/>
            </linux>
            <windows>
                <ram can-decrease-when-started="true" can-increase-when-started="true"/>
                <cpu can-change-when-started="true"/>
                <bandwidth can-change-when-started="true"/>
                <disk-size can-change-when-started="false"/>
                <disk-type can-change-when-started="false"/>
                <node can-change-when-started="true"/>
            </windows>
        </VM>
        <CT>
            <linux>
                <ram can-decrease-when-started="true" can-increase-when-started="true"/>
                <cpu-number can-change-when-started="true" />
                <cpu-freq can-change-when-started="false" />
                <bandwidth can-change-when-started="true"/>
                <disk-size can-change-when-started="true"/>
                <disk-type can-change-when-started="false"/>
                <node can-change-when-started="true"/>
            </linux>
            <windows>
                <ram can-decrease-when-started="true" can-increase-when-started="true"/>
                <cpu can-change-when-started="true"/>
                <bandwidth can-change-when-started="true"/>
                <disk-size can-change-when-started="false" can-decrease="true"/>
                <disk-type can-change-when-started="false"/>
                <node can-change-when-started="false"/>
            </windows>
        </CT>
    </ve-reconfig>
    <ve-reconfig-pcs6>
        <VM>
            <linux>
                <ram can-decrease-when-started="false" />
            </linux>
            <windows>
                <ram can-decrease-when-started="false" can-increase-when-started="true"/>
            </windows>
        </VM>
    </ve-reconfig-pcs6>
    <ve-reconfig-vz7>
        <CT>

            <linux>
                <cpu-freq can-change-when-started="false"/>
            </linux>
            <windows>
                <cpu-freq can-change-when-started="false"/>
            </windows>
        </CT>
        <VM>
            <linux>
                <ram can-decrease-when-started="false" />
            </linux>
        </VM>
    </ve-reconfig-vz7>

<ve-reconfig>...</ve-reconfig> is a general section from which the settings are applied.

If you want to redefine a particular setting for a particular virtualization technology (Virtuozzo 6, Virtuozzo 7, OpenVZ7), then you should redefine it in the respective section:

For Virtuozzo 6 – <ve-reconfig-pcs6>...</ve-reconfig-pcs6>
For Virtuozzo 7 – <ve-reconfig-vz7>...</ve-reconfig-vz7>
For OpenVZ 7 – <ve-reconfig-ovz7>...</ve-reconfig-ovz7>

The parameters are specified separately for the available virtual server types (<VM> – virtual machine; <CT> – container) and the operating system types (<linux>, <windows>).

<ram> element

RAM size changes.

<cpu> element

CPU changes.

<bandwidth> element

Network bandwidth changes.

<disk-size> element

Hard disk size changes.

<disk-type> element

Hard disk type changes.

<node> element

Live server migration between hardware nodes.

Each element can be assigned a value using the attributes listed below (all attributes are of type boolean). Please note that the default value for all attributes is "true". This means that you only have to include an attribute and specify its value if you want to set it to "false":

can-change-when-started

The corresponding configuration parameter can be changed (increased or decreased) when a server is started. You can use this parameter for CPU/RAM hot plugging functionality. If the value of this parameter is true, the hotplug functionality is enabled. Be aware that not all guest operating systems support RAM/CPU hot plugging functionality, for more information refer to https://kb.cloudblue.com/114970.

can-change-when-stopped

The corresponding configuration parameter can be changed (increased or decreased) when a server is stopped.

can-decrease

The corresponding configuration parameter can be decreased.

can-increase

The corresponding configuration parameter can be increased.

can-increase-when-started

The corresponding configuration parameter can be increased when a server is started.

can-increase-when-stopped

The corresponding configuration parameter can be increased when a server is stopped.

can-decrease-when-started

The corresponding configuration parameter can be decreased when a server is started.

can-decrease-when-stopped

The corresponding configuration parameter can be decreased when a server is stopped.

When modifying the XML configuration file, you should include only those attributes that prohibit a particular (desired) change. For example, if you want to allow changes to a configuration parameter except decreasing it when a server is started, you should include only the can-decrease-when-started attribute and set its value to "false".