From: Rich Persaud <rich.p@xensource.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Xen compatibility interface numbering
Date: Mon, 07 Mar 2005 05:43:56 -0500 [thread overview]
Message-ID: <422C306C.8080209@xensource.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3494@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>>2. Does Xen/dom0/Xend perform version checking on domUs?
>>
>>
>
>Yes.
>
>
Out of curiosity, what happens in dom0 if a domU spoofs its interface
version?
>>3. Can a binary Xen kernel be queried for its compatibility version?
>>
>>
>
>There's a dom0 op that queries the interface version.
>
>
Is this accessible to the management tools, i.e. can Xend report the
dom0 interface version to userland?
If I have a domU binary kernel image (vmlinuz), is there any way to
query its interface version (even a search string for strings+grep)?
>>4. How frequently does the Xen compatibility interface change?
>>
>>
>
>Only when there's a major release number change.
>
>
Major = 1.x, 2.x, 3.x, not 2.0.4 to 2.0.5-pre, right? So the Xen
interface is compatible between 2.0.4 and the testing/unstable tree.
Rich
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-07 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 7:50 Xen compatibility interface numbering Ian Pratt
2005-03-07 10:43 ` Rich Persaud [this message]
2005-03-07 17:39 ` John Kelly
2005-03-07 17:50 ` Grzegorz Milos
2005-03-08 0:46 ` Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2005-03-07 16:15 Ian Pratt
2005-03-07 0:26 Rich Persaud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=422C306C.8080209@xensource.com \
--to=rich.p@xensource.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.