Hyper-V Program Manager
Over on the virtualization team blog we have just posted a link to the first public demo of some of the new features coming in Hyper-V in “Windows Server 8”. Some of the features that were demonstrated included:
You can see the demo for yourself by going here and jumping to ~37:30.
I am sure that many of you will have lots of questions for me – but unfortunately I cannot say anything more than what is covered in the demo. So please be patient while we wait for more information to come out.
Is it just me, or is it annoying when these new technologies are introduced at WPC? Most of the time the people that go to WPC are the business types, not the techies types. At least that's my impression based on who my company sends.
On the other hand, Build is looking especially appealing.
Probably more details will be reveiled at the BUILD on September. It's not bad that biz people get to know with W8 earlier than techies.
does the replication work when you have a pass-through-disk in you vm?
I cannot (am not allowed to) talk about anything that was not shown in the demo video.
why a limit at all? whats the reason behind that? i could understand to distinguish the different editions, like say standard has a limit, datacenter no limit, but its pretty annoying to be told by your os how you are supposed to use your computer. if i have a westmere system with 40 cores, and want a sql server with 32 cores on it and a report server with 6, the gui says no, one can accomplish it technically with xml config file hack, but why this restriction at all (question is valid for hyper-v 2 already, if you feel like commenting on the old edition ;) )
forgot in my previous post, i am going on about vCore limit, never mentioned that explicit beside the example
wooooooow, a great addition to a great product.
I think that there is a place to add even the ability of Live VHD migration to another disk storage like VMWare has the VMotion disk accross storage arrays.
I don't work for MSFT, but they have always been careful to point out that when MSFT says that something is "supported" it means that they have tested it, validated correct function, and that they will provide technical support when you call them. They have been especially adamant on this point when it comes to Hyper-V and scalability (at least at the sessions I have attended), usually saying "going bigger will most likely work, but we haven't tested it and won't support it if you run into problems."
Part of the issue is that there hasn't been a great deal of demand for VMs above a certain size because the hardware to support it hasn't been widely available, ergo testing hasn't been extended that far and best practices for those situations haven't been defined. But as technology changes MSFT has been good about expanding their supported limits with each new release (with R2, with R2 SP1, etc), and it seems like the trend will continue with the next release supporting 16+ vCPUs. Personally, I would be shocked if they didn't meet (or more likely exceed) the 32 vCPU limit that VMware announced recently.