...
The next Hypervisor release 1.03 will remove the need to upgrade the Kernel, Xen and so forth, as all these Versions don't differ in the crash behaviour. It will disable swap, overcommitting and enable the noop I/O scheduler. These steps should finaly stabilize the hypervisor and make it also ready for kernel upgrades.
Is there a Workaround ?
Yes you can manually make above changes to your existing Hypervisor installation until the 1.03 will be released. First of all you need to create a root password (Management→Hypervisor Settings, change root pw). Then you can login with root into the Hypervisor via the console or via SSH.
Disabling Swap
To disable the swap permanently you need to edit the file /etc/fstab and put a # before the swap line, it should finaly look like:
| Code Block |
|---|
#/dev/sda2 swap swap defaults 0 0 |
Enable NOOP I/O Scheduler
You need to edit the file: /boot/extlinux.cfg and modify the Kernel Parameter, the option "elevator=noop" should be added. The line should look like:
| Code Block |
|---|
APPEND xen.gz dom0_mem=1024M --- vmlinuz-grsec root=UUID=f75fac6a-cf4d-48bd-89c5-5a9fffd0e23f modules=sd-mod,usb-storage,ext4 elevator=noop quiet --- initramfs-grsec |
Disable Memory Overcommiting
To disable memory overcommitting a sysctl-file should be created. We call it /etc/sysctl.d/01-overcommit.conf and fill it with the line:
| Code Block |
|---|
vm.overcommit_memory=2 |
2017-01-10 Current Hypervisor State is BETA
...