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 853] New: Destroy VMX domain causes Xen0 reboot in IA32E

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 853] New: Destroy VMX domain causes Xen0 reboot in IA32E Xen.
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sun, 7 Jan 2007 21:09:36 -0800
Delivery-date: Sun, 07 Jan 2007 21:10:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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=853

           Summary: Destroy VMX domain causes Xen0 reboot in IA32E Xen.
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ping.y.yu@xxxxxxxxx


Environment:
------------
Service OS (ia32/ia32e/IA64): x86_64
Guest OS (ia32/ia32e/IA64): x86_64
Change Set: CS 13282

Bug detailed description:
--------------------------
Destroy VMX domain causes Xen0 reboot.


Reproduce steps:
----------------
1. prepare a Linux/Windows image
2. prepare a coniguration file with pae=1, vcpus=2
3. xm cr "configuration file"
4. xm destroy <domid>

Current result:
----------------


Expected result:
----------------


Basic root-causing log:
----------------------
ip_tables: (C) 2000-2006 Netfilter Core Team
(XEN) BUG at common.c:823
(XEN) ----[ Xen-3.0-unstable  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    e008:[<ffff830000121268>] __bug+0x28/0x50
(XEN) RFLAGS: 0000000000010296   CONTEXT: hypervisor
(XEN) rax: 0000000000000000   rbx: ffff830000182131   rcx: 000000000000000a
(XEN) rdx: 0000000000001af3   rsi: 000000000000000a   rdi: ffff8300001e3334
(XEN) rbp: 0000000000000000   rsp: ffff830000ff3ca0   r8:  0000000000000000
(XEN) r9:  0000000000000002   r10: 00000000ffffffff   r11: ffff8300001213e0
(XEN) r12: 0000000000000337   r13: ffff8300001c4080   r14: 0000000000000020
(XEN) r15: ffff830000fca080   cr0: 0000000080050033   cr4: 00000000000026b0
(XEN) cr3: 00000000ace1a000   cr2: 00002aaaaaaf9120
(XEN) ds: 0000   es: 0000   fs: 0063   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff830000ff3ca0:
(XEN)    0000000000000296 0000000000000000 0000000000000004 0000000000000002
(XEN)    ffff83000015aa14 0000000000000000 ffff8300001c4080 0000000000000000
(XEN)    ffff830000ff3f28 ffff8300001c4f10 0000000000000000 ffff8300001e2000
(XEN)    ffff83000015ab22 0000000000000282 0000000000000000 ffff8300001c4080
(XEN)    ffff8300001c4080 ffffffffffffffea 0000000000000008 0000000000000000
(XEN)    ffff83000015c0f8 ffff830000fcb6a8 000000000008c101 0000000000000000
(XEN)    ffff830000127f08 ffff830000ff3e58 ffff8300001c4080 ffff830000ff3e58
(XEN)    0000000043001ff0 ffffffffffffffea ffff830000108358 ffff8300001c4080
(XEN)    ffff830000107474 0000000000000002 0000000000000004 0000000000000004
(XEN)    0000000000000292 ffff830000fe4080 ffff830000270080 0000000000000000
(XEN)    ffff83000010a040 ffff830000270080 0000000000000000 ffff88001ab1db44
(XEN)    ffff83000010a447 ffff830000127219 0000000080000004 0000000000270080
(XEN)    ffff830000270080 0000000080000004 0000000000270080 ffff830000270080
(XEN)    0000000000000246 ffff8300001a82a0 ffff8300001a7380 0000000400000002
(XEN)    0000000000000001 0000000000000000 00002ae861bf355c 00000000007362a0
(XEN)    00002aaaaab52200 00002ae8611e4d50 00002ae861bf3594 00002aaaaab52200
(XEN)    00000036190546ee 00000036191f3060 0000000000000069 00002ae8611e4d50
(XEN)    00000036190387e2 0000000000794168 0000000000000069 0000000000000069
(XEN)    00000036190636f4 0000000000000206 ffff830000fe2080 00000000ffffffe7
(XEN)    00000000ffffffda 0000000000305000 0000000000000008 0000000000000000
(XEN) Xen call trace:
(XEN)    [<ffff830000121268>] __bug+0x28/0x50
(XEN)    [<ffff83000015aa14>] shadow_prealloc+0x234/0x250
(XEN)    [<ffff83000015ab22>] sh_set_allocation+0xf2/0x1a0
(XEN)    [<ffff83000015c0f8>] shadow_teardown+0x108/0x160
(XEN)    [<ffff830000127f08>] domain_relinquish_resources+0x2b8/0x300
(XEN)    [<ffff830000108358>] domain_kill+0x28/0x60
(XEN)    [<ffff830000107474>] do_domctl+0x694/0xd40
(XEN)    [<ffff83000010a040>] evtchn_set_pending+0xf0/0x170
(XEN)    [<ffff83000010a447>] evtchn_send+0x117/0x140
(XEN)    [<ffff830000127219>] context_switch+0xa89/0xaa0
(XEN)    [<ffff83000016bbc2>] syscall_enter+0x62/0x67
(XEN)    
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 1:
(XEN) BUG at common.c:823
(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>