Re: [Xen-devel] RAMDISK: Image too big

Quoting Ian Pratt
> > > This is pretty odd. Are you able to build from source?
> >
> > Yes.
>
> Build from src by adding Linux-2.4 to the KERNELS line in the top-level
> Makefile, then 'make DEBUG=y world'.
>
> Next, add an early printk hack to linux 2.4 by edditing
> linux-2.4.29-xen0/kernel/printk.c to add the following call after the
> va_end:
>
>  HYPERVISOR_console_io(CONSOLEIO_write, sizeof(printk_buf), printk_buf)
>
> Then, 'make dist'.
>
> When you boot the kernel you should see kernel output much earlier on.

Well. I don't see more. I hope it's not due to that I changed printk before 
"make world" and not before "make dist".

I haven't seen anything on the serial console either.

I think I'd rather go on with the 2.6 kernel. Or any more hints?
-- 
Marcus


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

[Xen-devel] problems with console in domU if physdev access enabled, Maurice Meeden

Next by Date:

Re: [Xen-devel] severe security issue on dom0/xend/xm/non-root users, Tommi Virtanen

Previous by Thread:

RE: [Xen-devel] RAMDISK: Image too big, Ian Pratt

Next by Thread:

RE: [Xen-devel] RAMDISK: Image too big, Ian Pratt

Indexes:

[Date] [Thread] [Top] [All Lists]