[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


andre.przywara@xxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andre.przywara@xxxxxxx
           Severity|normal                      |major
         OS/Version|Windows                     |All




------- Comment #3 from andre.przywara@xxxxxxx  2009-05-15 06:43 -------
We can reproduce this with qcow images only. The problem is occuring only with
empty images (newly created with qemu-img create). Already (partly) populated
images are not affected. The problem can be reproduced with
xm block-attach 0 tap:qcow://path/to/empty.qcow /dev/xvda1 r 0
It seems like the initialization of a new blktap device fails. The only
difference in xend.log is: empty qcow image (failing):
DEBUG (DevController:643) hotplugStatusCallback 2
 populated (working) image:
DEBUG (DevController:643) hotplugStatusCallback 1
The Dom0 is the latest 2.6.18.8-xen.

Sadly this behaviour breaks our workflow of installing guests with empty QCOW
harddrives.


-- 
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