Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 600151

Summary: v2v failed convert windows guests with no OS detected inside disk image msg
Product: Red Hat Enterprise Linux 5 Reporter: Wayne Sun <gsun>
Component: v2v-libvirtAssignee: Matthew Booth <mbooth>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 5.7CC: berrange, cwei, gsun, mbooth, rjones, ryan.hogan, tools-bugs, veillard
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-03 12:49:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Wayne Sun 2010-06-04 03:09:15 UTC
Description of problem:
When converting the windows guests, it failed with under info:
2k3-32b-hv-raw-intel.xml
No operating system could be detected inside this disk image.

This may be because the file is not a disk image, or is not a virtual machine
image, or because the OS type is not understood by virt-inspector.

If you feel this is an error, please file a bug report including as much
information about the disk image as possible.


Version-Release number of selected component (if applicable):
virt-v2v-0.6.0-3.el5
v2v-libvirt-0.8.1-1.el5
libvirt-0.6.3-33.el5

How reproducible:
always

Steps to Reproduce:
1.virt-v2v -f /etc/virt-v2v.conf -i libvirtxml -op v2v_test 2k3-32b-hv-raw-intel.xml
2.
3.
  
Actual results:
converting failed

Expected results:
windows guest be converted successfully 

Additional info:
The xml info of guest 2k3-32b-hv-raw-intel:
<domain type='xen'>
  <name>2k3-32b-hv-raw-intel</name>
  <memory>524288</memory>
  <currentMemory>524288</currentMemory>
  <vcpu>2</vcpu>
  <os>
    <type>hvm</type>
    <loader>/usr/lib/xen/boot/hvmloader</loader>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <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='file'/>
      <source file='/mnt/V2V_image/xen-image/intel/2k3-32b-hv-raw-intel.img'/>
      <target dev='hda' bus='ide'/>
    </disk>
    <interface type='bridge'>
      <mac address='00:16:36:54:90:d1'/>
      <source bridge='xenbr0'/>
      <script path='vif-bridge'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/1'/>
      <target port='0'/>
    </serial>
    <console type='pty' tty='/dev/pts/1'>
      <source path='/dev/pts/1'/>
      <target port='0'/>
    </console>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='5902' autoport='yes' keymap='en-us'/>
  </devices>
</domain>

Comment 2 RHEL Program Management 2010-08-09 19:12:06 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 3 Ryan H. 2011-02-28 17:33:50 UTC
Hello, 

I'm having this same issue using virt-v2v. Here are my results: 

[root@WI16RDCNVRT01 ~]# virt-v2v -ic esx://wi16rdesx1.hommedeng.honeywell.com/?no_verify=1 -o rhev -osd 192.168.0.2:/rhev/export -network eth3 'Production Databases'
** HEAD https://wi16rdesx1.hommedeng.honeywell.com/folder/Production%20Databases/Production%20Databases-flat.vmdk?dcPath=ha-datacenter&dsName=datastore1 ==> 401 Unauthorized
** HEAD https://wi16rdesx1.hommedeng.honeywell.com/folder/Production%20Databases/Production%20Databases-flat.vmdk?dcPath=ha-datacenter&dsName=datastore1 ==> 200 OK
** GET https://wi16rdesx1.hommedeng.honeywell.com/folder/Production%20Databases/Production%20Databases-flat.vmdk?dcPath=ha-datacenter&dsName=datastore1 ==>200 OK (7081s)
open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support
No operating system could be detected inside this disk image.

This may be because the file is not a disk image, or is not a virtual machine
image, or because the OS type is not understood by virt-inspector.

If you feel this is an error, please file a bug report including as much
information about the disk image as possible.



Any thoughts?

Comment 4 Ryan H. 2011-02-28 19:13:10 UTC
Hello, 

I'm having this same issue using virt-v2v. Here are my results: 

[root@WI16RDCNVRT01 ~]# virt-v2v -ic esx://wi16rdesx1.hommedeng.honeywell.com/?no_verify=1 -o rhev -osd 192.168.0.2:/rhev/export -network eth3 'Production Databases'
** HEAD https://wi16rdesx1.hommedeng.honeywell.com/folder/Production%20Databases/Production%20Databases-flat.vmdk?dcPath=ha-datacenter&dsName=datastore1 ==> 401 Unauthorized
** HEAD https://wi16rdesx1.hommedeng.honeywell.com/folder/Production%20Databases/Production%20Databases-flat.vmdk?dcPath=ha-datacenter&dsName=datastore1 ==> 200 OK
** GET https://wi16rdesx1.hommedeng.honeywell.com/folder/Production%20Databases/Production%20Databases-flat.vmdk?dcPath=ha-datacenter&dsName=datastore1 ==>200 OK (7081s)
open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support
No operating system could be detected inside this disk image.

This may be because the file is not a disk image, or is not a virtual machine
image, or because the OS type is not understood by virt-inspector.

If you feel this is an error, please file a bug report including as much
information about the disk image as possible.



Any thoughts?

Comment 5 Matthew Booth 2011-03-01 10:14:13 UTC
(In reply to comment #4)
> Hello, 
> 
> I'm having this same issue using virt-v2v. Here are my results: 

Thanks, Ryan.

Can I assume this is on RHEL 5 with virt-v2v-0.6.3-5.el5 and libguestfs-1.2.7-1.el5.11?

Comment 6 Matthew Booth 2011-03-01 10:15:56 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > Hello, 
> > 
> > I'm having this same issue using virt-v2v. Here are my results: 
> 
> Thanks, Ryan.
> 
> Can I assume this is on RHEL 5 with virt-v2v-0.6.3-5.el5 and
> libguestfs-1.2.7-1.el5.11?

I ought to ask what the guest OS actually is, too :)

Comment 7 Ryan H. 2011-03-01 19:52:21 UTC
Th guest OS is Windows 2003 Server SP2. 

I'm using RHEL v6 with virt-v2v-06.2-4.el6 and libguestfs-1.2.7-1.24.el6

I'm tried updating the virt-v2v to the version you have above however when I run the package it throws me this: 

[root@WI16RDCNVRT01 ~]# yum update virt-v2v
Loaded plugins: refresh-packagekit, rhnplugin
Setting up Update Process
No Packages marked for Update

Comment 8 Matthew Booth 2011-03-02 09:54:41 UTC
(In reply to comment #7)
> Th guest OS is Windows 2003 Server SP2. 
> 
> I'm using RHEL v6 with virt-v2v-06.2-4.el6 and libguestfs-1.2.7-1.24.el6

Ah! You confused me because this is a RHEL 5 bug :)

In RHEL 6 we split NTFS support in libguestfs into a separate package: libguestfs-winsupport. You'll also need to add your host to the 'RHEL V2VWIN' channel on RHN to get access to it. This should allow libguestfs to detect the OS correctly. We've highlighted this requirement a bit better in the next version of the admin guide, and we will also mention it explicitly in the error message you saw.

You'll also need to install the virtio-win package on the host or the Windows virtio drivers won't be available.

Comment 9 RHEL Program Management 2014-03-07 12:48:20 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 10 RHEL Program Management 2014-06-03 12:49:15 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).