[Libguestfs] Virt-v2v conversion issue

[VONDRA Alain]

Rich,
The results of the guestfish command :

><fs> part-list /dev/sda
[0] = {
  part_num: 1
  part_start: 1048576
  part_end: 85906685951
  part_size: 85905637376
}
><fs> part-list /dev/sdb
[0] = {
  part_num: 1
  part_start: 32256
  part_end: 322126640639
  part_size: 322126608384
}
><fs> part-list /dev/sdc
[0] = {
  part_num: 1
  part_start: 32256
  part_end: 32210196479
  part_size: 32210164224
}
><fs> part-list /dev/sdd
[0] = {
  part_num: 1
  part_start: 32256
  part_end: 32210196479
  part_size: 32210164224
}
><fs> part-list /dev/sdf
[0] = {
  part_num: 1
  part_start: 32256
  part_end: 21476206079
  part_size: 21476173824
}
><fs> part-list /dev/sdg
[0] = {
  part_num: 1
  part_start: 32256
  part_end: 42952412159
  part_size: 42952379904
}
><fs> part-list /dev/sdh
[0] = {
  part_num: 1
  part_start: 32256
  part_end: 214745610239
  part_size: 214745577984
}
><fs> part-list /dev/sdi
[0] = {
  part_num: 1
  part_start: 32256
  part_end: 32224857087
  part_size: 32224824832
}

Alain



-----Message d'origine-----
De : Richard W.M. Jones [mailto:rjones at redhat.com] 
Envoyé : mardi 14 octobre 2014 22:52
À : VONDRA Alain
Cc : libguestfs at redhat.com
Objet : Re: [Libguestfs] Virt-v2v conversion issue

On Tue, Oct 14, 2014 at 03:40:22PM +0000, VONDRA Alain wrote:
> Rich,
> I've followed your instructions to trace, but I am not very skilful with gdb, maybe I made a mistake :
> 
> (1) As root do:
> 
>   echo core.%p > /proc/sys/kernel/core_pattern  -> OK
> 
> (2) Before running virt-v2v, do:
> 
>   ulimited -c unlimited                 -> I think it's ulimit -c unlimited     -> -> OK
> 
> and you should get a core.* file in the current directory when qemu-img segfaults.  Attach that file to gdb to get a stack trace:
> 
>   gdb /usr/bin/qemu-img core.XYZ                -> Do I need to wait the crash becase I don't have any core ???

Yes, you have to wait for qemu-img to crash before there will be a core dump.  If it's not crashing, then connect to qemu-img directly, something like this:

  gdb /usr/bin/qemu-img `pidof qemu-img`

and run this command:

>   (gdb) t a a bt

to show the stack trace in all threads.

If qemu-img is consuming CPU then it's probably not hung.

I'm still interested to find out why fstrim didn't work.  Can you run:

guestfish --ro -d unc-srv-qual03
><fs> run
><fs> part-list /dev/sda
><fs> part-list /dev/sdb
><fs> part-list /dev/sdc
><fs> part-list /dev/sdd
(etc)

I'd be interested to see if the partitions are unaligned, which is the only reason why fstrim should fail on NTFS.

Rich.

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html