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 77] New: System crashed when starting vmx domain if comp

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 77] New: System crashed when starting vmx domain if compiling xen with "debug=y"
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 17 Jun 2005 06:55:44 +0000
Delivery-date: Fri, 17 Jun 2005 06:55:48 +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>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: System crashed when starting vmx domain if  compiling
                    xen with "debug=y"
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: lifeng.yu@xxxxxxxxx

Using vmmassist, We've tried to start vmx domain on 32-bit dom0 on bk tree

We can success to enter dom0, but whole system crashed when trying to start vmx
domain. crashed with info:
(XEN)  0000000000000000 - 000000000009f800 (usable)
(XEN)  000000000009f800 - 00000000000a0000 (reserved)
(XEN)  00000000000a0000 - 00000000000c0000 type 16
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000007fff000 (usable)
(XEN)  0000000007fff000 - 0000000008000000 type 17
(XEN)  0000000008000000 - 0000000008003000 (ACPI NVS)
(XEN)  0000000008003000 - 000000000800d000 (ACPI data)
(XEN)  00000000fec00000 - 0000000100000000 type 16
(XEN) DOM1P1: SH_LOG(1466): Allocate more shadow hashtable blocks.
(XEN) Assertion 'VM_ASSIST(d, VMASST_TYPE_writable_pagetables) || shadow_mode_wr
ite_all(d)' failed, line 2341, file shadow.c
(XEN) BUG at shadow.c:2341
(XEN) CPU:    1
(XEN) EIP:    e008:[<ff13468e>]
(XEN) EFLAGS: 00010296   CONTEXT: hypervisor
(XEN) eax: 00000000   ebx: ff1661a3   ecx: 000016b3   edx: 00000000
(XEN) esi: ff1630f4   edi: 00000925   ebp: ff1b8080   esp: ffbf9d74
(XEN) cr0: 8005003b   cr3: 7b926000
(XEN) ds: e010   es: e010   fs: e010   gs: e010   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ffbf9d74:
(XEN)    ff15e932 ff1661a3 00000925 ff1661a3 fc400000 000088c5 e0000007 088c5067

(XEN)    ff1b8080 7b922067 088c5067 [ff12fb64] 088c5067 ff1b8080 00000000 ffbf9f
(XEN)    00000004 000088c5 00000000 00000000 00000000 7b922067 ff1b3080 [ff1380b
(XEN)    08bff025 ffbf9fb4 00000008 [ff130243] 00000000 00000000 e0000008 000000
(XEN)    00000020 00000000 fefdb000 fefdc000 fefda000 0007b922 ffbe1080 20000000

(XEN)    ff1b8080 000088c5 00000000 00000000 fefd9408 ff1b8080 088c5067 [ff134c4
(XEN)    fefd9408 ff1b8080 c0102000 000088c5 000c0102 ff1b8080 088c5065 ffffffff

(XEN)    c0101c00 ff1b3080 ff1b8080 [ff13f2b3] ff1b8080 c0101c00 80050033 [ff141
(XEN)    00000001 000000fc ff175110 ff1b3080 ff1a4080 088c5067 ff1b8080 000088c5

(XEN)    00000102 00000000 00102007 00102027 fc4cd260 ff1b8080 00000000 00000202

(XEN)    ff1b3080 088c5067 ffbf9f90 c0101c00 00000000 ffbf9fb4 c7fff000 [ff142d7
(XEN)    ff1b3080 ffbf9fb4 ff1a4080 00000080 00000202 00be0000 ff1b3080 ff1b3080

(XEN)    [ff11ff13] ff1b3080 00be0000 00000000 ffbfb080 00000000 02faf080 000000
(XEN)    003937ec 00000000 003937ec 00000000 f388445e 00000018 ff1a4080 ff1a4e00

(XEN)    f3f01ba0 00000060 00101d93 00000080 ec27165c ff1b3080 00000002 c010010d

(XEN)    00000002 ff1b3080 00800040 bfe9fbb7 f3f01ba0 00000018 00000080 00000001

(XEN)    00000002 00000080 00000001 00000001 00000080 ff1a4080 00000080 00102007

(XEN)    00000001 00fc0000 ffbf9fb4 c0103000 00000400 00000300 c7fff000 [ff149b3
(XEN)    c0103000 c0000000 c0101c00 00000400 00000300 c7fff000 00102063 00000003

(XEN)    00101d2a 00000060 00000000 0023a8cc 00000202 00000068 00000068 00000000

(XEN) Xen call trace from esp=ffbf9d74:
(XEN)    [<ff12fb64>] [<ff1380b5>] [<ff130243>] [<ff134c4d>] [<ff13f2b3>] [<ff14
(XEN)    [<ff142d7a>] [<ff11ff13>] [<ff149b3d>]

Panic on CPU1:
CPU1 FATAL TRAP: vector = 6 (invalid operand)

Reboot in five seconds...

------- 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 77] New: System crashed when starting vmx domain if compiling xen with "debug=y", bugzilla-daemon <=