Hello, Any update on this issue? Can I do anything to help?
cordialement, regards, Nelson LAMEIRAS Lyra Network Service Projets et Processus Tel : +33 (0) 5 32 09 09 70 109 rue de l’innovation 31670 Labège - France www.lyra-network.com ----- Original Message ----- From: "Michal Skrivanek" <[email protected]> To: "Tomas Golembiovsky" <[email protected]> Cc: "Nelson Lameiras" <[email protected]>, [email protected] Sent: Tuesday, October 11, 2016 4:11:36 PM Subject: Re: [ovirt-users] can't import vm from KVM host > On 11 Oct 2016, at 16:01, Tomáš Golembiovský <[email protected]> wrote: > > Hi, > > On Mon, 10 Oct 2016 12:21:47 +0200 (CEST) > Nelson Lameiras <[email protected]> wrote: > >> hello michal, >> >> Yes, both paths are correct and working on the source host since the VM >> starts and works correctly on source host. Nevertheless I have checked with >> fdisk and mount to assure that these devices are indeed reachable. >> >> Please understand that my setup is the following: >> source host : KVM (hosting the VM to migrate) >> target host : oVirt 4.0.4 (patched) >> >> The error "no storage vol with matching path '/dev/sdc'" is returned by the >> target host script /usr/lib/python2.7/site-packages/vdsm/v2v.py. >> This almost seems normal since the device /dev/sdc is not mounted on target >> host (where script is running) but only on source host. >> >> Can this be the source of the error ? > > To me this looks more like a bug in the engine, not in VDSM. > > The exception in the VDSM log is OK and it is not fatal. It is actually > to be expected for block devices. VDSM is trying to find out the size of > the disk, but the way it does that is tailored for volumes in storage > pool. But the block device is not a volume in a storage pool and that is > why libvirt complains. We can potentially skip the check for block > devices to avoid error in the log, or provide some other logic of > getting the size. > > > But the real problem is this error in engine.log: > >> 2016-09-29 14:13:48,637 ERROR >> [org.ovirt.engine.core.bll.GetVmsFromExternalProviderQuery] (default >> task-30) [] Exception: org.ovirt.engine.core.common.errors.EngineException: >> EngineException: java.lang.NumberFormatException: null (Failed with error >> ENGINE and code 5001) > > We don't send the size (or rather send null value) for the disk and > engine does not like that. I assume engine does not really consider all > the optional VM properties as optional. is it really optional in schema? even if it is, indeed it’s wrong:) the best would be to handle it on v2v.py side first to avoid libvirt err, but i don’t know if we can get that info via libvirt in any other way:/ > > > > Tomas > > -- > Tomáš Golembiovský <[email protected]> _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
