similar to: virt-v2v - Unable to authenticate to vCenter as DOMAIN\user

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' >

Thanks Richard, seems 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

On 17.09.14 10:02, Richard W.M. Jones wrote: > On Wed, Sep 17, 2014 at 10:58:18AM +0300, Shahar Havivi wrote: > > On 16.09.14 15:09, Richard W.M. Jones wrote: > > > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > > > I am using upstream qemu while using this local variables: > > > > export PATH=/home/shahar/git/qemu:$PATH > > >

Calculate dcPath correctly for vCenter conversions. Rich.

Since there is no more need to build nbdkit from sources, then there is no need to set $PATH with a custom build of nbdkit. Followup of commit 0704d8eb0bcc8139886eb4291f75a3ca49a91e58. --- v2v/virt-v2v-input-vmware.pod | 1 - 1 file changed, 1 deletion(-) diff --git a/v2v/virt-v2v-input-vmware.pod b/v2v/virt-v2v-input-vmware.pod index b3ebda182..3acdd773e 100644 ---

Hi, I am trying to import and convert some VMWare guests from a VMWare cluster with vCenter version 6, to a KVM (oVirt) host. The KVM node (RHEL 7.2) has virt-v2v 1.28.1, though I've also tried using Fedora 23 which has 1.32.4. The details are: vCenter server: nssesxi-mgmt Datacenter name: North Sutton Street esxi server which runs the VM: nssesxi-mgmt04 folder name: Systems VM name: wvm2

On 16.09.14 15:09, Richard W.M. Jones wrote: > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > I am using upstream qemu while using this local variables: > > export PATH=/home/shahar/git/qemu:$PATH > > export LIBGUESTFS_HV=/home/shahar/git/qemu/x86_64-softmmu/qemu-system-x86_64 > > > > Is that sufficient? > > Yup, upstream qemu should

Hi folks, I'm trying to connect to a vSphere cluster using the information from the libvirt documentation. ------------------- $ virsh -c "vpx://root at 10.51.4.11/dc1/dc1-cluster-e01/dc1-vsphere-e04/?no_verify=1" Enter root's password for 10.51.4.11: error: internal error HTTP response code 400 for call to 'Login' error: failed to connect to the hypervisor

Patch 1 was previously posted here: https://www.redhat.com/archives/libguestfs/2020-June/msg00086.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

On Friday, 8 December 2017 17:02:29 CET Richard W.M. Jones wrote: > Previously the presence of the ‘--vddk <libdir>’ option magically > enabled VDDK mode. However we want to introduce other transports for > VMware conversions so this wasn't a very clean choice. > > With this commit you must use ‘-it vddk’ to specify that you want VDDK > as a disk transport. The

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.

Previously posted: https://www.redhat.com/archives/libguestfs/2018-November/msg00000.html https://www.redhat.com/archives/libguestfs/2018-November/msg00001.html This completes the split and rewrite of the virt-v2v manual to make it much simpler to understand and digest. Rich.

On Sun, Sep 21, 2014 at 04:16:59PM +0300, Shahar Havivi wrote: > On 17.09.14 10:02, Richard W.M. Jones wrote: > > On Wed, Sep 17, 2014 at 10:58:18AM +0300, Shahar Havivi wrote: > > > On 16.09.14 15:09, Richard W.M. Jones wrote: > > > > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > > > > I am using upstream qemu while using this

This patch is incomplete, but early feedback would be welcome. Rich.

Hi everyone, I searched previous postings and I couldn't find a definitive answer on this.. I run a small lab of RHEL/Centos Based servers on which there's VMWare Workstation running on a non-standard port but still manageable by tools like VMrun (and the Fusion of Workstation GUI, of course). I'm trying to use virsh with this setup and getting the following error from both

Proposed small change to the command line of virt-v2v when specifying that you want VDDK mode. Rich.

Pass (again) around the libvirt URI string in the various input_libvirt subclasses so that input_libvirt#as_options does not need to connect to print the connection URI. As related change: pass input_conn as non-optional string parameter in classes that require one (all but input_libvirt_other, basically). This avoids the need for extra checks. --- v2v/input_libvirt.ml | 10

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.

To Whom may be concerned: I connect a vCenter by vpx://example-vcenter.com/dc1/srv1 , but how I get all esx servers managed by this vCenter? Thank you. Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20120412/4fe5527d/attachment.htm>

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 VCSA for example requires to use