All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel@lists.xensource.com,
	Mark Williamson <mark.williamson@cl.cam.ac.uk>,
	Horms <horms@verge.net.au>
Subject: Re: Re: [PATCH] Xen Guest Kexec
Date: Thu, 02 Mar 2006 12:34:23 +0100	[thread overview]
Message-ID: <4406D83F.3080709@suse.de> (raw)
In-Reply-To: <cc4d44aeb3f80fb3b1f2eb26e34a056b@cl.cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

> The default segment descriptors are *always* available. A guest can only
> install up to a 14-page GDT: the 15th and 16th pages are reserved by Xen
> and always present.

Ok, managed to fixup that, switching to the default descriptors and
killing the GDT works, so the gdt doesn't stop validating any more.

But I ran into the next bug now.  I think we have a funny
chicken-and-egg problem when validating a self-consistent but new page
table set (which also maps itself) from scratch, see messages attached
below.

cheers,
  Gerd

-- 
Gerd 'just married' Hoffmann <kraxel@suse.de>
I'm the hacker formerly known as Gerd Knorr.
http://www.suse.de/~kraxel/just-married.jpeg

[-- Attachment #2: oops --]
[-- Type: text/plain, Size: 2035 bytes --]

(XEN) DOM1: (file=mm.c, line=1501) Bad type (saw 33020001 != exp e0000000) for mfn 1c711 (pfn 0)
(XEN) DOM1: (file=mm.c, line=479) Error getting mfn 1c711 (pfn 0) from L1 entry 1c711063 for dom1
(XEN) DOM1: (file=mm.c, line=685) Failure in alloc_l1_table: entry 0
(XEN) DOM1: (file=mm.c, line=1542) Error while validating mfn 18c92 (pfn 35a8) for type 20000000: caf=80000003 taf=20000001
(XEN) DOM1: (file=mm.c, line=402) Attempt to create linear p.t. with write perms
(XEN) DOM1: (file=mm.c, line=846) Failure in alloc_l2_table: entry 0
(XEN) DOM1: (file=mm.c, line=1542) Error while validating mfn 18c95 (pfn 35a5) for type 40000000: caf=80000003 taf=40000001
(XEN) DOM1: (file=mm.c, line=1579) trying slow path via idle pagetables ...
(XEN) DOM1: (file=mm.c, line=1501) Bad type (saw 40000001 != exp e0000000) for mfn 18c95 (pfn 35a5)
(XEN) DOM1: (file=mm.c, line=479) Error getting mfn 18c95 (pfn 35a5) from L1 entry 18c95063 for dom1
(XEN) DOM1: (file=mm.c, line=685) Failure in alloc_l1_table: entry 421
(XEN) DOM1: (file=mm.c, line=1542) Error while validating mfn 18c85 (pfn 35b5) for type 200d0000: caf=80000002 taf=200d0001
(XEN) DOM1: (file=mm.c, line=402) Attempt to create linear p.t. with write perms
(XEN) DOM1: (file=mm.c, line=846) Failure in alloc_l2_table: entry 13
(XEN) DOM1: (file=mm.c, line=1542) Error while validating mfn 18c95 (pfn 35a5) for type 40000000: caf=80000002 taf=40000001
(XEN) DOM1: (file=mm.c, line=1593) Fatal error while installing new baseptr 18c95
(XEN) domain_crash called from mm.c:1594
(XEN) Domain 1 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0.0    Not tainted ]----
(XEN) CPU:    1
(XEN) EIP:    e019:[<c010ed3d>]
(XEN) EFLAGS: 00010206   CONTEXT: guest
(XEN) eax: c0012000   ebx: 00000000   ecx: fbf8d000   edx: 18c95000
(XEN) esi: 035a4000   edi: c0732400   ebp: c3e57e88   esp: c3e57e60
(XEN) cr0: 8005003b   cr3: 001b6000
(XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
(XEN) Guest stack trace from esp=c3e57e60:
(XEN)    Fault while accessing guest memory.

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2006-03-02 11:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-26 22:49 Re: [PATCH] Xen Guest Kexec Ian Pratt
2006-02-27  7:10 ` Keir Fraser
2006-02-27 15:34   ` Gerd Hoffmann
2006-02-27 16:19     ` Keir Fraser
2006-03-01 12:09       ` Gerd Hoffmann
2006-03-01 14:10         ` Gerd Hoffmann
2006-03-01 15:03           ` Keir Fraser
2006-03-01 17:35             ` Keir Fraser
2006-03-02  9:16               ` Gerd Hoffmann
2006-03-02  9:43                 ` Keir Fraser
2006-03-02 11:34                   ` Gerd Hoffmann [this message]
2006-03-02 11:55                     ` Keir Fraser
2006-03-02 16:36                       ` Gerd Hoffmann
2006-03-02 16:48                         ` Keir Fraser
2006-03-03  8:39                           ` Gerd Hoffmann
2006-03-03  9:14                             ` Keir Fraser
2006-03-03  9:35                               ` Keir Fraser
2006-03-03 11:19                                 ` Gerd Hoffmann
2006-03-06 14:15                                 ` Gerd Hoffmann
2006-03-06 16:04                                   ` Michael Vrable
2006-03-07 13:06                                 ` Gerd Hoffmann
2006-03-07 13:42                                   ` Keir Fraser
2006-03-07 14:43                                     ` Gerd Hoffmann
  -- strict thread matches above, loose matches on Subject: below --
2005-07-07 17:16 Mark Williamson
2006-02-23 10:52 ` Horms
2006-02-23 11:22   ` Gerd Hoffmann
2006-02-23 11:32     ` Mark Williamson
2006-02-23 13:03       ` Gerd Hoffmann
2006-02-23 14:49         ` Mark Williamson
2006-02-24 14:35           ` Gerd Hoffmann
2006-02-27 14:29             ` Mark Williamson
2006-02-27 15:39               ` Gerd Hoffmann
2006-02-23 11:36   ` Mark Williamson
2006-02-27  3:32     ` Horms
2006-02-27 14:58       ` Mark Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4406D83F.3080709@suse.de \
    --to=kraxel@suse.de \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=horms@verge.net.au \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=mark.williamson@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.