Thursday, April 12, 2012

Adjusting a VMware View 5.0 linked-clone pool’s virtual desktops’ memory

I’ve been asked a few times as to what was the best way to adjust a VMware View linked-clone pool’s virtual desktops’ memory and I have to admit that I never really tested all the possible ways so I’ve always suggested people to edit the master image’s memory and then recompose the pool with a new snapshot.  Since I had to do some maintenance on an environment that is over the N+1 capacity today (I’m going to lower the memory on the virtual desktops to bring it back to N+1), I thought I’d try out different operations to see what would happen and what I discovered was that the way I’ve been doing it appears to be the only way that reconfigures the linked-clones.

Methods that don’t work:

  • Edit the master image’s memory and then refresh the virtual desktops:

image

  • Edit the master image’s memory and then recompose the virtual desktops with the same snapshot that the virtual desktops are already using (you’ll notice that your virtual desktops don’t actually get recomposed):

image

What does work:

Edit the master image’s memory:

image

image

Create a new snapshot for the master image:

image

Recompose your pool’s desktops:

image

Select the new snapshot:

image

Recompose.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------

An alternative way of doing this is to manually shut down the virtual desktops and adjust the memory but if you opt to do it this way, it’s important that you update the master image’s memory and snapshot it again with the new settings.

No comments: