Re: [Libguestfs] Virt-v2v conversion issue

I see only qemu-img consumming some CPU and MEM : 25897 qemu 20 0 5825976 2,429g 4368 S 5,6 32,2 603:09.34 qemu-kvm I have indeed, some nfs errors : [475747.296041] nfs: server 192.203.100.247 not responding, still trying [475747.772022] nfs: server 192.203.100.247 not responding, still trying [475747.848023] nfs: server 192.203.100.247 not responding, still trying [475747.849014] nfs: server 192.203.100.247 not responding, still trying [475748.270030] nfs: server 192.203.100.247 not responding, still trying [475748.270038] nfs: server 192.203.100.247 not responding, still trying [475748.273016] nfs: server 192.203.100.247 not responding, still trying [475748.274016] nfs: server 192.203.100.247 not responding, still trying [475748.461023] nfs: server 192.203.100.247 not responding, still trying [475748.461028] nfs: server 192.203.100.247 not responding, still trying [475748.461031] nfs: server 192.203.100.247 not responding, still trying [475748.461034] nfs: server 192.203.100.247 not responding, still trying And a lot of : [785084.263606] kvm [12719]: vcpu0 unhandled rdmsr: 0x345 [785084.269594] kvm [12719]: vcpu0 unhandled wrmsr: 0x40 data 0 [785084.269999] kvm [12719]: vcpu0 unhandled wrmsr: 0x60 data 0 [785084.270406] kvm [12719]: vcpu0 unhandled wrmsr: 0x41 data 0 [785084.270826] kvm [12719]: vcpu0 unhandled wrmsr: 0x61 data 0 [785084.271231] kvm [12719]: vcpu0 unhandled wrmsr: 0x42 data 0 [785084.271633] kvm [12719]: vcpu0 unhandled wrmsr: 0x62 data 0 [785084.272023] kvm [12719]: vcpu0 unhandled wrmsr: 0x43 data 0 [785084.272410] kvm [12719]: vcpu0 unhandled wrmsr: 0x63 data 0 Alain -----Message d'origine----- De : Richard W.M. Jones [mailto:rjones@redhat.com] Envoyé : mercredi 15 octobre 2014 15:59 À : VONDRA Alain Cc : libguestfs(a)redhat.com Objet : Re: [Libguestfs] Virt-v2v conversion issue On Wed, Oct 15, 2014 at 01:49:55PM +0000, VONDRA Alain wrote: I'm not sure, but ... Are you sure this couldn't be an NFS server problem? Any message or errors in 'dmesg'? Any kernel threads (see top) which are consuming time or stuck in 'D' state? I've been playing around with various test scripts (see attached) to see if I could reproduce this problem, but I couldn't reproduce it yet on RHEL 7.1 or Fedora 21. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/