Solved Hyper-V for XP

Hyper-V has been enabled in Windows Features but when the management console appears it offers no list of choices in the righthand menu - just "connect." The lefthand menu is similarly bare.

Perhaps someone has a clue on what's missing, and a step-by-step tutorial on how to recreate the XP-mode experience of Win 7 via Hyper-V in W8.

Intel 2600K
64-bit
8G ram
W8 Pro

Thanks

you have to go in the bios and activate Intel VT

Virtualization has long been activated in the BIOS. XP mode in W7 required it, and it works well there. Same machine, so same hardware and almost identical software for both O/S. Thanks.

seem to me that you don't install the hyper-v platform, you probably just install the management, the 3 Hyper-v item as to be check, ( mine are not because I run Hyper-V in dedicated servers )

Followed a tutorial on the WEB precisely, and checked all three boxes. (When the main box is checked, the others are selected automatically.) It appears that the module installed, but the options shown are not as described and I have no clue...

Do you see your local machine there? Hyper-V is only going to show you connect to server in the main tree- you have to actually connect to a "server" to get VM options. Might want to try "connecting" to your own machine name to see if it works (it should).

Borgus - post a screen shot, please. That will help us help you.

UPDATE - Hyper-V for XP

Two images attached...
The first comes up when "Hyper-V manager" is clicked. I note now, after clicking on "HB" at the left, that choices appear at the right.

The second is after "Hyper-V virtual machine has been clicked." Note that it says "you don't have permission; contact HB." I am HB and have an administrative account.

Kindly point me to the best step-by-step tutorial - in layman's terms ^_^ - to install a virtual machine, then XP, then programs.

Will the virtualized XP have "integration features" to the various drives on the PC as it did with XP-mode in Windows 7?
If not, the exercise is moot, as I need that capability in order to save files to those drives from within the virtual machine.

Many thanks.

I'm not sure exactly what the problem is - you can now create virtual machines, VHDs, etc - the VM connection window is only for connecting to VIRTUAL MACHINES - not the virtual machine server itself. You've already done what you wanted to do, namely get the options for creating virtual machines!

Thanks for the follow up Cluberti. For now I have implemented a different plan that doesn't require virtualization.

That's OK - just wanted to point out that you had, in fact, gotten to the point where you could have created the VM you wanted.

Sorry I didn't see this earlier. Here's how to address permissions in Hyper-V (if you ever go back to it):

Allowing non-Administrators to control Hyper-V - Ben Armstrong - Site Home - MSDN Blogs

borgus said:

Thanks for the follow up Cluberti. For now I have implemented a different plan that doesn't require virtualization.

Click to expand...

Good luck!