[ovirt-users] can't import vm from KVM host

[Nelson Lameiras]

Shahar,

Thanks!
I'll keep an eye on this bug and try to be helpfull when testing the fix.

nelson

----- Original Message -----
From: "Shahar Havivi" <shavivi at redhat.com>
To: "Nelson Lameiras" <nelson.lameiras at lyra-network.com>
Cc: "Nisim Simsolo" <nsimsolo at redhat.com>, users at ovirt.org
Sent: Thursday, September 22, 2016 10:14:33 AM
Subject: Re: [ovirt-users] can't import vm from KVM host

Nelson,
I opened a bug regarding your issue
https://bugzilla.redhat.com/show_bug.cgi?id=1378340

And send a fix:
https://gerrit.ovirt.org/#/c/64272/

Thank you for your help!

 Shahar.

On 21.09.16 10:57, Shahar Havivi wrote:
> On 20.09.16 10:24, Nelson Lameiras wrote:
> > Here is the disk section of my vm,
> > 
> > ...
> >     <disk type='block' device='disk'>
> >       <driver name='qemu' type='raw' cache='none' io='native'/>
> >       <source dev='/dev/mapper/vg_01-lv_sys'/>
> >       <target dev='vda' bus='virtio'/>
> >       <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
> >     </disk>
> >     <disk type='block' device='disk'>
> >       <driver name='qemu' type='raw' cache='none' io='native'/>
> >       <source dev='/dev/sdc'/>
> >       <target dev='vdb' bus='virtio'/>
> >       <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
> >     </disk>
> > ...
> > 
> > nelson
> Thanks Nelson,
> bz 1362525 will not solve your issue.
> We will start work on that block device issue shortly and I hope that it will
> make it to the next release.
> 
> Thank you,
>  Shahar.
> 
> > 
> > 
> > ----- Original Message -----
> > From: "Shahar Havivi" <shavivi at redhat.com>
> > To: "Nelson Lameiras" <nelson.lameiras at lyra-network.com>
> > Cc: "Nisim Simsolo" <nsimsolo at redhat.com>, users at ovirt.org
> > Sent: Tuesday, September 20, 2016 8:04:41 AM
> > Subject: Re: [ovirt-users] can't import vm from KVM host
> > 
> > On 19.09.16 18:11, Nelson Lameiras wrote:
> > > Well I think I have a rather "classical" environment :
> > > 
> > > This is the test setup I created (from scratch) in order to simulate future migrations (which will be used to migrate our hundreds of vm in production)
> > > 
> > > On one side, I have a x86_64 centos7.2+KVM hosting one VM with 2 iscsi disks : 
> > >   1 LVM block device /dev/mapper/vg_01-lv_sys, using virtio
> > >   1 block device /dev/sdc, using virtio
> > > 
> > > on the other side, I have a x86_64 centos 7.2 oVirt cluster (2 hosts, same hardware as KVM hosts) installed with 4.0.3 oVirt (hosts and engine) fully upgraded to 4.0.4RC1 (hosts and engine)
> > > Target would be oVirt iscsi Data Domain disk (which is irrelevant because the problem I'm describing arises before selecting oVirt target)
> > > 
> > > I'm using the GUI to test the native import capabilities of oVirt "Import VM"
> > > When selecting KVM import, putting correct URL data (using either tcp or ssh transport), I get a list of VM machines running in the KVM cluster (for this exemple, only the one VM described above), but the disk count is always 0. Which makes it impossible to import the VM.
> > > 
> > > I should add that I made the same VM import using "local hard drives" (ie. local raw file) and it works as expected, I can see one or multiple disks and import them easily to oVirt. The problem seems to manifest itself only when importing disks using block devices directly.
> > > 
> > > Do you need more information from me, or make more tests?
> > > 
> > > thanks a lot,
> > > nelson
> > Can you post the libvirt xml as attachment here (at least the disks sections):
> > 
> > $ virsh -r dumpxml <vmname>
> > 
> >  Shahar.