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:
# cd xen-3.2.1
# make XEN_TARGET_ARCH=x86_32 linux-2.6-xenU-prep
# cd build-linux-2.6.18-xenU_x86_32
# make ARCH=i386 menuconfig
# make ARCH=i386
# make ARCH=i386 install modules_install
# mkinitramfs -o /boot/initrd.img-2.6.18.8-xenU 2.6.18.8-xenU
Then here is my domU.conf:
kernel="/boot/vmlinuz-2.6.18.8-xenU"
ramdisk = "/boot/initrd.img-2.6.18.8-xenU"
memory = 6144
name = "linserver"
cpus = "0-3"
vcpus = 4
vif = [ ''mac=00:40:f6:54:79:0f,
bridge=xenbr0'',''mac=00:16:3e:00:01:01,
bridge=xenbr1'' ]
disk = [ ''phy:/dev/system/linserv_root,sda1,w'',
''phy:/dev/system/linserv_usr,sda2,w'',
''phy:/dev/system/linserv_var,sda3,w'',
''phy:/dev/system/linserv_opt,sda4,w'',
''phy:/dev/system/linserv_home,sdb1,w'',
''phy:/dev/swap/linserv_swap,sdb2,w'' ]
dhcp="dhcp"
root = "/dev/sda1 ro"
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
(this domU is working with another 2.6.18 32bit xen kernel)
However when creating the domU in the xm console I see:
[...]
pnp: PnP ACPI: disabled
suspend: event channel 15
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
audit: initializing netlink socket (disabled)
audit(1234630146.450:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
(usb?)
Failed to obtain physical IRQ 6
floppy0: Unable to grab DMA2 for the floppy driver
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as xvc0
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
xen-vbd: registered block device major 8
blkfront: sda1: barriers enabled
blkfront: sda2: barriers enabled
blkfront: sda3: barriers enabled
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
blkfront: sda4: barriers enabled
blkfront: sdb1: barriers enabled
blkfront: sdb2: barriers enabled
XENBUS: Device with no driver: device/console/0
Freeing unused kernel memory: 196k freed
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
[and it hangs here]
What did I wrong?
--
Zsolt
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Sat, 14 Feb 2009, SZABO Zsolt 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: > > # cd xen-3.2.1 > # make XEN_TARGET_ARCH=x86_32 linux-2.6-xenU-prep > # cd build-linux-2.6.18-xenU_x86_32 > # make ARCH=i386 menuconfig > # make ARCH=i386 > # make ARCH=i386 install modules_install > # mkinitramfs -o /boot/initrd.img-2.6.18.8-xenU 2.6.18.8-xenU > > Then here is my domU.conf: > > kernel="/boot/vmlinuz-2.6.18.8-xenU" > ramdisk = "/boot/initrd.img-2.6.18.8-xenU"[...]> > > However when creating the domU in the xm console I see: > > [...] > XENBUS: Device with no driver: device/console/0 > Freeing unused kernel memory: 196k freed > request_module: runaway loop modprobe binfmt-464c > request_module: runaway loop modprobe binfmt-464c > request_module: runaway loop modprobe binfmt-464c > request_module: runaway loop modprobe binfmt-464c > request_module: runaway loop modprobe binfmt-464c > > [and it hangs here]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, 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. [...] ReiserFS: sdb1: found reiserfs format "3.6" with standard journal ReiserFS: sdb1: using ordered data mode ReiserFS: sdb1: journal params: device sdb1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: sdb1: checking transaction log (sdb1) ReiserFS: sdb1: Using r5 hash to sort names fuse init (API version 7.7) process `syslogd'' is using obsolete setsockopt SO_BSDCOMPAT Installing knfsd (copyright (C) 1996 okir@monad.swb.de). NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver [nothing else, no login prompt, no output from init.d, etc.] 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 -- Zsolt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Feb 15, 2009 at 5:38 AM, SZABO Zsolt <szazs@mm.bme.hu> 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 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)> > 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.> 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/LinuxHave you ever run a xen domU succesfully before? 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. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, 15 Feb 2009, Fajar A. Nugraha wrote:> On Sun, Feb 15, 2009 at 5:38 AM, SZABO Zsolt <szazs@mm.bme.hu> 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-bitI 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@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Feb 15, 2009 at 10:43 PM, SZABO Zsolt <szazs@mm.bme.hu> wrote:> 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 domUOuch. The old "I inherited a system" situation :) Which module is it? What distro? Some modules can be built out-of-tree. For example, if you need fuse on Centos, you can start with a domU having kernel-xen and kernel-xen-devel, and use it to compile a fuse module without having to recompile the kernel. If it were me, I''d simply use a vendor-provided xen-kernel (RHEL/Centos, in this example) and compile the module out-of-tree. This would reduce the chance of things going wrong.>> 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 notProbably because somehow the original kernel uses tty1 for xen console.> with the new one... So I should put a line > > 1:2345:respawn:/sbin/getty 9600 xvc0each line should have it''s own identifier. "1" is already taken for tty1. See the link I sent earlier. Try with xvc0 first, and if it doesn''t work try ttyS0. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users