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-devel] failed when boot the domain with shadow mode enabled

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] failed when boot the domain with shadow mode enabled
From: "Li, Chengyuan" <chengyuan.li@xxxxxxxxx>
Date: Thu, 23 Jun 2005 19:24:41 +0800
Delivery-date: Thu, 23 Jun 2005 11:23:40 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcV35iYZ7I2mbHE/QL28Pc5fzVfM1Q==
Thread-topic: failed when boot the domain with shadow mode enabled


I tried to run the dom0 & domU with shadow mode enabled, but both are failed.
For dom0:
1 Set opt_dom0_shadow=1
2.Compile the dom0 kernel with CONFIG_XEN_SHADOW_MODE
Then boot the system, but it failed in the function new_guest_cr3() when get_page_type().

For domU:
1.Compile the domU kernel with CONFIG_XEN_SHADOW_MODE
When "xm create" the domU, it failed at the similar point as dom0, because of get_page_type() failed.

Is it a bug in shadow mode for dom0 & domU, or the way I start the dom with shadow mode enabled is not right?

(XEN) DOM0: (file=mm.c, line=1389) Bad type (saw f0000001 != exp 40000000) for
fn 8102
(XEN) DOM0: (file=mm.c, line=370) Bad page type for pfn 8102 (f0000001)
(XEN) DOM0: (file=mm.c, line=1485) Error while installing new baseptr 8102
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) CPU:    0
(XEN) EIP:    e019:[<c01157bf>]
(XEN) EFLAGS: 00200282   CONTEXT: guest
(XEN) eax: ffffffea   ebx: c04fff24   ecx: 00000001   edx: 00000000
(XEN) esi: 00007ff0   edi: c0102fc0   ebp: c05b4000   esp: c04fff18
(XEN) cr0: 8005003b   cr3: 019f3000
(XEN) ds: e021   es: e021   fs: 0000   gs: e021   ss: e021   cs: e019
(XEN) Guest stack trace from esp=c04fff18:                                     0
(XEN)    c01157bf 0001e019 00210282 00000005 00008102 00000000 c04fe000 0000000
(XEN)    c05b4fc0 c050d710 00102000 c0567394 00100000 004b8fff 00001000 0000000
(XEN)    c05240d8 c0101000 00000000 c050d82b 004b8fff c0507bdb 00100000 004b8ff

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>