RE: [Xen-ia64-devel] Progress on RHEL4, but blocked at xlilo?

["Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>]

Hi Akio:
What you did should be correct, and we also look for the reason which result in 
the error .
        Thanks 
Zhang Xiantao
CSD-OTC PRC Virtualization 
Intel (China) Limited 

-----Original Message-----
From: takebe_akio@xxxxxxxxxxxxxx [mailto:takebe_akio@xxxxxxxxxxxxxx] 
Sent: 2005年11月8日 18:22
To: Zhang, Xiantao; Yang, Fred; Xu, Anthony; Magenheimer, Dan (HP Labs Fort 
Collins); xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Cc: takebe_akio@xxxxxxxxxxxxxx
Subject: RE: [Xen-ia64-devel] Progress on RHEL4, but blocked at xlilo?

Hi Zhang,

Thank you for your infomation.

>Please make sure your vmlinux-2.6.12-xen0 from .../xen-ia64-unstable.hg/
>linux-2.6.12-xen0/vmlinux , not ".../xen-ia64-unstable.hg/dist/install/
>vmlinux-2.6.12-xen0".
Yes. I don't use dist/install/vmlinuz-2.6.12.6-xen0xen.
I use linux-2.6.12-xen0/vmlinux.

I did as follows. :)

1. make xen
2. make kernels
3. cp xen/xen.gz /boot/efi/efi/xen/
4. cp linux-2.6.12-xen0/vmlinux /boot/efi/efi/xen/vmlinux-2.6.12-xen0
5. cd linux-2.6.12-xen0
6. make modules_install
7. mkinitrd -f /boot/efi/efi/xen/initrd-2.6.12-xen0.img 2.6.12.6-xen0xen
8. reboot and boot with xlilo

Best Regards,

Akio Takebe

>Hi Akio: 
>Please make sure your vmlinux-2.6.12-xen0 from .../xen-ia64-unstable.hg/
>linux-2.6.12-xen0/vmlinux , not ".../xen-ia64-unstable.hg/dist/install/
>vmlinux-2.6.12-xen0".
>Because  vmlinux is uncompressed and vmlinux-2.6.12-xen0 from dist 
>directory is compressed in despite of its no .gz end.
>
>     Zhang Xiantao
>CSD-OTC PRC Virtualization 
>Intel (China) Limited 
>
>
>
>
>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-ia64-devel-
>bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of takebe_akio@xxxxxxxxxxxxxx
>Sent: 2005ト・1ヤツ8ネユ 16:28
>To: Yang, Fred; Xu, Anthony; Magenheimer, Dan (HP Labs Fort Collins); xen-
>ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] Progress on RHEL4, but blocked at xlilo?
>
>Hi Fred,
>
>I used the following file.
>I should use uncompressed linux kernel, shouldn't I?
>
># file /boot/efi/efi/xen/vmlinux-2.6.12-xen0 
>/boot/efi/efi/xen/vmlinux-2.6.12-xen0: ELF 64-bit LSB executable, IA-64, 
>version 1 (SYSV), statically linked, not stripped
>
>Best Regards,
>
>Akio Takebe
>
>>Akio,
>>
>>To make sure, you are not using "compressed" XenoLinux image in the
>>configuration file
>>
>>> image=vmlinux-2.6.12-xen0  <=========== MUST not compressed
>>>         label=xen
>>>         vmm=xen.gz
>>>         initrd=initrd-2.6.12-xen0.img
>>>         read-only
>>
>>-Fred
>>
>>takebe_akio@xxxxxxxxxxxxxx wrote:
>>> Hi Dan, Fred and Anthony,
>>> 
>>> Thank you for your adivece.
>>> As you say, I used the following config file.
>>> But I couldn't boot.
>>> 
>>> ------------
>>> prompt
>>> timeout=20
>>> default=xen
>>> relocatable
>>> 
>>> image=vmlinux-2.6.12-xen0
>>>         label=xen
>>>         vmm=xen.gz
>>>         initrd=initrd-2.6.12-xen0.img
>>>         read-only
>>>         append="com2=115200,8n1 console=com2 sched=bvt -- nomca nosmp
>>> console=tty0 rhgb root=/dev/sda2" ------------
>>> 
>>> I suspect registrations of SCSI drivers and so on.
>>> I used vmlinux included "mptscsih and mptbase" now.
>>> Should I use a initrd included "mptscsih and mptbase"
>>> and a vmlinux not included these?
>>> 
>>> I will check the buffer of kernel_read() by using more printk(). :-)
>>> 
>>> Best Regards,
>>> 
>>> Akio Takebe
>>> 
>>> 


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