Bug 822221 - conversion/transfer of VM from libvirt to oVirt export domain fails
Summary: conversion/transfer of VM from libvirt to oVirt export domain fails
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-v2v
Version: 17
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Booth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-16 16:42 UTC by Jason Brooks
Modified: 2013-07-02 16:13 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2013-07-02 16:13:52 UTC


Attachments (Terms of Use)

Description Jason Brooks 2012-05-16 16:42:32 UTC
Description of problem:

Conversion/transfer of an F16 VM created with virt-manager to an oVirt 3.0 export domain fails with the error text:

Use of uninitialized value $transferdev in quotemeta at /bin/virt-v2v line 609.
Use of qw(...) as parentheses is deprecated at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 169.
Use of qw(...) as parentheses is deprecated at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 178.
Use of qw(...) as parentheses is deprecated at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 230.
Use of qw(...) as parentheses is deprecated at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 252.
umount: umount: /transferPCxaYv: umount: /sysroot/transferPCxaYv: not mounted at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 193.
 at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Config.pm line 262

Version-Release number of selected component (if applicable):

virt-v2v-0.8.3-2.fc17.x86_64

How reproducible:

sudo virt-v2v VMNAME -o rhev -os IP-ADDR:/nfs/export

Steps to Reproduce:
1.
2.
3.
  
Actual results:

Get error message noted above, VM doesn't appear in export domain.

Expected results:

VM appears in export domain.

Additional info:

Comment 1 Cole Robinson 2013-07-02 16:13:52 UTC
Sorry for the lack of response. virt-v2v has been updated quite a few times in F17+, so this bug may already be fixed. F17 is end-of-life in a month though, so if you can still reproduce, please verify against F19 and reopen.


Note You need to log in before you can comment on or make changes to this bug.