From: "Steven Hand" <steven.hand@cl.cam.ac.uk>
To: Jacek Konieczny <jajcus@jajcus.net>, xen-devel@lists.xensource.com
Cc: Steven Hand <Steven.Hand@cl.cam.ac.uk>
Subject: Re: Wrong binary in 32-bit PAE pre-built release
Date: Fri, 1 Jun 2007 14:37:08 +0100 [thread overview]
Message-ID: <086201c7a451$f42e74e0$21101fac@Violet> (raw)
In-Reply-To: 20070601125512.GB9591@jajo.eggsoft.pl
Yeah, you're right - sorry about that, not sure what happened.
I'll rebuild and update the tarball.
cheers,
S.
----- Original Message -----
From: "Jacek Konieczny" <jajcus@jajcus.net>
To: <xen-devel@lists.xensource.com>
Sent: Friday, June 01, 2007 1:55 PM
Subject: [Xen-devel] Wrong binary in 32-bit PAE pre-built release
> Hello,
>
> Trying to find a fix for my problem with Xen I decided to download
> an official build. I took 32-bit PAE SMP build
> (xen-3.1.0-install-x86_32p.tgz from
> http://www.xensource.com/download/dl_31tarballs.html), booted
> the boot/xen-3.1.0.gz image... and got "not a 64-bit CPU" message. The
> provided xen binary seems to be 64-bit instead of 32-bit PAE, indeed.
>
> There is also xen-3.0.5-rc1.gz image in the same archive and this one is
> 32-bit PAE, as expected.
>
> Greets,
> Jacek
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-06-01 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 12:55 Wrong binary in 32-bit PAE pre-built release Jacek Konieczny
2007-06-01 13:37 ` Steven Hand [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-01 12:25 Jacek Konieczny
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='086201c7a451$f42e74e0$21101fac@Violet' \
--to=steven.hand@cl.cam.ac.uk \
--cc=jajcus@jajcus.net \
--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.