Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

R

rene11

1 Rookie

 • 

74 Posts

6594

February 14th, 2011 06:00

vmware datastore distribution 'free space'

We are using VDI with vmware and use the auto expand function from quest.

During the setup you can specify how the machines are distributed across the datastores. We use the setting 'Distribution: Free Space'

So we have different datastores and newly created VDI's should be distributed on storge whith the most free space.

This function does not work when you are using 'auto expand'. It always puts the new machines on the first datastore.

I created a case for this when we where using vWorkspace 7.0

Now we are at 7.2, but it still doesn't work.

Case =  813636

Any idea's when this is being fixed?

1 Attachment

DELL-David Y

228 Posts

February 15th, 2011 11:00

Hello Rene,

Can you tell me are you creating linked clone VM's in the usage scenario above?

We only allow creating linked clones on the datastore on which the parent VM resides.
Regards
David

rene11

1 Rookie

 • 

74 Posts

February 16th, 2011 06:00

If you can take a look at the case number (813636) you can see we are not using linked clones and this bug has been identified already.
What I'm asking is: Should this bug be solved by now. In other words, should this be working the way it is designed?

What I'm seeing over time is that the first diskpool is always filling up. So every monday I'm storge-vmotioning VM's to the other diskpools.

rene11

1 Rookie

 • 

74 Posts

February 23rd, 2011 07:00

Hello, what is the best way to get this fixed?

I made a case a couple of months ago, but it seems there is no progress

DELL-David Y

228 Posts

March 1st, 2011 07:00

Hi Rene,

The datastore distribution problem that you encountered was verified as a product defect, TT 2268. I can tell you that this problem has now been resolved and will be fixed by vWorkspace 7.2 MR1, which is scheduled for release in April 2011.

DELL-Adam Dr

28 Posts

March 1st, 2011 18:00

Rene/David,

There are two related issues at play here.  The first, as David mentioned, is internal issue TT2268, and has to do with the datastore free-space information not being imported and updated in our database before doing an auto-expand.  This has been fixed, so that the auto-expand free-space distribution works off of accurate free-space information.  There is another related issue, which may or may not be fixed, which we are looking at right now.  This issue may arise when auto-expand adds a single machine, or very few machines.  In this case, the distribution algorithms may allocate machines to datastores incorrectly, in a manner consistent with what Rene is witnessing.   We'll keep you posted...
-Adam

rene11

1 Rookie

 • 

74 Posts

March 2nd, 2011 07:00

Adam,

The second issue you explain is exactly what we are experiencing.

The first issue is not a big deal. We can manually refresh the datastores every now and then. But the second one is a problem.

Because new users never login at the same time, but one at a time, new VM's are created one at a time.

I would expect vWorkspace would put a new VM on a datastore with the most freespace, however it puts it on the first datastore.

Over time you end up with the first datastore completely full.

DELL-Adam Dr

28 Posts

March 2nd, 2011 13:00

The first issue is not a big deal. We can manually refresh the datastores every now and then.

Rene, this first issue is fixed in 7.2.

rene11

1 Rookie

 • 

74 Posts

March 2nd, 2011 14:00

You mean 7.2 MR1?

rene11

1 Rookie

 • 

74 Posts

March 2nd, 2011 15:00

Oh ok. I was a bit confused because of David's reply:

David Young wrote:
I can tell you that this problem has now been resolved and will be fixed by vWorkspace 7.2 MR1

DELL-Adam Dr

28 Posts

March 2nd, 2011 15:00

No, 7.2 RTM.

Was this post helpful?

View All

No Events found!

Top