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

Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip

To: Ian.Jackson@xxxxxxxxxxxxx, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Sun, 22 Feb 2009 14:20:54 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Delivery-date: Sun, 22 Feb 2009 06:21:21 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=CndCkzdgFUuTW1q5LRBbXjsyZAD6vD8oInXdy7NxRMU=; b=Or6SLHhY//TQitDQs4wECve4uEoCar1N5HTmE0P4gS31ULYqIP+V6WRcaWR0tWWp5I NPCaSBHRXX4S2eE9CREIaA7wfzZG0BWOxyh7J06BeoBA3A4tK38gyH5IHreFzyV9DGLD HnuAZqUi8uP8AkwvBpIjAa9GPanHbKxj2lIeI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=gmXTZIdNuDLg/HC1LIJQbdThjL6lMu5ISzVl9pfQs/SRvEfWIPpmson+tRVjwODZZK ok/+7u12QancVrY9puwOTncD951xrNRzu0+Y1a6SjxlPP8JBdiiBJVIJPz9Rmu1fSakw qYZwbDj7I3qMKdtvY9eQ1I2q6h1sjQOL3Jv/o=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49A02366.3040505@xxxxxxxx>
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>
References: <310295.43521.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <927395.41213.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <f4527be0902181053kbcc1a03mc6ae385b805993cd@xxxxxxxxxxxxxx> <499D971C.7020304@xxxxxxxx> <f4527be0902200104u3e683de1he474b76e36be48f1@xxxxxxxxxxxxxx> <499E799B.2080008@xxxxxxxxxx> <f4527be0902210440l19a6c937h2b33c1ffca1b5971@xxxxxxxxxxxxxx> <49A02366.3040505@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, Feb 21, 2009 at 3:53 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> Andrew Lyon wrote:
>>
>> I've also tried using 3.3.1 with the backported patches as above, I
>> still get a device model failure error but this time there is no
>> mention of power management:
>>
>> [2009-02-21 12:32:33 3486] WARNING (image:472) domain xptest: device
>> model failure: pid 3766: malfunctioning (closed sentinel), killed; see
>> /var/log/xen/qemu-dm-xptest.log
>>
>
> IanJ would have more of an idea about this stuff than me.

I've now tried Xen 3.3.1 and 3.3.2 both with the backported patches
from xen-unstable for pv_ops dom0 support, and I've also tried Xen 3.4
with the fix applied for "pci device without power management", with
all 3 a existing VM which works under a non pv_ops Xen kernel fails to
start under pv_ops kernel, I've also tried different disk backends
(tap:io, file:/) the error is always the same:

[2009-02-22 14:07:25 3467] WARNING (image:470) domain xptest: device
model failure: pid 4224: malfunctioning (closed sentinel), killed; see
/var/log/xen/qemu-dm-xptest.log


cat /var/log/xen/qemu-dm-xptest.log
domid: 4
qemu: the number of cpus is 1
Using xvda for guest's hda
Strip off blktap sub-type prefix to /root/xp (drv 'aio')
Watching /local/domain/0/device-model/4/logdirty/next-active
Watching /local/domain/0/device-model/4/command
qemu_map_cache_init nr_buckets = 10000 size 3145728
shared page at pfn 1fffe
buffered io page at pfn 1fffc
Time offset set 0
Register xen platform.
Done register platform.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

Andy


>
>   J
>
>>
>>  cat /var/log/xen/qemu-dm-xptest.log
>>
>> domid: 1
>> qemu: the number of cpus is 2
>> Watching /local/domain/0/device-model/1/logdirty/next-active
>> Watching /local/domain/0/device-model/1/command
>> qemu_map_cache_init nr_buckets = 10000 size 3145728
>> shared page at pfn 1fffe
>> buffered io page at pfn 1fffc
>> Time offset set 0
>> Register xen platform.
>> Done register platform.
>> medium change watch on `hdc' (index: 1):
>> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
>> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
>>
>> Which logfiles do I need to post to investigate this problem?
>>
>> Andy
>>
>
>

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

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