Bug 601098 - virt-v2v | convert with wrong type didn't get any error or warning message
virt-v2v | convert with wrong type didn't get any error or warning message
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-v2v (Show other bugs)
5.7
All Linux
low Severity medium
: rc
: ---
Assigned To: Matthew Booth
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-07 04:27 EDT by Mohua Li
Modified: 2013-04-30 19:13 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-07 05:11:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mohua Li 2010-06-07 04:27:02 EDT
Description of problem:

convert the kvm image with xenpv/xenhvm configuration,get pass and without any message, better to check if the configuration in the guest image match with the configuration, if not, then give error message, but no just continue without any error, and it will make user confuse if convert with problem but without any warning or sth, although till now the wrong match could convert successfully,



virt-v2v -f /etc/virt-v2v.conf -i libvirtxml -o rhev -osd 10.66.90.115:/vol/v2vrwu/rwuv2v /tmp/RHEL-Server-5.4-32.raw.xml

[root@dhcp-66-70-148 v2v]# cat /tmp/RHEL-Server-5.4-32.raw.xml
<domain type='xen' id='307'>   //the configuration is for xen                      
  <name>RHEL-Server-5.4-32.raw</name>
  <memory>524288</memory>
  <currentMemory>524288</currentMemory>
  <vcpu>4</vcpu>
  <os>
    <type>hvm</type>
    <loader>/usr/lib/xen/boot/hvmloader</loader>
    <boot dev='hd'/>
  </os>
  <features>
    <pae/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
    <disk type='file' device='disk'>
      <driver name='tap' type='aio'/>
      <source file='/media/disk/RHEL-Server-5.4-32.raw'/>      //kvm image
      <target dev='hda' bus='ide'/>
    </disk>
   <interface type='bridge'>
    <mac address='00:16:36:13:66:38'/>
      <source bridge='xenbr0'/>
      <script path='vif-bridge'/>
      <target dev='vif70.0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/8'/>
      <target port='0'/>
    </serial>
    <console type='pty' tty='/dev/pts/8'>
      <source path='/dev/pts/8'/>
      <target port='0'/>
    </console>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='6207' autoport='yes'/>
  </devices>
</domain>

here is a summary, what i tested,

base kernel,

1,kvm image with (xenpv configuration file, xenhvm configuration file), pass without error
2,xenpv image with kvm configuration file,                              pass without error, 



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

How reproducible:
always

Steps to Reproduce:
1.convert with disk image and configuration didn't match like below,
virt-v2v -f /etc/virt-v2v.conf -i libvirtxml -o rhev -osd 10.66.90.115:/vol/v2vrwu/rwuv2v /tmp/RHEL-Server-5.4-32.raw.xml
2.check the convert result after finished,
3.
  
Actual results:
convert completed without any error or warning 

Expected results:
should have error message, continue or not should depends on the detail implementation of the convert process, 


Additional info:
add the log during the convert process,
Comment 1 Matthew Booth 2010-06-07 05:11:12 EDT
We can't second guess things like this. The tool is already pretty resilient to this kind of error as it mostly looks at the disk image in isolation, which is why it worked. I don't think it's worth risking adding a whole new class of potential bugs by second guessing the data we were given.

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