This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
We have a VMware environment with windows server. Until now ILMT had displayed the correct usage – full (physical) capacity of the server.
For some virtual VMWare Microsoft servers we have now enabled Hyper-V features (ILMT defines this as nested virtualisation). But in reality the virtual environment of our servers is a native VMWare Virtualization with an Microsoft Operation System on the VMs. None Hyper V servers, only the possibility to use Hyper-V features is enabled at our VMWare Servers.
For the virtual servers with enabled Hyper-V features, the hardware inventory in ILMT doesn‘t show VM Manager data. The "Status = OK" and the ID of the server is like "TLM_VM ....".
ILMT uses for these virtual Servers the PVU standard counting of 100 PVU per Core in opposite to the right messure of 70 PVU per Core. And it seams that it counts every server with enabled HyperV Feature additiv to the full capicity of the physical ESX-Host. As a result ILMT shows a much higher PVU consumption.
We have opened a PMR. No solution was available, because this virtualisation scenario is not supported by ILMT. The workaround doesn´t work for us, because in near future we will have all our VMWare VMs with enabeled Hyper-V feature, and we will have a huge manuell effort.
So we expect that ILMT counts the correct PVU-consumption again in the next release automatically.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
I confirm that this enhancement has been delivered in ILMT 9.2.25 ;)
This enhancement has been accepted and will be delivered with the ILMT updated targeted for end of September.