From: Luis Aranguren <pizzaman@hotmail.com>
To: kerolasa@iki.fi
Cc: util-linux@vger.kernel.org
Subject: Re: Hypervisor & Virtualization lscpu test fail
Date: Mon, 11 Feb 2013 11:44:55 +1000 [thread overview]
Message-ID: <BLU0-SMTP144C815AE93C94E539C372CD50A0@phx.gbl> (raw)
In-Reply-To: <CAG27Bk2XQxWUFZPuQP8JWJaJ5OuCrxspk==9saGO-Xv6yk=7Sg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2783 bytes --]
On 11/02/2013 7:04 AM, Sami Kerola wrote:
> On Sun, Feb 10, 2013 at 4:25 PM, Luis Aranguren <pizzaman@hotmail.com> wrote:
>> Hi, I'm trying to package util-linux for exherbo, a source based distro.
>>
>> util-linux's lscpu tests fail when compiled on a VM running under a VMware Vsphere esxi hypervisor.
>>
>> #cat ./C/64/tests/diff/lscpu/lscpu-x86_64-64cpu
>> --- /var/tmp/paludis/build/sys-apps-util-linux-2.22.2/work/util-linux-2.22.2/tests/expected/lscpu/lscpu-x86_64-64cpu 2012-10-15 10:09:42.000000000 +0000
>> +++ /var/tmp/paludis/build/sys-apps-util-linux-2.22.2/work/C/64/tests/output/lscpu/lscpu-x86_64-64cpu 2013-02-09 03:35:37.000000000 +0000
>> @@ -12,6 +12,8 @@
>> CPU MHz: 1064.000
>> BogoMIPS: 3989.44
>> Virtualization: VT-x
>> +Hypervisor vendor: VMware
>> +Virtualization type: full
>> L1d cache: 32K
>> L1i cache: 32K
>> L2 cache: 256K
>>
>>
>> # lscpu
>> Architecture: x86_64
>> CPU op-mode(s): 32-bit, 64-bit
>> Byte Order: Little Endian
>> CPU(s): 2
>> On-line CPU(s) list: 0,1
>> Thread(s) per core: 1
>> Core(s) per socket: 2
>> Socket(s): 1
>> NUMA node(s): 1
>> Vendor ID: AuthenticAMD
>> CPU family: 16
>> Model: 6
>> Stepping: 3
>> CPU MHz: 1497.506
>> BogoMIPS: 2995.01
>> Hypervisor vendor: VMware
>> Virtualization type: full
>> L1d cache: 64K
>> L1i cache: 64K
>> L2 cache: 1024K
>> NUMA node0 CPU(s): 0,1
>>
>> How can I solve this?
>> Luis Aranguren
> Hi Luis,
>
> I have a hunch best way to proceed is to get cpu data from your /proc.
> This can be achieved easiest by running a lscpu test data collector
> script.
>
> cd src/util-linux
> sh tests/ts/lscpu/mk-input.sh vmware-esxi
>
> After running the script you can find file vmware-esxi.tar.gz in
> current directory. Please send the file to mail list, and inform if it
> can be added to be part of regression test suite (which would of
> course is much preferred).
>
Hi Sami,
Thanks for the reply. I include the output file from mk-input.sh, I have
to note that there were a three permission denied instances.
# sh tests/ts/lscpu/mk-input.sh vmware-esxi
cp: cannot open ‘/sys/devices/system/cpu/microcode/reload’ for reading:
Permission denied
cp: cannot open ‘/sys/devices/system/cpu/probe’ for reading: Permission
denied
cp: cannot open ‘/sys/devices/system/cpu/release’ for reading:
Permission denied
Feel free to use it as part of the regression test suite.
Luis Aranguren
<http://paste.luisaranguren.com/index.php?8px@raw>
[-- Attachment #2: vmware-esxi.tar.gz --]
[-- Type: application/gzip, Size: 4268 bytes --]
next prev parent reply other threads:[~2013-02-11 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 16:25 Hypervisor & Virtualization lscpu test fail Luis Aranguren
2013-02-10 21:04 ` Sami Kerola
2013-02-11 1:44 ` Luis Aranguren [this message]
2013-02-11 22:56 ` Sami Kerola
2013-02-13 16:35 ` Luis Aranguren
2013-02-14 14:40 ` Karel Zak
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=BLU0-SMTP144C815AE93C94E539C372CD50A0@phx.gbl \
--to=pizzaman@hotmail.com \
--cc=kerolasa@iki.fi \
--cc=util-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox