linux-kernel - Re: linux 3.3-pre-rc1: Starting domU fails with Error: Failed to query current memory allocation of dom0.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Jan 2012 10:46:13 -0500
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Sander Eikelenboom <linux@...elenboom.it>, kay.sievers@...y.org,
	linux-kernel@...r.kernel.org
Cc:	xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: linux 3.3-pre-rc1: Starting domU fails with Error: Failed to
 query current memory allocation of dom0.

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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/