VMware Cloud Community
Hawkuz
Contributor
Contributor

ESXi 3.5 u4 no more start and stop on CLI / Fault string: fault.RestrictedVersion.summary Fault detail: RestrictedVersionFault Operation cannot be performed

Since the last update of ESXi 3.5 to Update 4 our scripts to shutdown and start the single VMs doesn't work anymore.

(We reverted to ESXi 3.5 U3 and our batch works fine, as it worked for months before on u2 and u3).

Is it really true, that the two commands

vmware-cmd.pl <conn_params> PathToVmwareGuest.vmx -stop

or

vmware-cmd.pl <conn_params> PathToVmwareGuest.vmx -start

doesn't work anymore? All that we get as response is:

SOAP Fault: Fault string: fault.RestrictedVersion.summary Fault detail: RestrictedVersionFault Operation cannot be performed.

SOAP Fault: Fault string: fault.RestrictedVersion.summary Fault detail: RestrictedVersionFault

And if it is really no more possible, why should we not move to the free MS Hyper V?

Reply
0 Kudos
12 Replies
lamw
Community Manager
Community Manager

The reason for this is the RCLI has locked down write access, you can find more details here: http://vmetc.com/2009/03/31/esxi-u4-ends-free-version-read-and-write-access-from-the-rcli/

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

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at:

Reply
0 Kudos
WiEmWaerUser
Enthusiast
Enthusiast

We have exactly the same problem. Even if this read/write-thing was just "made by mistake" we can not understand, why VMWare has closed this very usefull capability with U4. Are there any security reasons?

And even more important:

What is the easiest way to go back to the ESXi3.5 u3-Version? Somewhere else in this community, we found some lines about a mysterioius "CTRL-R pressing during the boot process" to switch back to the previous bootimage. But we can't find the "right" moment to press this combination.

Could anyone help us to go back from ESXi 3.5 u4 to u3? Any KB-entry? Any hint about this process is very welcome!

Reply
0 Kudos
lamw
Community Manager
Community Manager

There are many opinions on why this may have been done, if you're dissatisfy with this modification, provide feedback to VMware: http://www.vmware.com/support/policies/ (go to the bottom and there is a feedback box) The voice of people can make a difference and perhaps they may re-consider. In terms of rolling back, you'll need to rebuild and install U3, you can not revert upgrades or patches.

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

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at:

Reply
0 Kudos
WiEmWaerUser
Enthusiast
Enthusiast

We hope, that enough user will use the feedback and let VMWare know, how bad this latest patch is for this topic!

Can you please help us with your "In terms of rolling back, you'll need to rebuild and install U3".

How and what exactly do we have to "rebuild?

Can we burn a *.iso-file with the "[installable U3|http://download3.vmware.com/software/vi/ESXe350-200810401-O-UG.zip]" and then install this Version over the latest U4?

Thank you very much for your help, lamw!

Reply
0 Kudos
lamw
Community Manager
Community Manager

The rebuild process is exactly that, you'll need to reinstall as did in the initial installation of ESXi on your system.

Please note : Remember to backup your VM(s) to an external storage because when you reinstall it may override the local VMFS volume, I know in the classic ESX installation you can be prompted to not override the VMFS volume but for safety precaution, I highly recommend backing up your VM(s) before attempting this re-installation.

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

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at:

Reply
0 Kudos
Shaha
Enthusiast
Enthusiast

this is not good, vmware seem to be taking one step forward and 3 back Smiley Sad

Reply
0 Kudos
Severino
Contributor
Contributor

Well I've discovered that we can't really use the RCLI at all for things like creating snapshots etc, which kills my plans to use scripts to backup and restore VMs. This wipes out one of the two major advantages of using ESXi. Actually I'm not complaining; VMware has provided this software freely and it is good. They have the right to restrict it any way they like, and we could just pay the subscriptions to get access to what appears to be a great set of tools. We are very grateful for their VMware Server and all the associated tools, which is useful in a light use server environment (small non-profit organization in our case). For a slightly heavier use environment we need something a bit more performant. I'll have to move on to looking at Xen again.

Ken

Reply
0 Kudos
lamw
Community Manager
Community Manager

Take a look at this thread, you still might be able to automate using some CLI tools they haven't locked down .... yet Smiley Wink

http://communities.vmware.com/message/1230459#1230459

I agree a subset of features should be allowed, but I can see VMware's point. Just know when you're purchasing the Foundation license, you get more than just full r/w access to the VI API, that's the key you have other major features that can automate/manage your environment.

Remember, you still can use the unsupported SSH console on ESXi and use vimsh wrapper to automate all your tasks, there's always a way.

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

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at:

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

Reply
0 Kudos
Severino
Contributor
Contributor

Many thanks William, ssh and scp work fine so this is one possibility. I'll have a go at VMware-vix a bit later on.

cheers, Ken

Reply
0 Kudos
pwolf
Enthusiast
Enthusiast

I would suggest to use the repair option of the install scripts, instead of a reinstall (of course with the U3 installation medium). Thus you have a far better chance, that your local VMFS volumes remain intact.

Reply
0 Kudos
pwolf
Enthusiast
Enthusiast

While you are correct, that that VMware is free to modify free software as they like - they should have told this loss of functionality in a clear statement on the download page of the update.

Whereas the unablilty to to manage ESXi from any other OS than Windows in a supported way does not place a reliability problem onto existing installations, the removal of the possibility to shut down the guests and the host in an automated way via RCLI/CLI scripts without telling people in a not overseeable way can put existing installations in a very dangerous state:

I am pretty sure there are many people out, who had installed some RCLI script, to shut down their guests and the ESXi host in case of a power failure, which do not use those scripts every day and therefore do not know, that after installing U4 those scripts do not longer work. All those installations are now at a severe risk of data loss on all VMs running on ESXi 3.5 U4 because in case of a power failure their VMs and the host will run without any graceful shutdown till the UPS shuts off the power. That may easily lead to hardware defects, too.

I am pretty sure, that all people, which will get into data loss out of that situation are lost as customers for VMware forever - so a rethink of this situation should be done asap.

Reply
0 Kudos
selak1
Contributor
Contributor

Hi,

Unfortunately, I agree with you...

During too much time, I was debugging the script "shutdown.sh" to understand why the MGE UPS agent installed on the ViMA can't suspend my VMs...

It really sucks.

Reply
0 Kudos