similar to: VMware distributed port groups..Supported?

On 06/29/2013 03:22 AM, Morgan McLean wrote: > Does anybody have the great tip that is going to set me free? I hope? Hi, Distributed Port Groups come from the "vNetwork Distributed Switch" (vDS); a feature of VMware vCenter. You just can't throw a non-ESXi hypervisor into your vCenter datacenter and expect it to work with their proprietary technology. The same way you just

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.

Calculate dcPath correctly for vCenter conversions. Rich.

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

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.

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

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.

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 all, I am trying to install nested Esxi 6.x under a Centos7 kvm host to use it as test lab for new ESXi versions, but I am doing something wrong because I can't install it. I have configured kvm and kvm_intel modules with the following options: options kvm ignore_msrs=1 options kvm_intel nested=1 ept=1 and I add the following options in <cpu> xml guest file: <cpu

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

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

On Feb 6, 2018 11:06 AM, "Luca 'remix_tj' Lorenzetto" < lorenzetto.luca@gmail.com> wrote: On Mon, Feb 5, 2018 at 11:13 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > http://libguestfs.org/virt-v2v.1.html#vmware-vcenter-resources > > You should be able to run multiple conversions in parallel > to improve throughput. > > The only long-term

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 installing PS on it. thanks, nomad -------------- next part

It turns out that RHEL 5 Xen conversions don't work if the source disk is located on a block device. See patch 1/4 for the gory details. This patch series proposes a new tool called virt-v2v-copy-to-local which essentially is a way to make new virt-v2v work like the old virt-v2v, ie. copy first, convert after. Of course this is very slow and would only be used as a last resort, but I

On Tue, Feb 06, 2018 at 11:11:37AM +0100, Luca 'remix_tj' Lorenzetto wrote: > Il 6 feb 2018 10:52 AM, "Yaniv Kaul" <ykaul@redhat.com> ha scritto: > > > I assume its network interfaces are also a bottleneck as well. Certainly if > they are 1g. > Y. > > > That's not the case, vcenter uses 10g and also all the involved hosts. > > We

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

Hallo, actual Intel Ethernet cards PCI-E - Are normal recognized by Centos 5.5 Live CD - Not recognized by 5.2 Because of vmware, I will use 5.2 Update kernel? Update Modules? What Module? Thanks for help Helmut -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

The first patch was previously posted here: https://www.redhat.com/archives/libguestfs/2017-December/msg00018.html That patch hasn't changed except that I made the ‘input_transport’ variable type-safe. The second patch adds a significant new mode for liberating data from VMware: the ability to copy VMs over SSH directly from ESXi hypervisors. Although this requires enabling SSH access (a

That's certainly on the list of options. I'm doing data gathering right now to see what options 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 >