using SATA vs FC in Lab Manager

Hi, I'm new to Lab manager and we have noticed performance using LM, however by using virtual machines in Virtual Center have no problem. What are some bottlenecks, that I should look for? We use Server 2 GB for Lab Manager, Server 2 GB for VC, and two 32 GB connected SATA ESX servers. Upgrades to CF help considerably?

upgrade to FC shared will help a lot; SATA performance tends to be pretty poor and lose you out on the opportunity to share storage, but it is especially in the field of the performance of the virtual machine, which apparently is acceptable when it is directly accessible from VC.  I'll come back later.

Check use of memory on the servers of your LM and VC - the task manager's performance tab should be sufficient for this purpose.  If your use of the page file seems to be high, probably, and the biggest single performance gain noted by increasing real memory of the system in question.  2 GB seems reasonable, but you very well may benefit considerably with 4 GB of ram real at the VC server.

CPU utilization must above all be a non-issue.   I run my setup of LM in a virtual machine with a maximum of 512 mhz of limited resources and do not tend to notice the important, long cpu to load.  Memory is always the killer.

You can also Alternatively take advantages by adding a third win2k3 machine in the mix to install an external full version of MS SQL Server for your VC, rather than the bundled sql express - especially because it divides the workload on the vc server, that tends to get hammered by the demands of LM.

Network topology could be a problem.  From the sound of it, you have a LM separate, physical server and a server VC separate, physical, as well as some ESX servers.  Is the networking between the four devices complex or distorted? There are benefits to the use of the network paths separate for network LM/VC-esx service console that use virtual machines, and there are certainly benefits to all local to the other servers.

Or, Alternatively, if your LM and VC are actually themselves VM within your esx servers, you can save significantly by giving them minorants of resources and prioritization of memory/cpu to 'high' whereas they are less likely to get private by ESX resources.

Meanwhile, your virtual machine performance.  Director of the laboratory, because of related clones, use the drive a little differently, in order to really start to lose with the absence of tagged command queuing, rewriting, and other features in a high performance SCSI configuration, because an operation of e/s "sequential" may eventually be scattered all over the disk.  At the very least, a GNU / linux external and a high performance + disks SCSI controller, shared nfs or iscsi to your esx boxes should give significant benefits (especially if you can do an isolated for this traffic network) in the area of how to perform your VM.  Naturally, the CF will be faster, but there will be $$ involved.

Tags: VMware

Similar Questions

  • Why move them to the bottom of empty in VMware Lab Manager when you use Firefox 4 +?

    When using Mozilla Firefox 4.0 or later, drop boxes in VMware Lab Manager are populated is more if it is not possible to deploy new virtual machines.

    It turns out that VMware has released a Lab Manager in August (4.0.4) update that resolves this problem. I upgraded to LM 4.0.4 and dropdown lists are now met again.

  • Using Server 2008 R2 64-bit models in Lab Manager 2.5

    I created a template with Windows Server 2008 R2 64-bit; enabled installed VMware tools and LM.  But when I use the model in a configuration that the LM does not seem to work, the machine is not renamed, and now is waiting for activation.  Also, I get an error when the virtual machine tries to run the autoconfig.vbs on login.

    I understand that LM 2.5 does not support Server 2008, but is anyone aware of any workaround that I can put in place for this model is available to be used.  I really don't want to have to active post that we have only a limited deployment configuration Server 2008 activation available.

    All suggestions are well appecicated.

    -Greg

    Greg,

    Lab Manager 2.5 is not a the code for Windows 2008 R2 support.  Even if you have a template, it will customize ever since LM tools does not even what is Windows 2008 R2.

    The activation of Windows 2008 R2 component is due to hardware changes in the deployment of the model (new SID, UUID, NIC MAC addresses) and is a bit of a wait.

    I don't know of a workaround or the other and I have a kit of Lab Manager 2.5 around tinkering with since it's already past end of life care.

    Kind regards

    Jonathan

    B.SC., RHCT, VMware vExpert 2009

    NOTE: If your question or problem has been resolved, please mark this thread as answered and awarded points accordingly.

  • Using Lab Manager API Java code example

    VMware or anyone have a sample code for using the API in Java? I mean, I have the host name, user name, password, I would not immediately be able to use the API to write my automation tools? spend hours finding the right pots, generating all these strains and write my own code (100 lines) just for connection resembles a maddness for me...

    -J

    After posting my original answer, I remembered that I had posted a code on this forum before. It's a stripped down version is about what would later become the LabMinder code I mentioned previously.

    If you go to the post office: Re: sample SOAP API for Lab Manager in necessary Java at December 20, 2007 by Michael Ottati you can retrieve the zip file in.

    WSDL changes made by new VMware to display require 2 changes to the code for the example to complie. Two of these changes please refer to the HelloLabManager.java

    1: change the world

    VMwareX0020LabX0020ManagerX0020SOAPX0020Interface to LabManagerX0020SOAPX0020Interface

    2: change the occurrence of:

    VMware_x0020_Lab_x0020_Manager_x0020_SOAP_x0020_interface to LabManager_x0020_SOAP_x0020_interface

    I have made these changes and zipped the original example here. This has been tested now with under jdk1.6.0_11 and LM 3.0.1

  • Can I use Lab Manager with VirtualCenter Server Foundation

    Hi, now I'm choosing the license type for my gateway.

    Regarding now I can't manage through Virtual Center more than 3 knots.

    But I have a question. Can I use VirtualCenter Server Foundation License with VMware Lab Manager 3.0?

    You can use vCenter Server Foundation with PF3. We currently have 3 standard ESX licenses and a vCenter Server Foundation and it works very well. The only limitation is that you cannot manage more than 3 guests, but in your case it does not appear that it will be a problem.

  • VCenter Lab Manager 4.1 Linked mode

    Hello

    What is someone using a vCenter Lab Manager 4 configured in bound mode?  I would like to activate the connected mode, searching for traps that everyone can share.

    Thanks in advance

    No traps.  Bound Mode is independent of Lab Manager.

    Please be aware, Lab Manager works with exactly a vCenter and a data center object inside this vCenter.

    So once you activate the bound mode, you won't see all the resources here.

  • Lab Manager 4 will not release the license after the removal of host.

    Hey there,

    I am running Lab Manager 4 in my infrastructure.  I recently added a lot of CPU 2 and licensed.  Shortly after, I removed the host of Lab Manager, but he has not published the 2CPUs of licensing - which means that I am able to use my license 2CPU part to add new hosts.

    No idea how I can get the license for free?

    Thank you!

    You must "unprepare" this ESX host in the laboratory Manager.

    The 'prepare' function consumes your license, and similarly "unprepare" frees.

    This ESX host appears in the overall organization > resources > Hosts?

    Best regards

    Jon Hemming

  • vCenter 4.1 update level & Lab Manager

    Hello

    I upgraded to vcenter 4.1 and have begun upgrading our 4.1 esx host.  We have a Lab Manager cluster and I got to spend 2 to 3 hosts for ESX4.1... Currently, all Lab manager VMs are running on the ESX host 4.0 remaining in the cluster of Lab Manager.  I'm unable to migrate virtual machines to host 4.0 to ESX 4.1 two other guests offshore in this cluster to improve this host to esx 4.1.  When I select a VM to migrate, I get the following after error message select a host ESX4.1:

    "A general system error.  The virtual machine requires labmanagerhostserver/system.service.vmware.vsla labmanagerhostserver service, which is not available on this host "."

    Before the upgrade to vcenter 4.1, Director of the laboratory has been upgraded to 4.0.2

    Any hellp to resolve the above error is much appreciated.

    Sorry to hear that.

    I myself have strange problems with 4.1.

    I have stopped using 4.1 at the moment and re - install 4.0 on all new blades instead.

  • Storage for Lab Manager

    My client needs storage for Lab Manager running on 100 servers. Is it recommended to use the NAS or SAN for Lab Manager running and what type of e/s that you wait for the same thing?

    I did a little bit with storage of LM in recent years.

    I have a development/test environment on LM 600 machine, using 2 Sun 7210 storage devices (is no longer available) on NFS shares. We have 2 links 1 G servile vmKernel traffc as well as links to more vmnetwork, management, etc.  The devices are related to links of 4 x 1 G each.

    I don't know what are the current constraints of LM/ESX, but whenever we revisit the decision 'block vs NAS' we end up selecting NFS (our Sun boxes can present the iSCSI as easily).

    As Jon says, what storage you need certainly depend on your VMS and load.  NOTE: my experience is * NOT * in a production environment, where I am squeezing virtual machines performance.  It's more about the functionality and "adequate" performance (where "adequate" is a measure based on the user experience topic).

    Some things we have learned over the years:

    • IOPS / s are kings, and most of them are entries.  (Written at the moment, I have a few heavy ready operations push me down to about 65 percent.)  I saw > 80% of entries maintained for days.)
    • Latency does not seem as important - VMs run about the same at 10ms latency and latency 250ms NFS NFS.  When latencies above 750ms grows, they will be noticiable users and if they go more than a second over 1000 ms you will begin to see the impact on the guest OSes, especially Solaris x 86.
    • Normal operations don't care about bandwidth - just current execution machines don't even fill a link 1 G
    • Deployment operations * could * start filling to the top of the bandwidth, maybe
    • Betware storm IO.  Often people think the storm IO deployment/boot, but 400 RedHat machines all the kickoff of their 'updatedb' cron job at 04:00 can produce any IO storm as well.  NOTE: IMHO if you buy storage to handle this kind of thing, you're overpaying storage.  I've spread my cron through the night and now can not see on the graphs of storage performance.
    • There is * NOT * a good correlation between guest OS IOPS / s as shown, for example, iostat and PAHO are / s NFS presented to the storage system.  I'm guessing that ESX made a lot of caching.

    Most storage vendors I spoke last year does not seem to find it.  They think in terms of bandwdith and it accelerates with read cache, so unimportant in my environment - I had to push really hard to get sellers to think in the right conditions and some of them really seem out of their depth there.

    I think that this state of mind is important: consider the IOPS / s as you consider CPU: how much should I give to each machine?  How much should I oversubsubscribe?

    Like CPU, a physical machine which IO a lot more available that he needs and you can consolidate - but don't know how.  A physical machine with a pair of 15 k drives RAID1 has about 200 IOPS / s available and readers spend most of time inactive (a bit like the CPU).

    That will boost the machines and when?  Right now I'm on average 9 inputs/outputs by VM, which in my opinion is quite small.  My storage system can go higher under request, but I have enough machines that it is fairly constant.

    In my quest for the perfect storage of LM, I found the usual: good, not expensive or fast, you can choose any two.  How we use LM (lots and lots of shared models) we would really like a unique namespace shared (i.e. 1 data store). I have yet to find the 'perfect' - storage, the Suns are very profitable for the performance and space, but their management takes too much of my time and my 72XX are not expandable - the 74 might be a different experience.  I am currently looking to add some SSD storage, but the ideal configuration would be automated migratino between levels (for example, EMC QUICKLY) and if I bought only from EMC I would triple my cost per VM.

    I talked to people who have a pattern of use of different models that are quite happy on several data stores.  If you can move your load through many warehouses of data then Isilon looks like interesting storage.

    So, in summary:

    • Watch IOPS / s 1st, 2nd and 3rd, then the latency time, then (maybe) bandwidth
    • Manage the budget or the ability of the IOPS / s as you CPU
    • You may not use comments IOPS / s to provide shared storage IOPS / s

    I'm hoping to have a better storage solution in the next 6 months or more.

    --

    Dewey

  • Black Lab Manager VM Console under IE

    We start just our use of Lab Manager. Under IE8, windows 7 x 64, the console within EI, or separate window is black.

    Go to full screen displays the virtual machine properly.

    Under Firefox no problem?

    > > What is needed to make IE work?

    Thank you

    Hello

    I had the same problem and found this KB article which helped me to solve it: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1020474

    Hope it works.

    Kind regards.

  • Lab Manager licensing during the merger of vSphere environments

    Is there a small vSphere environment that is available for Lab Manager and a great environment vSphere and both are now completely separated (different vcenter servers, groups separated from ESX, etc.), and they are merged into one, what happens to the Lab Manager licenses?  Should be updated to take account of the increase in the number of ESX host in the new environment?  Environments can be merged without buying additional licenses?  If so, would be half the environment allowed for lab manager and others are not allowed?  How would the lab manager-under license, and lab-manager-without sections allowed environmental stands / separated?

    Thanks for your comments

    "Prepared" you went in in the section resources, hosts tab and see that the host is ready (green check mark), this means that there has been a 'prepare' to the host.  Prepare installs the agent LM, then she will deduct your license (settings > license).

    Kind regards

    Jon Hemming, b.SC., RHCT, VMware vExpert 2009
    http://Twitter.com/vJonHemming

    If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

  • Relationship of Lab Manager and vSphere

    My shop starts to think about his Lab Manager architecture design, and we have some questions about the relationship between vSphere and Lab Manager.

    (1) can Lab Manager leverage of resources defined outside its host vSphere environment?

    (2) must LM be hosted in a specific vSphere environment to effectively exploit the scene-to-production in this environment vSphere features?  In other words, what is the impact to the staging functionality when you move a virtual machine from a workspace of LM to a VSphere environment that does not host the environment of LM?

    The reason we ask is because we already have production environment vSphere, and we plan to install vCenter Lab Manager within this environment or install LM in a separate vSphere environment.

    Thank you.

    Tim

    (1) the laboratory director can leverage resources defined outside its host vSphere environment?

    All used 'resources' must be inside a vCenter server, and all objects must be contained within a single "Data center" object in the hierarchy.

    > LM (2) done must be hosted in a specific vSphere environment to effectively exploit the scene-to-production in this environment vSphere features? In other words, what is the impact to the staging functionality when you move a virtual machine from a workspace of LM to a VSphere environment that does not host the environment of LM?

    If the vCenter for production is not the same as Lab Manager, you must export the Configuration of LM in an SMB share (requires a classic ESX host in the middle of LM), and then import it to the appropriate location.

    I did not notice problems with Lab Manager VMs-by-side with use of regular production.  Just separate the ESX hosts in a dedicated Cluster or a Pool of resources.

    Kind regards

    Jon Hemming, b.SC., RHCT, VMware vExpert 2009
    http://Twitter.com/vJonHemming

    If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

  • I can point my Lab Manager 4.0.2 to point to another new vCenter Server?

    Hi guys,.

    I have a client with a LM4.0.2 production and we are considering moving to one another new/a vCenter server.

    It is important to note that the new vCenter will NOT have the same DB or FULL of the old domain name. It's a completely different vCenter with other ESX hosts.

    Now the questions:

    Can I redirect my Lab Manager (VM) at the new vcenter without any problem?

    What of the ESX (resource) on the old vcenter?

    Is it possible to do this without downtime for laboratories? If this is not the case, how can I minimize downtime? cancel the deployment will be enough?

    Does anyone have this done successfully?

    Any comments would be much appreciated.

    Eyal

    etamir,

    There are some excellent discussions within this forum on the same topic.  I strongly suggest to read first, and I'll see if I can find an example.

    Before going further, data warehouses used in the new vCenter/ESX environment will be exactly the same as the current one?  If you want to keep all of your configurations, I need to know that the UUID of the LUN does not change during this process.

    Can I redirect my Lab Manager (VM) at the new vcenter without any problem?

    You can change the IP/domain FULL name vCenter in the settings section of the Lab Manager site... now on the problems that could result.

    You will need to remove anything from the GUI of Lab Manager that has to do with the current vCenter (unedploy, unprepare host esx, resource pools, configurations etc.).  There will be more on this in the dedicated thread

    What of the ESX (resource) on the old vcenter?

    ESX doesn't really matter, it's the data UUID store that matters.  ESX is just virtual machines.  Note: you'll want to throw all States/suspend points on the VMS where processors are different on the ESX hosts.

    > Is it possible to do this without downtime for laboratories?

    No, there will be a form any downtime.  Either that LM site will be useless (no resources with Betclic, consoles will does not work until the guests are prepared, etc.).

    > If not, how can I reduce downtime? cancel the deployment will be enough?

    Yes, to cancel the deployment of will help... but there will be some lag as you reconfigure Manager of laboratory to use the new vCenter.

    > Has anyone successfully done this?

    Yes.  I saw others to do this.

    Subjects in the sample: http://communities.vmware.com/message/1592762

    Kind regards

    Jon Hemming, b.SC., RHCT, VMware vExpert 2009
    http://Twitter.com/vJonHemming

    If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

  • Lab Manager dependencies on vCenter and terminology

    I just Lab Manager, of course with ESX and vCenter.  I know very little about Virtualization, as this issue will prove.  What are the activities of configuration required on vCenter for Lab Manager able to build models, installation configurations and share library configurations?

    Also, I'm trying to get my head around the difference between the data store, data center and media store.  My current knowledge are:

    A data store has a one-way relationship to one or more hosts.  If storage is on a specific host (physical hard disk for example) then the data store has a relationship one of exlclusively with a single host.  Any file a host or a virtual machine can read/write can be read/written on this data store.

    A data center is a logical collection (non-brique and mortar) hosts, data warehouses and virtual machines.  A data center can aggregate various data stores in a single logical storage available to all virtual machines area?  Or another flavor of physical storage can same issue on a Server Windows 2008 physical logically be conifgured such as NFS, and can share NFS join a data center?

    A media store is a special part of a data store managed by the Manager of laboratory exclusively for the storage of files ISO for the construction of models in the laboratory Manager.  Is a media store part of a data store or part of a data center?

    Is a model of vCenter the same model Lab Manager?

    Any clarification on these questions would be more useful.

    Kind regards

    Rick

    Good questions! Welcome to the Forums as well!

    Your description data store is pretty right on. With the exception of the now for the storage of the local host, new technologies progressed to virtualize in the shared storage by the use of devices to Vritual Server.  Companies like HP lefthand and Openfiler to name a few.

    With regard to the issues of data center

    > A datacenter can aggregate various data warehouses into a single logical storage available to all virtual machines area?

    No, he learn better to keep data warehouses between HA/DRS separate clusters.  Now between the host in a cluster you "will share stroage" for the use of the DRS, HA or Storage vMotion.

    > can physical storage on a Server Windows 2008 physical logically be conifgured such as NFS, and can share NFS join a data center?

    Yes you can - use Openfiler VSA to connect the two iSCSI LUNS and NFS for ESX. As long as the ESX host can access the virtual machine through the network.

    For your other questions have a good read on a couple of things well:

    http://bsmith9999.blogspot.com/2010/02/Lab-Manager-40-Setup-and-best-practices.html

    This webcast was just as informative as well:

    http://www.VMware.com/a/webcasts/details/284

    See you soon,.

    Chad King

    VCP-410. Server +.

    Twitter: http://twitter.com/cwjking

    If you find this or any other answer useful please consider awarding points marking the answer correct or useful

  • Lab Manager Server in a domain?

    Hello

    What is position of everyone by joining the LM server in a domain? I know that the installation guide does no recommendation as to whether, it should / should not be part of a domain.

    I know that within 2.5 days, they have explicitly indicated that it should be a stand-alone server.

    It should really be part of a domain to Lab Manager 4.  Setup requires a COMPLETE domain name to be associated with it anyway, with a static IP address.

    Kind regards

    Jon Hemming, b.SC., RHCT, VMware vExpert 2009
    http://Twitter.com/vJonHemming

    If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

Maybe you are looking for