From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
kay.sievers@vrfy.org, linux-kernel@vger.kernel.org
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: linux 3.3-pre-rc1: Starting domU fails with Error: Failed to query current memory allocation of dom0.
Date: Thu, 12 Jan 2012 10:46:13 -0500 [thread overview]
Message-ID: <20120112154613.GA10148@phenom.dumpdata.com> (raw)
In-Reply-To: <498097597.20120112133832@eikelenboom.it>
On Thu, Jan 12, 2012 at 01:38:32PM +0100, Sander Eikelenboom wrote:
> Hi Konrad,
>
> Today i tried linuses tree of today (last commit is 4c4d285ad5665bfbd983b95fde8d7a477d24a361).
>
> It boots dom0 fine, but it fails to start any domU with: "Error: Failed to query current memory allocation of dom0."
> With my previous 3.1.5 kernel everything is fine, nothing else changed in config in between.
Hey Kay,
Your patch that converts the xen-balloon to use the regular device bus driver
(070680218379e15c1901f4bf21b98e3cbf12b527) has some not-so-happy consequences.
The toolstack (xen-tools) use:
/sys/devices/system/xen_memory/xen_memory0
But with the change, it is now:
/sys/devices/xen_memory0/target_kb
Which means that the tools can't find it now.
I did not see anything in feature-removal-schedule.txt so I don't know
exactly when the full sys_device structure is going away.
Is there any work-arounds that can be inserted in the kernel so that
the old directory still exists at least for 3.3 such that there will be
enough time for the tool-stack to be updated?
next prev parent reply other threads:[~2012-01-12 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 12:38 linux 3.3-pre-rc1: Starting domU fails with Error: Failed to query current memory allocation of dom0 Sander Eikelenboom
2012-01-12 15:07 ` Konrad Rzeszutek Wilk
2012-01-12 15:46 ` Konrad Rzeszutek Wilk [this message]
2012-01-12 16:05 ` Kay Sievers
2012-01-12 16:12 ` Konrad Rzeszutek Wilk
2012-01-12 16:40 ` Konrad Rzeszutek Wilk
2012-01-12 16:58 ` Kay Sievers
2012-01-12 17:05 ` Sander Eikelenboom
2012-01-12 17:10 ` Konrad Rzeszutek Wilk
2012-01-12 17:48 ` Kay Sievers
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=20120112154613.GA10148@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--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.