Bug 1378340 - v2v: Extended support for block device
Summary: v2v: Extended support for block device
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.0-beta
: 4.19.2
Assignee: Shahar Havivi
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On: 1416112
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 08:07 UTC by Shahar Havivi
Modified: 2017-08-27 11:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-15 14:55:20 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: planning_ack+
michal.skrivanek: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 64272 0 master MERGED v2v: support for block devices 2016-12-16 10:20:21 UTC
oVirt gerrit 67815 0 master MERGED kvm2ovirt: Support for downloading block devices 2017-01-12 18:50:40 UTC
oVirt gerrit 70419 0 ovirt-4.1 MERGED v2v: move kvm2ovirt to lib/vdsm/ 2017-01-16 09:00:02 UTC
oVirt gerrit 70420 0 ovirt-4.1 MERGED add tests for kvm2ovirt 2017-01-16 09:08:44 UTC
oVirt gerrit 70421 0 ovirt-4.1 MERGED kvm2ovirt: Support for downloading block devices 2017-01-16 09:18:44 UTC

Description Shahar Havivi 2016-09-22 08:07:32 UTC 
Extended support for block devices for KVM and VMWare.
currently we do support block devices that exported as file in libvirt:
<disk type='file' device='disk'>
  <source file='...'/>
  ...

Added support for type block is needed:
<disk type='block' device='disk'>
  <source dev='/dev/mapper/...'/>
  ...
Comment 1 Shahar Havivi 2017-01-18 08:00:34 UTC 
The fix presented a bug when importing from KVM and not supplying username.
As a workaround user can set any arbitrary username and password if the uri doesn't require authentication.
bz #1414256 fix this issue
Comment 2 Nisim Simsolo 2017-02-02 12:52:56 UTC 
Verification builds:
ovirt-engine-4.1.0.3-0.1.el7
libvirt-client-2.0.0-10.el7_3.4.x86_64
vdsm-4.19.4-1.el7ev.x86_64
qemu-kvm-rhev-2.6.0-28.el7_3.3.x86_64
sanlock-3.4.0-1.el7.x86_64
Comment 3 Nisim Simsolo 2017-08-27 11:52:16 UTC 
Verification scenario:
1. Edit KVM VM disk using virsh command and change it to block device:
    <disk type='block' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source dev='/var/lib/libvirt/images/nsimsolo_kvm_new /centos_minimal.qcow2'/>
      <target dev='sdb' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
2. From RHV host -> virsh dumpxml this VM and verify disk type='block':
virsh # dumpxml centos_minimal
<domain type='kvm'>
  <name>centos_minimal</name>
  .
  .
  .
  <disk type='block' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source dev='/var/lib/libvirt/images/nsimsolo_kvm_new/centos_minimal.qcow2'/>
      <target dev='sdb' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
3. Browse webadmin -> VMs tab -> import, select above mentioned VM and download it.
4. After download succeeded, run VM and verify VM is running properly.
Note You need to log in before you can comment on or make changes to this bug.