It did not hit me yet - thats why I can't really help.
mem=X should be right, but there was also a thread on xen-devel that
talked about some more arcane options.
Two routes:
a) Would you please try it over there on the other list? or
b) Can you try to run a current Linux kernel on the system? I know
that is not really a production-friendly choice, but it would be the
most easy thing to do right now.
i.e. do a test install with ubuntu 11.10 and install Xen on that. The
3.x kernel will just work[tm] on Xen, and the ones > 3.0.2 should not
have any dom0 mem issues.
I know this is not ideal :>
Florian
2011年10月16日 Ian Tobin <itobin@xxxxxxxxxxxxx>:
> Hi,
>
> What do you mean by setting the linux option? Do you mean mem=x ?
>
> If so i tried that but the kernel would panic on startup so didn't help me at
> all.
>
> What settings have you got that works?
>
> I think clearly there is a major bug here but doesn't seem to be Many people
> reporting it
>
> Thanks
>
> Ian
>
>
>
> On 14 Oct 2011, at 15:40, "Florian Heigl" <florian.heigl@xxxxxxxxx> wrote:
>
>> Hi,
>>
>> 2011年10月14日 Ian Tobin <itobin@xxxxxxxxxxxxx>:
>>> same issue? Specifying the above line doesn’t seem to have much affect, in
>>> fact it makes the system more unstable as it seems that when launching domUs
>>> it takes memory from dom0 to the point where it is running at its minimum.
>>> I have tested with various servers and all have the same issue.
>>
>> did you try adding the corresponding option for the linux kernel?
>> From what I understood one needs to set both the Xen and the Linux option.
>>
>> But, yeah, so far I still need to be affected by the issue. Running
>> mostly older versions of Xen.
>> Seems it's not going to pe possible to wait it out till it is fixed :)
>>
>> Flo
>>
>> --
>> the purpose of libvirt is to provide an abstraction layer hiding all
>> xen features added since 2006 until they were finally understood and
>> copied by the kvm devs.
>>
>
--
the purpose of libvirt is to provide an abstraction layer hiding all
xen features added since 2006 until they were finally understood and
copied by the kvm devs.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users