Boot from VHD

If you need to run multiple instances of Windows on your computer, you have different options. First you could use software like Microsoft Virtual PC or VMware Workstation to run a virtual instance. But if you need more performance, or you have to run for example Microsoft Hyper-V you need a native installed Operating System. Until Microsoft added the feature “boot from VHD”, you had to create different partitions for each installation. Since Microsoft allowed you to use VHD to boot you won a lot of flexibility.

This guide should show you how you can install a new operation system in a VHD, which you can boot from.

  1. First boot from a Windows Setup DVD or USB Stick
  2. On the screen where you could click “Install now” you have also a “Repair your computer” option in the bottom left corner. Click on this option or use the short cut “Shift + F10” to boot in to the command line mode.
  3. Enter diskpart
    Capture1
  4. Create a new VHD file
    create vdisk file=”filepathandfilename” type=”expandable” maximum=maxsiize
    Capture2
  5. Now you have to attach this VHD
    select vidsk file=”filepathandfilename”
    attach vdisk
    Capture3
  6. Now you can switch back to the “Install now” screenby pressing “ALT+TAB” and now do the setup on the new create vdisk.
  7. If you start Windows the next time you will see the new and the old Windows in the boot menu.

If you want to add a already existing VHD to the boot menu you can use bdcedit to edit the boot menu.

bcdedit /copy {originalguid} /d "New Windows 7 Installation"
bcdedit /set {newguid} device vhd=[D:]\Image.vhd
bcdedit /set {newguid} osdevice vhd=[D:]\Image.vhd
bcdedit /set {newguid} detecthal on

You can get more information here.

How Microsoft Hyper-V and the Cisco UCS changed our lives

Cisco UCS Hardware

At the end of last year we had our Cisco UCS ordered and in your datacenter. In January we started the testing and made the Clusters ready for the production environment. In February we started the migration of our existing environment, mostly P2V and also some V2V migrations.

Here some interessting facts about our Cisco UCS and Hyper-V project.

  • We use 12 Cisco UCS Blades this is like 10 HE of rackspace
  • We migrated 45 Windows Servers and 47 Unix Servers in just one week
  • We replace 2 racks of server with a half rack of two Cisco UCS Bladecenters
  • We think we can replace 2-3 racks more with our two Bladecenters.
  • At the end of this year we think we could replace 4-5 racks with 1/2 rack
  • We still have a lot of physical and virtual server which will be needed to be migrated to the Bladecenter.
  • We will get even more out of our Blade Servers by activting Hyper-V Dynamic Memory as a new feature of Hyper-V R2 ServicePack 1

This migration had a lot of positive influence on other things in the datacenter.

Datacenter Power

  • we need now 4% less energie overall
  • we need now 6% less cooling overall
  • we need less space (1 and 1/2 racks at the moment)
  • now our system administrator travel 50% less to the datacenter, because of hardware defects or other administrative tasks.
  • We can deploy new servers in minutes instead of hours

I think all of this numbers (except the time we need to deploy new servers )will increase after the next migrations.

Now I started to write a series of blog posts about installing Microsoft Hyper-V R2 on the Cisco UCS system:

Microsoft Hyper-V and the Cisco UCS Bladecenter are a powerful team. The UCS Virtual Hardware takes alot of complexety from the hypervisor in your case Hyper-V. You don’t need NIC teaming and stuff like that. Thats is making it very easy to deploy Hyper-V Clusters. And with the Microsoft System Center Virtual Machine Manager you can save a lot of time in managing your clusters, hosts, virtual machine and also in P2V and V2V migrations. Since Microsoft SCVMM supports Windows Powershell you can also do a lot of scripting automation. And with the release of the new Version of SCVMM (System Center Virtual Machine Manager 2012) this will even get better for deploying new virtual machines, services and even public and private clouds.

Hyper-V R2 SP1

We started with Microsoft Hyper-V R2 Servers before the release of Service Pack 1. We think we can even get a lot more out of your systems with the new Dynamic Memory feature for Hyper-V which comes in Service Pack 1.

At the end we think choosing the Cisco UCS, Microsoft Hyper-V and Microsoft System Center Virtual Machine Manager for our datacenter was the best choice we have made, in terms of costs and technology.

Cisco UCS Hyper-V Cluster – Configure Hyper-V Networks – Part 5

This How-To shows you how you configure the (Virtual) Network Adapters of the Hyper-V Servers. This is not really heavy, but to complete the UCS Hyper-V Guide I post this. If you use Microsoft System Center Virtual Machine Manager 2008 R2 you will find later a post about doing this in SCVMM 2008 R2.

  1. Connect to the Hyper-V Server with the Hyper-V Manager Console
    Hyper-V Manager
  2. Now you can configure the Networks under Virtual Network Manager on each Hyper-V Host.
    Hyper-V Virtual Network ManagerWhat we did is, we added 7 (Virtual) Network adapters to the UCS Bladenodes in the UCS Manager. We added the same on Configuration on the Blades which are using VMware ESXi and on the Blades with Microsoft Hyper-V and thats why we have a Network called vMotion on the Hyper-V Servers. We use the vMotion network adpater for the private Failover Cluster Heartbeat.

Basically we have the following Networks:

UCS Blade Server Networks

  • 1. Network adapter is the Hyper-V Management Network dedicated to the Hyper-V Node
  • 2. Network adpater for Hyper-V Cluster Live Migration
  • 3. Network adapter for private Failover Cluster Heartbeat
  • 4. Network adapter External Network, is used for our main external Network
  • 5. Network adapter Internal Network, is used for our internal Management Network for Servers
  • 6. and 7. Network adapters are used for VLAN Trunks

To get the best performance we don’t share any Network Adapter with the Hyper-V Host and a Virtual Network.

Cisco UCS Hyper-V Cluster – Part1

CISCO UCSThis is my first post on a Microsoft Hyper-V Cluster with a Cisco UCS. In the next parts I will write about how to setup a Hyper-V Cluster on a UCS.

After testing and evaluation Bladecenters for our Datacenter, we decided that the Cisco UCS is the best solution for us. There are a lot of reasons why the UCS (Cisco Unified Computing System) is one of the best systems for a datacenter. Some of them are:

  • Easy cabling
  • Single Management Console for Switches, Chassies and Blades (UCS Manager)
  • Hardware Virtualization
  • Made for Datacenters

About the Cisco UCS (Wikipedia):

The Cisco Unified Computing System (UCS) is a data center computing solution composed of computing hardware, virtualization software, switching fabric, and management software. The idea behind the system is to reduce total cost of ownership and improve scalability by integrating the different components into a cohesive platform that can be managed as a single unit. Just-In-Time deployment of resources and 1:N redundancy are also possible with a system of this type.

But lets start with our project. First of all what have we got in our starting configuration.

Cisco UCS Hardware

  • Two chassies with 6 Blade Servers each
  • 12 Blade Servers (2x Intel Xeon 6-cores and 72GB RAM)
  • 6 Nodes for VMware and 6 Nodes for Hyper-V
  • EMC Storage

Cisco UCS Hyper-V TaskmanagerIn the next part I will write about how to Setup the Blade Servers with Microsoft Hyper-V Server (Core).

Quest released PowerGUI® Pro and PowerGUI® 2.3

powergui-legoQuest released PowerGUI Pro and PowerGUI 2.3. Both get really cool new features. In the Pro version the most changes are done in the MobileShell. In the free version the most changes are done in the support for snippets. And they now support virtualization now with the VMware Powerpack right build in.

If you wanna know more about the changes of PowerGUI visit poshoholic.com.

Cisco UCS and Microsoft Hyper-V R2

Last week we run our first tests with the Cisco UCS Bladecenter, VMware ESXi and Microsoft Hyper-V R2.

I am really excited about the performance and the easy management of the Cisco Bladecenter. Maybe I get some more information about Hyper-V and the UCS out there for next week.

There is also a Microsoft TechNet event next Tuesday:

Cisco Unified Computing System + Microsoft Hyper-V/System Center = die Komplettlösung für Virtual IT und Private Cloud