[Xen-bugs] [Bug 1430] Failed to start guest with qcow/qcow2 image against c/s 19349

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1430





------- Comment #10 from arunain@xxxxxxxxx  2009-06-05 07:58 -------
Hello Andre

Still i am facing the same problem of cow overlay image not coming up.

# xm create winxp
Using config file "./winxp".
Error: Device 768 (tap) could not be connected. Setting up the backend failed.
See the log files in /var/log/xen/ for details.

Here are the steps i have done.

1. Xen build from 3.4-testing.hg
2.  Converted my existing winxp image file to qcow2 format.
# qemu-img-xen convert -O qcow2 winxp_pv.img winxp_pv_qcow2.img
3. Tested vm with below disk config in xen config file. Vm works fine here.
         disk = [ "tap:qcow2:/mnt/arch/winxp/winxp_pv_qcow2.img,hda,w" ,
                       "tap:aio:/mnt/arch/winxp/winxp.iso,hdb:cdrom,r" ]

4. Created cow overlay file.
# qcow-create -f qcow2 100M winxp.cow winxp_pv_qcow2.img
Optind 3, argc 6
Creating file size 104857600, name winxp.cow

5. Tested vm with below disk config in xen config file. Vm Fails
disk = [ "tap:qcow2:/mnt/arch/winxp/winxp.cow,hda,w" ,
         "tap:aio:/mnt/arch/winxp/winxp.iso,hdb:cdrom,r" ]

# xm create winxp
Using config file "./winxp".
Error: Device 768 (tap) could not be connected. Setting up the backend failed.
See the log files in /var/log/xen/ for details.

Code is also in patched state in my server. ( I have attached this source )
/usr/src/kernels/xen-3.4-testing.hg/tools/blktap/drivers/block-qcow.c

What mistake i am doing any guess. I have also attached the xen logs.

Any help will trigger the luck.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs