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] Unable to handle kernel paging request at virtual addres

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Jacob Gorm Hansen <jacobg@xxxxxxx>
Subject: Re: [Xen-devel] Unable to handle kernel paging request at virtual address e9042464
From: Andrew Theurer <habanero@xxxxxxxxxx>
Date: Mon, 25 Apr 2005 17:06:23 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 25 Apr 2005 22:06:36 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <cc604fa95dfc6414e10dcfbf1501a2f2@xxxxxxxxxxxx>
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>
References: <E1DPywO-0000oT-00@xxxxxxxxxxxxxxxxx> <426D4D07.9090606@xxxxxxx> <cc604fa95dfc6414e10dcfbf1501a2f2@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
On Monday 25 April 2005 16:54, Keir Fraser wrote:
> On 25 Apr 2005, at 21:03, Jacob Gorm Hansen wrote:
> > Do you know how the interface has changed, i.e. what I need to
> > modify in vmtools (xend is not an option since I am running with my
> > own userspace relinked above 0xf0000000 in dom0) to get this
> > working again?
>
> I don't think this was the problem actually, but anyway: createdomain
> no longer takes memsize nor initial mem size. To pin to a cpu you now
> use DOM0_PINCPU. To set max mem reservation you use DOM0_SETMAXMEM.
> To actually reserve memory you use
> do_dom_mem_op(MEMOP_increase_reservation).

FWIW, I think I am hitting an BUG on that very changeset (1.1367) by 
trying to start a smp domU.  I have narrowed it down the 1.1367, and I 
am going to remove that diff from very latest bk pull an see what 
happens.

-Andrew


BUG output:

Starting domain dom1
------------[ cut here ]------------

kernel BUG at <bad filename>:46733!
invalid operand: 0000 [#1]
PREEMPT
Modules linked in: ipt_MASQUERADE iptable_nat ip_conntrack ip_tables 
qla2300 qla2xxx scsi_transport_fc mptscsih mptbase
CPU:    0
EIP:    0061:[<c014c6e8>]    Not tainted VLI
EFLAGS: 00010286   (2.6.11-xen0-up)
EIP is at page_remove_rmap+0x3d/0x47
eax: ffffffff   ebx: 00000000   ecx: c04f771c   edx: c16fdfe0
esi: f48d5494   edi: 0feff067   ebp: 00001000   esp: f459de48
ds: 007b   es: 007b   ss: 0069
Process python (pid: 4300, threadinfo=f459c000 task=f76c3a80)
Stack: c1641640 f459c000 c0145244 c16fdfe0 0a3d5067 c01471fe 00000010 
c16fdfe0
       00000000 b7525000 c04f771c b7925000 f455fb78 b7526000 00000000 
c0145408
       c04f771c f455fb74 b7525000 00001000 00000000 b7525000 f455fb78 
b7526000
Call Trace:
 [<c0145244>] zap_pte_range+0x186/0x2f3
 [<c01471fe>] do_anonymous_page+0x169/0x210
 [<c0145408>] zap_pmd_range+0x57/0x75
 [<c0145460>] zap_pud_range+0x3a/0x5e
 [<c01454f8>] unmap_page_range+0x74/0x8b
 [<c014560c>] unmap_vmas+0xfd/0x223
 [<c0149ff4>] unmap_region+0x7b/0xe9
 [<c014a2c8>] do_munmap+0x122/0x191
 [<c014a37e>] sys_munmap+0x47/0x62
 [<c010965c>] syscall_call+0x7/0xb
Code: 0f 98 c0 84 c0 74 1c 8b 42 08 83 c0 01 78 1c c7 44 24 04 ff ff ff 
ff c7 04 24 10 00 00 00 e8 a3 ef fe ff 83 c4 08 c3 0f 0b eb d1 <0f> 0b 
8d b6 00 00 00 00 eb da 55 57 56 53 83 ec 1c 8b 4c 24 34
 <6>note: python[4300] exited with preempt_count 1
scheduling while atomic: python/0x00000001/4300
 [<c03ae564>] schedule+0x534/0x5d8
 [<c010980b>] hypervisor_callback+0x37/0x40
 [<c03af64d>] rwsem_down_read_failed+0x8d/0x18b
 [<c011da4b>] .text.lock.exit+0x27/0x8c
 [<c010a33f>] do_invalid_op+0x0/0xab
 [<c011c212>] do_exit+0x9d/0x36b
 [<c010a33f>] do_invalid_op+0x0/0xab
 [<c010a02d>] do_trap+0x0/0xd5
 [<c010a3e1>] do_invalid_op+0xa2/0xab
 [<c014c6e8>] page_remove_rmap+0x3d/0x47
 [<c013aa7e>] rmqueue_bulk+0x4a/0xd5
 [<c013a94a>] prep_new_page+0x72/0x77
 [<c013adfe>] buffered_rmqueue+0x153/0x2ba
 [<c01097cc>] error_code+0x38/0x40
 [<c014c6e8>] page_remove_rmap+0x3d/0x47
 [<c0145244>] zap_pte_range+0x186/0x2f3
 [<c01471fe>] do_anonymous_page+0x169/0x210
 [<c0145408>] zap_pmd_range+0x57/0x75
 [<c0145460>] zap_pud_range+0x3a/0x5e
 [<c01454f8>] unmap_page_range+0x74/0x8b
 [<c014560c>] unmap_vmas+0xfd/0x223
 [<c0149ff4>] unmap_region+0x7b/0xe9
 [<c014a2c8>] do_munmap+0x122/0x191
 [<c014a37e>] sys_munmap+0x47/0x62
 [<c010965c>] syscall_call+0x7/0xb


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

<Prev in Thread] Current Thread [Next in Thread>