This is my first time posting to this mailing list, so please let me know if I'm posting to the wrong place or otherwise not following the protocol.

I am trying to boot up a custom paravirtualized kernel in Xen domU. I have been following this thread from the same mailing list that has been extremely helpful, but I still get an error:
http://lists.xensource.com/archives/html/xen-users/2007-10/msg00378.html

My setup is Fedora Core 8 installation of Xen and dom0, which includes xen-3.1.0-13 and 2.6.21-2950.fc8xen Fedora kernel. I can create a Fedora Core 8 domU using xm create. So at this point I'm just trying to compile the vanilla kernel with paravirtual extensions to replace Fedora's kernel in the config file.

My procedure is as follows:
- download vanilla kernel 2.6.23 from kernel.org
- make defconfig
- edit .config and set all "xen" and "paravirt"setting to yes (config file attached)
- make vmlinux
- gzip vmlinux (... this step by following advice in the above mentioned thread)
- cp vmlinux.gz /boot/vmlinuz
- Then try to boot the kernel with the attached config file

At this point, an error occurs and domain-builder-ng.log reflects the following entries:
...
xc_dom_parse_elf_kernel: xen-3.0-x86_32: 0xc0100000 -> 0xc06d3000
...
xc_dom_compat_check: supported guest type: xen-3.0-x86_32p
xc_dom_compat_check: supported guest type: hvm-3.0-x86_32
xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p
xc_dom_boot.c:108: panic: xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry


When I boot the image that works (compiled from vanilla kernel 2.6.23 by Mark and attached in the abovementioned thread), it indeed boots and instead the log has the entries one would expect:
...
xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0xc0100000 -> 0xc0420000
...
x86_compat: guest xen-3.0-x86_32p, address size 32
...
xc_dom_compat_check: supported guest type: xen-3.0-x86_32p <= matches
xc_dom_compat_check: supported guest type: hvm-3.0-x86_32
xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p

Any idea what I am doing wrong?


One curious thing I've noticed is when I look at elf notes in my broken image, they look a bit different from the image that works. Don't know if that matters:

$ readelf -n marks_vmlinux

Notes at offset 0x002cd2b8 with length 0x000000e8:
Owner Data size Description
Xen 0x00000006 Unknown note type: (0x00000006)
Xen 0x00000004 Unknown note type: (0x00000007)
Xen 0x00000008 Unknown note type: (0x00000005)
Xen 0x00000004 Unknown note type: (0x00000003)
Xen 0x00000004 NT_VERSION (version)
Xen 0x00000004 NT_ARCH (architecture)
Xen 0x0000002a Unknown note type: (0x0000000a)
Xen 0x00000004 Unknown note type: (0x00000009)
Xen 0x00000008 Unknown note type: (0x00000008)

$ readelf -n my_vmlinux

Notes at offset 0x012d1330 with length 0x0000010c:
Owner Data size Description
Xen 0x00000006 Unknown note type: (0x00000006)
Xen 0x00000004 Unknown note type: (0x00000007)
Xen 0x00000008 Unknown note type: (0x00000005)
Xen 0x00000004 Unknown note type: (0x00000003)
Xen 0x00000004 NT_VERSION (version)
Xen 0x00000004 NT_ARCH (architecture)
Xen 0x0000002a Unknown note type: (0x0000000a)
Xen 0x00000003 Unknown note type: (0x00000009) <= this Xen field looks different
Xen 0x00000008 Unknown note type: (0x00000008)
GNU 0x00000014 NT_GNU_BUILD_ID (unique build ID bitstring)

Let me know if you have any thoughts or if there is any additional info I can provide.

Thanks,
Tom

Attachment: xen.cfg
Description: Binary data

Attachment: domain-builder-ng.log.bad
Description: Binary data

Attachment: domain-builder-ng.log.good
Description: Binary data

Attachment: .config
Description: Binary data

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

[More with this subject...]