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: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Subject: Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Sat, 21 Feb 2009 12:40:15 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, bderzhavets@xxxxxxxxx, "Marc - A. Dahlhaus \[ Administration | Westermann GmbH \]" <mad@xxxxxx>
Delivery-date: Sat, 21 Feb 2009 04:41:08 -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=uZ+FhloZD+dne/HA7f9MG8uW/BhnHvBebrDcMD5luLs=; b=uCCPrR/ovPLqX430G72sY6Tla1joOY6LGR0GXFGPSHg3Tb0cb0ks0x6+jVgaMNGlNC 1MJyAs6UhgddUhqW445/VyfHqb2ZGZmcolZJ/mMFmbDuRUTfIIrpbmgpdYOD4NZYDyhl ZKVTsls+NHtIlDi4UWALFNZSjI3h3SDoA088g=
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=eNn3q+LHtIr+lxYm143DbIZg35vYf0zdqR9cG7jEysVnwSsd+PSjYKtA+HhVko02Jc vBmg03uWm7xqqFt+0MXvAEMzgcjB8Zj1cej48N4yAy2kZ778w8PyHaIsE8ip5nRCor+e BHWuwil2wt1rHQDT8i67Dc5dL9CNS0Xc0BAfw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <499E799B.2080008@xxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Feb 20, 2009 at 9:36 AM, Gerd Hoffmann <kraxel@xxxxxxxxxx> wrote:
> Andrew Lyon wrote:
>> Awesome, the kernel  booted and ahci is working normally, and piix
>> isnt actually used on this system as all the devices are sata.
>>
>> xend failed to start saying it was not a privileged domain, first
>> thing I am going to try there is upgrading to Xen 3.3.1 final as I am
>> still running rc4 on my test box, but what is the minimum Xen version
>> to use pv_ops dom0?
>
> Try adding this line to /etc/fstab:
>
> xen /proc/xen xenfs defaults 0 0
>
> vanilla 3.3.1 isn't going to work, you need a few patches backported
> from unstable.  Current rawhide package has these changesets:
>
> xen-backport-hg18782.patch
> xen-backport-hg19075.patch
> xen-backport-hg19108.patch
> xen-backport-hg19109.patch
> xen-backport-hg19110.patch
>
> cheers,
>  Gerd
>
>

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


 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>