From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
Stephan Seitz <s.seitz@netz-haut.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: Shell test for pv vs hvm (vs dom0)
Date: Sat, 23 Feb 2008 09:48:19 -0700 [thread overview]
Message-ID: <20080223094819656.00000003172@djm-pc> (raw)
In-Reply-To: <C3E5DFB3.1446F%Keir.Fraser@cl.cam.ac.uk>
Perhaps there's something in sysfs or proc somewhere that
could discern between HVM and native?
> > So a HVM Guest would ask "What hardware am I running on?"
Interestingly, I just ran across a place in 2.6.18-based guests
(e.g. RHEL5) in the timer code where a test is made whether
an Intel or AMD "box" is being booted to decide whether
or not to trust that TSC will be syncrhonized across
multiple cpus. Obviously this test is invalid for virtual
machines (though in this case, it is probably correct
"most" of the time).
> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk]
> Sent: Saturday, February 23, 2008 7:36 AM
> To: Stephan Seitz
> Cc: dan.magenheimer@oracle.com; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] Shell test for pv vs hvm (vs dom0)
>
>
> There's already HVM strings in SMBIOS and ACPI tables, but they're not
> particularly accessible from shell scripts in a generic way.
>
> -- Keir
>
>
> On 23/2/08 14:26, "Stephan Seitz" <s.seitz@netz-haut.de> wrote:
>
> > Could it be possible to define some bios magic for
> "hardware vendor"?
> > So a HVM Guest would ask "What hardware am I running on?"
> >
> > Just a thought...
> >
> > Keir Fraser schrieb:
> >> There's no general way to discriminate between HVM and
> native from a shell
> >> script. You might discriminate between HVM and PV on Linux
> by looking for
> >> /sys/hypervisor or /proc/xen.
> >>
> >> -- Keir
> >>
> >> On 22/2/08 22:38, "Dan Magenheimer"
> <dan.magenheimer@oracle.com> wrote:
> >>
> >>> Thanks for pointing this tool out! Looks useful.
> >>>
> >>> Unfortunately, for it to be broadly useful, it would have
> >>> to ship with all distros as compiling it "on demand" on
> >>> the guest is often not an option.
> >
> >
>
>
>
next prev parent reply other threads:[~2008-02-23 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 20:58 Shell test for pv vs hvm (vs dom0) Dan Magenheimer
2008-02-22 21:18 ` 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 [this message]
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=20080223094819656.00000003172@djm-pc \
--to=dan.magenheimer@oracle.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=s.seitz@netz-haut.de \
--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.