Hyper-V Program Manager
In case you missed it - Hyper-V RC1 is now available for download.
Full details can be found here: http://blogs.technet.com/virtualization/archive/2008/05/20/hyper-v-rc1-release-available-on-microsoft-download-center.aspx
And the release notes are available here: http://www.microsoft.com/downloads/details.aspx?FamilyID=3ed582f0-f844-40ba-b692-230845af1149&displaylang=en
Any chance on some upgrade steps/guidance for folks that have rc0 installed and lots of VM with lots of RC0 integration components, pretty please :)
Ben, Maybe you could clear up a question that I have. All of the product lit for Win2008 has flavors with and without Hyper-V for both 64 and x86 versions. If Hyper-V is only for x64 versions, why does MS market x86 versions with and without? I find this totally confusing! Or is it that the beta / RC1 is only for x64 and the RTM will support x86? Thanks much.
I upgraded to RC1 and when I did I noticed that my virtual now only has one processor when before it had two. Under settings it still has 2 virtual processors selected.
Is there something else I need to do? I installed the integration services via the new disk feature. Do I also need to apply the patch to the virtual?
Andrew: there wont be a x86 version of hyper-V, Hyper-V requires VT technology and no execute om memory, all of these are features not found in x86 processors
I hear you on not having an x86 version and understand why, but MS should remove all the lit and downloads (MSDN) of x86 Win2008 with and without Hyper-V
There quite a few of us having problems with Hyper V and Dell servers:
Hyper-V: Installation succeeded with errors
<Error>: Attempt to configure Hyper-V failed with error code 0x80041001. Configuring the virtual network for Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) #2 failed. Please attempt to configure the virtual network again using Hyper-V Manager.
<Informational>: This is a pre-release version of Hyper-V. <a href="http://go.microsoft.com/fwlink/?LinkId=48557">Go to the Hyper-V TechCenter for more information.</a>
<Informational>: Hyper-V is installed, but additional steps are required to begin running server workloads on virtual machines. To add virtual machines, use the new virtual machine wizard by opening the Hyper-V role homepage in Server Manager
I am following the instructions above and have executed the netcfg.exe –u vms_pp command to remove 13 additional orphaned adapters, and rebooted the server. The 2008 Enterprise server hung on stage 3 of 3 after the reboot on configuring updates. I rebooted it, and I still have the annoying orphaned adapters, that I cannot uninstall. Certainly I do not have to reload the OS to remove these angry pieces of software?
I am a little confused about what one can do with the Primary VM. Is this simply a special VM that has an additional role to manage Hyper-V or does this service all the Child VM's? What I want to know is, should I leave the Primary VM for managing Hyper-V and service the child partitions and do nothing else with it or can I safely use it as a VM in its own right? Also if the primary VM goes down does it bring down all the child VMs?
Any idea how to do a standby or hibernate once we enable Hyper-V?
Standby and hibernate are disabled in Hyper-V: I learned this on my laptop I use for training.
I would like that support added, though. Sound reasonable?
Is Windows 2000 supported as a guest?
I read about that somewhere.
I wish NT4 was supported also so we could move all guests to Hyper-V from Virtual Server.
We are having the some problem with Hyper-V RC1 on DELL servers... :-(
Such documentation will be forthcoming once we release the RTM version.
Powershell / Andrew -
The x86 version indicates whether it comes with the Hyper-V management tools or not.
Bryant Likes -
This should just continue to work. What happens if you drop the VM settings down to one, boot and shutdown the VM and then change the settings back to two?
ewdev - The parent partition should be used just for managing virtual machine. If it goes down all the virtual machines go down too.
Jack - No.
Perhaps I haven't scoured the web enough, or read enough "readme" files, but I'm stumpted on something.
Dell PowerEdge 2900
Enterprise (or Datacenter) 64-bit, 8 GB RAM
Install the Windows6.0-KB950049-x64 update (via Windows Update).
System installs the update and reboots.
Add Hyper-v role.
System installs Hyper-v and reboots.
I believe there may be one more reboot here.
I have four NICs, the two integrated Broadcoms and a dual-port Intel pro.
The fourth NIC is not cabled to anything.
Currently (as I haven't gotten off this chair to go get another router to create a separate network for the VMs), all three cabled NICs go to the same router. As they all go to the same VLAN and network, I've disabled two, leaving one active with a single route to the network. (I've tried enabling all also, but that doesn't work either).
The option of which NIC to provide Hyper-v control over.
The install text doesn't explain it well. It almost sounds like it's an all or nothing feature. "You can either have your physical NIC talk to the network, or you can have yoru virtual NICs talk to the network, or if you have at least two physical adapters, you may have both."
Past MS VM solutions have always allowed the physical host to communicate on its NICs and let the VMs ride on top of that, also communicating with the network.
I would assume this would be true of Hypver-v, assuming an "external" NIC is used for the Hyper-v VM.
Create a Virtual Machine.
Chose External NIC.
Install Windows 2003 Standard 32-bit OS.
Network Adapaters: None Detected
Not a very nice greeting from your new VM.
I've seen talk about "Integrated Components." I haven't found any explanation of what this is or how to install it.
Inside Hyper-v, I've found Integrated Services, but those seem to be selected by default.
What is Integrated Components?
Where does one download it or install it from?
I've seen references to a "Legacy NIC," both on the web and in Hyper-v. I don't, however, see any option to "add" or "select" a "Legacy NIC."
What does this "Legacy NIC" refer to?
Where can it be found/added?
Is the Hyper-v implementation simply under-developed and doesn't yet play nice with Dells?
Bangs head in frustration at spending so much on a server and not being able to get Hyper-v working.
I'd like to use the VMs to help me study for MS Exams. Yes, I could probably use an earlier MS VM product, but I'd like to use Hyper-v.
I would be grateful if anyone could shed some actual light on how to fix this situation.
Please don't give simple answers like "install Integrated Components" or "use a Legacy NIC." Obviously, I haven't yet figured out what those instructions really mean (where to go and what to do to install such items).
Your assistance is very much appreciated.
Correction to above post:
The Guest OS is not 2003. I'm sleepy...sorry.
I've installed 2008 Standard (Full).
Not sure if this makes a difference or not. I assumed MS would make Hyper-v compatible with its latest OS as a guest OS.