[Xen-devel] problem with shared page on xen3.1

[abinash barik <abinash.nitr@xxxxxxxxx>]

Hi,

I am working with xensocket in the following settings

1) xen3.1 dom0 (rhel5)
    uname -a
    Linux polynesia1 2.6.18-194.3.1.el5xen #1 SMP Sun May 2 04:26:43 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

2) centos domU
    uname -a
    Linux polymoa1 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

A few words about xensocket: 
XenSocket module for a shared-memory sockets transport for
communications between two domains on the same machine, under the Xen
hypervisor.
Receiver grants pages which sender maps.


I am getting following errors when I am trying to establish communication between two identical domUs, i.e one as sender and the other as receiver
other scenario in which it fails is, when dom0 is the receiver and a domU (centos) is the sender.

The only scenario it works fine is
 "when domU(centos) is receiver and dom0 is the sender"

domid = 7
gref = 852
Unable to handle kernel paging request at ffffc2000003a000 RIP: 
 [<ffffffff8837b027>] :xensocket:xen_connect+0x1f8/0x5c2
PGD 27ea067 PUD 27eb067 PMD 27ec067 PTE 0
Oops: 0000 [1] SMP 
last sysfs file: /class/misc/autofs/dev
CPU 0 
Modules linked in: xensocket(U) autofs4 hidp rfcomm l2cap bluetooth lockd sunrpc ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables ipv6 xfrm_nalgo crypto_api loop dm_mirror dm_multipath scsi_dh scsi_mod parport_pc lp parport xennet pcspkr dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache xenblk ext3 jbd uhci_hcd ohci_hcd ehci_hcd
Pid: 1645, comm: sender Tainted: G      2.6.18-194.el5xen #1
RIP: e030:[<ffffffff8837b027>]  [<ffffffff8837b027>] :xensocket:xen_connect+0x1f8/0x5c2
RSP: e02b:ffff880031ec5e08  EFLAGS: 00010246
RAX: ffffc2000003a000 RBX: 00000000ffffffff RCX: 0000000000002000
RDX: 0000000000000001 RSI: ffff880031ec5e28 RDI: 0000000000000000
RBP: ffff880030353d00 R08: ffff880031ec5e28 R09: 0000000000000000
R10: ffff880031ec5dc8 R11: 0000000000000048 R12: ffff880031ec5e28
R13: 00007fffed3108c0 R14: 0000000000000000 R15: 0000000000000000
FS:  00002b797e855210(0000) GS:ffffffff805d2000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process sender (pid: 1645, threadinfo ffff880031ec4000, task ffff88003f4df860)
Stack:  0000000000000000  ffffffff802c3987  ffff88003283f080  0000000000000008 
 0000000000000007  0000035400000000  0000000000000007  0000000000000000 
 0000055100000551  00000040000000d0 
Call Trace:
 [<ffffffff802c3987>] mod_zone_page_state+0x27/0x3d
 [<ffffffff802d08f1>] kmem_cache_zalloc+0x62/0x80
 [<ffffffff80416f2d>] sys_connect+0x7e/0xae
 [<ffffffff80416aa3>] sock_attach_fd+0x8f/0xfd
 [<ffffffff802afe53>] audit_syscall_entry+0x180/0x1b3
 [<ffffffff802602f9>] tracesys+0xab/0xb6


Code: 8b 00 89 44 24 24 e8 ce b3 e8 f7 83 f8 da 89 c3 75 34 48 8d 
RIP  [<ffffffff8837b027>] :xensocket:xen_connect+0x1f8/0x5c2
 RSP <ffff880031ec5e08>
CR2: ffffc2000003a000
 <0>Kernel panic - not syncing: Fatal exception


Thanks for any help
Abinash

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