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 1189] New: Xen's paravirt won't boot a PaX patched kerne

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1189] New: Xen's paravirt won't boot a PaX patched kernel (
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 11 Mar 2008 07:31:17 -0700
Delivery-date: Tue, 11 Mar 2008 07:31:28 -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: Xen's paravirt won't boot a PaX patched kernel
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: a.grassi@xxxxxxxxxxxxxx

I'm running Xen Hypervisor 3.2.0-2, backported on Debian etch from sid, with a
Debian-patched Linux 2.6.18 as dom0

While a vanilla 2.6.24 (which includes domU support) boots normally, a kernel
patched with PaX (www.grsecurity.net), which boots on real hardware, will crash
on xen before even getting to the entry point.

By inspecting the memory of the running (crashed) kernel, most (if not all) of
the .data segment is filled with zeroes, thus making it die because the magic
is not "xen-3" (and this is because "xen-3" isn't there, just like the rest of
the constants)

The exact change in the PaX kernel that makes the dom die is in the file
arch/x86/kernel/vmlinux_32.lds.S, so i think (even if i'm not sure) that looks
like a problem with the relocation that Xen does when tries to load the domain

You can find all the info that i've discovered so far, including how to
reproduce the problem, in the thread i've started on grsecurity's forums:


(Please forgive me if i eventually made some mistakes in explaining xen-related
info, i'm quite new to Xen myself)

Thank you for your attention

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 1189] New: Xen's paravirt won't boot a PaX patched kernel (, bugzilla-daemon <=