You run out of space to create them (who has 512GB or more free space to write that dump to?) and it is problematic and time consuming to copy such files and upload them for analysis. The size of these memory dumps becomes problematically large on hosts with large amounts of memory. This contains the processor state and the content of what’s in memory at the time of the crash. To trouble shoot issues with a Hyper-V host support engineers often request a complete memory dump. The N+X nature of clusters means that even more RAM is provisioned as we need to allow for the hosts to serve extra virtual machines during scheduled or unscheduled maintenance. The second reason is that ever more high performance workloads that are resource intensive are being virtualized. In general, virtual machine density increases as the servers become ever more capable and affordable. 256GB to 1TB of RAM is not an exception anymore. Hyper-V clusters tend to exist out of multiple hosts with high amounts of RAM. But this is the poster child environment where this setting will make a significant impact when collecting MEMORY.DMP files trouble shooting. The new option – “Active Memory Dump” – to configure a memory dump is not strictly related to failover clustering or Hyper-V. In Windows Server 2016 we have a new option when it comes to creating memory dumps when a system failure occurs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |