Created attachment 1226644 [details] vdsm.log Description of problem: Guest will disappear soon after starting import from xen server on rhv4.0 Version-Release number of selected component (if applicable): The packages on registed host: qemu-kvm-rhev-2.6.0-29.el7.x86_64 virt-v2v-1.32.7-3.el7.x86_64 vdsm-4.18.9-1.el7ev.x86_64 RHV4.0:4.0.5-0.1.el7ev How reproducible: 100% Steps to Reproduce: 1.Environment setup: In order to import VMs password-less SSH access has to be enabled between VDSM host and the Xen host. The following steps needed to be done at the VDSM host: 1.1 Generate ssh key for vdsm user # sudo -u vdsm ssh-keygen 1.2 Copy vdsms public key to the Xen host # sudo -u vdsm ssh-copy-id root@*xen IP* 1.3 Login to the remote host (in order to test the connection and add the Xen host to the known_hosts file # sudo -u vdsm ssh root@* xen IP* Result: Can login without password 1.4 Exit the remote Xen host logout 2. Then login rhv 4.0 and try to import virtual machine from Xen. Virtual Machines-->Import-->Fill items on 'Import Virtual Machine(s)' window with: Data Center:xx Source: Xen(via RHEL) URI: xen+ssh://root@* xen IP* Proxy Host: *host * 3.After load, then select guest name list in "Virtual Machines on Source" to import, then click "Next" , then click "OK" in next page, then guest import start. 4.Guest will disappear soon after starting import from xen server on rhv4.0 Actual results: Step4 failed to convert xen server's guests with error: Fail to import Vm guest to Data Center Default,Cluster Default Expected results: Convert xen server's guests on rhv4.0 successfully Additional info: Could convert guest from xen server by v2v on the host which is registed on rhv4.0 1：ssh to registed host. 2：Define a password for user: # echo password |saslpasswd2 -p -a libvirt username 3:Using v2v to convert guest from xen server to rhv4.0: # virt-v2v -ic xen+ssh://IP $guest -o rhev -os IP:/home/nfs_export
Created attachment 1226645 [details] engine.log
Please also add host logs, vdsm.log and v2v
just the v2v log:)
Created attachment 1227186 [details] v2v.log
so..the log seems to show a successful conversion. Did you attach log from the failure? When you say it works on cmdline, does it work when running exactly this?: /usr/bin/taskset --cpu-list 0-3 /usr/bin/nice -n 19 /usr/bin/ionice -c 3 /usr/bin/virt-v2v -ic xen+ssh://root.144.38 -o vdsm -of raw -oa sparse --vdsm-image-uuid cf49654e-c756-474a-9f6f-866d0c382529 --vdsm-vol-uuid 20750a55-6e0a-416f-aba3-9e5c01a2d060 --vdsm-vm-uuid 8ebaa2fb-ff42-5dc1-b4c3-aca343f4a302 --vdsm-ovf-output /var/run/vdsm/v2v --machine-readable -os /rhev/data-center/ab6c235b-95ba-4eb5-b363-4c951413d716/b7258e76-a133-42ef-9e8c-583cdd8cec42 test1
Created attachment 1227256 [details] v2v-vdsm.log
This is a duplicate of already fixed bug. Please update your vdsm, this should be fixed in vdsm-4.18.12-1.el7ev.x86_64 *** This bug has been marked as a duplicate of bug 1367839 ***
Hi,I think it is still has some problem. when i update vdsm to the latest patch，it has another error. Version-Release： vdsm-4.18.18-1.el7ev.x86_64 qemu-kvm-rhev-2.6.0-29.el7.x86_64 virt-v2v-1.32.7-3.el7.x86_64 RHV4.0:4.0.6-3 Steps to Reproduce: 1:As above。 Actual results: 1：As the attach picture. It will give us the " some vms are running in the external system and therefore have been filtered"
Created attachment 1231442 [details] GUI_image
Created attachment 1231443 [details] new_vdsm.log
Only VMs which are down can be converted, others are filtered out. e.g. this is not an error message, it is just a warning which tells you why you don't see some (any) VMs in the list. Are the VMs on the source system down?
Yes,you are right.All the vms had been down. As you see,we can't see any one vms.
In logs I see problem with permissions while connecting to the Xen host. Can you recheck that the password-less ssh access still works after the upgraded of VDSM host?
Yes,I am sure password still works,and I am sorry the log maybe contain a long time,i will attach a new log.
Created attachment 1231938 [details] newvdsm
From logs it looks a lot like you have only one VM on the XEN server and that one is UP. If this is indeed the case it is an expected behavior. Could you please make double sure that you have a down VM on the XEN from the time you are providing the logs?
Yes , I am sure all the guest had dowm,when i run the command :virsh list [root@dell-op780-04 ~]# virsh list --all Id Name State ---------------------------------- 0 Domain-0 running - rhel6.7 shut off - xen-hvm-rhel6.7-mxie shut off So,in the Xen server has two guest ,and had been shut off.
4.0.6 has been the last oVirt 4.0 release, please re-target this bug.
Verification builds: rhevm-4.0.7-0.1.el7ev qemu-kvm-rhev-2.6.0-28.el7_3.3.x86_64 vdsm-4.18.22-1.el7ev.x86_64 libvirt-client-2.0.0-10.el7_3.4.x86_64 sanlock-3.4.0-1.el7.x86_64 virt-v2v-1.32.7-3.el7_3.2.x86_64 Verification scenario (Polarion test case) added to external trackers.