Displaying 2 results from an estimated 2 matches for "is_invalid_m2p_entry".
2006 Mar 29
0
Assertion ''! IS_INVALID_M2P_ENTRY(gpfn)'' failed kills machine
...have a good recipe for reproducing this one, and this is a reasonably
hacked up branch of (domU) XenLinux. So, while I can''t discount bugs
in this domU, a domU bug shouldn''t crash Xen like this:
(I belive this one was from simply typing halt in domU)
(XEN) Assertion ''! IS_INVALID_M2P_ENTRY(gpfn)'' failed, line 395, file shadow32.c(XEN) BUG at shadow32.c:395
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: e008:[<ff14ad8d>] free_shadow_page+0xd5/0x2ef
(XEN) EFLAGS: 00010282 CONTEXT: hypervisor
(XEN) eax: ff1a9818 ebx: ffffffff ecx: 00...
2006 Mar 29
1
RE: Assertion ''! IS_INVALID_M2P_ENTRY(gpfn)'' failedkillsmachine
Keir Fraser wrote:
> On 29 Mar 2006, at 17:09, Nakajima, Jun wrote:
>
>> Are you doing live migration? In the default setup for domUs, the
>> shadow code is never used.
>
> The mini patches for Linux we submitted to lkml depend on shadow mode.
>
> -- Keir
>
So this is _not_ for 3.0.2? I expect some hiccups with that if domUs
start using other than log-dirty