Re: [Xen-users] Re: What's the magic to compile a unified dom0 and domU kernel image?

[Marcus Brown <marcusbrutus@xxxxxxxxxxxxxxxx>]

Hi Markus,

How about this, then?
(for Xen 2.0.7)

CONFIG_XEN=y
CONFIG_ARCH_XEN=y
CONFIG_NO_IDLE_HZ=y

#
# XEN
#
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PHYSDEV_ACCESS=y
CONFIG_XEN_BLKDEV_BACKEND=y
# CONFIG_XEN_NETDEV_BACKEND is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER is not set
CONFIG_XEN_WRITABLE_PAGETABLES=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_X86=y
# CONFIG_X86_64 is not set
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y

Which is the start of the config I use for a Bluetooth Proxy Server
(for an ipaq)

I believe PRIVILEGED_GUEST and PHYSDEV_ACCESS to be the
'magical' options.

Marcus

Markus Schuster wrote:
> Marcus Brown schrieb:
> 
>>You could use a dom0 kernel for both dom0 and domU.
> 
> 
> Yes, that's actually what I want to to. But the default XEN dom0 config
> includes much too less modules to be of any use for me. And the XEN
> specific options (CONFIG_XEN*) are the same in my two configs and the
> default XEN dom0 config.
> 
> 
>>If compiling your own 'unified' kernel, make sure you
>>make ARCH=xen menuconfig
>>make ARCH=xen install (or whatever)
> 
> 
> That's more or less what I did to get a kernel. I did:
> # ARCH=XEN make clean
> # ARCH=XEN make menuconfig
> # ARCH=XEN make vmlinuz
> # ARCH=XEN make modules
> # ARCH=XEN make modules_install
> 
> In general I know how to compile a XEN kernel, but there must be some
> difference between my two configs that I don't realize to be important
> for XEN.
> 
> Greetings,
> Markus
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


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