How to adjust paging file for hyper‑V host stability

LD Lissandra 20 Reputation points
2026-09-03T09:27:57.8166667+00:00

Could you explain how to handle a situation where Hyper‑V fails to place running VMs into a saved state during automated host shutdown because of limited disk resources?

What is the best way to calculate paging file requirements for dense virtualization nodes, and how can we adjust allocations to ensure stability?

And i’d like to know the practical steps for configuring the system paging file so that shutdowns complete smoothly without VM state loss.

Windows for business | Windows 365 Enterprise
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jason Nguyen Tran 25,120 Reputation points Independent Advisor
    2026-09-03T10:53:32.76+00:00

    Hi LD Lissandra

    The paging file plays a critical role here, since Hyper‑V relies on it to temporarily store VM memory when transitioning to a saved state.

    As a rule of thumb, the paging file should be at least the size of the largest VM’s memory allocation, plus additional overhead for host operations. On dense virtualization nodes, many admins size the paging file to match total physical RAM or slightly above, ensuring enough space to capture multiple VM states at once. You can calculate requirements by reviewing the sum of active VM memory and factoring in 10–20% extra for host processes.

    To adjust allocations, go to System Properties > Advanced > Performance Settings > Advanced > Virtual Memory and configure the paging file on a volume with sufficient free space. It’s best to place the paging file on a fast local disk rather than the system drive if space is constrained. Set both the initial and maximum size to the calculated requirement so the file doesn’t need to expand dynamically during shutdown.

    After configuration, test an automated shutdown to confirm that VMs transition smoothly into saved state. Monitoring Event Viewer for Hyper‑V‑VMMS logs will also help validate that paging file adjustments resolved the issue.

    I hope the response provided some helpful insight. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.

    Jason.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-09-03T09:28:23.3033333+00:00

    For Hyper-V hosts, the recommended baseline is to let Windows manage the host page file size automatically. That is the documented recommendation after installing the Hyper-V role.

    For dense virtualization hosts, page file sizing is not based on a single fixed formula. It depends on installed RAM and workload commit demand. A common starting point in Windows is about 1.5 × installed RAM when no better workload-specific data is available, but on server systems the better goal is to have enough physical RAM so the page file is not heavily relied on.

    For Hyper-V-specific stability:

    1. Leave the host page file system-managed unless there is a measured reason to change it.
      • Hyper-V documentation recommends allowing the system to manage page file size.
      • This is the safest default for shutdown and memory-pressure scenarios.
    2. Measure actual host memory headroom before changing anything.
      • In Performance Monitor, check Hyper-V Dynamic Memory Balancer – Available Memory.
      • If this value is consistently low, the host is under memory pressure and page file changes alone will not fully solve stability issues.
    3. Check whether the VMs themselves are under memory pressure. Inside Windows guests, use these counters:
      • Memory – Standby Cache Reserve Bytes
      • Memory – Free & Zero Page List Bytes
      • Memory – Pages Input/Sec Suggested thresholds from Microsoft:
      • Standby Cache Reserve Bytes + Free & Zero Page List Bytes should be 200 MB or more on systems with 1 GB RAM.
      • The same combined value should be 300 MB or more on systems with 2 GB or more RAM.
      • Pages Input/Sec average over 1 hour should be less than 10. If these are poor, increase VM memory sizing rather than relying on paging.
    4. Use Dynamic Memory where appropriate. Hyper-V can adjust VM memory dynamically using startup, minimum, and maximum values.
      • If a VM has sudden large memory allocations, increasing the guest VM page file size can provide temporary backing while Dynamic Memory responds.
      • For restart scenarios, Hyper-V can use Smart Paging only temporarily and only under specific conditions, mainly when a VM is being restarted and there is no available physical memory.
      • Smart Paging is not the normal mechanism for general host memory oversubscription.
    5. Monitor paging behavior instead of sizing blindly. Useful counters include:
      • \Memory\Page/sec
      • \Memory\Page Reads/sec
      • \Memory\Page Inputs/sec
      • \Memory\Page Writes/sec
      • \Memory\Page Output/sec
      • \Paging File(*)% Usage Sustained high hard page fault rates indicate disk activity that can contribute to poor performance. Correlate these counters with disk performance on the volume hosting the page file.

    Practical configuration steps for the host page file:

    1. Open System Properties.
    2. Select Advanced.
    3. Under Performance, select Settings.
    4. Open the Advanced tab.
    5. Under virtual memory, configure the page file.
    6. Prefer automatic/system-managed sizing for the Hyper-V host.

    If a manual size must be used:

    • Start from workload measurement, not guesswork.
    • Use the Windows guidance of 1.5 × RAM as an initial baseline only when no better data exists.
    • Validate with Performance Monitor after the change.
    • Be aware that undersizing the page file can reduce stability under memory pressure, while oversizing mainly consumes disk space.

    For the shutdown problem described, the most practical approach is:

    • Ensure the host has sufficient free disk space on the volume used for paging.
    • Keep the host page file system-managed unless monitoring proves a different size is required.
    • Verify host available memory with Hyper-V Dynamic Memory Balancer – Available Memory.
    • Reduce VM memory pressure by correcting VM sizing or Dynamic Memory settings if guests are paging heavily.

    This combination is the supported path to improve shutdown reliability and reduce the chance of failures caused by memory and disk pressure.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.