In mid March Microsoft officially announced the upcoming introduction of Dynamic Memory for Hyper-V, a feature for memory overcommit that will arrive as part of the Windows Server 2008 R2 Service Pack 1.
Early information about how Dynamic Memory works were published a couple of weeks ago by a company evangelist but promptly removed.
Microsoft is receiving heavy criticism from VMware supporters about Dynamic Memory after downplaying the value of VMware overcommit techniques for years. So it is trying to be as careful and detailed as possible in explaining its approach to memory management in virtualization.
To do so Jeff Woolsey, Lead Program Manager, Windows Virtualization, is publishing on the corporate blog a series of very long posts that aims at explaining the different approach between Microsoft and VMware to memory overcommit.
The most relevant piece to date is the one appeared yesterday, where he talks about page sharing, one of the techniques used by VMware.








