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).
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?
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.
Any help is appreciated.
Thanks
Steve Timm
On Fri, 10 Aug 2007, Jesper Andersen wrote:
I still didn't try another kernel on that server. But I tried the
xensource 3.1 on an Intel 6300 cpu system running kubuntu and here it
worked fine with 32bit pae domU. So I guess it is the Fedora 7 kernel
that has a problem.
--
------------------------------------------------------------------
Steven C. Timm, Ph.D (630) 840-8525
timm@xxxxxxxx http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
| 
Home