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

Shahar Havivi shavivi at redhat.com
Sun Aug 28 06:45:48 UTC 2016


On 25.08.16 11:32, Nelson Lameiras wrote:
> Thanks for your answer. I do not think that I'm experiencing that same bug exactly.
> 
> The issue 1362525 (below) concerns a KVM VM with iSCSI disk being importend to RHEV that does not perform well.
> 
> In my case, when oVirt GUI proposes me the list of machines on KVM host to import, each machine as a "disk count" next to it.
> - This "disk count" is correct if the VM has it's storage on a raw/qcow file (local) - and import goes well
> - But "disk count" is 0 (always) if the VM has it's storage on a block device (ie iscsi) - and import is not possible at all!
> 
> It seems to me that current oVirt migration tool is unable to read/analyse distant VM machines with block device storage... Maybe I'm analysing this issue wrongly.
Yes,
This was the issue as well - seeing zero disks when the source VM had block disk devices.

Adding Nisim to verify it.

> 
> Thanks,
> nelson
> ----- Original Message -----
> From: "Shahar Havivi" <shavivi at redhat.com>
> To: "Nelson Lameiras" <nelson.lameiras at lyra-network.com>
> Cc: users at ovirt.org
> Sent: Tuesday, August 23, 2016 12:19:13 PM
> Subject: Re: [ovirt-users] can't import vm from KVM host
> 
> On 23.08.16 11:24, Nelson Lameiras wrote:
> > Hello,
> Hi,
> 
> We do have a bug on that issue:
> https://bugzilla.redhat.com/show_bug.cgi?id=1362525
> and its handled.
> 
> Thanks,
>  Shahar.
> > 
> > I'm trying to import virtual machines from a KVM host (centos 7.2) to an oVirt 4.0.2 Cluster using the "import" feature on GUI.
> > 
> > If the original VM is using RAW/QCOW2 files as storage, everything works fine. 
> > 
> > But if the original VM is using a special block special device as storage (like a LVM or SAN volume), it's simply not recognized. 
> > The VM does appear in the import list of the KVM host, but it's disk count is 0!
> > 
> > Is this a known technical obstacle or am I doing something wrong ?
> > 
> > below is the storage part of the xml describing the original 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>
> > 
> > We have hundreds of virtual machines in production with this type of configuration... How can we migrate them safely to oVirt?
> > 
> > thanks
> > 
> > Nelson
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users



More information about the Users mailing list