Re: [Xen-users] xen 4.3.3 -> 4.4.1 after dom0 upgrade : domU refuses to boot

[Pierre Peyronnel <pierre.peyronnel@xxxxxxxxx>]

Ok I'm off-topic here but :

yep 256M according to /boot/extlinux.conf

APPEND xen.gz dom0_mem=256M

and top shows 128M

Mem: 124688K used, 4920K free, 260K shrd, 4788K buff, 27028K cached

so my /var/run can't be bigÂ

On Tue, Apr 21, 2015 at 3:10 PM, Pierre Peyronnel <pierre.peyronnel@xxxxxxxxx> wrote:

On Tue, Apr 21, 2015 at 2:50 PM, Ian Campbell <ian.campbell@xxxxxxxxxx> wrote:

It's the sort of thing some distros have been transitioning recently, so
it may well have changed in the upgrade.

I can ask.

Â

> any chance this can be configured somewhere in pygrub ? or in the xl
> config file ?

AFAIK it is a compile time option only, so you'd need to rebuild.Â

Â

yeah, i avoid these things if i can, it's very time hungry :-) And i've never built Xen.

Of course my problem is gonna be that /run is destroyed at every reboot so i'll have to do everything manually...Â

Somehow i knew i should have stayed with my old Alpine and Xen.Â

13MB is pretty meagre for /var/run though, on Debian mine is a 700MB
ramdisk for example...

Isn't /var/run is for PIDs and named pipes mostly, so I'm not sure it needs to be big either.

As for Alpine, it is a pretty sleek running distro... It is only dom0 for me and runs on something like 256MB or maybe 512MB of RAM, the rest being available to domUs.

But is it really useful to have the kernel available for boot in a ramdisk ? After boot it will be in the domU RAM anyway, no ?

Pierre

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users