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-bugs

[Xen-bugs] [Bug 252] New: system crash while creating DomU on a large me

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 252] New: system crash while creating DomU on a large memorysystem/PAEenabled
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 22 Sep 2005 20:45:16 +0000
Delivery-date: Thu, 22 Sep 2005 20:45:21 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=252

           Summary: system crash while creating DomU on a large
                    memorysystem/PAEenabled
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: raj.subrahmanian@xxxxxxxxxx


I am running Xen on an ES7000 system with 4 procs and 4 GB memory.
I am running Suse Sles-9 (32-bit) on the machine.

I have compiled Xen (the tip on the unstable tree : 7029) with PAE enabled 
(XEN_TARGET_X86_PAE=y). 
The system boots fine.

I started xend and when I tried to bring up a virtual machine, the system 
crashed.
This is what I see on the serial output.

Raj

(XEN) (file=traps.c, line=960) Non-priv domain attempted RDMSR
(c0000080,00000000,00100000).
(XEN) (file=traps.c, line=952) Non-priv domain attempted WRMSR
(c0000080,00000800,00000000).
(XEN) CPU:    3
(XEN) EIP:    e008:[<ff1415b8>] get_page+0xd8/0x11a
(XEN) EFLAGS: 00010282   CONTEXT: hypervisor
(XEN) eax: 80000001   ebx: 80000002   ecx: ffbe2080   edx: ffbe2080
(XEN) esi: f7c57c7c   edi: 00000000   ebp: ff1fddd8   esp: ff1fdd90
(XEN) cr0: 8005003b   cr3: e742e000
(XEN) ds: e010   es: e010   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ff1fdd90:
(XEN)    00000000 ff11ec69 ffbe1080 00000038 00000067 00000001 fed6b020
ff1fddfc 
(XEN)    ffbe2080 00000000 ffbe2080 ffbe2080 ffbe2080 80000001 80000002
80000001 
(XEN)    fde00000 0042e008 ff1fddf8 ff141630 f7c57c70 ffbe2080 ff1fde58
00000286 
(XEN)    0000016b ff1fddfc ff1fde38 ff13945f f7c57c70 ffbe2080 e0000000
000003a9 
(XEN)    00000004 000003aa 000003a9 ff18f56c 80000063 ffbe2088 f7c57c70
000d8fda 
(XEN)    d8fda063 80000000 ff1fde78 ff13f609 d8fda063 80000000 ffbe2080
ff144cf7 
(XEN)    ff1fde80 00000020 ff1fde78 ff14483d 00000000 00000001 d8fda063
80000000 
(XEN)    00000000 00000000 ff1fdec8 ff13f90b ffbe2080 fed6d000 ffbad000
000003a6 
(XEN)    e7494061 00000000 e7494063 00000000 00000000 00000000 ffbfa000
fde00000 
(XEN)    e7494061 00000000 fed6d000 c0000005 0042e008 fdfef000 ff1fdf48
ff14032a 
(XEN)    ffbe2080 00000000 00000008 00000004 e742c067 00000000 000e742d
00000000 
(XEN)    00000000 00000001 00000000 00000000 00000008 fde02170 ff1fdf28
00000600 
(XEN)    00000001 00000000 e742c067 00000000 00000000 fdfef000 e742c021
00000000 
(XEN)    f7dae420 000e742c fed6a000 ffbe1080 0042e008 00000000 ff1fdf78
ff148222 
(XEN)    ffbe2080 c042e00c ff1fdfb4 00000001 00000000 f7dae438 00000001
00000003 
(XEN)    ffbe2080 ffbe1080 ff1fdfa8 ff1482a7 c042e00c ff1fdfb4 00000001
00e02037 
(XEN)    ff15cd6f c0355ea4 00000001 00000001 00007ff0 c042e00c 00e02037
ff15d002 
(XEN)    ff1fdfb4 ffffffff e7492063 00000000 0042e008 00000000 c0001000
e7492063 
(XEN)    000e0003 c0115af6 0000e019 00010202 c0355ea0 0000e021 0000e021
0000e021 
(XEN)    00000000 00000000 00000003 ffbe1080 
(XEN) Xen call trace:
(XEN)    [<ff1415b8>] get_page+0xd8/0x11a
(XEN)    [<ff141630>] get_page_and_type+0x18/0x4e
(XEN)    [<ff13945f>] get_page_from_l1e+0x273/0x298
(XEN)    [<ff13f609>] revalidate_l1+0x109/0x1a4
(XEN)    [<ff13f90b>] ptwr_flush+0x267/0x32f
(XEN)    [<ff14032a>] ptwr_do_page_fault+0x2fc/0x57c
(XEN)    [<ff148222>] fixup_page_fault+0x1ef/0x256
(XEN)    [<ff1482a7>] do_page_fault+0x1e/0x104
(XEN)    [<ff15d002>] error_code+0x62/0x7d
(XEN)    
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 3:
(XEN) CPU3 FATAL TRAP: vector = 17 (alignment check)
(XEN) [error_code=0000]
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

-- 
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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 252] New: system crash while creating DomU on a large memorysystem/PAEenabled, bugzilla-daemon <=