![]() ![]() Now the size you pick also depends on if your going to use snapshots, and for how long, and for how many VM's. I just add 15GB to whatever the total of all the VM's is. Size of all my VMDK files (virtual disks) + size of the memory assigned to the VM + 1GB for general files associated + 15GB = Lun size Now mind you this is 15GB free after the VM's are turned on. I generally want 15GB of free space on my lun no matter how many VM's I'm running. If you see a lot of ballooning (this is the process of the ESX server reclaiming memory from the VM) then you'll start seeing performance problems. It not quite as bad to overcommit memory, but you'll want to watch that too. If you drop the vCPU's down to 2 on each VM, there will always be free threads available to the physical CPU's. This means that 2 VM's will have all 8 CPU's tied up. ![]() This is because when a VM make's a call for CPU time, each vCPU needs to attach to an HEC thread on the physical CPU. ![]() For example if you have a ESX server with 8 CPU's, and you have 4 VM's with 4 vCPU's each, you will see significant wait times with cpu usage. What I mean is only give the VM what it needs, especially where CPU is concerned. In the VM world, when you start dealing with many VM's, less is usually better. This means that the largest single VMDK file or Virtual disk you can have is 256GB. When you create your VMFS volume, the 256 Max file size is not relevant to your lun. You do however have to have the Enterprise Plus license, shared storage, GB connections, and supported processors for that to work. FT allows you to have a live secondary VM in case your production VM goes down. I've learned a lot in the past few days, but I have a long ways to go. Thank you for any help you can pass along. i was testing some file copies to the system disk and as I got it down to around 4 GB free, the VM would crash. I ask this because while I was waiting for some more hardware to come in on the blades, I did a test install and VM setup, using Thin format that time on the datastore. I'm a little worried even if I pick 125 or 120 GB size for the datastore and it works to get the system up and running, is there really enough space for VMware files even though the system IS running now. will vCenter server be able to migrate the VM off of that host onto another blade? If so then this really isn't an issue. When creating the VM, can I use the Internal disk to the blade to store the VM files, and then just map the SAS storage to the VM and install windows on those? But if I do that. not sure if having that up would help some of this setup or not? When I mapped the storage to the system in vSphere client I used the option of 256 GB max file size, and 1 MB block size, and leave the radial for maximize capacity clicked. I was under the impression that this was needed in order for VMotion to be able to migrate VM's as needed? I do not have our vCenter Server running yet, waiting on some hardware to come in a couple days. During the creation process, for the location of the datastore I'm using the LUN on the DS3200, I enter Datastore size of 130 GB (Available space says 135.5), and I click the radial for Support clustering features (FT). Unfortunately, the project already has the 12 drive slots filled for the creation of the three VM's, so we would have to buy another DS3200 to add-on.Īs I said, I'm completely new at this though.Maybe I'm creating the VM wrong? We have some training material on the way. On this particular LUN they want two 36 GB Partitions and one 73 GB partition, and we are mirroring two 146 GB drives, after the Array creation (RAID 1) of the two 146 GB drives we only have 136.23, then down to 135.5 after VMware provisioned 500 some odd MB when adding the storage device to the System. Is there a rule of thumb for how much space to leave on the LUN for VMware overhead? I read on a post here 20%? If that is the case we will probably have to order more drives in order to meet the space requirement configuration for the project we are working on. I tried to make the datastore size 132 GB, but the VM would not start with the error "Insufficient disk space on datastore" I tried 130 (leaving 5.45 GB free), and had the same problem again. I'm not sure how much overheard VMware needs for its files though on the datastore. I'm trying to get the guest operating system installed (Windows server 2003 ENT), but when I create the new Virtual machine and map the LUN we are planning to use for the OS / SQL disk, it says I have available 135.5 GB. We added the two 73 GB of internal drives (Mirrored) to the blades for ESX install to boot from because at this time it is not supported on the DS3200. We are running HS22's Blades and have a DS3200 for our SAS storage. I've just started at this shop and I am completely new to VMware, and, Blade configurations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |