As it is quite difficult to configure Windows Server 2008 Core – speciali if you are not used to use command prompt as your main configuration utility … 🙂 There is a tool available online that helps you configure some basic tasks…
It is quite similar to Windows Hyper-V server 2008 configuration menu…
http://www.codeplex.com/CoreConfig
Happy core configuring… 🙂
Thanks to Mike …Â
Mike wrote:Â
“I’ve found an even easier way to do this. I found a PowerShell Hyper-V script at:
http://www.codeplex.com/PSHyperv
It has a lot of functions already, and I added a “Kill-VM” function that automates the kill process:
Kill-VM <VM name>
My modified script is attached to this message.
To use it, you need to install PowerShell (Under Server Manager -> Features in Win2008). Once installed, run PowerShell from Start -> Search, find the script, and type:
. .hyperv.ps1
Once loaded into memory, type:
Kill-VM <VM Name>
Enjoy”
If I try to reboot my working FreeBSD machine in HyperV it does not work… FreeBSD somehow hangs the reboot procedure and I need to reboot my Windows server 2008 with Hyper-V – it can not be turned off even by clicking on “Turn off…” in a virtual machine context menu…
For now the only solution I found is to use command:
shutdown -p now
and when it turns off I turn it back on with Hyper-V console…
 🙂 hope it helps
I am so happy – I managed to make it work…
What we need to make FreeBSD run on Hyper-V:
– download FreeBSD ISO image from:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200806
Download this ISO image:
7.0-STABLE-200806-i386-disc1.iso
– create new Virtual Machine using Hyper-V
– remove default network card that is added by wizard
– add hardware and chose Legacy network adapter
– start the machine and “mount” ISO image to start booting FreeBSD…
– install it with parameters you want…
– **** NETWORK PROBLEMS **** Even if you are runing DHCP server on your network your FreeBSD machine will not get IP from your DHCP server (my machine did not) so I used ifconfig to add IP and gateway this way:
ifconfig de0 10.70.60.201 – this is IP in my subnet you should use one of your free IP’s
ifconfig de0 down
ifconfig de0 up
You can now chec status of your IP with:
ifconfig
Ok, now we need a gateway to get to the internet:
route add 0.0.0.0 10.70.60.1 This will add your default gateway (for example my gateway is 10.70.60.1)…
try to ping an public IP address to see it is working… As you can see in my screenshots it works for me. 🙂
FreeBSD on Hyper-V [docx]
FreeBSD on Hyper-V [pdf]
*** There is still one problem unsolved for now… If you try to reboot Free BSD, Hyper-V does not Turn off the machine … I am trying to solve that with some Nejc tricks 🙂
Alot of people does not know that there are no Virtual Machine additions any more in Hyper-V this are now called Integration services and you can install them on this OS-es. So if you use for example Ubuntu on Hyper-V you need to remove Network card that it added to Virtual machine by default and then Add Hardware and add Legacy Network Adapter (it behaves the same way as bridged adapter in Virtual PC and Virtual server) – as it is used for machines that do not have Integration services installed.
You need to intall Integration services on all MS Windows server 2008 machines to get best performance!
If you you need network connectivity imediatly after installation you can first use Legacy network adapter and after Integration services intallation you can replace it with Network adapter that was configurated during creation of Virtual Machine.
Integration services will also solve your unknown devices in device manager.
You install Integration services by clicking on Action / Insert Integration Services Setup Disk when you are logged on your virtual machine.
If you like your Hyper-V story to run smoothly your server needs two network cards – my HP DL380 has two gigabit cards – one is used for Hyper-V server to have internet connectivity (updates, remote management …) second one is given to Virtual network manager to be used by virtual machines.
If you did not select any network adapters to be used by Hyper-V during Hyper-V installation you can see your physical two adapters in Network connections.
After you run Virtual network manager and you create new network for example “External network” that is connected to your second physical card your physical card lose connectivity and all protocols and services are unchecked except Microsoft Virtual Network Switch Protocol (and HP Network configuration utility – but this is specific to my case becouse I use HP server). When you finish the wizard you can see that in your Network connections there is another adapter called “External network” – it is now used for your Virtual machines.
HINT! Do not do that remotely if you are not completely shure which adapter is which… If you make a mistake you will need physical access to the machine to change network parameters. 🙂
Example:
Hyper-V virtual network manager example [docx]
Hyper-V virtual network manager example [pdf]
Hyper-V final is ready to be installed so I created a Step-By-Step tutorial how to install Hyper-V final version on Windows server 2008 64 bit server (Hyper-V role works only on 64 bit!!!)
This Step-By-Step have some specific information regarding installing Hyper-V on HP DL380 server which I have at home – so I have explained how to enable virtualization in BIOS (it may vary from bios to bios) and some specific problem HP servers with HP Network configuration utility have when you try to install Hyper-V (server hangs on “Configuring Updates Stage 3 of 3” on 54%Â or 75%).
Step-by-step installing Hyper-V final version [docx]
Step-by-step installing Hyper-V final version [pdf]
Additional resources:
http://www.microsoft.com/windowsserver2008/en/us/virtualization-consolidation.aspx – Microsoft Virtualization
http://blogs.technet.com/virtualization/Â – Microsoft Virtualization blog
http://www.microsoft.com/downloads/details.aspx?FamilyId=F3AB3D4B-63C8-4424-A738-BADED34D24ED&displaylang=en – Hyper-V Final version update
http://support.microsoft.com/default.aspx/kb/950792 – HP servers problem when installing Hyper-V
 Great stuff!!!
Where it happened? On HP DL380!!!
This problem occurs when the following conditions are true:
• You enabled, disabled, or updated Hyper-V on a Hewlett-Packard (HP) server.
• The HP Network Configuration Utility was installed.
Â
I enjoyed 3 days of NT Konferenca 2008 in Portoroz.
For atendees of my sessions…
Luka Manojlovic 