Using Perfmon in a Windows VM Get VMworld Into Your Budgets
Dec 15

I wrote a few days ago that the ESXi 3.5 U3 update unlocked the API set. Well, this was only partially true. I was just trying out some power operations and the command line kept staring back at me blank. I went back and pinged some of the folks in engineering and low and behold I ran into bigger issues. Turns out that while fixing an API bug the API set got partially unlocked. Yes, you read that right, VMware didn’t mean to unlock the API set – at least not wholly and not yet.

So, if you went out and started madly coding some killer VirtualCenter Client replacement then hold off because I’m told the U4 update will lock things back down again. Good news is that only customers who are using the free version of ESXi have been affected. VirtualCenter and VI (Foundation, Standard, Enterprise) customers are not affected since they had rights to the API set all along.

That’s what I get for running off and blogging about new finds too quick.

No TweetBacks yet. (Be the first to Tweet this post)
VN:F [1.7.8_1020]
Rating: 5.0/5 (3 votes cast)
VN:F [1.7.8_1020]
Rating: 0 (from 0 votes)
UPDATE: VMware RCLI now writes to ESXi Free Hosts5.053

  • lundrog
    Thanks, I added a blog link to you.
  • Hi Mike,

    thanks for the updates, I guess I’ll have to "curb my enthusiasm" and not play with what is open now, but it's good also to know that there is a U4 coming soon ;)
  • Nothing about being to quick. Open and transparent is always best. Sometimes you win and sometimes you loose. That what you get for trying to be "first post".
blog comments powered by Disqus