similar to: Install nested ESXi 6.x host under CentOS 7 kvm host

On 11/27/2015 01:32 PM, Patrick Laimbock wrote: > On 11/26/15 09:47, C. L. Martinez wrote: >> 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

On 11/26/15 09:47, C. L. Martinez wrote: > 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

On 11/27/2015 01:46 PM, Patrick Laimbock wrote: > On 11/27/15 14:40, C.L. Martinez wrote: > [snip] >>> >>> or with the e1000 nic: >>> >>> # virt-install --connect=qemu:///system -n esxi6 --cpu=host --vcpus=2 >>> --ram 4096 --os-type=linux >>> --cdrom=/var/lib/libvirt/images/VMware-VMvisor-Installer-6.0.0-2494585.x86_64.iso >>>

Dear Gianluca, Thanks for sharing this information it will take my whole week again to read the architecture and to understand it. By the way is it recommended to run the OpenStack on top of ESXi6 for testing purpose? When I provision the CentOS VMs for this test I append this line 'vhv.enable=true' inside the .vmx file to support Nested-Environment inside my ESXi6 Its my first time to

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

On 11/27/15 14:40, C.L. Martinez wrote: [snip] >> >> or with the e1000 nic: >> >> # virt-install --connect=qemu:///system -n esxi6 --cpu=host --vcpus=2 >> --ram 4096 --os-type=linux >> --cdrom=/var/lib/libvirt/images/VMware-VMvisor-Installer-6.0.0-2494585.x86_64.iso >> >> --disk >>

Calculate dcPath correctly for vCenter conversions. Rich.

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

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

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.

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

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

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

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

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:

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.

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

Hi all, I'm attempting to PXE boot ESXi, which uses the syslinux mboot.c32 module. The mboot.c32 included with ESXi seems to be an older version that runs into an "out of memory loading.." problem halfway through, even though the box has 8GB memory. This may be related to NUMA, since it works fine on an older box but not the newer blade. I saw that some non-contiguous memory issues