The current stable (3.1.2) version of Xen has a lot of bugs, which get fixed in Xen-Unstable but it takes way to long until they get backported to the 'stable' branch. I would like to request an ebuild that builds the mecury version of Xen-Unstable. Reproducible: Always
Do you have an example of a bug that is in 3.1.2 but fixed in unstable that is causing problems for you? I don't really have time to keep a xen-unstable ebuild up to date but some bugs may be fixable in 3.1.2 without too much pain.
My biggest problem is the shutdown function in XenAPI that is broken in 3.1.2. http://marc.info/?l=xen-devel&m=119574772510556&w=2
It seems today 3.2.0-rc1 is released. Probably better to put that one in portage and see if it is fixed.
...and fixed in 3.1.3
http://bugzilla.xensource.com/bugzilla/attachment.cgi?id=704&action=view Fix for 3.1.2.
To extract your own source tarball: # hg clone http://xenbits.xensource.com/xen-3.2-testing.hg # cd xen-3.2-testing.hg # hg archive -t tgz -r RELEASE-3.2.0 ../xen-3.2.0.tar.gz And we bump straight on to 3.2 :)
There's an actual tarball though: http://bits.xensource.com/oss-xen/release/3.2.0/xen-3.2.0.tar.gz
Beware that de default bridge change name to eth0. Your netweork setup might be broken by this.
3.1.3 has also been tagged just a few days ago...
I added 3.1.3 to portage yesterday, now I just need to do 3.2.0...
well, the initially requested version is in the tree for quite some time... time for RESOLVED FIXED, no?!
(In reply to comment #11) > well, the initially requested version is in the tree for quite some time... > time for RESOLVED FIXED, no?! Lets bump it to 3.3... to many problems in 3.2.1 anyway!
already working on that
Before I forget; Could you do an extensive test if GCC4 is supported? Otherwise I urge you to explicitly do some beeps/masking if the package is compiled with an incompatible compiler. From my experience on Xeon/AMD64X2 with GCC4 it was a kernel and userland no-go. And I needed to revert back for Xen to 3.4.6.
Stefan, I've bumped to Xen 3.3. It compiles and works fine in my testing setups with GCC 4.3. Prior versions have worked fine too with GCC 4.1. Please open new bugs if you experience bugs with that compiler, and include full version information and what breaks. I'm going to close this bug, looking forward to new bug reports when new versions are released.
(In reply to comment #15) > Stefan, I've bumped to Xen 3.3. Good work :) Thanks for the effort you put into it. > It compiles and works fine in my testing > setups with GCC 4.3. Prior versions have worked fine too with GCC 4.1. Please > open new > bugs if you experience bugs with that compiler, and include full version > information and what breaks. The basic setup would already be the 2.6.21 kernel compiled with GCC4.3 to produce a direct crash at boot. So I'll do a 'I feel lucky' but I expect this is going to cost me many hours to get right again. > I'm going to close this bug, looking forward to new bug reports when new > versions are released. Ok. Will open something new and try to produce some screenshots if I can get it to break.
If your hardware allows you to, please use the 2.6.18 kernel. 2.6.21 is hardly up for compilation with GCC 4.3 (for instance bug 213811), only 2.6.18 is kept up-to-date at the moment.
(In reply to comment #17) > If your hardware allows you to, please use the 2.6.18 kernel. 2.6.21 is hardly > up for compilation with GCC 4.3 (for instance bug 213811), only 2.6.18 is kept > up-to-date at the moment. Is the Gentoo kernel any different than the upstream Xen kernel? Because I have tried that .18, but my main problem is the Dell ethernet stuff is in from .19, that takes care the interfaces are not swapped, if this is backported I can go back to .18 without a problem. (So I did not try .18 lately...)
Our Xen kernel are based on the xensource.com version, but we ship very few Gentoo specific changes, and a lot of security updates. See http://dev.gentoo.org/~marineam/xen-sources/broken-out/2.6.18-12/00000_README for a list of current patches. If you can find your driver as a backport in the following repository, please open a new bug and we can include it in our kernel sources: svn://svn.debian.org/kernel/releases/linux-2.6/2.6.18.dfsg.1-22etch2/debian/patches
