diff options
| author | rebortg <github@ghlr.de> | 2020-11-29 19:24:16 +0100 |
|---|---|---|
| committer | rebortg <github@ghlr.de> | 2020-11-29 19:24:16 +0100 |
| commit | a6c226d4b4e79c07121b0a609d2fb78cae70f3b0 (patch) | |
| tree | db8458fb85776d482c14038498264aa4140a0762 /docs/installation/virtual/vmware.rst | |
| parent | 371bf8185f3cd0628969a8603aa92503b2fc3853 (diff) | |
| download | vyos-documentation-a6c226d4b4e79c07121b0a609d2fb78cae70f3b0.tar.gz vyos-documentation-a6c226d4b4e79c07121b0a609d2fb78cae70f3b0.zip | |
arange installation and image management
Diffstat (limited to 'docs/installation/virtual/vmware.rst')
| -rw-r--r-- | docs/installation/virtual/vmware.rst | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/docs/installation/virtual/vmware.rst b/docs/installation/virtual/vmware.rst new file mode 100644 index 00000000..c4299cbf --- /dev/null +++ b/docs/installation/virtual/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 artificial 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
+
|