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/
Home Products Support Community News


[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: Wed, 15 Apr 2009 11:51:39 -0700
Delivery-date: Wed, 15 Apr 2009 11:51:45 -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

------- Comment #2 from xen@xxxxxxx  2009-04-15 11:51 -------
I have the same problem with a freshly created qcow2 image using the
qemu-img-xen tool.  The original qcow2 image works perfectly with
tap:qcow2, but attempting to use it as a base for a new image halts the
boot immediately.  The xend.log file don't show any errors, it only
points me to the VM-specific log, which just stops dead.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 1430] Failed to start guest with qcow/qcow2 image against c/s 19349, bugzilla-daemon <=