What do you want to know about "Viridian" / Windows Server virtualization?

To go along with all of the wonderful blog posts that we’ve been clogging the Intarwebs with this week, some of the other virtualization bloggers here at Microsoft and I are planning to start creating podcasts.  We’ve got some ideas on the type of content we want to provide in the podcast, but we’re also interested in what *you* want, since – after all – we’re making this for you, dear reader.

So, what do you want to know?

  • Would you like to meet some of our team members? 
  • Would you like to hear from people working on Microsoft’s other virtualization technologies (SoftGrid, SCVMM, Virtual PC, Virtual Server, etc)?
  • Would you like to hear about the fishing trip I took last weekend?
    Please, leave a comment and let us know!

Also, one of the things that we want to do in each podcast is answer questions from our users and community.  If you have questions about "Viridian" / Windows Server virtualization, or any of Microsoft’s other virtualization offerings, please leave your question in the comment section, and we’ll pick some questions to answer each time.

Comments (6)

  1. Aitor Ibarra says:

    Yes, Yes, No (unless something exciting happened – like how you narrowly avoided becoming a Great White’s lunch)

    WRT to Virtual PC and Virtual Server – any news on these will be appreciated. With Viridian you made the sensible choice of requiring AMD-V / Intel VT cpu enhancements, but that means that older hardware, and even not so old (like my Opteron 275 workstation with 8GB RAM) can’t run it, so Virtual PC / Virtual Server are still relevant for a lot of people.

    I don’t expect much development of Virtual Server, which with VRMC+ and SCVMM is about as good as it can get without radical changes that would overlap with WSV (64bit guests, >3.6GB RAM per guest etc).

    However I imagine Virtual PC still has a future going forward (unless you also introduce Viridian to Vista x64 – why not?).

    But obviously the main focus is going to be Viridian. It’s great that you’ve made it available to a much wider audience, and that MS insiders are blogging about it, but it would be great to see:

    – more documentation – esp docs on the WMI API. Would be really cool to see some powershell examples

    – general performance guidelines (I know you are still tweaking stuff, but you should have a pretty good idea, e.g. local VHD vs iSCSI volume)

    – security. I’ve seen some stuff on the benefits of your thin hypervisor approach re security; and I imagine that security is up there with bug fixes, reliability and performance as a reason that you need another 8 months before RTM – it would be good to read more about what you’ve done here and also see some operational best practices, with a comparison with the VS2005R2 way of doing things (e.g. restricting access to VMs via NTFS)

    – some idea about whether feedback you get now has a chance of making a difference to the RTM, considering that you’re pretty much feature complete!



  2. Adam says:

    Hi – I’m wondering if there’s any way to control server 2008’s virtual machines directly from windows XP right now?

  3. DannyC says:

    Definitely the SoftGrid/SCVMM side of things for me..

  4. Aitor Ibarra says:


    You can control VM remotely just like you would do a physical machine; e.g. enable remote desktop in a Windows VM and then use the Remote Desktop client from XP to control it. I’m doing exactly this to test Viridian; I can connect to both the Windows Server 2008 physical machine and any virtual machines running on top of it this way. The VMs must be connected to the same network as your XP box; or you can just RDP to Windows 2008 and control any VMs not connected to your network from there.

  5. Some of you may remember that, a long while ago, I asked what sort of things you’d like to see in a Virtualization-themed