separte the service console

[xooops]

Hello

I should setup 3 new hosts which have only local store. On this local storage we have to run three VM’s. I’m thinking about to separate the data store which contains the service console from the data store which contains the vm’s. With that setup I hope to have the most flexibility for the further regarding knowledge with block size or re format.

Does anybody have the same idea? Or I am absolutely wrong?

Thanks, Sven

[AWo]

I do not get your point exactly.

The guests are stored on vmfs volumes and the console runs on the local ESX partitions. That is how a host is setup. What is left to separate?

AWo

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

[xooops]

Hello

Hm, I think the service console runs on vmdk which is on the same vmfs as local vm’s run. I would also prefer to run the vm’s on a 8MB block size vmfs.

-Sven

Example

Raid 10

-viirtualdisk1

--datastore1 1MB block size

---service console vmdk

-virtualdisk2

--datastore2 8MB block size

-- vm001 vmdk

-- vm002 vmdk

-- vm003 vmdk

[xooops]

That's an other reason for me to separate the COS VMFS from the running VM's VMFS

http://communities.vmware.com/docs/DOC-10510

Note that the first VMFS volume of a ESX 4.0 could not be aligned:

the reason is that the volume contain the COS vmdk, so is not possible to free the volume to do the alignment.

-Sven

[DSTAVERT]

Automatically created VMFS volumes should already be aligned like those created with the vSphere client. I would check to see if this is really a problem.

fdisk -l

>Partition 1 does not end on cylinder boundary.

should show you whether it is a problem or not.