[Pkg-xen-devel] Changes for 3.2

[Ralph Passgang]

Am Montag, 3. Dezember 2007 20:29:51 schrieb Bastian Blank:
> On Mon, Dec 03, 2007 at 06:46:21PM +0100, Ralph Passgang wrote:
> > Am Montag, 3. Dezember 2007 15:59:35 schrieb Bastian Blank:
> > > On Mon, Dec 03, 2007 at 03:21:55PM +0100, Ralph Passgang wrote:
> >
> > If I am not wrong, shype is just another term for acm.
>
> Hmm.

https://www.dfn-cert.de/events/ws/2007/dfncert-ws2007-f8.pdf
(interessting german presentation about shype/acm + vtpm)

> > why not also the vtpm stuff? I think providing the userspace parts
> > might be usefull.
>
> Well, it was not included in my proposals, bug I would not vote against.
>
> > 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.
>
> .22 was only available from Ubuntu which did not work for me at all.

I think I will try the ubuntu kernel. who knows what happens ;)

> > hmmm, you know something about the paravirt_ops in recent kernels? is
> > it useable already? maybe this is a better solution for the future?
>
> Upstream is currently working on full support.
>
> > > > 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?
>
> They use the qemu vnc support now.

hmmmm :)

> Bastian