This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] Xen 3.0.0 released!

On Wed, 7 Dec 2005, Ian Pratt wrote:

> Do you have 2.6.14? You could build based on linux-2.6-xen.hg, but this
> hasn't has s much testing (we know of at least on issue on x86_64)

We do, but the new way I'll be packaging the source doesn't require any kernel
source in debian.  Whatever xen ships, will be in the xen deb.

I'd prefer to only use real releases; if I have multiple xen versions, then it
becomples complex with file overlaps and dependencies and parallel installs.

And, even then, it's not hard to see a point in the future where a new linux
kernel comes out, but xen-stable(3.0) doesn't upgrade to it, and then the
source I do require gets removed.  My new way gets rid of all of these
problems, and makes the local admin get the kernel source his own way.

> > 2) vif-route.sh is buggy; it doesn't handle the case where
> > multiple adapters
> >    exist.  So, dom0_ip(and the functions it calls) ends up
> > returning 2 ip
> >    addresses, which makes ifconfig complain.
> >
> >    I've got a fix hot-patched on our deployed server, I'll be
> > sending that
> >    soon.
> Please post it, thanks.

In vif-common.sh, ip_of should be this:
function ip_of()
  ip addr show "$1" | awk "/^.*inet.*$1\$/{print \$2}" | sed 's,/.*,,'

Sorry it's not in diff form, I just pasted what is on our production server.

> > 3) It appeared that when I tried the final 3.0.0 release,
> > that xenstored was
> >    very sick.  I had a previous(20051116 snapshot) installed,
> > and the tdb file
> >    was corrupted(sorta).  xenstore-list / shows to local
> > paths, but no vm nor
> >    tools.  Removing the file 'fixed' this.  I'm not certain
> > exactly what
> >    happend, tho.
> It's possible that the install scripts should delete the database when
> performing an upgrade. I don't think there have been any format changes
> in a while, though.

Well, not delete.  Maybe dump to a text form, then reimport.

> > 5) I see it's not possible to have both a xen microkernel
> > that supports both
> >    pae and non-pae.  For individuals who are compiling
> > themselves, that's
> >    fine; they can select which they want.
> Yep, no real way round that. Most users are already trained to this
> thanks to it being a compile time option in Linux.

That's true, but the xen hypervisor is not compiled by users; it's built once,
and installed thru a deb.

> >    Also, what other options are available, that would require multiple
> >    compiles?  Also, I don't see a concise list of what config
> > options I can
> >    tweak for xen itself; the documentation is a bit poor in
> > that regard(pae
> >    isn't even mentioned in the documentation; you have to
> > read a separate
> >    README).
> Having a debug/verbose build of xen is sometimes handy for debugging
> things, but since debug builds are deliberatly combatitive its probably
> not a good idea for production.

Then that sounds like a candidate for xen-debug.deb.

Xen-devel mailing list