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

[Michael Gregg <mgregg@xxxxxxxxxxxxxxxx>]

The trick for me was to be sure that I included ARCH=xen in EVERY make
line when building the kernel.

make ARCH=xen menuconfig
make ARCH=xen modules
make ARCH=xen -j 6

etc.

You may need to start over again with your original config file AND to
run a make mrproper if you have not been using ARCH=xen everywhere.



On Thu, 2005-09-15 at 12:41 +0200, Markus Schuster wrote:
> Marcus Brown schrieb:
> > How about this, then?
> > (for Xen 2.0.7)
> > [..]
> 
> That's exactly what I have standing on the top of my two config files.
> I've also set CONFIG_XEN_NETDEV_BACKEND, but that's set in the working
> and in the non-working config, so I don't think it is the problem.
> 
> > I believe PRIVILEGED_GUEST and PHYSDEV_ACCESS to be the
> > 'magical' options.
> 
> I've set both options in both of my config files. One works, the other
> not...
> Maybe you want to have a look at my two config files (URL is in my first
> message).
> 
> 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