On Monday 03 March 2008 01:20:09 pm you wrote:> Would the below steps work for you?
>
> Pull the src rpm;
>
> cp /boot/config-<SOMETHING-THAT-WORKS>.fc8xen .config; yes
"" | make
> oldconfig; grep XEN .config (see below) ; make.
>
> I have:
>
> CONFIG_XEN=y
> CONFIG_XEN_BLKDEV_FRONTEND=m
> CONFIG_XEN_NETDEV_FRONTEND=m
> CONFIG_XEN_KBDDEV_FRONTEND=y
> CONFIG_HVC_XEN=y
> CONFIG_XEN_FBDEV_FRONTEND=y
>
> fbdev and kbddev aren''t upstream yet, so you won''t see
these.
>
> pushd
> make modules_install
> cd /lib/modules/2.6.25-rc2/kernel/drivers/block
> ln -sf xen-blkfront.ko xenblk.ko
> cd ../net && ln -sf xen-netfront.ko xennet.ko
> popd
> install kernel 2.6.25-rc2 vmlinux System.map
>
>
> IMHO, you are requested to test this with the rawhide version. 2.6.23
> may or may not work.
Ok, I''ve finally gotten to the ''it boots and panics''
stage :-) I''m using
kernel-2.6.24.3-12.fc8.src.rpm now.
It took me awhile to notice some things, like a couple of those config lines
above are modules, and just setting CONFIG_XEN only sets the other options
to ''y''. Also, I was using the wrong vmlinux file, from
arch/$Arch/boot/compressed, instead of the top level vmlinux.
Trying to use a xen config doesn''t really do anything. Running it thru
''make
oldconfig'' just ignores any options not used by the bare metal kernel.
I incorporated the module soft links into the kernel .spec file, added a a
couple of lines to copy the correct vmlinux, and put it in the macro for the
filelist kept by rpmbuild. I also added ''nomce'' to my extra=
parm
(besides ''console=hvc0'') for an unrelated, non-fatal error
that has been seen
in this list before:
[887] > tail /var/log/xen/console/hypervisor.log
(XEN) traps.c:1698:d13 Domain attempted WRMSR 00000411 from 00000000:00000011
to 00000000:00000000.
Now, the tail end of my dmesg is:
XENBUS: Device with no driver: device/console/0
Magic number: 1:252:3141
Freeing unused kernel memory: 300k freed
Write protecting the kernel read-only data: 905k
BUG: unable to handle kernel paging request at virtual address c152e074
printing eip: c0406d6e *pdpt = 0000000060aa7001
Oops: 0003 [#1] SMP
Modules linked in:
Pid: 1, comm: init Not tainted (2.6.24.3-12.fc8PAE #4)
EIP: 0061:[<c0406d6e>] EFLAGS: 00010286 CPU: 0
EIP is at arch_add_exec_range+0x56/0x5e
EAX: 00cffb00 EBX: 0000ffff ECX: dec39000 EDX: c152e000
ESI: df326720 EDI: 00000000 EBP: 00000000 ESP: dfc23d78
DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: e021
Process init (pid: 1, ti=dfc22000 task=dfc20000 task.ti=dfc22000)
Stack: 00000000 c04b65dc 00000080 dfc686c0 00000000 dfc23f38 df326600 dfc68780
df326700 00000003 dfc68840 c049e1a7 dfc20000 c0442f95 dec372e0 00000002
00000080 00000000 c04d8b1e c048d931 dfc04c00 df326600 df8112b0 00000001
Call Trace:
[<c04b65dc>] load_elf_binary+0x4da/0x1515
[<c049e1a7>] dput+0x30/0xd7
[<c0442f95>] autoremove_wake_function+0x0/0x35
[<c04d8b1e>] security_dentry_open+0xc/0xd
[<c048d931>] __dentry_open+0xf1/0x185
[<c04de7fb>] selinux_bprm_set_security+0x20/0x183
[<c048da3a>] nameidata_to_filp+0x24/0x33
[<c04925a8>] search_binary_handler+0x91/0x1d4
[<c04b59c1>] load_script+0x191/0x1a4
[<c047bf06>] get_user_pages+0x350/0x3d3
[<c042921e>] __might_sleep+0x21/0xd3
[<c04925a8>] search_binary_handler+0x91/0x1d4
[<c04937d2>] do_execve+0x130/0x19b
[<c04061ae>] sys_execve+0x31/0x51
[<c040818e>] syscall_call+0x7/0xb
[<c04900d8>] get_empty_filp+0x86/0x152
[<c040bf58>] kernel_execve+0x14/0x18
[<c0401082>] init_post+0x6e/0xdc
[<c07606b7>] kernel_init+0x356/0x360
[<c042fa70>] schedule_tail+0x16/0x4d
[<c040804a>] ret_from_fork+0x6/0x1c
[<c0408197>] syscall_exit+0x5/0x1b
[<c0760361>] kernel_init+0x0/0x360
[<c0760361>] kernel_init+0x0/0x360
[<c0408dbf>] kernel_thread_helper+0x7/0x10
======================Code: 81 6c 01 00 00 64 a1 00 40 7a c0 3b 88 74 01 00 00
75 1e 64 a1 08 40 7a
c0 ba 00 50 7a c0 03 14 85 00 5f 75 c0 8b 81 6c 01 00 00 <89> 42 74 89 5a
70
5b c3 53 89 c1 3b 90 70 01 00 00 75 6f 8b 10
EIP: [<c0406d6e>] arch_add_exec_range+0x56/0x5e SS:ESP e021:dfc23d78
---[ end trace 36dd4c40a31b61f1 ]---
Kernel panic - not syncing: Attempted to kill init!
It should be closer to:
XENBUS: Device with no driver: device/console/0
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Freeing unused kernel memory: 188k freed
Write protecting the kernel read-only data: 795k
USB Universal Host Controller Interface driver v3.0
xen-vbd: registered block device major 202
xvda: xvda1 xvda2
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised:
dm-devel@redhat.com
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
audit(1205025741.579:2): policy loaded auid=4294967295
Anybody know where to go from here? Thanx.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users