similar to: Re: virt-v2v stuck EDAC sbridge

On Mon, Sep 11, 2017 at 04:27:30PM +0000, Seth Tanner wrote: > Rich, > Here you go > I also noticed that if I use the direct backend rather than libvirt, the conversion gets farther, but still does not complete, when pulling directly from vSphere. please let me know if you would like the output of direct as well. > starting version 233 > + udevadm trigger > + udevadm settle

On Mon, Sep 11, 2017 at 06:38:14PM +0000, Seth Tanner wrote: > The virt-v2v machine is running inside openstack, so there is nested > virtualization. To the best of my understanding all of the > appropriate flags have been set to support nested virtualization. Ah OK, it's likely to be a bug in nested virt. Unfortunately nested virt is a bit of a minefield, and often has bugs. Also

On Fri, Sep 08, 2017 at 06:33:58PM +0000, Seth Tanner wrote: > [fedora@virt-v2v-fedora ~]$ virt-v2v -ic vpx://AXIA-EFT%5cstanner@192.168.28.9/Axia/galleon.axia-eft.local/?no_verify=1 "Axia-DEV" -o glance -on Axia-DEV Some of the debug info is missing here. Can you run it with ‘-v -x’ added to the virt-v2v the command line. Rich. -- Richard Jones, Virtualization Group, Red Hat

On Tue, Apr 09, 2019 at 06:37:46PM -0700, Sureshkumar Kaliannan wrote: > Hi, > > I'm trying to create a clone of a physical Window VM using p2v. > > My goal is to create a cloning tools VM that has libguestfs tools installed > and acts as the convertor. > VM conversion works just fine but the conversion rate is significantly > slow(1/3) when running inside the VM

Hi, I'm trying to create a clone of a physical Window VM using p2v. My goal is to create a cloning tools VM that has libguestfs tools installed and acts as the convertor. VM conversion works just fine but the conversion rate is significantly slow(1/3) when running inside the VM compared to when the v2v is run on the same bare-metal host. On the host:

thanks Richard, The experiment was indeed done with nested VM enabled. I am not sure about the internals, but i thought once overlay is setup the 2 main processes are sshd and qemu-img convert (reading data from sshd and doing the conversion) I don't see any of the qemu process running. Initial overlay setup was pretty quick and rest of the time was spent in qemu-img convert operation Suresh

Killall does nothing the process is still alive... If I do kill -9, do I get a core dump ? Each time I got this hang, I find only umount -f /tmp/xxxx to force qemu-img to stop. Alain -----Message d'origine----- De : Richard W.M. Jones [mailto:rjones@redhat.com] Envoyé : mercredi 15 octobre 2014 14:41 À : VONDRA Alain Cc : libguestfs@redhat.com Objet : Re: [Libguestfs] Virt-v2v conversion

On Wed, Oct 15, 2014 at 12:23:17PM +0000, VONDRA Alain wrote: > Now, the conversion hangs on the first disk at 54,03/100%, here is the gdb result : OK I just talked to Paolo about this, and it's fairly serious. Can you get a core dump from this? You will need to set up the ulimit etc as outlined in the previous email: https://www.redhat.com/archives/libguestfs/2014-October/msg00102.html

Hey everybody, Richard, you were right. I managed to reproduce the same crash without dealing with v2v (and libguestfs). Actually - it's reproducible really ease - I write a big file to /tmp on L0 (till it 100% full) and then run a L2 VM. Almost every time it crushes with double fault. Debugging, debugging and more debugging. Marcelo/Paolo, if you have any clue, I would like to hear from you.

Hi The Dragon book, led my thoughts to "Here be dragons" http://en.wikipedia.org/wiki/Here_be_dragons "In another context, software programmers sometimes use it to indicate especially difficult or obscure sections of code in a program so that others do not tamper with them." Why not some dragon name ? or maybe someone can use this idea to come up with something else. /f

On Mon, Jul 27, 2015 at 07:10:05PM +0200, Arsène Gschwind wrote: > Hi, > > I'm trying to migrate some VMs from KVM to oVirt using virt-v2v and > I cannot get it to work. > > What will be the best/working strategy for doing such a migration. You don't need to (and _shouldn't_) use virt-v2v if the guest already works on KVM. It's only for importing guests which

On 03/19/2014 06:07 AM, Paolo Bonzini wrote: > Il 19/03/2014 04:15, Waiman Long ha scritto: >>>> You should see the same values with the PV ticketlock. It is not clear >>>> to me if this testing did include that variant of locks? >>> >>> Yes, PV is fine. But up to this point of the series, we are concerned >>> about spinlock performance when

On 03/19/2014 06:07 AM, Paolo Bonzini wrote: > Il 19/03/2014 04:15, Waiman Long ha scritto: >>>> You should see the same values with the PV ticketlock. It is not clear >>>> to me if this testing did include that variant of locks? >>> >>> Yes, PV is fine. But up to this point of the series, we are concerned >>> about spinlock performance when

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #8 from Philippe Condé <conde.philippe at skynet.be> --- Hello, I desactivated kscreenlocker which resolve the reactivate problem. But the problem of corrupt screen when starting different programs remains and is worst since the last zypper dup. I found this error still related to nouveau when the two screen got corrupted ov

On Thu, Sep 18, 2014 at 10:20 AM, KY Srinivasan <kys at microsoft.com> wrote: > > >> -----Original Message----- >> From: Paolo Bonzini [mailto:paolo.bonzini at gmail.com] On Behalf Of Paolo >> Bonzini >> Sent: Thursday, September 18, 2014 10:18 AM >> To: Nakajima, Jun; KY Srinivasan >> Cc: Mathew John; Theodore Ts'o; John Starks; kvm list; Gleb

Il 18/01/2014 23:01, Rom Freiman ha scritto: > Hey everybody, > Richard, you were right. I managed to reproduce the same crash without > dealing with v2v (and libguestfs). > Actually - it's reproducible really ease - I write a big file to /tmp > on L0 (till it 100% full) and then run a L2 VM. Almost every time it > crushes with double fault. > Debugging, debugging and more

Quite frankly it might make more sense to define a cross-VM *cpuid* range. The cpuid leaf can just point to the MSR. The big question is who will be willing to be the registrar. On September 18, 2014 11:35:39 AM PDT, Andy Lutomirski <luto at amacapital.net> wrote: >On Thu, Sep 18, 2014 at 10:42 AM, Nakajima, Jun ><jun.nakajima at intel.com> wrote: >> On Thu, Sep 18, 2014

Kashyap, just to be sure - it happens to you during the v2v conversion? on L2? While L1 and L0 works fine afterwords, right? Thanks On Fri, Jan 17, 2014 at 4:45 PM, Kashyap Chamarthy <kchamart@redhat.com> wrote: > On 01/17/2014 03:38 PM, Richard W.M. Jones wrote: >> On Fri, Jan 17, 2014 at 04:14:03PM +0200, Rom Freiman wrote: >>> How do you know that the problem is with

On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: >Hi Linus, > >Up to now we see the below boot error/warnings when testing v4.14-rc6. > >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. >

On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: >Hi Linus, > >Up to now we see the below boot error/warnings when testing v4.14-rc6. > >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. >