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. [email protected]<mailto:[email protected]> On 10 Apr 2019, at 09:36, Benny Zlotnik <[email protected]<mailto:[email protected]>> wrote: 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 <[email protected]<mailto:[email protected]>> 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 provider. Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. [email protected]<mailto:[email protected]> On 9 Apr 2019, at 12:12, Callum Smith <[email protected]<mailto:[email protected]>> wrote: 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 Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. [email protected]<mailto:[email protected]> On 8 Apr 2019, at 15:42, Callum Smith <[email protected]<mailto:[email protected]>> wrote: Dear All, We've exported some VMs from our old oVirt infrastructure and want to import them into the new one, but qemu-img appears to be failing. We have mounted an export domain populated from the old oVirt in the new hosted engine and are using the GUI to import the VM. Manually running the command sits at 16% CPU, 0% network usage and no progress. It appears to lock the NFS mount and ls and lsof both hang. sudo -u vdsm /usr/bin/qemu-img convert -p -t none -T none -f raw <path to source> -O raw <path to dest> Conversely a simple cp will work (ruling out file permissions errors): sudo -u vddm cp <path to source> <path to test> What might we be doing wrong? Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. [email protected]<mailto:[email protected]> _______________________________________________ Users mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/ZUBKWQIGGSJETPVRWN42R4J7COPFV6GS/ _______________________________________________ Users mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/6EE6X43GTAJ6L4QBH2XQJ4LVPIXCZC3T/ _______________________________________________ Users mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/GD2XCKEIPNCXXQWMR4OP5IKGCORJQEGB/
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/SV3V34DQJZ7A3MH4CQMMIZ4GPPHWFB7E/
