[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-22 Thread Benny Zlotnik
Can you enable vdsm debug level logs[1] so we can see the exact command? [1] - https://www.ovirt.org/develop/developer-guide/vdsm/log-files.html On Sat, Apr 20, 2019 at 1:42 PM Callum Smith wrote: > > Dear Benny, > > This is via VDSM, but a manual one fails too. > > Background: cloning of an

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-20 Thread Callum Smith
Dear Benny, This is via VDSM, but a manual one fails too. Background: cloning of an image fails in any context, whether creating from template, using Clone VM, etc etc. Tested on any 4.3+ on multiple NFS servers etc. Even tried allowing root access and not, seems to not fix. gdb is blank and

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-20 Thread Benny Zlotnik
Sorry, I kind of lost track of what the problem is The "KeyError: 'appsList'" issue is a known bug[1] If a manual (not via vdsm) run of qemu-img is actually stuck, then let's involve the qemu-discuss list, with the version of the relevant packages (qemu, qemu-img, kernel, your distro) and the

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-19 Thread Callum Smith
Dear Benny and others, So it seems I wasn’t being patient with GDB and it does show me some output. This error of qemu-img convert even is failing and preventing updating ovirt-node version from 4.3.2 to 4.3.3.1. I get a feeling this is an unrelated error, but I thought I’d be complete:

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-11 Thread Callum Smith
Without the sudo and running in a dir where the root has access to, gdb has zero output: [cid:CCCDE95C-DD82-48AE-90E0-68295827C3F9@in.bmrc.ox.ac.uk] Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e.

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-11 Thread Callum Smith
Some more information: running qemu-img convert manually having captured the failed attempt from the previous: sudo -u vdsm /usr/bin/qemu-img convert -p -t none -T none -f raw

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-11 Thread Callum Smith
Dear Benny, It would seem that even cloning a VM is failing, creating a VM works on the same storage. This is the only error i could find: ERROR Internal server error Traceback (most recent call last):

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-10 Thread Callum Smith
Creating a disk on the target share works fine. - This seems to specifically be an issue to do with moving a disk to/from a share. Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e.

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-10 Thread Callum Smith
gdb -p $(pidof qemu-img convert) -batch -ex "t a a bt" 289444: No such file or directory. Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. cal...@well.ox.ac.uk On 10 Apr 2019, at 09:36, Benny

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-10 Thread Benny Zlotnik
Can you run: $ gdb -p $(pidof qemu-img convert) -batch -ex "t a a bt" On Wed, Apr 10, 2019 at 11:26 AM Callum Smith wrote: > > Dear All, > > Further to this, I can't migrate a disk to different storage using the GUI. > Both disks are configured identically and on the same physical NFS

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-10 Thread Callum Smith
Dear All, Further to this, I can't migrate a disk to different storage using the GUI. Both disks are configured identically and on the same physical NFS provider. Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e.

[ovirt-users] Re: Import of VMs failing - 0% progress on qemu-img

2019-04-09 Thread Callum Smith
Dear All, It would seem this is a bug in 4.3.? - As upgrading the old oVirt HE to 4.3 (from 4.2.latest) now means that the export of VMs to export domain no longer works. Again qemu-img convert is using some cpu, but no network. Progress is 0. Regards, Callum -- Callum Smith Research