Presentation:- Hyper-V V3 Demos Extravaganza

 

In this session, i have presented a session on “Hyper-V V3 Demo Extravaganza” to 60 audience at Microsoft Malaysia Office.

Session included with

• Hyper-V Replica
• Live Migration Enhancement
• Dynamic Memory Enhancement

Slide

Hyper-V V3 Demo Extra

View more presentations from Lai Yoong Seng.

Recording

Windows 8:- Minimum and Maximum Memory Configuration

 

Product tested:- Windows Server Developer Preview

Few months ago, i have discussed about Dynamic Memory enhancement . This round i am going to explore on how to changing Dynamic Memory for Minimum Memory and Maximum Memory when the VM is running. Not that complex step but just some guidance when changing these memory.

Before boot up:-

1. Configure Start-up Memory

2. Configure Minimum Memory

3. Configure Maximum Memory

Example:-

• Start-up – 4GB
• Min memory – 2 GB
• Max memory – 8 GB

Configuration when VM is up and running.

Minimum Memory:-

You can lower the memory from 8 MB to 2 GB. If you try to configure more than 2GB , then it will prompt an error “Out of Bounds”.

So if you set to 1200 MB. The next range that you can change is 8MB to 1200 MB.

To increase up to 2GB, then you need to shutdown the VM.

Maximum Memory:-

Same scenario on Maximum Memory. You can change the value from 8GB to maximum allowed. Therefore, you cannot lower the value than 8GB. To change lower value, you need to shutdown the VM. If you set to 10GB, the same behaviour apply (mean from 10GB to max).

Therefore, plan wisely on the configuration before boot up the VM and also when VM is running.

Hope this information is informative.

Windows 8–Hyper-V Cluster Enhancement

 

In today post, we will look into some new improvement on Hyper-V Cluster on Windows 8 (Currently this screenshot is taken from Windows Server Developer Preview- Build 8102. It may subject to change when release to beta and it is tested on my test lab environment. )

One of the key improvement on the high availability Virtual Machine is you can configure start-up priority. This option allow you to configure which VM has the high, medium, low priority and even No Auto Start. The VM with high priority start-up will boot up first compare to Medium or Low.

Here is the end result which i’ve configured. (Refer to Priority column)

Move on in term of live migration enhancement, you can now perform multiple Live Migration rather than 1 times. The limit of the multiple live migration is depend on your configuration at the Hyper-V Host and NIC bandwidth throughput.

Setting:- refer to Virtual Machine Move Configuration.

Here is the screenshot of of the live migration. I have initiated 2 Live Migration and the 3rd VM is put into Queue. Once 1st or 2nd VM complete, the 3rd VM will start to perform Live Migration without giving any error message.

Well, i have highlighted 2 improvement: Start-Up Priority and Live Migration Enhancement. Will keep you posted on some new improvement for Hyper-V on Windows 8.

Free NFR License for Veeam Backup and Replication 6.0

 

Thanks to our sponsor : Veeam. They provided a FREE NFR license for Veeam Backup and Replication 6.0 to Microsoft Certified Professional (MCP) and Microsoft Most Valuable Professional (MVP).

To get it, click here . The NFR license valid for 12 month.

For VMware vExpert, VMware Certified Professional (VCP), VMware Certified Instructor (VCI) or VMware User Group (VMUG) member, pls click here .

On behalf of the ms4u.info visitor and myself,

Thank you.

Changing NIC Order On Server Core

 

For those of you who are deploying Hyper-V on Server Core, there is one very important thing to configure before setup Hyper-V Cluster. This step is changing NIC order. In Full installation, it is easy to change the NIC order since the GUI is present.

However in Server Core, since there is no GUI, you need to change the NIC order in registry.

Before we modify the registry, use nvspbind utilities to capture the MAC address for each NIC.

nvspbind.exe > C:\nicmac.txt

The end result will transfer to a text file. Use it as a reference to identify the MAC address.

Once you’ve complete this step, proceed to modify on registry

Go to

1. HKLM\System\CurrentControlSet\services\TCPIP\Linkage
   1. Bind: Contains NIC GUIDs
   2. Export: Contains NIC GUIDs
   3. Route: Contains NIC GUIDs

Sample result on my server:-

Bind

\Device\{F95F9F29-2440-45AF-ADD9-60EA6479FDFD} \Device\{29D39985-50FC-4B3E-A39D-8C79CDDF9205} \Device\{1D683A18-B32A-4436-8C61-728F2E57ACD0} \Device\{D42AB6E5-3C77-430C-95F8-7226B353B6EF} \Device\{2E04C18D-622C-4217-A1E9-F2B81EFE657A} \Device\{6BE58993-C250-4BCF-A96F-A43C0A5EBDE7} \Device\{C10CDD27-6802-43E1-8AC9-3F45FC93FE71} \Device\{35F54C5A-36D1-46B4-A493-BAAE914D10B9} \Device\{79BE86E5-1A1E-4136-9A5C-54705045289D} \Device\{1F01EA62-2D73-4AE0-833A-058781F95140} \Device\{96790720-8BE9-4465-8309-74EF2142632B} \Device\{E80BD870-B6C0-415A-BEBB-108FA83B3019}

 

Export

\Device\Tcpip_{F95F9F29-2440-45AF-ADD9-60EA6479FDFD} \Device\Tcpip_{29D39985-50FC-4B3E-A39D-8C79CDDF9205} \Device\Tcpip_{1D683A18-B32A-4436-8C61-728F2E57ACD0} \Device\Tcpip_{D42AB6E5-3C77-430C-95F8-7226B353B6EF} \Device\Tcpip_{2E04C18D-622C-4217-A1E9-F2B81EFE657A} \Device\Tcpip_{6BE58993-C250-4BCF-A96F-A43C0A5EBDE7} \Device\Tcpip_{C10CDD27-6802-43E1-8AC9-3F45FC93FE71} \Device\Tcpip_{35F54C5A-36D1-46B4-A493-BAAE914D10B9} \Device\Tcpip_{79BE86E5-1A1E-4136-9A5C-54705045289D} \Device\Tcpip_{1F01EA62-2D73-4AE0-833A-058781F95140} \Device\Tcpip_{96790720-8BE9-4465-8309-74EF2142632B} \Device\Tcpip_{E80BD870-B6C0-415A-BEBB-108FA83B3019}

Route

"{F95F9F29-2440-45AF-ADD9-60EA6479FDFD}" "{29D39985-50FC-4B3E-A39D-8C79CDDF9205}" "{1D683A18-B32A-4436-8C61-728F2E57ACD0}" "{D42AB6E5-3C77-430C-95F8-7226B353B6EF}" "{2E04C18D-622C-4217-A1E9-F2B81EFE657A}" "{6BE58993-C250-4BCF-A96F-A43C0A5EBDE7}" "{C10CDD27-6802-43E1-8AC9-3F45FC93FE71}" "{35F54C5A-36D1-46B4-A493-BAAE914D10B9}" "{79BE86E5-1A1E-4136-9A5C-54705045289D}" "{1F01EA62-2D73-4AE0-833A-058781F95140}" "{96790720-8BE9-4465-8309-74EF2142632B}" "{E80BD870-B6C0-415A-BEBB-108FA83B3019}"

Modify the NIC GUID order according to

1. Management

2, Cluster Heartbeat / CSV

3. Live Migration

4. iSCSI

5. MS Virtual Network Adapter

6. Microsoft Failover Cluster Virtual Adapter

and so on…

Once complete, reboot the server for the NIC order to take place.

Configure Intel NIC Teaming on Server Core

 

Recently, I have deployed Hyper-V Host Cluster and the server came with Intel NIC card.

On Full Installation of Windows, you can use device manager to create NIC teaming for the Intel NIC. Now, how about create a teaming on Server Core. There is no device manager snap-in which you can call. Therefore, you cannot go to Device Manager to create a teaming.

To create Intel NIC teaming, you need to use PROSETCL which located in

C:\Program Files\Intel\DMIX\CL Execute PROSETCL.exe

Before that, let have a look on some command:-

a) List adapter according to Index.

PROSETCL.exe adapter_enumerate

Sample result:-

1) Intel ® Gigabit ET Quad Port Server Adapter #2

2) Intel ® Gigabit ET Quad Port Server Adapter #4

3) Intel ® Gigabit ET Quad Port Server Adapter

4) Intel ® Gigabit ET Quad Port Server Adapter #3

b) Create teaming

Format:-

PROSETCL.exe Team_Create (Adapter Index) (Teaming name) (Teaming Mode)

PROSETCL.exe Team_Create 1,2,4 ProductionTeam 802.3AD

Valid team mode:-

• ALB, AFT, SLA, 802.3AD and SFT

c) List teaming

PROSETCL.exe Team_Enumerate

Sample result:-

Number of teams currently present: 1

1) ProductionTeam

More information, you can refer to http://download.intel.com/support/network/sb/prosetcl.txt

Veeam Backup and Replication v6 has Launched

 

Good news! One of our major sponsor Veeam has just launched a product called “Veeam Backup and Replication v6 “ Sorry a bit late on the announcement since i just saw my email regarding this excited news.

For those of you who would like to know more and get your hand dirty on the trial version, please click on below picture and register.

Once register, Veeam sales rep will send an email and provide a download link. I’m currently downloading this software and the size is around 463MB.

Some of the key features on Hyper-V Version:-

• 2-in-1: backup and replication in a single solution
  Changed block tracking: 20x faster backup, plus near-continuous data
  protection
  Built-in deduplication and compression: 75% reduction in backup size
• Forever incremental
• Agentless
• Instant File-Level Recovery

Linux Integration Services v3.2 for Hyper-V

 

Linux IC v3.2 has just released to public. To get the IC, please go to http://www.microsoft.com/download/en/details.aspx?id=28188

For this release, the major key improvement is Integrated Mouse. On previous IC version you need to use Project Satori in order to get the mouse working.

With the new improvement, you no longer need to download 3rd party support on the mouse.

This version of Integration Services can support the following guest operating system:-

• Red Hat Enterprise Linux 6.0 and 6.1 x86 and x64 (Up to 4 vCPU)
• CentOS 6.0 x86 and x64 (Up to 4 vCPU)

Other version such as SUSE Linux Enterprise Server 10 and Red Hat Enterprise Linux 5 should use the version of Linux Integration Services available at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=eee39325-898b-4522-9b4c-f4b5b9b64551.

To install the Linux IC,

1. Mount the Linux IC v3.2.iso using Hyper-V Manager

2. Access with root right. Type the following command:-

# mount /dev/cdrom /media [host media]# sh install.sh # reboot

Screenshot:- Centos 6

Article featured in MVP Friday Five November 25, 2011

 

Just heard that my article:- Inventory Hyper-V Machine and Virtual Machine using PowerShell has featured in MVP Friday Five November 25,2011. You can refer to http://blogs.msdn.com/b/mvpawardprogram/archive/2011/11/25/mvp-friday-five-november-25-2011.aspx

TechNet Forum Assistant Gadget

 

The TechNet Forum Assistant is a free Windows gadget, available in the Microsoft Download Center. This gadget will help you better utilize the great information in  TechNet Forums and community. By downloading, you have the support and expertise of Microsoft TechNet Forum Support Engineers directly right on your desktop. Receive support on your terms by downloading the TechNet Forum Assistant.

Inventory Hyper-V Machine and Virtual Machine Using PowerShell

 

In this article, we will look into using PowerShell in order to get some information about Hyper-V Host and VM. I’m using this to simplify on my documentation at the end of the project.

Before we begin, you need to download Powershell Management Library for Hyper-V. To download, go to http://pshyperv.codeplex.com/releases . Current latest version is R2 SP1. Well, most people don't like coding and prefer to use GUI. However, in certain way in order to get the end result faster then PowerShell is the answer.

Let look into some PowerShell command that you can use especially want to document your final result.

Pre-requisite:-

a) .Net Framework

b) Windows Powershell

Installation

a) Extract the zip file and execute install.cmd from command line.

To use the PowerShell, you need to import the Hyper-V Module.

Type:-

Import-Module .\HyperV.psd1

Let get started:-

To know which command available, you can export the command to a text file.

Just type

Get-command > C:\command.txt

Some sample that might be useful:-

1. Get memory information such as dynamic memory on the entire VM

Get-VmMemory

2. Get virtual cpu information that assign to the VM

Get-VmCpuCount

3. Get network information such as network type, virtual switch and mac address assign to vm. I often use this command to identify duplicate mac address assign to the VM.

get-VMNic

4. Get information about virtual cpu on the running vm or per vm basis.

Get-VMProcessor

5. Get information such as snapshot apply to the vm.

Get-VmSnapshot

6. Get virtual switch information created on the host

Get-VMSwitch

That’s all for now, a simple cmdlet. Do explore on other PowerShell cmdlet that get you to another end result that you want.

Veeam Backup and Replication 6

 

Veeam Backup & Replication v6 is a major release of Veeam’s industry-leading data protection and disaster recovery solution for virtual environments, which combines agentless image-based backup and replication in a single product. And with v6, Veeam is taking data protection to the next level for both VMware vSphere and Microsoft Hyper-V.

5 new features will be available in V6:-

a) Enterprise scalability

b) Advanced Replication

c) Multiple Hyper-visor support. v6 adds support for Windows Server Hyper-V and Microsoft Hyper-V Server.

d) 1-Click File Restore

and more, click here to read more detail.

Don’t miss the chances to be notified when v6 release to public, click here to register.

TechInsight 2011 Presentation: Virtualization Best Practise-Tip and Trick From Expert

 

Today at Monash University (Malaysia), i have delivered my last session for TechInsight 2011 event. The topic covered are

• Virtualization Best Practice on Planning, Deployment and Management
• 10 Tips and Trick
• Useful tools

Slide

Virtualization Best Practices-Tips and Tricks From Expert

View more presentations from Lai Yoong Seng.

Recording

TechInsight 2011 Presentation: What’s Coming in Hyper-V VNext on Windows 8

 

In today session, I've discussed about the new features which available in Hyper-V Vnext on Windows 8 to TechInsight members.

Venue: Monash University, Malaysia

Slide

What is Coming in Hyper-V Vnext on Windows 8

View more presentations from Lai Yoong Seng.

Recording

No recording on this session

Running Hyper-V Monitor Gadget in Windows Server 2008 R2

 

In windows Server 2008 R2, you cannot add gadget into Windows Server 2008 R2 as similar as Windows Vista or Windows 7. By default, Windows Sidebar is not a feature on Windows Server 2008 R2. Therefore, Hyper-V Monitor Gadget only can use on Windows 7 or Vista. To download  Hyper-V Monitor Gadget, please go to http://hypervmonitor.codeplex.com/

However there is a way to add Windows Sidebar into Windows Server 2008 R2

1. Download Windows Sidebar from here.

2. Extract it into C:\Windows Sidebar

3. Open Command prompt and execute install.cmd

4. Press a key to start the installation

5. Install Hyper-V Monitor Gadget by open it and select Install Gadget

6. Open Control panel and double click Desktop Gadget

7. Click on Hyper-V Monitor Gadget and click Add

8. On your desktop, click Options at the Hyper-V monitor to start the configuration.

9. Enter Hyper-V Host details.

10. Here is the end result. You can console/remote desktop to Hyper-V Host or Virtual Machine.

Additional tool tip able to provide additional information.

Note:- Limitation. So far it did not work when connect to local Hyper-V Host. However, you can use to monitor Remote Hyper-V Host.

Reverse Replication on Hyper-V Replica

 

Product:- Windows Server Developer Preview

In this post, we will look into how to switch primary to recovery VM or via versa.

1. On the Recover VM, right click to select Replication and Reverse Replication

2. The remainder of the screenshot will display in thumbnail. Pls click to view on larger view. The configuration is similar as configure Hyper-V replica.

3. Once you have set Reverse Replica, both VM will transfer the role.

Related post:-

• Configure Hyper-V Replica
• Test Hyper-V Replica
• Monitor Hyper-V Replica
• Perform Planned or Unplanned Hyper-V Replica

Perform Planned or Unplanned Failover Hyper-V Replica

 

In this post, we are going to test perform planned or unplanned failover Hyper-V Replica.

Product: Windows Server Developer Preview

Planned Failover

Planned failover mean the existing primary VM is intact but you would like to use the replica VM. In order to achieve this scenario, you must turn off the primary VM before initiate Planned Failover. If you did not turn off the primary VM and initiate the boot up the system will provide an error message at the pre-requisite check.

How about manual start the replica VM? You will receive an error message as display below

Therefore, you are require to use failover option to start the VM.

Now let see how we can achieve this scenario:-

Scenario:-

Primary VM is offline

1. Right click the primary VM, select Replication and select Planned Failover.

2. Select Failover. The system will perform pre-requisite check. If passed then it will start to perform action as displayed on the below screenshot.

Unplanned Failover

Unplanned Failover occur when the primary VM has corrupted/unavailable. Therefore, from replica server, you will initiate failover.

Scenario:-

Primary VM- Make sure is offline.

1. Select the Replica VM, select Replication and select Failover

2. Select the Replica that you would like to recover

3. The system will perform the pre-requisite check and action as listed below for the Failover to happen.

Related Post:-

• Configure Hyper-V Replica
• Test Hyper-V Replica
• Monitor Hyper-V Replica
• Reverse Replication on Hyper-V Replica