From: Ralph Passgang <ralph@debianbase.de>
To: xen-devel@lists.xensource.com
Cc: James Harper <james.harper@bendigoit.com.au>
Subject: Re: Xen 3.1.2 for Debian?
Date: Thu, 22 Nov 2007 13:53:18 +0100 [thread overview]
Message-ID: <200711221353.19077.ralph@debianbase.de> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0131A0DC@trantor>
Hi James,
I made my own packages for 3.1.2, which are quite close to the debian
pkg-xen version (I am part of that team, but not very active at the
moment).
There are only some very small differences, espacially I numbered my
packages in a diffrent style then debian does, because I want to have the
full xen version in the pkg-name.
My packages are running on two productive machines since one week without
any problems at all. On one machine Xen 3.0.3 made serious trouble, but
3.1.2 fixed them, so 3.1.2 seems to be quite stable to me.
My packages are available for the following debian distributions and
architectures:
i386: etch, lenny, sid
amd64: only etch (because I have no automatic build system for amd64)
Just add these lines to your /etc/apt/sources.list:
deb http://packages.debianbase.de/<distro>/<arch>/xen3.1 ./
deb-src http://packages.debianbase.de/sources/xen3.1 ./
So for amd64 and etch this would be the correct line:
deb http://packages.debianbase.de/etch/amd64/xen3.1 ./
There is still one bug open within my packages (and maybe even in the orig
pkg-xen packages, haven't checked). The hvmloader stuff isn't found when a
symlink from /usr/lib/xen to /usr/lib/xen-3.1.2-1 is missing. So set this
symlink to be on the safe side.
But please be aware, that the 2.6.18-5-xen-amd64/686 kernel from debian is
build with xen 3.0.x patches (actually taken from fedora), which are
working with xen 3.1, but you will not be able to use 32bit domUs on 64Bit
Dom0/Hypervisor. If you need that too, then you need a newer kernel with
xen 3.1.x patches.
Hope this helps ;)
-- Ralph
Am Dienstag, 20. November 2007 02:23:03 schrieb James Harper:
> Has anyone put any 3.1.2 packages together for Debian yet? I've been
> spoilt by having them for just about every other recent release, and
> Debian does things a little differently (eg allows you to have several
> versions installed simultaneously and automatically detect which Dom0
> runtime stuff to use).
>
> Thanks
>
> James
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-11-22 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 1:23 Xen 3.1.2 for Debian? James Harper
2007-11-20 22:02 ` Markus Schuster
2007-11-20 22:29 ` James Harper
2007-11-22 12:53 ` Ralph Passgang [this message]
2007-11-26 14:41 ` Otavio Salvador
2007-11-27 19:42 ` Ralph Passgang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200711221353.19077.ralph@debianbase.de \
--to=ralph@debianbase.de \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.