From: Valtteri Kiviniemi <valtteri.kiviniemi@dataproof.fi>
To: xen-devel@lists.xensource.com
Subject: Latest pv_ops (2.6.30-rc3) and xen-unstable
Date: Tue, 05 May 2009 08:55:13 +0300 [thread overview]
Message-ID: <49FFD4C1.9070803@dataproof.fi> (raw)
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?
- Valtteri Kiviniemi
next reply other threads:[~2009-05-05 5:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 5:55 Valtteri Kiviniemi [this message]
2009-05-05 21:17 ` Latest pv_ops (2.6.30-rc3) and xen-unstable Jeremy Fitzhardinge
2009-05-06 16:50 ` Backport ZFS support and pygrub from Xen 3.4-rc4-pre to xen-3.3.1-11.fc11.src.rpm Boris Derzhavets
2009-05-06 19:39 ` Boris Derzhavets
2009-05-07 9:49 ` Boris Derzhavets
2009-05-07 17:21 ` Boris Derzhavets
2009-05-07 18:47 ` Latest pv_ops (2.6.30-rc3) and xen-unstable Valtteri Kiviniemi
2009-05-08 9:03 ` Ian Campbell
2009-05-08 18:48 ` Valtteri Kiviniemi
2009-05-25 9:24 ` [xenstat] Use backend path which is compatible with pvops -- status request Daniel Schroeder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49FFD4C1.9070803@dataproof.fi \
--to=valtteri.kiviniemi@dataproof.fi \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.