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

[Xen-devel] Reproduced error when creating Intrepid HVM at Xen Unstable

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Reproduced error when creating Intrepid HVM at Xen Unstable Dom0(vmlinuz-2.6.29-rc5-tip)
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Sat, 21 Feb 2009 01:01:39 -0800 (PST)
Delivery-date: Sat, 21 Feb 2009 01:02:45 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1235206899; bh=R5juH8Ww4TJwqsKTtZQLqug6v24q2omuQZo1VnKwG2Q=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=l01enuseWQhugEG2H9riZkGgpi+u7IcwXVOjRbHaN4Do6f+Zgfi0OJF77Sc5coiahKCPlu/yqAZSUhxpSSiKUEu69yUNs6OfMVf+cXKGWCaZOuAcGUw8sSjSCYffJLz1jKJBkfS/Z7nKUTi4sSJ5DamUF3qDtzg/wHqeIkr6VME=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=aBAMhAYliYsSem63ieFcfUZha/So3GJY/FMaavZ5KkqOEAuaF/Lal374ZpozO1Z3+7HhUoDCq+jPV2OLakdE6MMLpA3VpHhGBEqyc51I/boznDBH31cbtI6HXdXCQ9LHy1likJAbR0fNRo7kF6MQJjCUuGwVXi8ERSC6Q9h67hs=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f4527be0902200739s1d234567qf9ede85f917bfaf7@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bderzhavets@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
After fresh port Xen Unstable:-

[root@ServerXen xen]# ls -l qemu-dm-UbuntuHVM.log
-rwxr-xr-x 1 root root 810 Feb 21 11:29 qemu-dm-UbuntuHVM.log
[root@ServerXen xen]# cat qemu-dm-UbuntuHVM.log
domid: 1
qemu: the number of cpus is 1
config qemu network with xen bridge for  tap1.0 eth0
Watching /local/domain/0/device-model/1/logdirty/next-active
Watching /local/domain/0/device-model/1/command
xs_read(): vncpasswd get error. /vm/eea6ff6e-737f-b453-94e4-c6015c5a9aa0/vncpasswd.
qemu_map_cache_init nr_buckets = 10000 size 3145728
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = eea6ff6e-737f-b453-94e4-c6015c5a9aa0
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/1/xen_extended_power_mgmt): read error
medium change watch on `hdc' (index: 0): /dev/loop0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
cirrus vga map change while on lfb mode

No patching has been done due to zero awareness what to apply.


"If we assign the device that doesn't have Power Management Capability
Structure to guest domain, qemu accesses NULL pointer."

I am getting the same error
"xs_read(/local/domain/0/device-model/2/xen_extended_power_mgmt): read
error"

Yuji said "I'll submit the patch to fix the bug ASAP", I will try
again once his patch is submitted.

Andy

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

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