WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1430] Failed to start guest with qcow/qcow2 image agains

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1430] Failed to start guest with qcow/qcow2 image against c/s 19349
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 15 May 2009 06:43:00 -0700
Delivery-date: Fri, 15 May 2009 06:43:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1430-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@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

<Prev in Thread] Current Thread [Next in Thread>