Re: [Xen-devel] [PATCH] docs, Add HowTo use QEMU upstream.

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

On Thu, 27 Oct 2011, Ian Campbell wrote:

> I suppose a bunch of this becomes obsolete when Stefano's patches to
> integrate SeaBIOS/qemu into the build land, but perhaps it is worth
> documenting the manual steps anyway?

It is at least more easier than trying to read the build system :). But
I will add a note about this.

> Is the plan to retire the wiki page?

I don't know, should we keep both? or just this text file? All I know,
it's easier to maintaine that file than the wiki page as we do not have
to worry about which revision of xen-unstable we use.

> I don't have much comment on the text other than spelling and some minor
> grammar.
>
> On Wed, 2011-10-26 at 17:55 +0100, Anthony PERARD wrote:
> > Signed-off-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
> >
> > ---
> >  docs/misc/qemu-upstream_howto_use_it.markdown |  122 
> > +++++++++++++++++++++++++
> >  1 files changed, 122 insertions(+), 0 deletions(-)
> >
> > diff --git a/docs/misc/qemu-upstream_howto_use_it.markdown 
> > b/docs/misc/qemu-upstream_howto_use_it.markdown
> > new file mode 100644
> > index 0000000..cdf920a
> > --- /dev/null
> > +++ b/docs/misc/qemu-upstream_howto_use_it.markdown
> > @@ -0,0 +1,122 @@
> > +Help to use QEMU (upstream version) with Xen
> > +============================================
> > +
> > +How to build it
> > +---------------
> > +
> > +### SeaBIOS
> > +
> > +This new device-model need a different bios, SeaBIOS. Clone the repository 
> > from:
>    The                   needs            BIOS
>
> It is usually "BIOS" not "bios", I think.

Yes, BIOS is not a word.

> > +
> > +  - git://git.qemu.org/seabios.git
> > +  - http://git.qemu.org/git/seabios.git
> > +
> > +Put the `.config` file in the appendix at the root of seabios.git and 
> > build SeaBIOS.
> > +
> > +In xen-unstable source tree, add the file `.config` with
> > +`SEABIOS_DIR = /path/to/seabios.git`.
> > +To build hvmloader with SeaBIOS, you propably need to `make -C 
> > tools/firmware
>                                         probably
>
> > +clean` first and then `make tools`, to use the new SEABIOS_DIR parameter.
> > +
> > +
> > +### QEMU
> > +
> > +Get QEMU upstream source from:
> > +
> > +  - git://xenbits.xensource.com/qemu-upstream-unstable.git
> > +  - http://xenbits.xensource.com/git-http/qemu-upstream-unstable.git
> > +
> > +To configure build QEMU upstream with Xen
> > +
> > +    ./configure --enable-xen --target-list=i386-softmmu 
> > --extra-cflags="-I$path_to_xen_source/tools/include 
> > -I$path_to_xen_source/tools/libxc -I$path_to_xen_source/tools/xenstore" 
> > --extra-ldflags="-L$path_to_xen_source/tools/libxc 
> > -L$path_to_xen_source/tools/xenstore"
> > +
>
> Perhaps wrap this somehow?
>
> Incidentally, would upstream accept a --xen-dir type option (or an
> argument to --enable-xen?) to which you could pass $path_to_xen_source
> and have it do all this automatically?
>
> Can you omit all that if you have installed Xen on the current host
> (i.e. pick all that up from /usr/{lib,include})?

Yes :), so the only way to build QEMU with a fresh Xen build is to
specifie the all path. I'm actually only specify the path to the dist
dir: --extra-cflags=-Ixen.git/dist/install/usr/include
--extra-ldflags=-Lxen.git/dist/install/usr/lib
but this propably does not work for some people because that have been
changed on the wiki page.

> > +You can also use other several options such as `--disable-kvm`.
> > +
> > +
> > +How to use QEMU upstream
> > +------------------------
> > +
> > +Only xl support QEMU upstream.
> > +
> > +To actually use it, add or change this in your VM configuration file:
> > +
> > +    device_model_version = 'qemu-xen'
> > +    device_model_override = '/path/to/qemu/i386-softmmu/qemu'
>
> This second one should become unnecessary (and unadvised) when Stefano's
> build integration patches hit.

Yes, as well the build of SeaBIOS and QEMU and everything a part from
device_model_version maybe.

-- 
Anthony PERARD

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