| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] 32bit kernel under amd64
On Sun, 15 Feb 2009, Fajar A. Nugraha wrote:
On Sun, Feb 15, 2009 at 5:38 AM, SZABO Zsolt <szazs@xxxxxxxxx> wrote:
I have an xen-3.2.1 source under amd64 arch:
# uname -a
Linux xenserver 2.6.18.8-xen #1 SMP Thu Jul 31 23:51:53 CEST 2008 x86_64
GNU/Linux
I would like to compile a 32bit kernel for my domU, so I did the
following:
What distro are you using? Any particular reason to compile your own xen
kernel? both 32 and 64 bit domU kernel can load just fine on 64-bit
I need to compile an own modul under domU... I inherited a more or
less working xen setup with a linux (PV?) domU and a windows2003 HVM domU
hypervisor. dom0 kernel can be 32 or 64 bit, as long as the hypervisor
is 64 bit. IMHO, the easiest, failproof method to achive that is :
- Install 64bit RHEL/Centos dom0 with Virtualization option selected.
If you use Centos 5.2, this will get you RH's version of Xen 3.1 which
is already capable of runnig 32 and 64 bit domU
- Install xen-related packages from http://www.gitco.de/repo/ if you
want to use newer version of Xen. I'd recommend going straight to
3.3.1
- Use a working existing 32bit (pae) or 64bit domU, or create a new
one (with virt-install or whatever method you're familiar with)
Thanks for the hints... I have never ever used virt-install.
Now, I booted the domU with the older 32bit kernel, and I have issued
# mkinitramfs -o /boot/initrd.img-2.6.18.8-xenU 2.6.18.8-xenU
in the domU. Then shutdown the domU copy the initrd.img to dom0-s /boot,
This can be simplified by using pygrub. When you use
virt-install/virt-manager, the kernel will be in domU. This will
greatly simplify your setup as you don't need to copy it to dom0 on
every kernel update. domU will manage it's own kernel, just like any
normal Linux installation.
I see.
and trying again. Now, it boots, however I get no console prompt using
xm console domU... I just see the kernel messages of the domU.
I can ssh to the domU and it seems that every other things are working.
# uname -a
Linux linserver 2.6.18.8-xenU #2 SMP Sat Feb 14 15:44:35 CET 2009 i686
GNU/Linux
Have you ever run a xen domU succesfully before?
Yes, I have a working 32bit domU linux kernel, but I do not have the
xen-patched kernel source... So I decided to compile a new one (based on
the old's config) for myself under xen-3.2.1, and then copy the source
into domU and compile the needed module there.
This seems like the classical case of xen console listening on ttyS0
or xvc0, but your inittab does not spawn a login prompt on it.
Something like
http://wiki.centos.org/TipsAndTricks/Xen#head-860e915b4834566a29d7dd343d847e459b047e02
Look for inittab and securetty. Depending on your setup, you might
also need to add entry for ttyS0.
Hmm... in the inittab are the lines as follows:
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
and nothing for xvc0. However, this works with the original kernel but
not with the new one... So I should put a line
1:2345:respawn:/sbin/getty 9600 xvc0
or alike?
--
Zsolt
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home