Skip navigation

Tag Archives: Hyper-v 3


This is Part 2 of installing SCVMM 2012 SP1 on virtual cluster and on Hyper-v Cluster hosts.

Part 1 can be found from here

Let’s review what we have installed.

We have installed File server which provides Quorum disks. We have created AD components and two VMM virtual servers.

We have installed Failover features on VMM servers and all other prerequisites.

Let’s start the Part 2 with Create a Cluster on VMM servers.

Start Failover manager and Validate a cluster first (if you don’t do this step, the creation wizard will also do it)

 

image

Now, with any clusters, a heartbeat network is required. Since our VMMs will sit on same Hyper-v Host, so what I need is to build a new Virtual Switch called Heartbeat.

Notice:

If you want to join these two Hyper-v hosts in the future, you must have EXACTLY same virtual network settings on both Hyper-v hosts. Therefore, a internal switch or private switch is NO NO for cluster. You have to build External switches with same name on both Hyper-v Hosts.

 

image

Once this is done, add a new virtual Nic on VMM and connect to heartbeat switch.

SNAGHTML1c00f2

 

image

Configure Heartbeat IP on both VMMs

 

clip_image002

 

clip_image002[5]

You also make sure you have create DNS A records for this cluster and also VMM app cluster.

clip_image002[7]

image

 

image

 

clip_image002[11]

 

image

With Windows 2012 Cluster, we can actually use share folder as quorum.

image

 

clip_image002[13]

 

clip_image002[15]

 

image

image

image

 

Install VMM 2012 SP1

Well, most jobs are done. Here is the final installation.

clip_image002[17]

 

clip_image002[19]

System automatically detects you are on cluster. so click Yes.

clip_image002[23]

 

image

 

clip_image002[25]

 

clip_image002[27]

 

clip_image002[29]

Yes, it’s installed on C drive.

 

clip_image002[31]

Oops, I didn’t setup enough start up memory on this VMM vm.

I went back and made adjustment.

clip_image002[33]

image

Be aware to make sure svc_vmmadmin has rights to create DB on your SQL database server.

image

Make sure VMMCLU01 exists in your DNS server.

image

The location of AD can be found via ADSI EDIT. Just found the OU like this

image

 

clip_image002[37]

 

clip_image002[39]

DOn’t do that now, you are on cluster.

 

clip_image002[41]

clip_image002[43]

Now, do the same thing on the other VMM VM. Most critical settings are already setup.

image

 

image

Once the wizard go through, you installed VMM on cluster successfully.

clip_image002[45]

 

clip_image002[47]

 

This is the end of this post. There will be other posts soon talking about how to configure VMM 2012 SP1.

Advertisements

image

Last week, I presented my design chart of my Lab. Today, I’m going to build SCVMM2012 cluster on Virtual Machine. In another word, this post will also show you how to build Virtual Cluster on Hyper-V.

Environment:

Physical Host:

Before you start, you need to make sure that you have at least one Hyper-v Host available. You will also need a windows File Server which will provide quorum disk for your vmm cluster. You can use a virtual file server(Windows 2012) but I have a physical box.

Clearly, you need a virtual SQL server as database source.

Virtual Machine:

Since we are building cluster, so you will need to VMs which I install Windows 2012 on that. Each VM has 2 nics. One is heartbeat and the other is for production and management.

What you will install on VMM01 and VMM02:

  • AD Preparation

Create two user accounts, svc_vmm and svc_vmmadmin

image

 

image

  • Configure distributed Key Management (DKM)

DKM is critical for VMM which stores encryption key for both VMM servers to access.

clip_image002[23]

clip_image002[25]

clip_image002[27]

image

grant Vmmadmins rights for this AD  object

 

image

image

image

image

 

  • Install Windows 2012 Standard version

Build windows 2012

Add IP address

Join VM into domain

Turn off Firewall

Enable Remote Desktop

Disable IE security

Disable UAC

test remote winrs /r:vmm01 ipconfig

image

  • Add SCVMM accounts into local Administrator groups

You must add those two accounts separately.

Please DO NOT create a group and put users into group and put group into local administrator group, because it won’t work!

image

 

  • Install Failover Manager
  • Install .NET Framework 3.5 Feature

clip_image002

When you install that, be aware you need to have Windows 2012 ISO or CD ready like following

clip_image002[5]

You instruct installation application where to find source code, otherwise, it will fail.

Tip:

You will be surprised that how many features actually coded base on 3.5 rather than 4.1. This is one of “must install” for me every time I install a VM.

  • Install Windows ADK for Windows 8

clip_image002[7]

 

clip_image002[9]

 

clip_image002[11]

 

clip_image002[13]

 

clip_image002[15]

 

  • Install SQL Native Client (I’m using SQL 2008 R2 SP1)
  • Install SQL Command Line Utilities

clip_image002[17]

Build windows 2012 File Server

A file server is important for cluster. As cluster, you need a quorum disk which can be accessed by all members of cluster so they can exchange data, voting etc. You can have a NAS or SAN blah,blah, but the cheapest way is to use a free windows Server to provide shared folder. Windows 2012 cluster has this capability to use this share folder as quorum storage, thank for SMB 3.0 which allows multiple accesses at same time.

By saying that, we can also build iSCSI features on both File server and VMM01,02. No additional software required, Windows 2012 will allow us to have a iSCSI storage. I will write another post about it.

Let’s install

Make sure you have these service installed on your windows File server.

clip_image002[31]

You will also need a separated physical disk attached to file server.

clip_image002[33]

Once you have this physical disk, you can build a new storage Pool.

clip_image002[35]

clip_image002[37]

clip_image002[39]

clip_image002[41]

Now, I have storage Pool, I will start build a virtual disk on the pool.

clip_image002[43]

clip_image002[45]

clip_image002[47]

clip_image002[49]

clip_image002[51]

clip_image002[53]

clip_image002[55]

You will also need to build another virtual disk for storing VMs as to be used by VMMLibrary Role later on.

Now, you need to install Share feature.

clip_image002[57]

clip_image002[59]

 

clip_image002[61]

Once that’s done, Let’s come back and share the quorum

clip_image002[63]

clip_image002[65]

clip_image002[69]

clip_image002[67]

clip_image002[71]

don’t need anything here for quorum

clip_image002[73]

However, we do need permission to be added here. You need to add svc_vmm, svc_vmmadmin and also two VMM computer AD objects.

image

image

 

I’m not going to repeat similar steps here.

clip_image002[75]

With this File server, you can also build quorum for Hyper-v Hosts as well.

 

To be continued….


I understand there are quiet few articles regarding monitoring Memory status of Hyper-v. But I would still prefer to write down at least you don’t need to dig around again.

Hyper-v memory status is one of critical parameter you would always focus on.

If it was in Vmware, you would use Vmware embedded performance monitoring to see how much memory your host has and how much your VM takes.

You can do that either from vCenter or ESXi (esxtop).

With Microsoft Hyper-V, you can use following solutions.

  1. Hyper-v manager
  2. Powershell on Hyper-v Host
  3. Performance monitor on Hyper-v Host
  4. PAL analyse result of Performance Monitor
  5. SCOM
  6. SCVMM

 

Hyper-V is using Dynamic memory to allocate physical memory to VM. Instead of like Vmware which uses balloon, sharing to “work around” on optimizing memory usaging, Hyper-V simply just gives memory or take it back since it’s Microsoft Product.

Hyper-v Manager

 

image

The startup RAM is related with smartpage. If there is not enough physical memory available in host, Hyper-V will use SmartPage to use storage as memory to start machine.

Minimum RAM is guaranteed memory server assign this VM. As you know, with Dynamic memory, host does take memory back from VM when VM doesn’t need it. but host won’t take memory below minimum RAM.

Maximum RAM should be reasonable memory a VM may need.

Memory buffer is how much memory increases at time.

 

clip_image002

 

From above picture, the Assigned Memory is actually important. that’s how much memory a physical host has assigned to a VM but it doesn’t mean that’s how much VM believes it has.

For example, a VM can have 8GB memory but assigned memory could be 512MB. This case is important when host try to retrieve memory from VM. With dynamic Memory, when you increase memory on VM, you will see total physical memory from VM increase. but when host takes memory back, it won’t decrease that figure from VM.

 

Powershell on Hyper-v Host

 

image

image

image

image

 

image

 

Performance monitoring on Hyper-v

 

clip_image002[5]

 

clip_image002[7]

 

PAL analyse result of Performance Monitor

 

You can also download PAL

image

Generate Hyper-v performance monitor template

image

Import template to performance monitor and start monitoring for certain time, import result back to PAL

 

image

You will get report like this

image

 

image

 

SCOM and SCVMM is not discussed in this post.

But you can check out following reference to get more details.

 

 

 

Reference:

http://blogs.technet.com/b/haroldwong/archive/2013/03/26/server-virtualization-series-performance-management-memory.aspx

 

http://blogs.technet.com/b/haroldwong/archive/2013/03/08/hyper-v-2012-dynamic-memory-what-does-the-vm-think-it-has-versus-what-it-really-has.aspx

 

http://blogs.technet.com/b/chrisavis/archive/2013/03/06/monitoring-dynamic-memory.aspx


This Post is introducing Hyper-V VM to everyone. What’s Hyper-v 2010 VM components and what Hyper-v 2012 can do in vMotion.

Test environment:

Hosts:

Testhyp01, Testhyp02

Windows 2012

VM:

TestWin12-01

Hyper-v VM components

image

This is best to describe what components a VM would have.

VHDX File

clip_image002

This is main disk file which contains all data, similar to vmdk file. The vhdx is the new format while the old format is called vhd which MS strongly suggests you to upgrade to vhdx due to possible data corruption.

The size of file is depending on what kind of disk you are choosing. If you choose Dynamic disk, then it could be small file like less than 10GB.

 

AVHDX File

AVHDX is the snapshot of that VM which basically increases size every time when you write to your VM. MS strongly suggests DO NOT use snapshot but I found it comes quite handy. Especially, you can always vMotion it or storage vMotion snapshot with VM.

Configuration File

clip_image002[5]

This lovely xml file is using computer GUID as file name. Yes, GUID not the name of your VM. So basically, it makes me very hard to locate configuration since there is no option for me to see what VM GUID is from Hyper-v Manager.

Imaging if you put all vms’ configuration files in the same folder, how can you tell which one is which one? so the best practise here is to put each VM in the separated folder.

P.S: You do can move files around later on.

Here is Powershell which helps you to fetch GUID

Using PowerShell you can find which GUID belongs to which VM.

 

PS> get-vm | ft -autosize vmname, vmid

 

VMName                 VMId

——                 —-

… 2012 DC            a1e1ab6b-a595-4089-bd9d-ab2040f3f603

2008 R2 Cluster Node 1 dbee3803-bf07-423d-84b7-3e0f98fafe2c

2012 Cluster Node 1    f3f0f575-1f00-4b4a-a07d-eb674c771bb5

2012 Cluster Node 2    6d10d079-90b4-4366-abc7-8df9ab4b3c60

 

PS> get-vm -id 6d10d079-90b4-4366-abc7-8df9ab4b3c60 | ft -autosize vmname, vmid

 

VMName              VMId

——              —-

2012 Cluster Node 2 6d10d079-90b4-4366-abc7-8df9ab4b3c60

 

 

BIN File

clip_image002[7]

BIN file is basically VM memory dump file. It is sued to recover your VM from fast turn on and turn off. For example, if you restart your Hyper-v host without shutdown VMs running on it, you will find all VMs are still in last running status after reboot hyper-v host. It’s quite good feature. Again, the size of BIN is the size of memory you assigned to your VM or if you are using dynamic memory, then that’s how much system gives to it.

The funny thing about BIN is you can’t put it into separate folder away from your VM. If you review VM configuration file (XML file) you won’t find setting for BIN.

I think this is very important feature like Vmware swap file. You may want to collect all swap file in one location rather than attaching with VM so you will be able to estimate how big VM folder will be.

Well, you do can turn off BIN file though, by changing following settings to Option 2 and 3.

clip_image002[9]

Once you are done that, you will see the size of BIN is 0, but again, you loss that useful feature of saving VM state.

P.S: If you are using DC as VM, please do choose Option 3. You don’t want to mass up with AD from saving state.

Smart Paging File

Well, this is rarely used or even appear. This file will appear only there is no free memory available and you want to start your VM. The system will use disk as memory (Minimum memory setting of your VM) to start your VM.

vMotion and storage vMotion

There is no doubt that Vmware is first company starting using vMotion and storage vMotion. But MS is the first company using storage vMotion without cluster and share storage. I guess this is dramatically disturb Vmware’s plan and they also announce vSphere 5 can do the same thing.

Anyway, let’s briefly go through what Hyper-V does for vMotion and storage vMotion.

If you go to Hyper-v Manager, right click VM you want to move

clip_image002[11]

You get this interface.

image

That’s right. There is no other option it’s just move. You can choose to move to different host or same host but different file location.

Let’s say if you choose option 1

clip_image002[15]

Type the other host name here

clip_image002[19]

If you choose Option 3

clip_image002[25]

That’s where you can choose destination location. Now, be aware that the destination folder need to have write permission and also permission to register VM into Hyper-v host.

clip_image002[1]

clip_image002[3]

clip_image002[5]

clip_image002[7]

clip_image002[9]

Please any feedback if you want. More posts are coming.


So one of most common software is Microsoft Office 2010. We all want that software be installed regardless it’s on physical machine or VDI. There are so many different options you can choose and you may face. This post is focusing on deploying Microsoft Office 2010 to VDI via App-V.

 

Why do we need to use App-V?

App-V allows user to steam down application parts which this app really needs when it runs. With VDI solution, if we don’t use App-V, we may install entire Office 2010 on each VDI VM and if you have 100 VDI VMs in your environment, it may use 200 or 300GB precious SAN space easily just for this software only. With tons of benefits of using App-V, I am not going to explain it too detail.

 

Why don’t people use App-V Office?

Well, reason No.1, it’s complicated. With using App-V, it involves so many different other technologies and all of them have to work together. Second reason is App-V still has some limitation with one app working other app since each App is supposing to work in it’s own sandbox. But this is going to change with App-v 5.0 sp1 and other tools to help you deploy office.

with no further ado, Let’s start

Environment introduction

Server:

Testhyp02: Windows 2012 with Hyper-v running on it, App-V Server & Management component has been installed. For more details, please to see my last post.

Workstation:

All workstations are VMs running on Hyper-v.

You will need to have at least two workstations.

VM1:

Windows 7 SP1, 32bit (As App-v Sequencing server to catch software installation)

VM2:

windows 7 SP1, 64bit ( As VDI template to run App-V software).

Note:

You must use Windows 7 with Service Pack 1 as client. Win7 without SP1 doesn’t support App-v Client. You must use 32bit for App-v Sequencing server since there are certain software which only has 32bit version!

Preparation for your VMs:

Now, I must ask you to focus on preparation of your VMs before you start installing.

  1. Build windows 7 32bit SP1 VM from scratch. (64bit if it is VM2)
  2. Make sure you have installed Integrated Service
  3. Make sure you have join the VM into your domain
  4. Disable firewall
  5. Create Install folder under c:\

 

  Search Internet and download following software on your c:\install\Other Toolsclip_image002

Notice: You need both 32bit and 64bit Powershell to install on VM1 and VM2.

6.    Install above software

7.    Download following software and put into c:\install\AppV Prep

clip_image002[5]

                 You need both 32bit and 64bit version of Deployment Kit

  • Office 2010 SP1 Professional Plus 32bit ISO (extract to a folder)
  • Office 2010 SP1 Profession Plus Volume License (XXXXX-XXXXX-XXXXX)
  • Microsoft Desktop Optimization Package (It contains App-V 5.0 sp1 non RDS client)
  • Microsoft Application virtualization 5.0 SP1 (from Volume License Portal)

 

 

You need to extract Office Deployment Kit to separated folder like above picture shows. Also extract Sequencing kit.

clip_image002[7]

clip_image002[9]

Extract Office 2010 Professional Plus ISO (must be 32bit) to a folder. Only 32bit Office will work with integration and it can work on both 32bit and 64bit Win7.

Copy App-V_Seq_Kit into Office folder and also Deployment kit as well

clip_image002[11]

 

clip_image002[13]

 

Deploy Office 2010 App-v Kit

There are lots of articles about it on the Internet. In this case, I’m using MAK to register.

image

Few things about this deployment.

1. Must use elevated CMD to run this command

2. Must NOT USE Powershell to run, it won’t work

3. When it is running, don’t jump on Services.msc to check what’s New, it will crash the installation

 

So what this command does is to install a License service like KMS in local PC with Volume serial number of Office 2010 to make sure Office application works correctly.

After installation, you can open servcies.msc and see whether it works or not.

clip_image002[27]

 

Install App-V Sequence

Install App-V Sequence on VM1 which is running windows 7 sp1 32bit with “Other Tools” installed first. Add IP address, DNS, Join domain, disable firewall and copy all above software on the VM1.

You shouldn’t have issue to run App-V Sequence

clip_image002[15]

clip_image002[17]

clip_image002[19]

 

Run App-v Sequence and do following steps

clip_image002[21]

Add keys like following

Open the "Exclusion Items" tab and add the following: [{Common AppData}]\Microsoft\OfficeSoftwareProtectionPlatform [{Common AppData}]\Microsoft\Windows With Mapping Type = “VFS”

clip_image002[23]

 

clip_image002[25]

 

 

Capture Office 2010 with Accelerate Package

Yes, you are very lucky that Microsoft has this accelerate package which does lots of work for you.

Now, it’s time to start App-v sequence

clip_image002[29]

 

clip_image002[31]

 

clip_image002[33]

 

clip_image002[35]

If you don’t have AP, you have to capture office installation procedure and hope it’s clean capture!

clip_image002[37]

 

clip_image002[39]

With AP helps, system all generate 3 copies of appv file with some modification in each. All what you need is the last version with integration embedded.

 

clip_image002[41]

 

clip_image002[43]

 

clip_image002[45]

 

Following is the first version.

clip_image002[47]

Continue to capture running parameters, do not run Sharepoint and Outlook components

 

clip_image002[49]

clip_image002[51]

clip_image002[53]

 

clip_image002[55]

 

clip_image002[57]

 

clip_image002[59]

 

Now, start to integration procedure

clip_image002[61]

 

clip_image002[63]

clip_image002[65]

You need to be patient since VM1 is loading 1.5GB office installation appv file.

 

clip_image002[67]

 

clip_image002[69]

 

clip_image002[71]

 

clip_image002[73]

Save as your package to new folder

clip_image002[75]

 

Deploy Office 2010 with App-v

Add your App-V package

clip_image002[81]

 

clip_image002[83]

Setup connection group and grant domain users group permission to connect

image

 

Setup Package access permission with domain users

 

image

 

image

Log on Publishing port to test

If it is empty like below, then it’s time to run IISRESET on app-v server.

clip_image002[85]

 

check again

clip_image002[87]

 

Deploy on VDI client

This is VM2 which needs to install all “other tools” list above.

App-v client must be installed on this template machine which will be used to deploy VDI.

There are two typies of Client. with RDS and without RDS. With RDS version is used in Session Host. In this case, we use without RDS version.

clip_image002[89]

clip_image002[91]

 

clip_image002[93]

 

image

clip_image002[99]

You also need to run Set-AppvClientconfiguration –EnablePackageScripts 1

 

image

 

Wait for 5 mins, Office applications should be push down to this client

clip_image002[101]

 

clip_image002[103]

Prepare VM for VDI

 

clip_image002[105]

 

Once you create new pool and deploy VM as VDI, the Office 2010 will just work. Winking smile

 

Please leave any feedback.

 

 

Reference:

How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0 using a Package Accelerator


Well, with my last post, I was not able to join Hyper-v 3 to SCVMM 2012 RC. Therefore, most of labs can’t be done. After I cried loud, our MS TAM help me to find a new copy of SCVMM 2012 CTP. This version is designed for Windows 8 and all functions are in Go status!!

With this exciting news, I managed myself (thanks a lot to my team mates!) to get 3 HP G5 servers to build a test environment today. Just like all test labs, I spent lots of time to work hard to find solutions and I hope my post will save your time and let’s uncover Hyper-v 3 true power together!!

Again, if I made any mistakes, please feel free to point out.

Introduce my Test Lab:

My test lab involves 3 physical hosts in the same subnet. There is no FC SANs available nor NAS exists. Each Hosts has it’s own local disks. I installed Windows 8 Beta on all 3 servers since this is one of conditions to do labs. 2 Servers I have enabled with Hyper-v 3 and I installed SCVMM 2012 CTP on the last server.

Note:

There is no issue of installing Windows 8. But with SCVMM, you need to install AIX and .NetFramework 3.5. You can’t tick the .NetFramework inside of W8, that would fail with not able to download. What you can do is following:

And restart server afterwards

Hyper-v 3 Storage vMotion is quite good

The one thing Hyper-v R2 can’t do is storage vMotion. Without this feature, I’m not able to migrate a live VM from one share LUN to another shared LUN without powering off VM. In the Hyper-v 3, MS not only managed to do a share storage vMotion in a cluster with SAN, you can storage vMotion between two standalone Hosts with a windows 8 share folder (SMB 2.2) !! (No more expensive VSA?).

Create a share folder

Live Migration is just normal vMotion with disk files sitting on the share storage. In this case, it’s a windows 8 share folder.

Since I have only local disks, I want to have some shared storages as the part of habit I got from Vmware. With Hyper-v 3, all what you need is a Windows 8 server and create a traditional share.

That’s it. No drama. No need for any specific share rights. This share purpose is to enable you to see this share when you add it into VMM. Once it is added, VMM will modify the accessing rights.

There are 2 steps to add this Share resource. The first steps is to add it to VMM library. so all VMs will sitting on that. You also need to add share resource to individual hosts so VMM will add hosts ID to security list.

Add to VMM Library

Add to individual host

Once it is added, your host is able to migrate VMs to share library.

This is how VMM setup access rights on the folder.

Storage vMotion (between host and share folder)

Basically, you can migrate VM files from local disk of your host to a share folder and from share folder to share folder or move it back to local disk.

According to my calculation, there is no ping drop during moving. The ping value sometimes is increase from 2ms to 65ms.

Storage vMotion from host to host

It’s interesting that MS say Hyper-v 3 is able to storage vMotion between two standalone host but they recommend to do it with a share folder accessable by both hosts. So does that mean you can Storage vMotion + vMotion from Stand alone host to stand alone host?

From my test result, It actually tried but failed at 81%. What it happened was Storage vMotion kicked in and copied 9GB data from one host to another host. During the copy procedure, the ping value jump up to 600ms. But the file is copied completely. Then, ping drop back to 2ms and tried to translate the last bit in the memory and that’s where it failed.

Overall, Hyper-v 3 can do Storage vMotion and with at least 2 sessions at same time. The ping value jump up can be contributed with my 100Mbit/s network limitation. Hyper-v 3 can use a normal windows 8 share folder as storage space which saves tons of money. so no more NAS and VSA? The new Windows 8 vhdx supports 64TB so there is no worries on how big a single file can be.

Bugs I have found:

1.With Windows 8 beta, RDP connection seems dropped if I started to copy large files via network. The whole server actually seems to be frozen status until copy is finished. My guess is that W8 didn’t prioritize RDP over copy session.

2.When I storage vMotion a VM which use differencing disk, the original disk (or parent disk) are not moved with storage vMotion.


I was trying to install SCVMM 2012 to manage Windows 8 beta. But unfortunately, Windows 8 Hyper-v has some major changes in services and you can’t import any Hyper-v 3 beta into SCVMM 2012 RC at this stage.

 

I will confirm with MS and update it later.

 


Oh, OMG. The ugly Windows 3.1 style fish. ……

This is first feature I’m testing with Hyper-v 3. I personally is shocking with how good Dynamic Memory is. If I make any wrong comments in this blog due to lack of knowledge of Hyper-v, please leave comment. Thanks

We all know Dynamic Memory feature in Hyper-v R2. This is quite argument point between Vmware and Microsoft. Vmware claims they have Memory over committing, memory sharing(schedule not real time), memory paging and memory balloon technology. Well, Personally, I have to say Vmware has done great job to allow more VMs memory consumption then what a host can hold. It is hard to do it without knowing OS core to reuse the memory.

Microsoft, on the other hand, has Dynamic Memory. It allows you to “Dynamic using memory” by setting up lowest memory and maximized memory for each vm. Well, to be honest, I’m not very interesting about this tech since it’s very similar as what Vmware does.

Now, thing is completely different from Hyper-v 3.

You can increase your vm memory on the fly!

Yes, Vmware can do same thing long time ago. I used to write a post about it. However, it can only happen to Windows Datacenter version. Vmware does that by physically plug in virtual memory DIMMs into OS hardware. However, only Windows Datacenter level has capability to pick them up and add them into OS on the fly.

Hyper-v 3 does that with almost every Microsoft system. Following is the list.

  • Guest operating system Editions Configuration requirements
    Windows Server 2008 R2 Standard and Web editions Install Windows Server 2008 R2 SP 1 in the guest operating system.
    Windows Server 2008 R2 Enterprise and Datacenter editions Do one of the following:

    • Install Windows Server 2008 R2 SP 1 in the guest operating system.
    • Upgrade the integration services in the guest operating system to the SP 1 version.
    noteNote
    Installing Windows Server 2008 R2 SP1 is the recommended method because it provides the added benefit of installing all updates included with SP1.
    Windows 7 Ultimate and Enterprise editions (32-bit and 64-bit) Do one of the following:

    • Install Windows 7 SP1 in the guest operating system.
    • Upgrade the integration services in the guest operating system to the SP1 version.
    noteNote
    Installing SP1 is the recommended method because it provides the added benefit of installing all updates included with SP1.
    Windows Server 2008 with Service Pack 2 (SP2) Standard and Web editions (32-bit and 64-bit) Upgrade the integration services in the guest operating system to the SP1 version.Apply a hotfix as described in article 2230887(http://go.microsoft.com/fwlink/?LinkId=206472).
    Windows Server 2008 with Service Pack 2 (SP2) Enterprise and Datacenter editions (32-bit and 64-bit) Upgrade the integration services in the guest operating system to the SP1 version.
    Windows Vista with Service Pack 1 (SP1) Ultimate and Enterprise editions (32-bit and 64-bit) Upgrade the integration services in the guest operating system to the SP1 version.
    Windows Server 2003 R2 with Service Pack 2 (SP2) Standard, Web, Enterprise, and Datacenter editions (32-bit and 64-bit) Upgrade the integration services in the guest operating system to the SP1 version.
    Windows Server 2003 with Service Pack 2 Standard, Web, Enterprise, and Datacenter editions (32-bit and 64-bit) Upgrade the integration services in the guest operating system to the SP1 version.

Let’s Testing!!

I tested both on windows 2008 R2 SP1 and Windows 2003 R2. The result is the same. As long as you install “Intergration Services Setup Disk”, you will be able to increase memory on any VMs on the fly!
First, I created a VM and go into settings.
This is the default settings of maximum memory settings. It has nothing to do with  your host memory. It’s just maximum figure of Hyper-v 3 can handle. We don’t want Hyper-v to handle all memory. so I changed this figure to 512MB also changed start memory to 500MB like following picture.
Then, I restarted W2K3 and you can see how much physical memory it has.  Please be aware this physical memory is just figure of minimum memory figure. It will increase with how much memory you consume.
Now, let’s change the maximum memory figure on the fly to 1GB!
Once you increased the memory, you won’t see it reflect to OS immediately. You have to use memory and beyond the current physical memory level. Let’s increase number of IE window from 1 to 102. -_-b
Amazing! isn’t it?
Few other points:
At Hyper-v 3, you can increase maximum memory but you can’t decrease them on the fly! You do can decrease minimum memory memory on the fly although I don’t see much point here.
Hyper-v 3 supports balloon technology as well. The smart-page feature may contribute some scenarios with HA. But I haven’t got time to test it.
More features updates are coming. Please stay in tune. 🙂
Reference: