Skip to main content

Windows 8:- Dynamic Memory Enhancement

Well, dynamic memory is one of the features available in Windows Server 2008 r2 SP1. I do hope that you have tested dynamic memory. Let have a look on Dynamic memory Enhancement which available in Hyper-V Vnext (Code name that I give for new version of Hyper-V in Windows Developer Preview).

Note:- Subject to change and feature is available during my testing using Windows Developer Preview Edition.

Enhancement #1:- Dynamic memory options is available when create a new Virtual Machine. Previously, you can only configure static memory when provision Virtual machine.

Enhancement #2:- Dynamic Changing of Memory when Run Time. That's mean you no longer need to shutdown the Virtual Machine when you want to configure Min and Maximum Memory. You can change the amount of memory when VM is up and running. Find it quite useful especially the Vm has hit to Maximum memory and i can easily increase the amount of memory.

Enhancement #3:- Ability to configure Minimum Memory.





Initially we allow to configure
a) startup memory- amount of memory to use during boot up
b) maximum memory - amount of memory that VM can use.

Now
c) minimum memory - minimum of memory that VM can shrink. This is quite useful for increase the ratio of VM that we want to host. We often saw the memory demand is less but due to Microsoft support policy on certain amount of minimum memory to start up memory, then we need to follow to the policy to avoid any issue. Therefore, we assign the exact startup memory. However VM detected VM does not require that much of memory. So you can consider it is a waste. With minimum memory, we can use the memory as mentioned in the start up and able to shrink until minimum memory when require. This concept is use balloon technique.

Refer to attached diagram above and you will see that
VM boot up - using 512 MB
Minimum memory configure 128MB
From Assigned Memory column, it has shown 321MB rather than 512MB.

For Maximum memory, do i allow to memory over-commit? Well, the answer is "No". So please do not configure more than what is available on your physical Hyper-V Server.

Popular posts from this blog

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N...

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this...