similar to: esx/vcenter: create a domain inside an folder

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>

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

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

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

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

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

On Sat, Jan 06, 2018 at 05:27:52PM +0200, Hetz Ben Hamo wrote: > 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: I'm not

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 previous ‘--vddk <libdir>’ option has been renamed to ‘--vddk-libdir <libdir>’ to be

Hello, I’m running virsh v1.1.3 compiled on a ubuntu system with the "--with-esx=yes” support. root@kvm-189:/home/cisco# virsh --version 1.1.3 I also have a vcenter 5.5 environment that has following structure (couple of hosts at datacenter level, others part of cluster group): MIC-VC-ADMIN MIC-DC-ADMIN 10.58.6.110 10.58.6.113 MIC-CL-ADMIN 10.58.6.109 10.58.6.118

Calculate dcPath correctly for vCenter conversions. Rich.

With modern libvirt, when fetching the XML of a VMware guest libvirt passes us the datacenter path (dcpath). However with older libvirt we had to guess this value, or else the user had to supply it on the command line. This commit removes all the guessing code and the --dcpath parameter (which will now give an error). This requires libvirt >= 1.2.20 for virt-v2v, released Oct 2015. ---

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

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

On Thu, Jan 25, 2018 at 10:08 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > There's got to be some difference between your staging environment and > your production environment, and I'm pretty sure it has nothing to do > with the version of oVirt. > > Are you running virt-v2v inside a virtual machine, and previously you > ran it on bare-metal? Or did you

2015-05-21 22:53 GMT+02:00 <vincent@cojot.name>: > > 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

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

Since RHV 3.6.10, the default network name is 'ovirtmgmt' instead of 'rhvm'. This is just a documentation change. --- p2v/virt-p2v.pod | 10 +++++----- v2v/cmdline.ml | 2 +- v2v/virt-v2v.pod | 12 ++++++------ 3 files changed, 12 insertions(+), 12 deletions(-) diff --git a/p2v/virt-p2v.pod b/p2v/virt-p2v.pod index ea685be..4a5f587 100644 --- a/p2v/virt-p2v.pod +++