Skip to main content

Hyper-V and reserving RAM for the host/root/parent partition

After a long process, I finally have a real-world calculation for determining how much RAM to reserve for a Hyper-V host. The question/answer about it is here. But the summary is that Hyper-V loses RAM to the Nonpaged pool (and all of it is "untagged") in addition to the "standard" stuff that Microsoft has documented.

Be aware that I write MB/GB here, when I actually mean MiB/GiB. I feel it will be more intuitive to see the notation that Windows (incorrectly) uses.

Host Overhead
  1. 300 MB for the Hypervisor services
  2. 512 MB for the Host OS (This is a recommended amount; you have some wiggle-room with this.)
  3. [The amount of physical RAM available to the host OS] multiplied by 0.0425 (result in GB) for the Nonpaged pool (Which means multiply that by 1024 to convert to "MB")
Per-VM Overhead
  1. 24 MB for the VM
  2. 8 MB for each 1 GB of RAM allocated to the VM.

Examples


12 GB RAM, 1 VM @2 GB, 1 VM @4 GB
  • Host: 812 + (0.0425 * 12 * 1024) = 1,334.24 MB
  • VM1: 24 + (2 * 8) = 40 MB
  • VM2: 24 + (4 * 8) = 56 MB
  • Total:  1430.24 MB (~1.4 GB)
24 GB RAM, 2 VM @8 GB, 1 VM @ 4 GB
  • Host: 812 + (0.0425 * 24 * 1024) = 1856.48 MB
  • VM1: 24 + (8 * 8) = 88 MB
  • VM2: 24 + (8 * 8) = 88 MB
  • VM3: 24 + (4 * 8) = 56 MB
  • Total: 2088.48 MB (~2.04 GB)
36 GB RAM, 1 VM @24 GB
  1. Host: 812 + (0.0425 * 36 * 1024) = 2,378.72 MB
  2. VM1: 24 + (24 * 8) = 216 MB
  3. Total: 2,594.72 (~2.53 GB)
You can see why most people just say "2GB for the host" and stop there. Essentially, you can get away with 2 GB until you get up to a 24 GB server. But after that you have to start caring more about the amount of RAM lost to the Nonpaged pool.

Comments

Post a Comment

Popular posts from this blog

Live Migration between domains

For those of you like me who aren't experts at all things Active Directory (AD) and Hyper-V Live Migration (LM) permissions, it can be enough of a pain to LM a Virtual Machine (VM) between domains that you simply decide to take the VMs offline to affect the move. See, I only tolerate AD because it's required for LM'ing VMs; there isn't a choice. (It's also required for Windows Clusters, but that's a different topic.) But I figured it out. My back-story is that we setup a cluster using Windows 2012 r1 as the AD Domain Controller (DC) and Hyper-V Server 2012 r1 for the VM hosts. Then we decided we wanted to use r2 for the AD DC and Hyper-V hosts. Upgrading Hyper-V was easy. But I found that there's some unresolved Microsoft bug with Windows Clustering when upgrading the AD DC from Windows 2012 r1 to Windows 2012 r2--- clustering simply doesn't work correctly anymore . So we gave up and created a from-scratch Windows 2012 r2 AD DC then made a new cluster
Post a Comment
Read more

SqlBulkCopy and the "colid" error

I thought there was a page explaining this somewhere out there on the Internet, but I can't find it anymore. So here's what I re-discovered. When you try to insert the rows from a DataTable and the data in one of the columns of one of the rows is too big to fit into the destination column in the database, you get a SqlException with this error message: "Received an invalid column length from the bcp client for colid N." (Where "N" is a number.) It doesn't tell you which row, and it's a pain to figure out what column to look at. To determine what column it is referring to, you first need to get a listing of all columns in the table, listed in the order as they have been defined in the database. Next, you remove any columns in the list that are not represented in SqlBulkCopy.ColumnMappings (the order of the column mappings is irrelevant). The list that remains is what "colid" is referring to, with the first column corresponding to colid &
Post a Comment
Read more