From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Latest pv_ops (2.6.30-rc3) and xen-unstable
Date: Tue, 05 May 2009 14:17:31 -0700
Message-ID: <4A00ACEB.1070904@goop.org>
References: <49FFD4C1.9070803@dataproof.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <49FFD4C1.9070803@dataproof.fi>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Valtteri Kiviniemi <valtteri.kiviniemi@dataproof.fi>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Valtteri Kiviniemi wrote:
> Hi,
>
> I am testing the latest pv_ops kernel with xen-unstable. With a quick 
> test run I got everything working except xentop (all the domUs start 
> up with no problem.)
>
> xentop gives this warning:
>
> root@sm:/# xentop
> Failed to retrieve statistics from libxenstat
>
> and dmesg:
>
> xenbus_probe wake_waiting
> xenbus_probe wake_waiting
> XENBUS: Unable to read cpu state
> XENBUS: Unable to read cpu state
> XENBUS: Unable to read cpu state
> XENBUS: Unable to read cpu state
> XENBUS: Unable to read cpu state
> XENBUS: Unable to read cpu state
> XENBUS: Unable to read cpu state
> XENBUS: Unable to read cpu state
> xenbus_probe_devices backend
> xenbus_probe_devices failed xenbus_directory
> backend_probe_and_watch devices probed ok
> backend_probe_and_watch watch add ok ok
> backend_probe_and_watch all done
> xenbus_probe_devices device
> xenbus_probe_devices failed xenbus_directory
> frontend_probe_and_watch devices probed ok
> frontend_probe_and_watch watch add ok ok
> frontend_probe_and_watch all done
>
> /proc/xen is mounted.
>
> What could be the problem? 

I'm guessing that whatever file it uses for statistics hasn't been 
implemented yet.  Could you have a look at tracking down what files it 
wants to use (strace might be a good start).

    J