From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Fireinfo update [testers needed]
Date: Wed, 04 Sep 2013 15:09:10 +0200 [thread overview]
Message-ID: <1378300150.21541.94.camel@rice-oxley.tremer.info> (raw)
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
tl;dr The hypervisor detection code has been updated and we need testers
to confirm that the new code still finds the right hypervisor.
Instructions on how to test are to be found below.
----
Hi,
we always felt that the hypervisor detection in fireinfo was not very
reliable and sometimes detected the wrong hypervisor. So I rewrote the
detection code in order to get better results.
If you just look at the data, I don't really believe that more people
are running IPFire inside VirtualBox than in Microsoft's Hyper-V.
http://fireinfo.ipfire.org/stats/virtual
Before we release the code, I need you people to check if this code is
now actually better and correctly identifies all known hypervisors.
Please help me with that and download the attached tarball and extract
it on your IPFire x86 system:
tar xvfz fireinfo-2.1.7-testing-for-ipfire.tar.gz -C /
Then run sendprofile --dump and search for the hypervisor, that has
been detected:
...
"hypervisor": {
"vendor": "KVM"
},
...
Please install this on your testing machines in a virtualized
environment and get back to me if your hypervisor could be correctly
identified or not.
Best,
-Michael
[-- Attachment #2: fireinfo-2.1.7-testing-for-ipfire.tar.gz --]
[-- Type: application/x-compressed-tar, Size: 20671 bytes --]
next reply other threads:[~2013-09-04 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 13:09 Michael Tremer [this message]
2013-09-09 14:23 ` Robertm
2013-09-09 18:50 ` Robertm
2013-09-09 20:23 ` Michael Tremer
2013-09-09 23:10 ` R. W. Rodolico
2013-09-09 23:29 ` R. W. Rodolico
2013-09-10 8:20 ` Michael Tremer
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=1378300150.21541.94.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox