On Thu, May 19, 2022 at 12:29:36PM +0200, Laszlo Ersek wrote: > On 05/19/22 10:52, Richard W.M. Jones wrote: > > From: Ming Xie <m...@redhat.com> > > > > Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1817050 > > --- > > docs/virt-v2v-input-vmware.pod | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/docs/virt-v2v-input-vmware.pod b/docs/virt-v2v-input-vmware.pod > > index ab2d28e41f..60cff93994 100644 > > --- a/docs/virt-v2v-input-vmware.pod > > +++ b/docs/virt-v2v-input-vmware.pod > > @@ -585,6 +585,7 @@ Enable (check) the following objects: > > Provisioning: > > - Allow disk access > > - Allow read-only disk access > > + - Allow virtual machine download > > > > Cryptographic operations: > > - Decrypt > > > > The context a bit higher up includes "using VMware vCenter 6.5"; does > that still apply here? > > ... Either way, if this new permission simply didn't exist under VMware > vCenter 6.5 yet, users on that platform will just ignore this new hint here. > > Acked-by: Laszlo Ersek <ler...@redhat.com>
I tightened up the preceeding text to say that users should set as many as possible. v2 sent. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com nbdkit - Flexible, fast NBD server with plugins https://gitlab.com/nbdkit/nbdkit _______________________________________________ Libguestfs mailing list Libguestfs@redhat.com https://listman.redhat.com/mailman/listinfo/libguestfs