I am using Xen 3.3.1 (release version). I cannot start my PV domU with pv-grub
when I allocate more than 1023MB RAM to the guest.
I have seen another thread on xen-devel that looks exactly like my case:
http://www.nabble.com/pv_grub-and->1023M-RAM-%3D%3D-death-td20819433.html. I
have checked on my pv-grub code under extras/mini-os/... and it seems as if the
patch is applied already. However, I still cannot boot up my guest with over
1023MB RAM. I have listed the logs below. I have 2GB RAM on the system, dom0
owns 512MB only.
Many thanks,
Anna
[root@localhost user]# xm create -c pv.cfg
Using config file "./pv.cfg".
Started domain sos-pv
Xen Minimal OS!
start_info: 0xa64000
nr_pages: 262144 shared_inf: 001c8000
pt_base: 0xa67000 mod_start: 0x0
mod_len: 0
flags: 0x0
cmd_line: (hd0)/boot/grub/menu-pv.lst
stack: 0x943780-0x963780
MM: Init
_text: 0x0
_etext: 0x5f8b5
_erodata: 0x73000
_edata: 0x786d4
stack start: 0x943780
_end: 0x963d14
start_pfn: a73
max_pfn: 40000
Mapping memory range 0xc00000 - 0x40000000
setting 0x0-0x73000 readonly
skipped 0x1000
MM: Initialise page allocator for c6d000(c6d000)-0(40000000)
MM: done
Demand map pfns at 40001000-c0001000.
Heap resides at c0002000-2000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x40001000.
Initialising scheduler
Heap exhausted: 0xc0002000 + 480 = 0xc0002480 > 0x2000
Heap exhausted: 0xc0002000 + b80 = 0xc0002b80 > 0x2000
Page fault at linear address 0x4, eip 0x51e90, regs 0x95feb8, sp 0x77da0, our_sp
0x95fe98, code 2
Page fault in pagetable walk (access to invalid memory?).
xm dmesg shows
(XEN) mm.c:676:d0 Non-privileged (3) attempt to map I/O space 00000000
(XEN) mm.c:676:d0 Non-privileged (3) attempt to map I/O space 00000000
(XEN) printk: 56822 messages suppressed.
(XEN) mm.c:676:d0 Non-privileged (3) attempt to map I/O space 00000000
(XEN) printk: 67717 messages suppressed.
(XEN) mm.c:676:d0 Non-privileged (3) attempt to map I/O space 00000000
xm info shows
host : localhost.localdomain
release : 2.6.18.8-xen
version : #5 SMP Thu Mar 5 04:14:30 PST 2009
machine : i686
nr_cpus : 2
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2200
virt_caps : hvm
total_memory : 2039
free_memory : 1501
node_to_cpu : node0:0-1
node_to_memory : node0:1501
xen_major : 3
xen_minor : 3
xen_extra : .1
xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xf5800000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
cc_compile_by : root
cc_compile_domain : localdomain
cc_compile_date : Thu Mar 5 07:47:18 PST 2009
xend_config_format : 4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Hello, Fischer, Anna, le Sat 07 Mar 2009 00:52:17 +0000, a écrit :> I am using Xen 3.3.1 (release version). I cannot start my PV domU with pv-grub when I allocate more than 1023MB RAM to the guest. > > I have seen another thread on xen-devel that looks exactly like my case: http://www.nabble.com/pv_grub-and->1023M-RAM-%3D%3D-death-td20819433.html. I have checked on my pv-grub code under extras/mini-os/... and it seems as if the patch is applied already. However, I still cannot boot up my guest with over 1023MB RAM. I have listed the logs below. I have 2GB RAM on the system, dom0 owns 512MB only.Could you send us the log? Samuel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Subject: Re: [Xen-devel] pv-grub heap exhausted? > > Hello, > > Fischer, Anna, le Sat 07 Mar 2009 00:52:17 +0000, a écrit : > > I am using Xen 3.3.1 (release version). I cannot start my PV domU > with pv-grub when I allocate more than 1023MB RAM to the guest. > > > > I have seen another thread on xen-devel that looks exactly like my > case: http://www.nabble.com/pv_grub-and->1023M-RAM-%3D%3D-death- > td20819433.html. I have checked on my pv-grub code under extras/mini- > os/... and it seems as if the patch is applied already. However, I > still cannot boot up my guest with over 1023MB RAM. I have listed the > logs below. I have 2GB RAM on the system, dom0 owns 512MB only. > > Could you send us the log?Attached domain-builder log and xm log. What else do you need? Thanks, Anna _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> From: Samuel Thibault [mailto:samuel.thibault@ens-lyon.org] > Could you send us the log?Oops sorry, it was in. Could you try the patch below? Samuel minios: Fix 18874 memory clipping Fix 18874''s memory clipping: there are three page-sized holes between direct mapping, demand mapping, heap pages and the end of memory. Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org> diff -r f8187a343ad2 extras/mini-os/arch/x86/mm.c --- a/extras/mini-os/arch/x86/mm.c Fri Feb 20 17:02:36 2009 +0000 +++ b/extras/mini-os/arch/x86/mm.c Sat Mar 07 02:33:30 2009 +0100 @@ -599,7 +599,7 @@ void arch_init_mm(unsigned long* start_pfn_p, unsigned long* max_pfn_p) { - unsigned long start_pfn, max_pfn, virt_pfns; + unsigned long start_pfn, max_pfn; printk(" _text: %p\n", &_text); printk(" _etext: %p\n", &_etext); @@ -614,9 +614,13 @@ max_pfn = start_info.nr_pages; /* We need room for demand mapping and heap, clip available memory */ - virt_pfns = DEMAND_MAP_PAGES + HEAP_PAGES; - if (max_pfn + virt_pfns + 1 < max_pfn) - max_pfn = -(virt_pfns + 1); +#if defined(__i386__) + { + unsigned long virt_pfns = 1 + DEMAND_MAP_PAGES + 1 + HEAP_PAGES; + if (max_pfn + virt_pfns >= 0x100000) + max_pfn = 0x100000 - virt_pfns - 1; + } +#endif printk(" start_pfn: %lx\n", start_pfn); printk(" max_pfn: %lx\n", max_pfn); _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Subject: Re: [Xen-devel] pv-grub heap exhausted? > > > From: Samuel Thibault [mailto:samuel.thibault@ens-lyon.org] > > Could you send us the log? > > Oops sorry, it was in. Could you try the patch below? > > Samuel > > > minios: Fix 18874 memory clipping > > Fix 18874''s memory clipping: there are three page-sized holes between > direct mapping, demand mapping, heap pages and the end of memory. > > Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org> > > diff -r f8187a343ad2 extras/mini-os/arch/x86/mm.c > --- a/extras/mini-os/arch/x86/mm.c Fri Feb 20 17:02:36 2009 +0000 > +++ b/extras/mini-os/arch/x86/mm.c Sat Mar 07 02:33:30 2009 +0100 > @@ -599,7 +599,7 @@ > void arch_init_mm(unsigned long* start_pfn_p, unsigned long* > max_pfn_p) > { > > - unsigned long start_pfn, max_pfn, virt_pfns; > + unsigned long start_pfn, max_pfn; > > printk(" _text: %p\n", &_text); > printk(" _etext: %p\n", &_etext); > @@ -614,9 +614,13 @@ > max_pfn = start_info.nr_pages; > > /* We need room for demand mapping and heap, clip available memory > */ > - virt_pfns = DEMAND_MAP_PAGES + HEAP_PAGES; > - if (max_pfn + virt_pfns + 1 < max_pfn) > - max_pfn = -(virt_pfns + 1); > +#if defined(__i386__) > + { > + unsigned long virt_pfns = 1 + DEMAND_MAP_PAGES + 1 + > HEAP_PAGES; > + if (max_pfn + virt_pfns >= 0x100000) > + max_pfn = 0x100000 - virt_pfns - 1; > + } > +#endif > > printk(" start_pfn: %lx\n", start_pfn); > printk(" max_pfn: %lx\n", max_pfn);Yes, works now. Many thanks. Anna _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 07/03/2009 01:34, "Samuel Thibault" <samuel.thibault@ens-lyon.org> wrote:> minios: Fix 18874 memory clipping > > Fix 18874''s memory clipping: there are three page-sized holes between > direct mapping, demand mapping, heap pages and the end of memory. > > Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>This is for xen-unstable and xen-3.3? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser, le Sat 07 Mar 2009 06:23:48 +0000, a écrit :> On 07/03/2009 01:34, "Samuel Thibault" <samuel.thibault@ens-lyon.org> wrote: > > > minios: Fix 18874 memory clipping > > > > Fix 18874''s memory clipping: there are three page-sized holes between > > direct mapping, demand mapping, heap pages and the end of memory. > > > > Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org> > > This is for xen-unstable and xen-3.3?Yes. Samuel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel