[Xen-bugs] [Bug 591] New: xen0 kernel OOPS when starting xenU

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=591

           Summary: xen0 kernel OOPS when starting xenU
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: jan.oravec@xxxxxxx


I have tried both Xen rev. 9029 (kernel 2.6.16-rc5) and Xen rev. 9459 (kernel
2.6.16). Xen0 boots without any problems and when I try to start new xenU with
'xm create configfile' I get the following OOPS in xen0:

Unable to handle kernel paging request at ffff880010800008 RIP:
<ffffffff80119d04>{__direct_remap_pfn_range+260}
PGD 94f067 PUD 950067 PMD 0
Oops: 0002 [1] SMP
CPU 0
Pid: 5195, comm: python Not tainted 2.6.16-xen #2
RIP: e030:[<ffffffff80119d04>] <ffffffff80119d04>{__direct_remap_pfn_range+260}
RSP: e02b:ffff88000ca7fa98  EFLAGS: 00010286
RAX: 80000000becc3027 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000010800000 RSI: 00002aaaab1b3000 RDI: 0000000000000068
RBP: ffff880010800000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000001000 R12: ffff880010800000
R13: 00002aaaab1b4000 R14: ffff880000000000 R15: 00000000000becc4
FS:  00002acbe7330d80(0063) GS:ffffffff80723000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process python (pid: 5195, threadinfo ffff88000ca7e000, task ffff88000ea52380)
Stack: ffff88000ca7fad8 ffff8800015cdb00 0001000000000002 8000000000000027
       0000000000001000 ffff88000f2ab400 ffff880010800000 0000000000000000
       0000000000000001 0000000000000000
Call Trace: <ffffffff803802dc>{privcmd_ioctl+476}
<ffffffff802706c8>{xfs_bmap_search_extents+136}
       <ffffffff80271e02>{xfs_bmapi+962} <ffffffff80151bfe>{file_read_actor+206}
       <ffffffff80151b1e>{do_generic_mapping_read+1422}
<ffffffff80151b00>{do_generic_mapping_read+1392}
       <ffffffff80155960>{get_page_from_freelist+832}
<ffffffff80155a69>{__alloc_pages+89}
       <ffffffff80154fd2>{free_hot_cold_page+258}
<ffffffff801550b5>{__pagevec_free+37}
       <ffffffff80159215>{release_pages+533} 
<ffffffff802f04a0>{prio_tree_insert+48}
       <ffffffff8015c5d8>{vma_prio_tree_insert+40} 
<ffffffff8016528c>{vma_link+252}
       <ffffffff8018ac54>{do_ioctl+116} <ffffffff8018af1b>{vfs_ioctl+667}
       <ffffffff8018afad>{sys_ioctl+77} <ffffffff8010b146>{system_call+134}
       <ffffffff8010b0c0>{system_call+0}

Code: 48 89 45 08 48 83 c5 10 4c 3b 5c 24 20 0f 82 4e ff ff ff 4c
RIP <ffffffff80119d04>{__direct_remap_pfn_range+260} RSP <ffff88000ca7fa98>
CR2: ffff880010800008

The hardware is 2x dual-core Opteron, AMD 8111+8131 chipset (tried also with
nVidia nForce 4). The xenU config looks as follows:

kernel = "/boot/linux-2.6.16-xenU"
memory = 64
name = "test"
vcpus = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"

xen0 OOPS immediatelly after xm create, but it does not crash - when I restart
xend, I can even do 'xm list' showing:

Domain-0                           0      251     4 r-----    20.1
Domain-1                           1       64     1 --p---     0.0

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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