Re: [ovirt-users] vmware import hangs after click load button on 3.5 rc5

On Wed, Sep 23, 2015 at 8:21 PM, Nir Soffer <nsoffer(a)redhat.com&gt; wrote: > On Wed, Sep 23, 2015 at 12:40 PM, Ian Fraser <Ian.Fraser(a)asm.org.uk&gt; > wrote: > >> Hi Nir, >> >> I have changed the v2v.py file as per your request, it has now changed >> the behaviour. The popup window still hangs and I get the following two >> events: >> >> Failed to retrieve VMs information from external server >> vpx://username%40domain@vcenter.server >> /datacentre_name/hostname?no_verify=1 >> >> VDSM ovirt-host-02 command failed: internal error: Invalid or not yet >> handled value 'emptyBackingString' for VMX entry 'ide1:0.fileName' for >> device type 'cdrom-image' >> > > Fixing the first error, we see now the real error; libvirt cannot handle > this vm configuration. We will ask one of the libvirt guys to look into > this. >

> You may try to disable the cdrom device on that vm, which is probably > useless now. > > >> >> I have attached the vdsm.log to this email, should I also attach to the >> BZ I opened? > > > Yes, please attach it. > Hmm, this is a new issue, as the original issue is solved by the patch. Please open a new bug for the libvirt error: internal error: Invalid or not yet handled value 'emptyBackingString' for VMX entry 'ide1:0.fileName' for device type 'cdrom-image' Thanks, Nir > > (Adding back users(a)ovirt.org, since this thread may help others with > same issue.) > > >> >> Many thanks >> >> Ian >> >> From: Nir Soffer [mailto:nsoffer@redhat.com] >> Sent: 23 September 2015 00:04 >> To: Ian Fraser <Ian.Fraser(a)asm.org.uk>; Shahar Havivi < >> shavivi(a)redhat.com&gt; >> Cc: users(a)ovirt.org >> Subject: Re: [ovirt-users] vmware import hangs after click load button >> on 3.5 rc5 >> >> Hi Ian, >> >> Your import failed because looking up some disk failed. Unfortunately, >> we don't have enough information in the log abut this failure. >> >> Because of incorrect error handling, this error failed the entire >> request, failing your import. >> >> Patch [1] fixes the second problem. If is possible that with this patch >> listing the external vms will work and you will be able to import the vm, >> but it is also possible that the first error was significant and will fail >> the import later. >> >> It would be useful if you test this patch and report if it works for you. >> >> Would you open an ovirt bug for this issue, attaching the vdsm log? >> >> [1] https://gerrit.ovirt.org/46540 >> >> Nir >> >> On Tue, Sep 22, 2015 at 9:09 AM, Ian Fraser <Ian.Fraser(a)asm.org.uk&gt; >> wrote: >> Thanks Nir, >> >> File attached. >> >> From: Nir Soffer [mailto:nsoffer@redhat.com] >> Sent: 21 September 2015 23:16 >> To: Ian Fraser <Ian.Fraser(a)asm.org.uk&gt; >> Cc: users(a)ovirt.org >> Subject: Re: [ovirt-users] vmware import hangs after click load button >> on 3.5 rc5 >> >> On Tue, Sep 22, 2015 at 12:14 AM, Ian Fraser <Ian.Fraser(a)asm.org.uk&gt; >> wrote: >> I did get a “VDSM <hostname> command failed: local variable 'capacity' >> referenced before assignment” error in the events I have just noticed, does >> that shed any more light? >> >> This shed some light. Can you share the vdsm.log containing this error? >> >> Look in /var/log/vdsm/vdsm.log* >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> ________________________________________ >> >> The information in this message and any attachment is intended for the >> addressee and is confidential. If you are not that addressee, no action >> should be taken in reliance on the information and you should please reply >> to this message immediately to inform us of incorrect receipt and destroy >> this message and any attachments. >> >> For the purposes of internet level email security incoming and outgoing >> emails may be read by personnel other than the named recipient or sender. >> >> Whilst all reasonable efforts are made, ASM (UK) Ltd cannot guarantee >> that emails and attachments are virus free or compatible with your systems. >> You should make your own checks and ASM (UK) Ltd does not accept liability >> in respect of viruses or computer problems experienced. >> Registered address: Agency Sector Management (UK) Ltd. Ashford House, >> 41-45 Church Road, Ashford, Middlesex, TW15 2TQ >> Registered in England No.2053849 >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> ________________________________ >> >> The information in this message and any attachment is intended for the >> addressee and is confidential. If you are not that addressee, no action >> should be taken in reliance on the information and you should please reply >> to this message immediately to inform us of incorrect receipt and destroy >> this message and any attachments. >> >> For the purposes of internet level email security incoming and outgoing >> emails may be read by personnel other than the named recipient or sender. >> >> Whilst all reasonable efforts are made, ASM (UK) Ltd cannot guarantee >> that emails and attachments are virus free or compatible with your systems. >> You should make your own checks and ASM (UK) Ltd does not accept liability >> in respect of viruses or computer problems experienced. >> Registered address: Agency Sector Management (UK) Ltd. Ashford House, >> 41-45 Church Road, Ashford, Middlesex, TW15 2TQ >> Registered in England No.2053849 >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> > >