VMware

This Question is Answered

1 "correct" answer available (10 pts)
7 Replies Last post: Mar 16, 2006 11:02 PM by ly9cs  

what type of volume ? posted: Mar 15, 2006 3:33 AM

Click to view ly9cs's profile Enthusiast
ly9cs
40 posts since
Apr 20, 2005
Hello
I have got a IBM 346 that I have installed a ESX server on. It is only a trailversion of ESX. This is for my own education and to present ESX to my company.

Now I have a some questions.

The server has 2 disk raid 1 (vmhaba0.0.0)which I have installed the ESX on. The rest of the disk are raid5 (wmhba0.1.0 205 gig)

My plan is to use hba0.0.0 only for the esx os and the rest of the disks for clients.

Now my question.
Is it only to add a disk in the webadmin gui for the clients ? If so ? Does it matter what kind of area it is ? I have done it as public now.
Since this only a demo to my friends at work this might not be important but I want to do this correct from the start.

Is this the way to do it ?

Re: what type of volume ?

1. Mar 15, 2006 3:56 AM in response to: ly9cs
Click to view MR-T's profile Champion User Moderators
MR-T
4,146 posts since
Apr 19, 2005
Public is fine, this is the default.

Re: what type of volume ?

2. Mar 15, 2006 12:15 PM in response to: ly9cs
Click to view maxtrax's profile Enthusiast
maxtrax
56 posts since
Apr 27, 2005
Since the ESX install is on your hba0.0.0 and your RAID 5 is for your Virtual Machines, you will create your VMFS volume/s on there. VM disk files can only exist on VMFS volumes. When you go through the VM creation wizard you will create the VMDK disk file on the VMFS volume. It will be in public mode. Shared is for doing clustering between VMs.

Re: what type of volume ?

3. Mar 15, 2006 12:57 PM in response to: maxtrax
Click to view jasonboche's profile Champion User Moderators vExpert
jasonboche
5,918 posts since
Jan 7, 2004
Shared
is for doing clustering between VMs.

Clustering across ESX hosts.

Re: what type of volume ?

4. Mar 16, 2006 6:17 AM in response to: ly9cs
Click to view ly9cs's profile Enthusiast
ly9cs
40 posts since
Apr 20, 2005
Thank You, Thank You, Thank You !!!!!

But......
When I try to add a hos it allways end upp in
/root/vmware/win2000Serv/win2000Serv.vmx

What shall I do to get it to the raid 5 disk. Correct me if I am wrong but on the above path my client will end up on the raid1 disk. As I statet before I think it would be great to separate the ESX os and the client.

What shall i wright as the path to the raid5 disk ?
Can I make this path permanent for all new clients

Re: what type of volume ?

5. Mar 16, 2006 6:49 AM in response to: ly9cs
Click to view Ken.Cline's profile Champion VMware Employees User Moderators vExpert
Ken.Cline
5,156 posts since
Jul 7, 2004
The .vmx file is simply the configuration file for your VM. The file you're primarily concerned with is the .vmdk file (your virtual disk file), that you allocate further into the VM creation process.

Re: what type of volume ?

6. Mar 16, 2006 6:56 AM in response to: ly9cs
Click to view nkrick's profile Hot Shot
nkrick
136 posts since
Jan 3, 2006
In ESX 2.x, the .vmx file, .nvram, and .log files go on the Linux COS file system. the disk (.vmdk) files go on the VMFS file system. VMFS 2 is a flat file system with no directory support.

Re: what type of volume ?

7. Mar 16, 2006 11:02 PM in response to: nkrick
Click to view ly9cs's profile Enthusiast
ly9cs
40 posts since
Apr 20, 2005
ahh...! thouhgt that was the file was the client....

Actions

VMware Beta Programs

Want to be Considered for Future Beta Programs?

Learn More

VMware Developer

Download SDKs, APIs, videos,
training, and more in the Developer community.

Learn More

Developer
Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld
Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

Only VMware ... Delivers Nexus 1000V

Ensure consistent, policy-based network capabilities to virtual machines across your data center.

Learn More

Communities