RE: Xen 3.0.0 released!

[Paul Dorman <paul.dorman@solnetsolutions.co.nz>]

[-- Attachment #1.1: Type: text/plain, Size: 2486 bytes --]

And then there's the linux-2.6-xen.hg no PTYs problem I've asked about
previously. Selecting Xen subarchitecture nukes 90% of the device
drivers section. Consequently I can't get a shell running on 2.6.14 domu
machines. I've asked about this before but no-one seems to have an
answer for me.

Paul

On Wed, 2005-12-07 at 21:32 +0000, 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)
>  
> > 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.
>  
> > 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.
> 
> > 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.
>  
> >    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. 
> 
> Ian
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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