Hi,
i've been experimenting with an older test setup cluster before i make the move from VMware.
I noticed when stressing a host with memory hungry VM's that:
-Starting a 2nd VM that exceeds free MEM on the host makes the host crash and reboot (did that on purpose)
-Using ballooning, linux clients profit more from this feature than windows, but if 1 starts using it, the host may become in danger and may reboot.
A possible solution is to disable ballooning in the client on huge VM's. 8 or 16+GB
Is there an easier way to get a grip on this?
Regards,
Martijn
i've been experimenting with an older test setup cluster before i make the move from VMware.
I noticed when stressing a host with memory hungry VM's that:
-Starting a 2nd VM that exceeds free MEM on the host makes the host crash and reboot (did that on purpose)
-Using ballooning, linux clients profit more from this feature than windows, but if 1 starts using it, the host may become in danger and may reboot.
A possible solution is to disable ballooning in the client on huge VM's. 8 or 16+GB
Is there an easier way to get a grip on this?
Regards,
Martijn
Last edited: