Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have one computer that running windows 7 and want to have a Dev Environment running on this machine.

I tried to install Windows Server 2008 r2 with Hyper-V role on a VirtualBox virtual machine, but I can't get this role to be installed, since it's need a raw access to the processor.

My goal is to have a virtualized windows server that running Hyper-V, that I can install on it all the machines that I want to have in my environment: 2 IIS servers, 1 SQL Server, Load Balancer, and build server.

Can I get a little help from you guys, to help me achieve this?

share|improve this question

closed as off topic by MDMarra, voretaq7 Jun 12 '13 at 1:52

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

3 Answers 3

up vote 3 down vote accepted

Simple: by getting rid of the illusion that you can do that.

A Hyper-Visor needs raw hardware access. So, it can not run virtualized. Get usedto it.

What you CAN do is install WIndows Server in a VHD file and then boot from that instead your Windows 7.

My goal is to have a virtualized windows server that running Hyper-V,

When deluisions meet reality, reality wins. Reality says: Hyper-V does not run within a virtual machine.

Alterantives:

  • Boot into Server 2008 R2 installed in Hyper-V
  • Dump Windows 7. Install Server 2008 R2 and use that as primary operating system. You CAN make it behave and look like a Windows 7 install.

I personally do - depending what I do:

  • Develop in a virtual machine on a number of larger virtualizing servers
  • Use my own workstation to boot into a vhd mounted server 2008 to use virtualiaztion there (mostly for training - allows me to show off a domain without bringing more than a little cube with 16gb RAM).
share|improve this answer
    
It turns out that I can't have a VHD file for Window Server 2008 R2, Virtual PC can't run 64bit OS. social.technet.microsoft.com/Forums/en/w7itprovirt/thread/… –  stacker Oct 27 '10 at 14:03
    
That's not what he meant. Forget about Virtual PC: it is not useful to you for this project. He meant that you could boot Server 2008 R2 natively from a VHD file. –  Skyhawk Oct 27 '10 at 14:53
    
Exactly. Ever sind Windows 7 / 2008 R2 you can MOUNT AND BOOT from a VHD file. –  TomTom Oct 27 '10 at 15:31
    
Do you get support for Dual Screen on your computer? Do you get 1092*1080 resolution on it? As I found out, Windows server 2008 R2 that run Hyper-V, aren't capable of installing a driver the video card. –  stacker Nov 3 '10 at 12:32
    
Hm... it works for me ;) Never used a dual screen with Hyper-V though. I use it mostly for training (customers dont have two screens). Otherwise I RDP into the VM (on a server) and get multiple screens there (thanks to Windows 7 support for multiple screens). –  TomTom Nov 3 '10 at 18:03

Hyper-V can't be ran from within any other hypervisor, VMWare's ESXi can however.

share|improve this answer
    
So, maybe should I create the all servers that I want, using a VirtualBox virtual machine? is this option have any drawback over using Hyper-V? –  stacker Oct 27 '10 at 10:30
    
Well Hyper-V is a far more 'production-ready' hypervisor, whereas VB is more of a 'desktop' product but their basic functionality is pretty comparible. What you're trying to do is more of a personal development machine, you can always install Hyper-V as a bare hypervisor on your W7 box (W7 will effectively run as a VM at that point) - it may not be what you're after but is another option. Hope you have lots of memory :) –  Chopper3 Oct 27 '10 at 11:09
    
I have 8 RAM. I didn't get your solution. DOes it mean that I can install hyper-v on my windows 7, and don't reinstall my windows 7 as VM? Do you think that for my situation, that I want a few (like 5) servers to have, is maybe good to install each one as a separate VM? or it better recommend to haev them all on a one Hyper-V windows server? –  stacker Oct 27 '10 at 13:36
    
How can I achieve what you'he suggested? should I use a VirtualPC for that? (I says that it's not compatible with my windows). it seems like a nice solution :) –  stacker Oct 27 '10 at 13:52
    
Not virtualPC no, just Hyper-V Server 2008 R2, the stand alone hypervisor - have a look here; microsoft.com/hyper-v-server/en/us/default.aspx –  Chopper3 Oct 27 '10 at 14:02

Today I try something and it works! first, you can install Hyper-V server 2008 r2 in VirtualBox, you can enable all the things and administer it from a server 2008 or by a client like this: http://www.microsoft.com/en-us/download/details.aspx?id=7887

The other way is to install windows server 2008 r2 and you can add a role by comand console like this:

Dism.exe /online /enable-feature /featurename:Microsoft-Hyper-V

And no errors!

If you want to, can add the MMC whit this command:

Dism.exe /online /enable-feature /featurename:Microsoft-Hyper-V-Management-Clients
share|improve this answer
    
You've been able to do this for several years with VMWare Workstation. I've setup two Hyper-V servers with a FreeNAS shared storage and demo'ed live migration and failover all within VMWare Workstation on a windows 7 laptop. –  Rex Jun 12 '13 at 1:51

Not the answer you're looking for? Browse other questions tagged or ask your own question.