[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] 32 & 64 & the FAQ


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Jesper Andersen <ii1fm0ay@xxxxxx>
  • Date: Thu, 16 Aug 2007 15:13:54 +0800
  • Delivery-date: Thu, 16 Aug 2007 00:23:52 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Wednesday 15 August 2007, Steven Timm wrote:
> Just one question, how do you specify in your xen.cfg
> file to pick up the 32-bit kernel and start the xen instance?
> Right now I am doing the following:
>
> kernel = "/boot/vmlinuz-2.6-xen"
>
> ramdisk = "/boot/initrd-2.6.18-xen.img"
>
> But this seems to be picking up the 64-bit xensource kernel
> in my dom0's /boot directory, not the identically-named
> /boot/vmlinux-2.6-xen in what is going to be the /boot partition
> of dom1 (which I have populated with 32-bit rhel5).

When specified this way kernels are picket from dom0. So to make it work 
you will have to copy the kernel to dom0. If you want to keep the kernel 
in domU you can use pygrub to write something like grubs menu.lst to 
choose kernel.

> Do I have to have the 32-bit kernel that the domU is going to
> boot, visible to user space within the dom0 so xen can start the
> instance properly?

When you specify this way you have to.

> What is happening now is that the domU is starting and I am
> ending up running a 64-bit kernel on top of a 32-bit distro,
> which I thought was impossible but it is mostly working.

64 bit kernels can have support for executing 32 bit code. I have been 
using that for a long time.

-- 
Jesper
 11:04:10 up 13:58,  5 users,  load average: 0.60, 0.28, 0.11

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.