All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Shell test for pv vs hvm (vs dom0)
Date: Fri, 22 Feb 2008 13:58:14 -0700	[thread overview]
Message-ID: <20080222135814906.00000003172@djm-pc> (raw)

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

Is there an "officially sanctioned" method for a shell script to
test whether it is running on a native OS vs pv OS vs hvm OS
(and possibly also dom0 OS)?

I know there are lots of different ways to determine this but
am wondering if any one will work across all (recent and future)
implementations of Xen and across multiple (at least Linux-based)
distros.

If not, perhaps there could/should be a C/python tool in the Xen tree
that does this?

===================================
If Xen could save time in a bottle / then clocks wouldn't virtually skew /
It would save every tick / for VMs that aren't quick /
and Xen then would send them anew
(with apologies to the late great Jim Croce)

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

             reply	other threads:[~2008-02-22 20:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 20:58 Dan Magenheimer [this message]
2008-02-22 21:18 ` Shell test for pv vs hvm (vs dom0) Keir Fraser
2008-02-22 22:38   ` Dan Magenheimer
2008-02-23  5:36     ` pradeep singh rautela
2008-02-23  8:18     ` Keir Fraser
2008-02-23 14:26       ` Stephan Seitz
2008-02-23 14:35         ` Keir Fraser
2008-02-23 16:48           ` Dan Magenheimer
2008-02-25 12:58       ` Alex Williamson
2008-02-25 13:40         ` Keir Fraser
2008-02-25 13:45           ` Daniel P. Berrange
2008-02-25 15:38             ` Dan Magenheimer

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=20080222135814906.00000003172@djm-pc \
    --to=dan.magenheimer@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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.