This configuration is used by the daily cron task /etc/cron.daily/logrotate.

The configuration is located in /etc/nf the /etc/logrotate.d directory is included by this file for additional rules (for example for specific packages after RPM installation like xha, blktap, SMlog.). Logrotate is the tool to administrate the rotation, compression, removal. Avoid modifying them and ask for advice if you have a use case that appears to require such modifications.

There is no need to re-enable the host: it is done automatically when it starts.Īny manual modification to the configuration files described below may prevent future XCP-ng updates to update the contents of those files. (After a reboot or host startup) Move VMs back to the host if appropriate.

If you prefer to do it from command line, this is equivalent to: xe host-disable host=. This will disable the host, then evacuate its VMs automatically to other hosts. * Put the host into maintenance mode from Xen Orchestra. If all your VMs are 'agile', that is, they're not tied to local storage or local devices (device pass-through), and if there are enough resources on other hosts in the pool, the above can be simplified as: Alternatively, you can also disable HA on the pool for the duration of the maintenance operations to avoid issues caused by HA. You don't want the other hosts to believe that a host crashed or self-fenced - and take consecutive action - when it's actually planned maintenance. Step 1 is especially important if High Availability is enforced on your pool.

Virtualbox vs vmware .pdf