Re: [Xen-devel] Crashing / unable to start domUs due to high number of luns?

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

> >>I've still got 1 dom0 that's exhibiting the problem, if anyone is able
> >>to suggest any further debugging steps?
> >>
> >>- Nathan
> >>
> >>
> >>(XEN) Xen version 4.1.1 (root@) (gcc version 4.3.4 (Gentoo 4.3.4 p1.1,
> >>pie-10.1.5) ) Mon Aug 29 16:24:12 PDT 2011
> >>
> >>ukxen1 xen # xm info
> >>host                   : ukxen1
> >>release                : 3.0.3
> >>version                : #4 SMP Thu Dec 22 12:44:22 PST 2011
> >>machine                : x86_64
> >>nr_cpus                : 24
> >>nr_nodes               : 2
> >>cores_per_socket       : 6
> >>threads_per_core       : 2
> >>cpu_mhz                : 2261
> >>hw_caps                :
> >>bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000
> >>virt_caps              : hvm hvm_directio
> >>total_memory           : 98291
> >>free_memory            : 91908
> >>free_cpus              : 0
> >>xen_major              : 4
> >>xen_minor              : 1
> >>xen_extra              : .1
> >>xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> >>hvm-3.0-x86_32p hvm-3.0-x86_64
> >>xen_scheduler          : credit
> >>xen_pagesize           : 4096
> >>platform_params        : virt_start=0xffff800000000000
> >>xen_changeset          : unavailable
> >>xen_commandline        : console=vga dom0_mem=1024M dom0_max_vcpus=1

It could be that you are running out of memory. So the pvops kernel
(or at least the one you are running) has a bug in that it will
allocate pages up to 98GB. The solution for that is to use
dom0_mem=max:1024M , not dom0_mem=1024M.

Please try that.

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