25 messages in com.xensource.lists.xen-ia64-develRE: [Xen-ia64-devel] RFC: Switch to x...
FromSent OnAttachments
Magenheimer, Dan (HP Labs Fort Collins)16 Nov 2005 10:32 
Yang, Fred16 Nov 2005 12:39 
Magenheimer, Dan (HP Labs Fort Collins)16 Nov 2005 12:44 
Yang, Fred16 Nov 2005 12:56 
Magenheimer, Dan (HP Labs Fort Collins)16 Nov 2005 13:36 
Tristan Gingold17 Nov 2005 02:00 
Tristan Gingold17 Nov 2005 03:05.diffs
take...@jp.fujitsu.com17 Nov 2005 05:10 
Magenheimer, Dan (HP Labs Fort Collins)17 Nov 2005 05:26 
Magenheimer, Dan (HP Labs Fort Collins)17 Nov 2005 05:41 
take...@jp.fujitsu.com17 Nov 2005 05:53 
take...@jp.fujitsu.com17 Nov 2005 05:56 
Magenheimer, Dan (HP Labs Fort Collins)17 Nov 2005 06:14 
take...@jp.fujitsu.com17 Nov 2005 06:25.config
Magenheimer, Dan (HP Labs Fort Collins)17 Nov 2005 10:08 
Alex Williamson17 Nov 2005 15:31 
Magenheimer, Dan (HP Labs Fort Collins)17 Nov 2005 20:13 
Matt Chapman17 Nov 2005 23:35 
Tian, Kevin17 Nov 2005 23:37 
Matt Chapman18 Nov 2005 00:58.patch
take...@jp.fujitsu.com18 Nov 2005 01:11.patch, .patch
竹部18 Nov 2005 01:32 
Magenheimer, Dan (HP Labs Fort Collins)18 Nov 2005 09:17 
Magenheimer, Dan (HP Labs Fort Collins)18 Nov 2005 09:32 
Matt Chapman18 Nov 2005 16:58 
Subject:RE: [Xen-ia64-devel] RFC: Switch to xlilo now? Or post-3.0?
From:Magenheimer, Dan (HP Labs Fort Collins) (dan.@hp.com)
Date:11/17/2005 10:08:25 AM
List:com.xensource.lists.xen-ia64-devel

Thank you very much for your complete instructions.

I am now able to get further but domain0 still crashes. Just after

Freeing unused kernel memory... Warning: unable to open an initial console... cdrom: open failed

I get a very long string of errors

nbd0: Request when not-ready end_request: I/O error, dev nbd0, sector 0 Buffer I/O error on device nbd0, logical block 0 [ and 1]

this repeats for nbd1-nbd15. After which I get:

kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filessystem with ordered data mode

But then (from Xen):

handle_op: can't handle privop at 0xa000000000010670 (op=0) slot 0 (type=5)

(note, NOT 0xa000000100010670)

and

udevstart[1047]: General Exception: IA-64 Privileged Operation fault 16 [1] Modules linked in:

and then a a long string of kernel core dumps, the first of which is comm=udevstart.

One difference in my process is that mkinitrd unless I add the following arguments: "--builtin mptbase --builtin mptscsih" (These are the Fusion drivers necessary to boot the HP box.)

So I am still not able to boot RHEL4 with Xen but I guess this is progress :-)

Dan

-----Original Message----- From: take@jp.fujitsu.com [mailto:take@jp.fujitsu.com] Sent: Thursday, November 17, 2005 6:54 AM To: Magenheimer, Dan (HP Labs Fort Collins); xen-@lists.xensource.com Cc: take@jp.fujitsu.com Subject: RE: [Xen-ia64-devel] RFC: Switch to xlilo now? Or post-3.0?

Hi Dan,

Plese call Akio. :-)

I probably did the following step.

# cd /root # hg clone http://xenbits.xensource.com/ext/xen-ia64-unstable.hg # cp /home/takebe/linux-2.6.12.tar.bz2 /root/xen-ia64-unstable.hg # cd /root/xen-ia64-unstable.hg # patch -p1 < /root/xen-xlilo.patch <-----Tristan's Patch # make world # make install-tools # cp xen/xen.gz /boot/efi/efi/xen/ # cp linux-2.6.12-xen0/vmlinux /boot/efi/efi/xen/vmlinux-2.6.12-xen0 # cd linux-2.6.12-xen0 # make modules_install # mkinitrd -f /boot/efi/efi/xen/initrd-2.6.12-xen0.img 2.6.12.6-xen0 # vi /boot/efi/efi/xen/elilo.conf 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 maxcpus=1 -- nomca nosmp console=tty0 console=ttyS1,115200,8n1 rhgb root=/dev/sda2"

# reboot and boot with /boot/efi/efi/xen/xlilo.efi

Best Regards,

Takebe -- (Sorry, should I call you Akio or Takebe?)

Did you build and install from xen-ia64-unstable tip (cset 7734 or greater)?

If so, could you again provide the recipe for building and installing on RHEL4? I would like to try again and some things have changed (such as CONFIG_LOCALVERSION and the build process for domU) so I would like to understand the exact steps you used successfully first.

Thank you! Dan

-----Original Message----- From: take@jp.fujitsu.com [mailto:take@jp.fujitsu.com] Sent: Thursday, November 17, 2005 6:11 AM To: Tristan Gingold; Magenheimer, Dan (HP Labs Fort Collins); Yang, Fred; xen-@lists.xensource.com Subject: Re: [Xen-ia64-devel] RFC: Switch to xlilo now? Or post-3.0?

Hi Tristan,

Great!!! I test your patch with xlilo on RHEL4. I confirmed Dom0 can be booted.

The following is my elilo.conf. :-) -------------------------- 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 maxcpus=1 -- nomca nosmp console=tty0 console=ttyS1,115200,8n1 rhgb root=/dev/sda2"

--------------------------

Best Regards,

Akio Takebe

Le Mercredi 16 Novembre 2005 22:36, Magenheimer, Dan (HP Labs Fort Collins) a 馗rit :

Magenheimer, Dan (HP Labs Fort Collins) wrote:

Once the xen4elilo patch got applied, this no longer worked for me. It may have been my pilot error.

The key descision is when to move to new elilo.efi for Xen to take advantage of xen.gz loading. We should all move forward together to get the feature -Fred

Perhaps. But there is not a patch on the table for support of compressed images yet, and there is one waiting for xlilo. Since 3.0 is imminent, let's decide on the xlilo patch that is waiting. If a compressed image patch is available and tested prior to 3.0 freeze, we can consider that one too.

Here is the change. I have only tested it with the old elilo on my RHEL 3.

Tristan.

Signed-off-by: Tristan Gingold <tris@bull.net>

-------------------------------text/plain-------------------- -----------