Does anyone know if there is an OID I can use to get the average CPU load from an esxi 5.1 machine? (UCD-SNMP-MIB::laLoad is not available)
You should use http://www.circitor.fr/Mibs/Html/VMWARE-RESOURCES-MIB.php MIB file to monitor ESXI 5.1 via SNMP
Related
i have an old pc that has a network drive by netware 3.12 in dos 6.22 . i backup hard disk by microsoft disk2vhd and now have an vhd file. i add vhd file in virtualbox and dos successfully boot. i can input server command, but when i input server command show this error:
volume sys could not be loaded
some or all volume segments cannot be located
and virtualbox screen image:
why this error show? netware was successfully work in my old pc but in virtualbox does not work,why?
DOS works because it uses the VM BIOS to access HDDs. Netware for performance reason does not use the BIOS to access HDDs. What is likely happening is Netware does not have the required device driver to access the disk controller exposed by the VM. As a result Netware cannot find the SYS volume. I have never tried to install Netware in a VM so I am unsure where you'd go to find appropriate drivers.
I found the following that might be worth your while to explore to see if it can help: https://www.foxdogstudios.com/installing-netware-3-12-on-virtual-box
I have openstack deployed across multiple servers. Each server has 2 CPU, 8 Cores each, 16 threads each. If I turn hyper-threading on, how many max vCPUs can I use on my openstack deployment so that I don't overcommit any vCPUs for any VM.
Hyperthreading
I recommend against turning on hyperthreading in when working with KVM in general, however I am biased. When hyperthreading and kvm were both young, there were many issues that cropped up around vcpu and hyperthreading.
For clarity, hyperthreading simply creates a soft-logical processor in the linux kernel in an effort to reach a higher efficiency in the cpu processing queue.
Overcommitting, vCPUs and logical CPUs
A vCPU is a virtual cpu allocated to a virtual machine.
A logical CPU is a CPU logically allocated to your host system's Linux kernel.
As seen with hyperthreading, sometimes the logical CPUs outnumber the physical CPUs or cores on the host.
You are technically overcommitting the moment you have more vcpu cores than physical cores. Note how I said PHYSICAL cores, not logical CPUs. What linux shows you in proc/cpuinfo may not be an accurate reflection of available physical cores, in part thanks to hyperthreading.
As kvm allocates vCPUs they are not set with any sort of CPU affinity by default. What this means is, the vCPUs are going to whichever logical processor in linux seems to be most available at the time. If someone kicks off a make 'MAKE=make -j64' World sort of job, you might see some pretty significant utilization spin up and begin to fire hose around whatever logical CPUs are most available at any given instruction set.
Now if you have an 8 physical core box, hosting 4 virtual machines, with 2 vCPUs a piece this is fine. But think about what happens with hyperthreading enabled... now you have 16 logical CPUs, but only 8 cores. What happens when you bring up 4 more virtual machines? You run the risk of having virtual machines directly impacting resource availability to their neighbors. This is technically overcommitting.
Don't overcommit if you don't have to.
Also consider the needs of the host. You might want to set cpu_affinity on the host system when you perform CPU intensive actions and consider that physical core as dedicated to the HOST, and subtract it from the available ( max ) vCPU count available to VMs.
Learn how to set affinity's with taskset:
ref: http://manpages.ubuntu.com/manpages/hardy/man1/taskset.1.html
Max vCPU per VM
As for cpu quotas, this is basically a function of your hypervisor not of OpenStack. You'll want to handle that with a CFM and some careful planning.
For instance, RedHat tunes their own KVM packages:
The maximum amount of virtual CPUs that is supported per guest varies
depending on which minor version of Red Hat Enterprise Linux 6 you are
using as a host machine. The release of 6.0 introduced a maximum of
64, while 6.3 introduced a maximum of 160. Currently with the release
of 6.7, a maximum of 240 virtual CPUs per guest is supported.
ref: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html
Here is some info on tuning PER vm cpu / resource allocation
ref: http://libvirt.org/formatdomain.html#elementsCPUAllocation
My current application is comprises of 3 tier- Web tier - App Tier - Database
While testing with 100 users, we found that App tier's cpu is touching almost 90% where as web server and database server are doing fine.
I am not able to figure out what code is causing high cpu usage. Majorly we have CRUD operation there. We take input in the form of DTO, we transfer them into entities (using Entity framework), add/update/delete into database. In case of Get operation, we fetch data into EF entities, store them in DTO and then send DTO to client.
I have tried to use DebugDiag but could not figure out any useful information.
Following are the server's configuration:
Web Server (Quantity = 1) Processor Intel Xeon CPU X5675 #3.07 GHz 2.19 GHz
Number of Cores (Virtual) 8
RAM 8GB
Operating System Windows Sever 2012 Standard
Processor Type 64 Bit
Softwares Installed NET Framework 4.5
App Server (Quantity = 1) Processor Intel Xeon CPU X5675 #3.07 GHz 3.07 GHz
Number of Cores (Virtual) 8
RAM 8GB
Operating System Windows Sever 2012 Standard
Processor Type 64 Bit
Softwares Installed NET Framework 4.5
DB Server (Quantity =1) Processor Intel Xeon CPU E7-4830v2 # 2.20 GHz 2.19 GHz
Number of Cores (Virtual) 8
RAM 8GB
Operating System Windows Sever 2012 Standard
Processor Type 64 Bit
Softwares Installed Microsoft SQL Sever 2014
There is no better solution than to install an APM tool. With them you'll find the root cause very quickly. AppDynamics or NewRelic are easy, Dynatrace a bit more complex but maybe more powerful.
Else go on shooting in the dark
Windows sysinternal tool Process Explorer(Procexp) is a good tool to find the high CPU process and thread call stack(method calls)
OR
- Collect multiple full user dump using task manager/Procexp on the high CPU process
And collect perfmon log with Thread counter. Perfmon -> Add counter -> Thread under thread select %Processor Time, ID thread, ID process.
From the perfmon you can find the high CPU thread ID. Now you can co-relate the thread ID with debug diag analysis report and find the thread call stack.
Hope this helps.
Thanks,
Parthiban
I have an activeMQ network with 2 instances. Those 2 instances are running 5.5 version of activeMQ. I want to add a new server in 5.9 version. Is this feasible? What should I have in mind? Any gotchas?
Thanks.
We don't test the network of brokers between versions. It may work but we encourage users to upgrade all their brokers to the latest release once the messages contained in those broker's stores have been migrated to a new broker. You can do this by networking an older broker to a newer one and then creating a subscription on any destination that has messages on the old broker on the new one and letting the demand drain the old broker.
I need to reduce the time to get an error when connecting to an unavailable instance.
The problem is that I can't modify the machine configuration. And currently I'm using the ODBC drivers.
The Informix client-sdk can be from 3.50 to 3.70tc3
the instance version is probably 10.x
and the clients run from windows XP thru Windows 7
Set the environment variable INFORMIXCONTIME to any value in seconds that fits your application