On Thu, May 07, 2026 at 03:45:03PM +0200, Martin Kletzander wrote: > Hello, > > so we found an issue in the ESX driver which is pretty easy to solve, > but requires an update to the communication with the server. The newer > VI API allows for the instanceUuid parameter when searching for VMs, but > only since 4.0, but because we do not send any "SOAPAction:" header it > behaves as if we used the oldest one. If we add the header "SOAPAction: > urn:vim25/4.0" (at least 4.0) it works, but I'm not sure if there are > any incompatibilities and whether there is a use case for older clusters > that do not support at least this version. > > If there is a reasonable use case for it (well, anyone saying "here, me, > I'd like to keep it") we could change the behaviour based on the version > we parse when connecting to the server. But that's an extra bit of > mess, although not totally big one. > > So I would like to know your opinion on this. Adding few people into Cc > who found about the issue.
Do you know how the VI API versions compare to vSphere versions? Basically we only care about vSphere >= 7, so if that still works then we're all good. I believe the MTV server you are using may actually be vSphere 7. Rich. > Have a nice day, > Martin -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html
