[Pkg-xen-devel] Of historical interest only [u]

[Julien Danjou]

On Thu, Feb 16, 2006 at 10:49:54AM +0100, Ralph Passgang wrote:
> Not all Debian and/or xen beginers are able to compile their own kernel and 
> even if they are, if they don't check the right options they probably have to 
> do it over and over again which costs a lot of time. I would like to help the 
> user with kernel images, but of course this has to be an option, if someone 
> wants his own kernel he always can use the kernel-patch-xen package and 
> create his own kernel.

I think it's possible, on the other side, to explain how to compile a
Xen kernel from the current kernel package in Debian, maybe in a
automagically way.
(means: applying patch, using config file from debian's kernel, etc)

> but also not very easy to solve I guess... What is the right direction 
> anyways? disabling tls by moving the folder (but having problems with updates 
> of libc6 then) or using a special libc6 package which is compiled with some 
> special flags? (see: http://wiki.xensource.com/xenwiki/DebianSarge)
> 
> this could get quite difficult I think.

Right, not moving away the /lib/tls does not prevent Xen to works.
So my opinion is: just leave it, and alert our user on install that they
*really* should move this directory away.
But trying to do this by the package, will probably break the policy
rules.

Managing another libc6 should be ok, maybe we could do something with
glibc maintainers ?

> the problem I see is, that update-grub only makes sense if we also provide 
> kernel images, otherweise what kernel image should be in the menu.lst?

update-grub manage self-compiled linux kernel images.
So it could manage self-compiled linux xen kernel images too.

> in xen3 the default behaviour is to suspend/save the running domains before 
> shutdown and to restore them after the reboot. This is configured 
> in /etc/sysconfig/xendomains (I don't like the location for this config file, 
> but it's hardcoded in xen source). For example you can also have your domUs 
> migrated before shutdown and do other things.

We will have to patch the source, /etc/sysconfig really sucks.

> In this config file there is also an option to tell xendomains how long to 
> wait before skipping an operation (xm shutdown, xm migrate, xm save, ...) if 
> nothing happens anymore. I think this solves the problems you experienced in 
> xen2.

Good point.

-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20060216/80a0cc56/attachment-0001.pgp