Bug 1303548 (virt-v2v-from-rhel-xen)

Summary: [RFE] Add ability to import RHEL Xen guest images directly into oVirt
Product: [oVirt] ovirt-engine Reporter: Shahar Havivi <shavivi>
Component: GeneralAssignee: Shahar Havivi <shavivi>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: bugs, mavital, michal.skrivanek, nsimsolo, sbonazzo, shavivi, tgolembi
Target Milestone: ovirt-4.0.0-alphaKeywords: FutureFeature
Target Release: 4.0.0Flags: rule-engine: ovirt-4.0.0+
mavital: testing_plan_complete?
rule-engine: planning_ack+
rule-engine: devel_ack+
mavital: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt 4.0.0 alpha1 Doc Type: Bug Fix
Doc Text:
In order to import VMs from Xen via RHEL passwordless SSH access has to be enabled between VDSM host and Xen. The following steps must be taken under vdsm user in the VDSM host that will perform the import of VMs: 1. Generate ssh keys for vdsm user: $ sudo -u vdsm ssh-keygen 2. Login to the Xen server via ssh in order to exchange keys with the Xen host: $ sudo -u vdsm ssh root@xenhost 3. Transfer public key to allow the access to Xen host: $ sudo -u vdsm ssh-copy-id root@xenhost oVirt is using virt-v2v to import the VMs from Xen servers, for more information on xen+ssh via virt-v2v reffer to http://libguestfs.org/virt-v2v.1.html under the "INPUT FROM RHEL 5 XEN" section. Example of a valid Xen URI: xen+ssh://root@xen.example.com
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-17 14:37:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1332167    
Bug Blocks: 1330517, 1373343    

Description Shahar Havivi 2016-02-01 09:37:28 UTC
For VMs that run on RHEL Xen and managed by Libvirt.

Comment 1 Red Hat Bugzilla Rules Engine 2016-02-01 09:41:56 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Red Hat Bugzilla Rules Engine 2016-02-01 09:41:56 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 8 Nisim Simsolo 2016-08-16 15:23:51 UTC
Verified 
ovirt-engine-4.0.2.6-0.1.el7ev
libvirt-client-1.2.17-13.el7_2.5.x86_64
vdsm-4.18.11-1.el7ev.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.21.x86_64
sanlock-3.2.4-3.el7_2.x86_64
virt-v2v-1.28.1-1.55.el7_2.4.x86_64