search for: vcenter

The curl binary is used in the VCenter module, so require it up-front. This let us remove the need to point the user to check whether curl is installed in an error message. --- v2v/input_libvirt_vcenter_https.ml | 13 ++++++++++++- v2v/vCenter.ml | 2 +- 2 files changed, 13 insertions(+), 2 deletions(-) diff --git...

Hi, I am encountering an issue with virt-v2v where I need to authenticate to the vCenter as DOMAIN\user. I have tried the following with the resulting errors: 1. 'virt-v2v -v -x -ic 'vpx://vcenter/Datacenter/cluster_name/esx_server?no_verify=1' vm_name -o local -of raw -os /tmp' - prompted for username password - entered 'DOMAIN\User' as username - successf...

vCenter 7 answers with an HTTP/2 status string, so we cannot extract the status code from it by using fixed positions in that string. Hence, pick the status code by reading what's after the whitespace. Tested with vCenter 6.5 and 7. --- v2v/vCenter.ml | 4 +++- 1 file changed, 3 insertions(+), 1 dele...

The first commit removes the --dcpath parameter, which just makes the following stuff simpler. Since libvirt has supported getting datacenterpath from VMware since Oct 2015, it's time to drop this hairy parameter. The rest is quite a complicated series of refactorings, followed by a very simple change to add handling of snapshots taken from old virt-v2v. Rich.

See earlier thread on libvir-list: https://www.redhat.com/archives/libvir-list/2015-September/thread.html#00201 Libvirt >= 1.2.20 supplies the correct dcPath parameter. If it is available in the libvirt XML, use it, otherwise fall back to the old method of trying to guess it from the vpx:// path. Patches 1, 2 and 4 are just refactoring around this change. Rich.

Thanks Bart. Unfortunately "The VIB module does not comply with the security recommendations imposed by VMWare. You lose VMWare support by installing this package." This pretty much rules out this option. :( We need vCenter support, as well. nomad On Thu, May 14, 2020 at 10:06 AM Bart J. Smit <bart at smits.co.uk> wrote: > This shuts down the hosts directly (by-passing vCenter) > > > > http://rene.margar.fr/2012/05/client-nut-pour-esxi-5-0/ > > > > in spite of the title, it works fo...

Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/vCenter.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/vCenter.ml b/v2v/vCenter.ml index 89c5579b..d9bf12c1 100644 --- a/v2v/vCenter.ml +++ b/v2v/vCenter.ml @@ -79,7 +79,7 @@ let rec map_source ?bandwidth ?password_file dcPath uri server path = let nbdkit = Nbdkit.crea...

....html to handle this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1848862 I was able to observe this bug and for me at least disabling readahead seems to cure it. Patches 2 and 3 are simplifications, removing a now-undocumented feature of virt-v2v-copy-to-local and thus simplifying greatly the VCenter module. Patch 4 contains the change to use cookie-script to renew the VMware cookie. Rich.

On Mon, Dec 22, 2014 at 02:03:50PM +1100, Ben Hooper wrote: > Hi, > > I am encountering an issue with virt-v2v where I need to authenticate to the vCenter as DOMAIN\user. > > I have tried the following with the resulting errors: > > 1. 'virt-v2v -v -x -ic 'vpx://vcenter/Datacenter/cluster_name/esx_server?no_verify=1' vm_name -o local -of raw -os /tmp' > - prompted for username password > - entered 'DOMAIN\Use...

...to work well. Cheers, Ben. > On 22 Dec 2014, at 7:50 pm, Richard W.M. Jones <rjones@redhat.com> wrote: > >> On Mon, Dec 22, 2014 at 02:03:50PM +1100, Ben Hooper wrote: >> Hi, >> >> I am encountering an issue with virt-v2v where I need to authenticate to the vCenter as DOMAIN\user. >> >> I have tried the following with the resulting errors: >> >> 1. 'virt-v2v -v -x -ic 'vpx://vcenter/Datacenter/cluster_name/esx_server?no_verify=1' vm_name -o local -of raw -os /tmp' >> - prompted for username password >>...

Is anyone using NUT to signal/control vCenter and vServer (6.x) for shutdown when batteries are getting low? Any recommendations? We've found https://4sysops.com/archives/startup-and-shutdown-a-vmware-cluster-with-powercli-and-powershell/ but I'd prefer to do this from the master (which is running CentOS 8) and not pollute it by insta...

...w give an error). This requires libvirt >= 1.2.20 for virt-v2v, released Oct 2015. --- v2v/cmdline.ml | 6 +---- v2v/copy_to_local.ml | 6 +++-- v2v/input_libvirt.ml | 4 ++-- v2v/input_libvirt.mli | 4 ++-- v2v/input_libvirt_vcenter_https.ml | 31 +++++++----------------- v2v/input_libvirt_vcenter_https.mli | 2 +- v2v/test-v2v-docs.sh | 2 +- v2v/vCenter.ml | 47 +------------------------------------ v2v/vCenter.mli | 8 ------- v2v/virt-v2v.pod |...

...tions there are. I'd prefer not to rashly decide to run off in a direction only to discover this is already a Solved Problem. nomad On Thu, May 14, 2020 at 1:13 PM Bart J. Smit <bart at smits.co.uk> wrote: > What about the REST API to do a graceful shutdown of your VM’s and the > vCenter appliance: > https://code.vmware.com/web/sdk/6.7/vsphere-automation-rest > > > > Bart… > > > > *From:* Lee Damon <nomad at ee.washington.edu> > *Sent:* 14 May 2020 20:29 > *To:* Bart J. Smit <bart at smits.co.uk> > *Cc:* nut-upsuser at lists.alioth.de...

Hi, I'm looking for a way to use virsh to connect to vCenter/VCSA and do some simple management of the VM's in case of power loss (I'm planning to run the script upon UPS/apcd event of power failure). Looking through the virsh documentation, I didn't find 2 things: 1. Login through a script (I don't see any user/password, specially since VC...

What about the REST API to do a graceful shutdown of your VM’s and the vCenter appliance: https://code.vmware.com/web/sdk/6.7/vsphere-automation-rest Bart… From: Lee Damon <nomad at ee.washington.edu> Sent: 14 May 2020 20:29 To: Bart J. Smit <bart at smits.co.uk> Cc: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] NUT control of vCenter & v...

Hi, I installed libvirt on CentOS 6 today, only to find I could create the volume, create the VM, but could not assign the interface to a distributed port group. I then downloaded the latest source, compiled, and it looks to be the same...unless its under a command I'm not recognizing? Does anybody have the great tip that is going to set me free? I hope? Everything we use is on the

Calculate dcPath correctly for vCenter conversions. Rich.

--- v2v/vCenter.ml | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/v2v/vCenter.ml b/v2v/vCenter.ml index d5e7c0378..434c93395 100644 --- a/v2v/vCenter.ml +++ b/v2v/vCenter.ml @@ -113,7 +113,7 @@ let get_session_cookie password scheme uri sslverify url = Some !session_cookie...

This implements a missing feature from old virt-v2v, namely being able to cope with a guest with snapshots. Note this only converts the top (latest) snapshot. As in old virt-v2v it does NOT convert the whole chain of snapshots. --- v2v/vCenter.ml | 28 ++++++++++++++++++++++++---- 1 file changed, 24 insertions(+), 4 deletions(-) diff --git a/v2v/vCenter.ml b/v2v/vCenter.ml index c96ebdb8b..8e0795c3c 100644 --- a/v2v/vCenter.ml +++ b/v2v/vCenter.ml @@ -33,6 +33,7 @@ type remote_resource = { } let source_re = PCRE.compile "^\\[(....

...estfs (master) LIBGUESTFS_BACKEND=direct ./run ./v2v/virt-v2v -ic "esx://10.35.5.45/?no_verify=1" -o local -of raw -os /tmp/v2v RHEL > > I see - the esx:// URL won't work (I guess virt-v2v should explicitly > reject these). > > Anyway for new virt-v2v you have to have vCenter installed. It's > available as an OVA that you can install on top of ESXi. And then the > URL would be: > > vpx://user@vcenter/Datacenter/10.35.5.45?no_verify=1 > > where 'user' is probably 'administrator' and 'vcenter' is the address > of the...