6 messages in com.xensource.lists.xen-ia64-devel[Xen-ia64-devel] IA64 Intel further p...
FromSent OnAttachments
Radek Antoniuk28 May 2007 09:13 
Radek Antoniuk28 May 2007 09:21 
Alex Williamson28 May 2007 09:45 
Radek Antoniuk28 May 2007 10:04 
Alex Williamson28 May 2007 11:36 
Radek Antoniuk29 May 2007 04:02 
Subject:[Xen-ia64-devel] IA64 Intel further problems
From:Radek Antoniuk (r.an@pixel.com.pl)
Date:05/28/2007 09:13:36 AM
List:com.xensource.lists.xen-ia64-devel

Hi!

I've overcame the problem with the blank screen. The reason was that there was wrong path in the vmm= section in the elilo.conf file :)

Now, there is something more. I've compiled into kernel all modules needed for booting, created an initrd image even. The problem is that, that the kernel panics because it can't mount rootfs. The weird thing is that some lines up, I can see that the responsible controller is found, and that sda1 sda2 sda3 are visible. The message then says: Cannot mount rootfs with any filesystem! tried: ext2 ext3 reiserfs ..... And in fact the rootfs is ext3(however in an EFI partition?).

My elilo.conf:

install=/usr/lib/elilo/elilo.efi boot=/dev/sda1 delay=20 default=Linux relocatable

image=/boot/vmlinuz-2.6.18-4-mckinley label=Linux root=/dev/sda2 read-only initrd=/boot/initrd.img-2.6.18-4-mckinley

image=/boot/vmlinuz-2.6.18-xen label=xen root=/dev/sda2 vmm=/boot/xen.gz read-only initrd=/boot/initrd.img-2.6.18-xen append="com2=115200,8n1 console=com2 dom0_mem=1G -- nomca nosmp console=tty0 console=ttyS1,115200,8n1 rhgb root=/dev/sda2"

And for curiosity: fdisk -l /dev/sda

Disk /dev/sda: 36.7 GB, 36701199872 bytes 255 heads, 63 sectors/track, 4462 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System /dev/sda1 1 4463 35841015 ee EFI GPT

Remark: the non-xen kernel works of course :) Any ideas?

Thanks in advance for help! Radek