Yup, it was my understanding that the (ELF 32-bit LSB executable) xen hypervisor handed off control to a 64-bit hyper-visor.
This 32-bits step was required for the boot loader (e.g.: grub) to hand over control.
-M
> Date: Tue, 18 May 2010 10:13:22 -0500
> From: dunlapg@xxxxxxxxx
> To: yanglei.fage@xxxxxxxxx
> CC: xen-devel@xxxxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Re: [Xen-devel] Re: How to build a 64 bit xen
>
> I've cross-compiled 64-bit xen exclusively since I've worked for
> XenSource basically. Here's what I get:
>
> $ file xen/xen
> xen/xen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
> statically linked, stripped
> $ file xen/xen-syms
> xen/xen-syms: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> statically linked, not stripped
>
> So I think 'file' is just making a mistake.
>
> -George
>
> On Tue, May 18, 2010 at 9:40 AM, lei yang <yanglei.fage@xxxxxxxxx> wrote:
> > Is there some body to help see your "$file xen-4.0.0" if your xen is 64 bit
> >
> > Thanks
> > Lei
> >
> > On Tue, May 18, 2010 at 9:11 PM, lei yang <yanglei.fage@xxxxxxxxx> wrote:
> >>
> >> Hi experts,'
> >>
> >> I build xen on my 64 bit redhat with "make xen", I got the image
> >> xen-4.0.0.gz
> >> then
> >> $gunzip xen-4.0.0.gz
> >> $file xen-4.0.0
> >> it tells me it's 32 bit,but I saw it link the 64 bit lib
> >>
> >> Thanks
> >> Lei
> >> --
> >> "We learn from failure, not from success!"
> >
> >
> >
> > --
> > "We learn from failure, not from success!"
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >
> >
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
Win a $10,000 shopping spree from Hotmail! Enter now Enter now
|
