[Xen-devel] single kernel for xen0 & xenU

["James Harper" <JamesH@xxxxxxxxxxxxxxxx>]

I'm sure someone asked in this list if they can run the same kernel in
xen0 and xenU and that the answer was yes, but now I can't find it - did
I imagine it?

Presumably all I need to do is compile the kernel with frontend and
backend drivers and xen will sort the rest out itself right? What
disadvantages are there to this approach apart from kernel bloat? Are
there any optimisations made in the kernel compile if it is front- or
back-end?

In the testing phase, especially where the xen api is changing a lot,
one of the things I find hard is when I build a new kernel, I also need
to recompile iscsi etc. Having to only do this once would make it
easier.

Which brings up another point, how often these days is xen changing such
that a xenU domain won't migrate between domains if one is todays build
and another is yesterdays build?

Finally, is anyone working on a shared memory filesystem that can be
exported by xen0 and read by xenU, and would be available very early on
in the boot cycle? I ask because updating modules is one of the hard
things to do in xenU on boot when the xenU filesystem isn't readily
mountable by xen0.

My workaround is to put all the xenU modules in the initrd and copy them
out of that on boot into the live filesystem before they are required.
Or at least it will be once I get it going. Is anyone interested in a
quick howto on that assuming it works well?

Thanks

James



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel