Hyper-V Program Manager
While this will not surprise my regular readers – some of you will be interested to know that blogging is usually only a very small fraction of my job. My official title is “Program Manager Lead” which means that my responsibilities roughly break down into the following buckets:
As you can see – that is a lot of “non-blogging work”. The truth is that I started out blogging mainly as a way to ensure that I used my own software on a regular basis – but it has come to be something that I really enjoy doing. Most of my blogging is actually done after hours (and often on a Sunday afternoon). The average blog post takes ~1 hour to write (I have a strict policy of only blogging about things that I have personally done, so that I know that there will not be errors in my information) and I aim to have 5 blogs each week (though I often fall short of this goal).
One of the interesting side effects of blogging, for me, has been that it has helped with getting to know my customers. These days I get so much feedback from you all that there is no way for me to keep up with responses. So while I apologize to everyone who has emailed me through the blog, and has not heard back – know that I do read every email, and I respond when I can. All of this information gives me a very good indication of what is going on out there.
With all of that aside – back to the topic at hand “Welcome to blog week!”
Thanks to a combination of having just got back from TechEd China (lots of fun – but now I am quite jetlagged) and being without an office (due to my current office being moved to a new building) I have arranged to cancel most of my meetings / responsibilities for this week – and just focus on the blog. I have a number of activities planned for this week. In no particular order they include:
Now I have some questions for you:
So as not to spam my own blog, I will be posting status updates on what I am working on to Twitter.
I would be interested in a blog post revealing the command line parameters for VMWindow.exe in Windows Virtual PC.
I would like to see recommendations, if any, for placing multi vCPU VM's on a host. Especially with regards to overcommit (more vCPU's than lCPU's) and mixing single vCPU VM's with multi vCPU VM's on the same host.
How does Hyper-V handle multi vCPU VM's?
Maybe details on how the scheduler works. Mappings of vCPU's to lCPU's.