VMware Cloud Community
kasperottesen
Contributor
Contributor

resxtop vMA 4.1

Hi

Yesterday I installed a clean vMA 4.1. When I call resxtop to a ESXi 4.0 host and tries to see the storage (disk) VM resource utilization screen an empty screen comes up, like there are no VM's running on the host. There is no problem in the cpu, mem and other disk screens.

Does anyone have the same problem and are there any fixes/workarounds?

I have not tested againts any ESXi 4.1 hosts btw.

Kasper

Reply
0 Kudos
8 Replies
rob2282
Contributor
Contributor

I am having the vert same problem, I have not found a work around yet

Reply
0 Kudos
kasperottesen
Contributor
Contributor

Looks like a bug. Lets hope for a hotfix/update soon.

Reply
0 Kudos
EverL0ng
Contributor
Contributor

Any one get an answer to this question? I am able to see the disk stats for VMs on a 4.1 host, but not on a 4.0 host. For not I am going to use the version 4.0 instead of vMA 4.1.

Thanks,

Reply
0 Kudos
lamw
Community Manager
Community Manager

As mentioned before, it looks like a bug. I can confirm the same behavior. If you want a confirmation on whether this is a true bug, you'll probably want to file a ticket with VMware.

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

Twitter: @lamw

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

If you find this information useful, please award points for "correct" or "helpful".

Reply
0 Kudos
RParker
Immortal
Immortal

I have not tested againts any ESXi 4.1 hosts btw.

Well I don't think it's a bug.

We have VMA 4.1. I have an ESXi 4.0 host build 244038.

vCenter is 4.1

Works fine, no blank screen. I see the VMs, CPU and Memory all fine.

Reply
0 Kudos
lamw
Community Manager
Community Manager

RParker,

The issue is with displaying the VM Disk or using option "v", cpu/memory has always worked. I'm able to reproduce the error when connecting to ESX 4.0 and 4.1 host, you don't get the VM's disk stats when connecting to ESX(i) 4.0 using vMA 4.1 or vCLI 4.1

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

Twitter: @lamw

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

If you find this information useful, please award points for "correct" or "helpful".

Reply
0 Kudos
lamw
Community Manager
Community Manager

After doing a bit of research the resxtop issue is actually in the vCLI 4.1 installation, this issue occurs if you install vCLI 4.1 on separate Linux system which I confirmed using CentOS. I've already contacted the vMA product manager regarding the issue and hopefully we'll see a patch or new release for vCLI 4.1 and vMA 4.1

I also wrote about the issue on my blog here - http://www.virtuallyghetto.com/2010/10/resxtop-bug-in-vma-41.html You can monitor it for new updates

Thanks

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware VCP3,4

VMware VCAP4-DCA

VMware scripts and resources at:

Twitter: @lamw

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

If you find this information useful, please award points for "correct" or "helpful".

Reply
0 Kudos
kasperottesen
Contributor
Contributor

Looking forward to a hotfix/patch.

Reply
0 Kudos