When I pull the VM details using powershell, the Guest OS for all of my VM is empty.
I am using the correct syntax '$vm.guestOperatingSystem' to pull the information. All the other information like VMName, Container, PowerState, NetworkAdapters, etc... are coming except Guest OS and Description of VM.
Even if I create a new Windows Server 2012 R2 VM, the Guest OS field shows nothing for new VM as well. I have 47 VMs currently on a Nutanix host but the Guest OS information is empty for all of them.
Please let me know if anyone else is having this issue and how to resolve it.
Details:
----------------------
Hypervisor: AHV
Solved
Why the 'Guest OS' field in nutanix vm is NULL?
+3Best answer by RichardsonPorto
Hi @darshan.patel ,
Unfortunately that information is not exposed when you are using AHV hypervisor. I recommend you open a support ticket and request attach your case to the feature request to add Guest OS information on Prism to AHV VMs.
View originalUnfortunately that information is not exposed when you are using AHV hypervisor. I recommend you open a support ticket and request attach your case to the feature request to add Guest OS information on Prism to AHV VMs.
1 person likes this
This topic has been closed for comments
+3If theres a manual way to achieve the solution? then I can log a support ticket.
Thanks,
+5- Nutanix Employee
Hi @darshan.patel ,
Unfortunately that information is not exposed when you are using AHV hypervisor. I recommend you open a support ticket and request attach your case to the feature request to add Guest OS information on Prism to AHV VMs.
Unfortunately that information is not exposed when you are using AHV hypervisor. I recommend you open a support ticket and request attach your case to the feature request to add Guest OS information on Prism to AHV VMs.
Richardson Porto - LinkedIn: http://linkedin.com/in/richardsonporto
1 person likes this
+6We opened a ticket about this (00487751) early Feb 2019 - ENG-177417, resolved in 5.10.1 was the answer.
+3DavidN wrote:
We opened a ticket about this (00487751) early Feb 2019 - ENG-177417, resolved in 5.10.1 was the answer.
If you have a solution or work around, please share.
+5- Nutanix Employee
Hi @DavidN , glad to know that your problem was fixed on AOS 5.10.1, but the @darshan.patel issue is another, since he is using AHV hypervisor and in your case your are using vSphere ESXi as hypervisor. For AHV, the FEAT-8002 is still open.
+3RichardsonPorto wrote:
Hi @DavidN , glad to know that your problem was fixed on AOS 5.10.1, but the @darshan.patel issue is another, since he is using AHV hypervisor and in your case your are using vSphere ESXi as hypervisor. For AHV, the FEAT-8002 is still open.
Hi
Yes you are correct. I also upgraded my PC and PE to 5.10.2, but the issue is still present in AHV. Thanks for posting out details.
I am just curious about FEAT-8002, can a nutanix user is able see cases/details about future features or future enhancements? If yes, can you post links?
I was just writing a PowerShell script and encountered the same thing on 5.10.2 on a cluster running AHV. I can confirm this is still an issue. I’ll open a ticket for a feature request. This is definitely disappointing, especially considering how easy it is to do on ESXi.
+3McCranium wrote:
I was just writing a PowerShell script and encountered the same thing on 5.10.2 on a cluster running AHV. I can confirm this is still an issue. I’ll open a ticket for a feature request. This is definitely disappointing, especially considering how easy it is to do on ESXi.
darshan.patel wrote:
McCranium wrote:
I was just writing a PowerShell script and encountered the same thing on 5.10.2 on a cluster running AHV. I can confirm this is still an issue. I’ll open a ticket for a feature request. This is definitely disappointing, especially considering how easy it is to do on ESXi.
Thanks for the reply and the confirmation
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.