diff options
| author | SquirePug <42793435+SquirePug@users.noreply.github.com> | 2019-09-25 12:08:43 +1000 |
|---|---|---|
| committer | Daniil Baturin <daniil@baturin.org> | 2019-09-25 09:08:43 +0700 |
| commit | b6ffe890003bcaab1dcb0eaefcb6762d0069f1ac (patch) | |
| tree | 4e9213c5146792eb953b73fb255e93a644b7731e /docs/appendix | |
| parent | 8ead8165512f76ed32431cfc224f8e5d392c51c8 (diff) | |
| download | vyos-documentation-b6ffe890003bcaab1dcb0eaefcb6762d0069f1ac.tar.gz vyos-documentation-b6ffe890003bcaab1dcb0eaefcb6762d0069f1ac.zip | |
Added vyos on vmware page and rudimentary structure. (#118)
* feature: adding notes for running on vmware around contending memory and memory management in low memory situations
Diffstat (limited to 'docs/appendix')
| -rw-r--r-- | docs/appendix/vyos-on-vmware.rst | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/docs/appendix/vyos-on-vmware.rst b/docs/appendix/vyos-on-vmware.rst new file mode 100644 index 00000000..6feb95ba --- /dev/null +++ b/docs/appendix/vyos-on-vmware.rst @@ -0,0 +1,32 @@ +.. _vyosonvmware:
+
+Running on VMWare ESXi
+######################
+
+ESXi 5.5 or later
+*****************
+
+.ova files are available for supporting users, and a VyOS can also be stood up using a generic Linux instance, and attaching the bootable ISO file and installing from the ISO
+using the normal process around `install image`.
+
+.. NOTE:: There have been previous documented issues with GRE/IPSEC tunneling using the E1000 adapter on the VyOS guest, and use of the VMXNET3 has been advised.
+
+Memory Contention Considerations
+--------------------------------
+When the underlying ESXi host is approaching ~92% memory utilisation it will start the balloon process in s a 'soft' state to start reclaiming memory from guest operating systems.
+This causes an artifical pressure using the vmmemctl driver on memory usage on the virtual guest. As VyOS by default does not have a swap file, this vmmemctl pressure is unable to
+force processes to move in memory data to the paging file, and blindly consumes memory forcing the virtual guest into a low memory state with no way to escape. The balloon can expand to 65% of
+guest allocated memory, so a VyOS guest running >35% of memory usage, can encounter an out of memory situation, and trigger the kernel oom_kill process. At this point a weighted
+lottery favouring memory hungry processes will be run with the unlucky winner being terminated by the kernel.
+
+It is advised that VyOS routers are configured in a resource group with adequate memory reservations so that ballooning is not inflicted on virtual VyOS guests.
+
+
+
+
+
+References
+----------
+
+https://muralidba.blogspot.com/2018/03/how-does-linux-out-of-memory-oom-killer.html
+
|