My hypervisor is running out of memory, VMs crash or fail to start.
Memory pressure comes from overprovisioning, a memory leak in a VM, or a forgotten 16 GB allocation to a test box. Measure first, clean up, then consider buying hardware.
Try this first
- 1Check hypervisor view: Hyper-V via Performance Monitor (Hyper-V Dynamic Memory Balancer), VMware via vCenter, host, Performance, Memory.
- 2Per VM: is Dynamic Memory or memory ballooning enabled, and sized correctly? A SQL server should not balloon, a file server can.
- 3Find the top three consumers, verify they actually use the memory (Task Manager / free -h inside the VM) or just have an oversized assignment.
- 4Reduce where you can: ordinary office VMs rarely need more than 4 to 8 GB, terminal servers scale with user count. Let a SQL server only get what it really uses.
- 5After re-checking, plan a hardware upgrade if needed: extra DIMMs are usually cheaper than a new host, provided motherboard slots are free.
When to bring us in
Memory ballooning in production databases is serious: SQL/Oracle want to hold memory. Reduce overcommit or expand to a second host.
See also
- One DC or two DCs for an SMB office?Two is almost always the right answer; one DC is a single point of failure for logon, DNS and GPOs.
- Should I split FSMO roles across two DCs?For a small domain all on one DC is fine; with two DCs splitting is tidier but not required.
- How do I know my AD replication is healthy?Replication errors creep in silently; they only surface when logins or GPOs misbehave.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.