xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "szilagyi@nyo.unep.org" <szilagyi@nyo.unep.org>
Cc: Martin Kraus <lists_mk@wujiman.net>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Thiago Camargo Martins Cordeiro <thiagocmartinsc@gmail.com>,
	xen-users <xen-users@lists.xensource.com>
Subject: Re: Xen 3.4.2 hypervisor crash, Cannot access memory beyond end of bootstrap direct-map area, Unknown interrupt
Date: Fri, 29 Jan 2010 06:36:03 +0000	[thread overview]
Message-ID: <C7883253.7F02%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B624DF4.2050109@nyo.unep.org>

On 29/01/2010 02:54, "gabor" <szilagyi@nyo.unep.org> wrote:

> Sounds something interesting ... to try...
> Could you give some pointers as to how to compile the hypervisor as
> 64-bit???
> 
> I currently have a 32-bit setup but the hardware (CPU/MB/RAMetc) is
> 64-bit capable and I could just run 32-bit domUs I wanted to run more
> than a bare dom0 on the hardware for continutity ....  but I am kind of
> free to try ANYTHING .... but I need to run stuff in Debian/32-bit ...
> 
> So can you tell me how to compile a 64-bit xen.gz on my current Debian
> 32-bit PAE setup??? (the host needs to be up for certain other things
> although 24/7 is not an issue...)

Assuming you know how to download and build and install 32-bit Xen, what you
may be able to do is: cd xen; XEN_TARGET_ARCH=x86_64 make install

It depends if your 32-bit gcc can cross-compile to 64-bit target.

 -- Keir

  reply	other threads:[~2010-01-29  6:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100126155046.GD6085@finrod>
     [not found] ` <6b7f6eb1001261134sf59257ag8335a2189565eb71@mail.gmail.com>
     [not found]   ` <20100127104417.GA2346@finrod>
     [not found]     ` <4B60507E.6080705@nyo.unep.org>
     [not found]       ` <20100127202649.GU2861@reaktio.net>
     [not found]         ` <4B61B746.8050207@nyo.unep.org>
     [not found]           ` <20100128162610.GR2861@reaktio.net>
     [not found]             ` <4B61ECC9.1090404@nyo.unep.org>
     [not found]               ` <20100128200240.GA2861@reaktio.net>
     [not found]                 ` <4B61F7D8.5050604@nyo.unep.org>
2010-01-28 21:16                   ` Xen 3.4.2 hypervisor crash, Cannot access memory beyond end of bootstrap direct-map area, Unknown interrupt Pasi Kärkkäinen
2010-01-28 23:04                     ` [Xen-users] " Keir Fraser
2010-01-29  0:23                       ` Martin Kraus
2010-01-29  2:54                       ` gabor
2010-01-29  6:36                         ` Keir Fraser [this message]
2010-01-29 15:50                           ` Gabor Szilagyi
2010-01-29 16:40                             ` [Xen-users] " Keir Fraser
2010-01-30 14:54                               ` [Xen-devel] " Pasi Kärkkäinen
2010-02-04  7:50                               ` Pasi Kärkkäinen

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=C7883253.7F02%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=lists_mk@wujiman.net \
    --cc=szilagyi@nyo.unep.org \
    --cc=thiagocmartinsc@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).