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] New: Failed to start guest wih qcow/qcow2 image ag

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1430] New: Failed to start guest wih qcow/qcow2 image against c/s 19349
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 12 Mar 2009 21:21:07 -0700
Delivery-date: Thu, 12 Mar 2009 21:21:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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

           Summary: Failed to start guest wih qcow/qcow2 image against c/s
                    19349
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Windows
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx


Environment:
------------
Service Arch (ia32/ia32e/IA64): ia32/ia32e
Guest Arch (ia32/ia32e/IA64): ia32/ia32e
Guest OS Type (Linux/Windows):
Change Set: 19349
Hardware: Stoakley
Other:


Bug detailed description:
--------------------------
fail to bootup guest with qcow/qcow2 images against C/s 19349


Reproduce steps:
----------------
1. bootup xen
2. use "qcow-create -f qcow2 -r 10 qcowimg baseimg" to create a qcow2 image
3. bootup qcow2 image, failed


----------------


Basic root-causing log:
----------------------
Error: Device 768 (tap) could not be connected. Setting up the backend failed.
See the log files in /var/log/xen/ for details.

qemu log:
domid: 52
qemu: the number of cpus is 1
config qemu network with xen bridge for  tap52.0 xenbr2
Strip off blktap sub-type prefix to /share/xvs/var/img.vmxCPL_MEM_02 (drv
'qcow')
Watching /local/domain/0/device-model/52/logdirty/next-active
Watching /local/domain/0/device-model/52/command
xs_read(): vncpasswd get error.
/vm/89909713-da49-1a8e-65f7-1d1b7b674846/vncpasswd.
char device redirected to /dev/pts/4
qemu_map_cache_init nr_buckets = 10000 size 3145728
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 89909713-da49-1a8e-65f7-1d1b7b674846
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
xs_read(/local/domain/0/device-model/52/xen_extended_power_mgmt): read error
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0


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