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/
Home Products Support Community News


[Xen-bugs] [Bug 1264] New: Destorying DomU guest will cause dom0 crash o

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1264] New: Destorying DomU guest will cause dom0 crash on 32PAE host
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 27 May 2008 04:52:36 -0700
Delivery-date: Tue, 27 May 2008 04:52:51 -0700
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

           Summary: Destorying DomU guest will cause dom0 crash on 32PAE
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P1
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx

Service OS (ia32/ia32e/IA64): ia32pae
Guest OS (ia32/ia32e/IA64): ia32pae
Change Set: 17731
Hardware: Clovertown

Bug detailed description:
on 32pae host, when we create one DomU guest, we can not see the boot steps,
using "xm list" we can find guest is running, but can not connect it with "xm
when we destory guest using "xm destory", it would cause dom0 crash. 

[root@vt-dp1 root]# xm cr -c x1
Using config file "./x1".
Started domain x1

[root@vt-dp1 ~]# xm li
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  1024     8     r-----     20.9
x1                                           1   256     1     r-----     14.7
[root@vt-dp1 ~]# xm des 1

Reproduce steps:
1) prepare one DomU image
2) creat DomU guest
3) xm destory guest_dom_ID

Current result:

Expected result:

Basic root-causing log:
BUG: soft lockup detected on CPU#2!
 [<c014ffd7>] softlockup_tick+0x97/0xd0
 [<c01097ba>] timer_interrupt+0x2fa/0x6c0
 [<c011c219>] __wake_up_common+0x39/0x60
 [<c0137413>] __rcu_process_callbacks+0x143/0x230
 [<c0150343>] handle_IRQ_event+0x33/0xa0
 [<c0150458>] __do_IRQ+0xa8/0x120
 [<c010770f>] do_IRQ+0x3f/0xa0
 [<c0249d20>] evtchn_do_upcall+0xe0/0x1f0
 [<c0105bbd>] hypervisor_callback+0x3d/0x45
 [<c0108c7a>] raw_safe_halt+0x9a/0x120
 [<c0104709>] xen_idle+0x29/0x50
 [<c01036dd>] cpu_idle+0x6d/0xc0

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 1264] New: Destorying DomU guest will cause dom0 crash on 32PAE host, bugzilla-daemon <=