Mailing List Archive

On Fri, Dec 16, 2005 at 04:57:14PM +0100, Jan Beulich wrote:
> What is the recommended way to find out which hypervisor version matches
> (a given snapshot of) the merge tree? I had hoped that interfaces
> wouldn't change anmore at this point in time, but I just saw that there
> was another addition to event channel as well as dom0 ops...

I include the xen-unstable changeset number in the comments of
changesets from xen-unstable. You should look for the latest
changeset with such a line:
hg -v history | sed -n '/^linux-2.6-xen-sparse cset:/ {p;q}'

Have you identified which changeset broke compatibility? I'm always
watching for such changesets and it might be possible to add some
backwards compatibility without too much ugliness. At least the
hypervisor/guest and xenbus/xenstore/guest interface should be
compatible within the xen 3.0 series...

christian


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

On 17 Dec 2005, at 00:34, Christian Limpach wrote:

> On Fri, Dec 16, 2005 at 04:57:14PM +0100, Jan Beulich wrote:
>> What is the recommended way to find out which hypervisor version
>> matches
>> (a given snapshot of) the merge tree? I had hoped that interfaces
>> wouldn't change anmore at this point in time, but I just saw that
>> there
>> was another addition to event channel as well as dom0 ops...
>
> I include the xen-unstable changeset number in the comments of
> changesets from xen-unstable. You should look for the latest
> changeset with such a line:
> hg -v history | sed -n '/^linux-2.6-xen-sparse cset:/ {p;q}'
>
> Have you identified which changeset broke compatibility? I'm always
> watching for such changesets and it might be possible to add some
> backwards compatibility without too much ugliness. At least the
> hypervisor/guest and xenbus/xenstore/guest interface should be
> compatible within the xen 3.0 series...
>
> christian

The control interfaces (dom0) are not frozen. We'll be adding to and
changing that interface as the control tools evolve. The event-channel
change is an extension of the interface, which is entirely backwards
compatible with the 3.0.0 release.

-- Keir



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