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

[Kay Sievers]

On Thu, Jan 12, 2012 at 16:46, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Thu, Jan 12, 2012 at 01:38:32PM +0100, Sander Eikelenboom wrote:

>> 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.
> 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

Urks, seems like a mistake on my side.

Please try if changing:
  bus_unregister(&balloon_subsys);
to:
  subsys_system_register(&balloon_subsys, NULL);
in:
  drivers/xen/xen-balloon.c
fixes the issue.

Sorry for that,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/