Hyper-V Program Manager
While I did not realize it - my presentation on Dynamic Memory at TechEd US 2010 this week was recorded - and is now available for all to see:
Which means that everyone can see how my demo went off the tracks for a moment! (sigh). Apart from that - there is lots of good information about dynamic memory in there. You can also download a copy for offline viewing from the official TechEd site here: http://www.msteched.com/2010/NorthAmerica/VIR304
Finally, I should also say thanks to Matt McSpirit - aka virtualboy - for alerting me to the existence of this video.
Great Presentation Ben. Really enjoyed it. Looking forward to testing Dynamic Memory when SP1 arrives.
PS: I've been a regular reader of your Blog and have been a fan sinse I first watched your Channel 9 Intervew, back in April 2005! :
really enjoyed your presentation - cant wait to implement dynamic memory! great story regarding vmware current memory mgmt techniques and memory doubler from the days of old!
I attended your presentation last week. But I had no idea you were the guy from "Virtual PC guy's blog". I end up on your blog quite often when I google for a question. The presentation gave me a good insight into Dynamic memory and I think you did a great job engineering this. It mainly took away the misunderstanding regarding dynamic memory vs VMWare's memory overcommitment. Hopefully it will work as good as it was presentation during your talk. ;-) Looking forward to test it anyway. I have been looking for you for a while aferwards to discuss something about it but didn't find you around the TLC.
I'm watching your presentation after just finishing the "Windows Server 2008 R2 SP1" presentation and there's some conflicting information with regard to Dynamic Memory that I hoped you could clarify for me.
In your presentation, you mentioned that "Startup memory" is essentially the minimum memory that Hyper-V will allocate and that it will not reduce the memory below that setting. The SP1 talk says that this is simply the amount of memory given at startup and that if there is memory contention and the VM is not using the memory, it can be reduced below the "Startup memory" figure and that this was the reason the setting is called "Startup memory" rather than "Minimum memory".
Also in your presentation, the memory buffer slider is said to be the percentage of memory to keep available based on how much memory is currently in use (which makes sense to me based on the UI setting's text mentioning of workload). However, the SP1 presentation says that this percentage is multiplied by the "Startup memory" and that is how much memory is kept available.
Great presentation. Thanks for sharing the info in advance! One question. Are there any constraints on processors that will support Dynamic Memory? Does it require SLAT or do SLAT processors tend to get better back channel performance?