On 05/05/2014 03:47 AM, Martin Kletzander wrote: > Signed-off-by: Martin Kletzander <mklet...@redhat.com> > --- > docs/drvesx.html.in | 14 ++++++++++++++ > src/esx/esx_util.c | 13 ++++++++++++- > src/esx/esx_util.h | 2 ++ > 3 files changed, 28 insertions(+), 1 deletion(-) > > diff --git a/docs/drvesx.html.in b/docs/drvesx.html.in > index 0816baf..d941763 100644 > --- a/docs/drvesx.html.in > +++ b/docs/drvesx.html.in > @@ -185,6 +185,20 @@ > vpx://example-vcenter.com/folder1/dc1/folder2/example-esx.com > override the default port 1080. > </td> > </tr> > + <tr> > + <td> > + <code>allow_unsafe</code> > + </td> > + <td> > + <code>0</code> or <code>1</code> > + </td> > + <td> > + If set to 1, this disables check for supported > + virtualHW.version, so connections to newer versions > + than supported is possible. The default value is 0.
"connections" is plural, so s/is possible/are possible/ On the surface this (and the rest of the series) makes sense - it allows older libvirt to be used with a newer ESX version which may or may not work, until such time as newer libvirt has been tested to explicitly work with that ESX. But I'd like an opinion from someone that actually uses esx:// URIs before checking this in. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
