From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Coretemp ERROR: Can't get value of subfeature
Date: Thu, 27 May 2010 08:56:08 +0000 [thread overview]
Message-ID: <20100527105608.276fc3dc@hyperion.delvare> (raw)
In-Reply-To: <AANLkTil33EQzUCcwbJT_VHMZKj1FPCwrTCkH28i3FcC5@mail.gmail.com>
Hi Huang,
On Thu, 27 May 2010 10:41:14 +0200, Dong Huang wrote:
> Hello everyone,
>
> i am a newbie here, want to check the temperature of my motherboard with
> lm_sensors, unfortunately i got error message as i run sensors. So I really
> need your help, thanks in advance.
>
> (...)
> *5. output of sensors-detect*
> Shutting down sensors:
>
> done
> # sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)
> # System: VMware, Inc. VMware Virtual Platform
> # Board: Intel Corporation 440BX Desktop Reference Platform
It makes no sense to run sensors or any _hardware_ monitoring
application on a _virtual_ machine. Hardware monitoring should be done
on the host system, not on the guests.
> (...)
> *3. The output of sensors: *
> coretemp-isa-0000
> Adapter: ISA adapter
> ERROR: Can't get value of subfeature temp1_input: Can't read
> Core 0: +0.0°C (high = +100.0°C, crit = +100.0°C)
I presume that VMware simply doesn't allow guest drivers to access CPU
MSR. Nothing we can do.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-05-27 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 8:41 [lm-sensors] Coretemp ERROR: Can't get value of subfeature Dong Huang
2010-05-27 8:56 ` Jean Delvare [this message]
2010-05-27 9:37 ` Jean Delvare
2012-08-14 19:37 ` [lm-sensors] Coretemp ERROR: Can't get value of subfeature temp1_input Guenter Roeck
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=20100527105608.276fc3dc@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.org \
/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.