Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 725685 - xenpv linux guest can not start after conversion because qemu get 'aio' invalid format
xenpv linux guest can not start after conversion because qemu get 'aio' inva...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-v2v (Show other bugs)
6.2
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: Matthew Booth
Virtualization Bugs
: TestBlocker
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-26 05:56 EDT by Huang Wenlong
Modified: 2013-10-20 17:44 EDT (History)
4 users (show)

See Also:
Fixed In Version: virt-v2v-0.8.3-1.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-12-06 09:49:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1615 normal SHIPPED_LIVE Low: virt-v2v security and bug fix update 2011-12-05 19:51:05 EST

  None (edit)
Description Huang Wenlong 2011-07-26 05:56:15 EDT
Description of problem:
xenpv linux guest  can not start after conversion because qemu get 'aio' invalid format.
qemu-kvm can not start with "format=aio "


Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.171.el6.x86_64
augeas-libs-0.7.2-6.el6.x86_64
febootstrap-supermin-helper-2.11-7.el6.x86_64
hivex-1.2.4-3.el6.x86_64
libguestfs-1.7.17-19.el6.x86_64
libguestfs-winsupport-1.0-6.el6.x86_64
libvirt-0.9.3-7.el6.x86_64
virtio-win-1.1.16-3.el6.noarch
virt-v2v-0.8.2-1.el6.x86_64



How reproducible:
100%

Steps to Reproduce:
1. convert guest 
#virt-v2v -ic xen+ssh://10.66.72.123 -os r6 -b breth0 xen-pv-rhel6.1-x86_64

2. try to start guest 
# virsh start  xen-pv-rhel6.1-x86_64
error: Failed to start domain xen-pv-rhel6.1-x86_64
error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/3
qemu-kvm: -drive file=/home/v2v/rhel6u1-64b-pv.img,if=none,id=drive-virtio-disk0,format=aio: 'aio' invalid format

  
3.
#virsh dumpxml xen-pv-rhel6.1-x86_64
...
<disk type='file' device='disk'>
      <driver name='qemu' type='aio'/>
      <source file='/mnt/data/images/rhel6u1-64b-pv.img'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
...


Actual results:
guest can not start 

Expected results:
guest can  start 

Additional info:
If we modify xml file from <driver name='qemu' type='aio'> to <driver name='qemu' type='raw'> ,the guest can start
Comment 2 yuping zhang 2011-07-27 06:44:07 EDT
As this issue stop all xen-pv guests started after conversion,so add the TestBlocker keyword.
Comment 5 Matthew Booth 2011-07-27 11:57:11 EDT
Fix for this is upstream.
Comment 8 Huang Wenlong 2011-08-25 22:53:14 EDT
Verify this bug in virt-v2v-0.8.3-3.el6 

#  virt-v2v -ic xen+ssh://10.66.72.123 -os r6 -b breth0 xen-pv-rhel6.1-i386
root@10.66.72.123's password: 
rhel6u1-32b-pv.img: 100% [=========================================================================================================]D 0h02m09s
virt-v2v: xen-pv-rhel6.1-i386 configured with virtio drivers.


# virsh start xen-pv-rhel6.1-i386 
Domain xen-pv-rhel6.1-i386 started


# virsh dumpxml xen-pv-rhel6.1-i386
....
<devices>
    <emulator>/usr/libexec/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/data/images/rhel6u1-32b-pv.img'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
  
....
Comment 9 errata-xmlrpc 2011-12-06 09:49:41 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2011-1615.html

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