VM /ETC

Posts Tagged ‘resourcepools’

I thought I was done blogging about VMware Partner Exchange 2010, but, twist my arm, there seems to be enough public knowledge about an upcoming feature of vSphere that I thought I would briefly point it out.

Steve Herrod discussed in his Wednesday Keynote  that vSphere will soon have the ability to set DRS Resource Shares on I/O per VM. Here’s a photo of Herrod discussing the feature last Wednesday.

Other’s have posted on this feature this week as well as in the not to distant past. Check out these posts for more info:
Read the rest of this entry »

It’s been well publicized that Microsoft’s System Center Virtual Machine Manager (SCVMM) can manage VMware Virtual Infrastructure. In fact, Microsoft has demonstrated that SCVMM can initiate virtual machine (VM) VMotions between VMware ESX hosts. However, Eric Gray points out on his VCritical blog that if you use SVCMM to VMotion VMs that are members of ESX Cluster Resource Pools the Resource Pool membership disappears afterwords.

The following was taken from Eric’s post Don’t know much about resource pools:

“Now, let’s say that one of your fellow administrators wants to use SCVMM to manage this VMware environment.  He uses the SCVMM console to migrate a QA virtual machine from one ESX host to another in order to perform maintenance.

The VMotion completes without incident and everything seems OK…

Before too long, a QA engineer is on the phone asking what happened to his VM.  From his perspective, the VM has disappeared.

It’s not really gone, it has just been moved out of the resource pool.  Fortunately, you can log in with the VI Client and fix this problem by moving the VM back to the resource pool.”

I must first admit I have not done this personally, but I assume 2 things are happening here.

Read the rest of this entry »

Look for a new VMware KB article in the near future for this VMware VDM error.

I helped implement a VDI solution for a customer that ended up revealing an issue with VMware Desktop Manager (VDM) 2.1 and the resource pools of an ESX Cluster. The explanation of the problem to me was that the VDI desktops auto-deployed via persistent VDM pools were out of sync with the ESX resource pools they were members of, and therefore new VDI desktops could not be cloned by VDM. That’s a little confusing I know, so I’ll try to explain it better by providing the sequence of implementation steps that resulted in the issue.

Here’s how it happened. Read the rest of this entry »