2016-02-16 16:13 GMT+01:00 Richard W.M. Jones :
> On Mon, Feb 15, 2016 at 11:22:27PM +0100, Matthias Bolte wrote:
>> 2016-02-11 12:59 GMT+01:00 Richard W.M. Jones :
>> > Is calling SessionIsActive necessary? From my (very limited)
>> > understanding, it seems
On Mon, Feb 15, 2016 at 11:22:27PM +0100, Matthias Bolte wrote:
> 2016-02-11 12:59 GMT+01:00 Richard W.M. Jones :
> > Is calling SessionIsActive necessary? From my (very limited)
> > understanding, it seems as if we might use 'SessionManager.
> > currentSession' property
On Mon, Feb 15, 2016 at 11:22:27PM +0100, Matthias Bolte wrote:
> Here's a patch that basically reverts the offending commit. The patch
> is only compile tested, as I don't have a vCenter at hand to test
> this. Do you have the option to test this in an actual setup?
Yes - I will be able to test
2016-02-11 12:59 GMT+01:00 Richard W.M. Jones :
> Is calling SessionIsActive necessary? From my (very limited)
> understanding, it seems as if we might use 'SessionManager.
> currentSession' property instead, which doesn't require admin
> permissions. Actually the code [see
The VMware driver currently calls the SessionIsActive API, which
requires the vCenter Sessions.ValidateSession permission.
https://libvirt.org/git/?p=libvirt.git;a=blob;f=src/esx/esx_vi.c;h=af822b14cfc5ba93c9c2ab4dfa2cb72a23a74a1a;hb=HEAD#l2068
This causes a problem that you have to give this