WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] "xm mem-max" problem on PAE xenlinux

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] "xm mem-max" problem on PAE xenlinux
From: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date: Fri, 11 Nov 2005 12:44:04 -0800
Delivery-date: Fri, 11 Nov 2005 20:44:13 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXm8NNTz8G2IIU2Qem1hq4pNJFw6wADlLYA
Thread-topic: [Xen-devel] "xm mem-max" problem on PAE xenlinux
BTW, 

# xm mem-set 5000

worked fine. Looks like it's already in 
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=212

So we need to remove it from xm?

BTW Xen on FC4 page
(http://www.fedoraproject.org/wiki/FedoraXenQuickstart) suggests the
user do the following (as an exmaple)
xm mem-max 0 384
xm mem-set 0 384


Nakajima, Jun wrote:
> I tried this on PAE Xen on a machine with 8GB.
> 
> # xm list
> Name                              ID Mem(MiB) VCPUs State  Time(s)
> Domain-0                           0     7964     1 r-----   137.9
> 
> Then, simply
> # xm mem-max 0 5000
> # xm list
> 
> Causes:
> 
> kernel BUG at arch/xen/i386/mm/hypervisor.c:381 (xen_create_con
> tiguous_region)!
>  [<c0119faa>] xen_create_contiguous_region+0x34a/0x4e0
>  [<c0116ec2>] pgd_ctor+0x22/0x130
>  [<c014b0a7>] cache_init_objs+0x67/0x70
>  [<c014b282>] cache_grow+0x122/0x210
>  [<c014b4e3>] cache_alloc_refill+0x173/0x250
>  [<c014b805>] kmem_cache_alloc+0x95/0xa0
>  [<c01170e3>] pgd_alloc+0x23/0x320
>  [<c0111301>] sync_single+0x51/0xa0
>  [<c011db23>] mm_init+0xa3/0xe0
>  [<c011de6e>] copy_mm+0xbe/0x3d0
>  [<c010484c>] force_evtchn_callback+0xc/0x10
>  [<c011ea97>] copy_process+0x3f7/0xd40
>  [<c011f4d9>] do_fork+0x69/0x184
>  [<c0223142>] copy_to_user+0x42/0x90
>  [<c0107b9c>] sys_clone+0x3c/0x40
>  [<c0109355>] syscall_call+0x7/0xb
> Kernel panic - not syncing: BUG!
>  (XEN) Domain 0 shutdown: rebooting machine.
> 
> I used:
> changeset:   7745:b9e8654c3f10
> tag:         tip
> user:        kaf24@xxxxxxxxxxxxxxxxxxxx
> date:        Thu Nov 10 19:43:56 2005 +0100
> summary:     Fix Linux fault.c indentation.
> 
> I tried samething on x86_64 xenlinux, but it worked fine.
> 
> Jun
> ---
> Intel Open Source Technology Center
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



Jun
---
Intel Open Source Technology Center

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel