From: Anthony Wright <anthony@overnetdata.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: First DomU started goes into a busy loop
Date: Tue, 25 Sep 2012 17:30:50 +0100 [thread overview]
Message-ID: <5061DC3A.7070704@overnetdata.com> (raw)
In-Reply-To: <1348561254.3452.103.camel@zakaz.uk.xensource.com>
On 25/09/2012 09:20, Ian Campbell wrote:
> (putting Anthony back on the CC)
>
> On Mon, 2012-09-24 at 18:18 +0100, Andrew Cooper wrote:
>> 32bit builds of Xen have been removed from 4.3. As far as I am aware,
>> there has been no serious effort to maintain them. I highly suggest
>> using a 64bit Xen.
> Anthony's references to 32-bit all seem to be in the context of the
> Linux kernel.
>
> Just to be clear we have removed support for the 32-bit hypervisor only.
> We have not and will not be removing support for 32-bit (PAE) PV
> domains, running as either guest or dom0 on a 64-bit hypervisor. 32-bit
> HVM guests, with or without PAE enabled, also remain fully supported.
>
> Ian.
>
Could you give me some pointers regarding building a 64 bit Xen
hypervisor on a 32 bit linux system, or do I need to build it on a 64
bit system?
I've found the XEN_TARGET_ARCH setting in the makefile which looks like
setting it to x86_64 might be the right direction, but I'm trying to
determine if there's an "official" way of doing it.
thanks,
Anthony.
next prev parent reply other threads:[~2012-09-25 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 15:31 First DomU started goes into a busy loop Anthony Wright
2012-09-24 17:18 ` Andrew Cooper
2012-09-25 8:20 ` Ian Campbell
2012-09-25 16:30 ` Anthony Wright [this message]
2012-09-25 16:33 ` Ian Campbell
2012-09-25 16:35 ` Andrew Cooper
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=5061DC3A.7070704@overnetdata.com \
--to=anthony@overnetdata.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.