[Pkg-xen-devel] Changes for 3.2

Ralph Passgang ralph at debianbase.de
Mon Dec 3 17:46:21 UTC 2007

Am Montag, 3. Dezember 2007 15:59:35 schrieb Bastian Blank:
> On Mon, Dec 03, 2007 at 03:21:55PM +0100, Ralph Passgang wrote:
> > > > * Include the security tools.
> >
> > do you mean sHype and vtpm? I would really like seeing that in the
> > debian packages.
> No, the tools for the two security modules: acm and flask.

If I am not wrong, shype is just another term for acm.

why not also the vtpm stuff? I think providing the userspace parts might be 

> > I think a dom0 kernel compiled against a recent xen version is needed
> > for that. at least the debian 2.6.18-5-xen kernels aren't new enough
> > for that.
> Yep.
> > do you have plans for a new -xen kernel too?
> I have a 3.1 based .18 kernels, can't be pushed into stable.

me has those kernels, too. And that these updated kernels can't be pushed 
into stable is one thing, but what about trying to have .22-xen kernels in 
unstable (for lenny). I think some other distros have such kernels, because 
they can't keep stuck with .18 but at the same time want xen support for 
their customers.

hmmm, you know something about the paravirt_ops in recent kernels? is it 
useable already? maybe this is a better solution for the future?

> > we should think about including vfb/xenfb. might be useful for some
> > people.
> It is included in 3.1, deprecated in 3.2.

really? why that, it was a quite new feature, so why it's already 
deprecated? is there some alternative?


> Bastian

More information about the Pkg-xen-devel mailing list