Displaying 20 results from an estimated 10000 matches similar to: "Finding real cpuinfo and meminfo"
2005 Dec 05
2
Permission Denied: /proc/cpuinfo
> -----Original Message-----
> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
> Behalf Of Mark Sargent
> Sent: Sunday, December 04, 2005 10:38 PM
> To: CentOS mailing list
> Subject: [CentOS] Permission Denied: /proc/cpuinfo
>
> HI All,
>
> why do I get the below,
>
> [root at status1 ~]# /proc/cpuinfo
> -bash: /proc/cpuinfo:
2008 Sep 20
2
Re: My domU cpuinfo shows "cache seize: 16KB" ater upgrading to Xen-3.3.0... but in Xen-3.2 it has 2048KB!
No one knows about this?!
It''s normal for domU in Xen-3.3 to have only 16KB of CPU cache size?
Thanks!
Thiagi
2008/9/18 Thiago Camargo Martins Cordeiro <thiagocmartinsc@gmail.com>
> Hi folks!
>
> After upgrading my Xen-3.2.0 to new Xen-3.3.0/Linux-2.6.18.8-xen-3.3.0 my
> domU /proc/cpuinfo shows only:
>
> administrativo@vsrvXX:~$ cat /proc/cpuinfo
>
2018 Jan 08
1
C6 KPTI cpuinfo flag?
Noticed C6 had a kernel update on Friday.
2.6.32-696.18.7.el6.x86_64
What is the flag in /proc/cpuinfo that indicates the KPTI patch for
Meltdown CVE-2017-5754 for C6?
Some distros are using "kaiser" some like Fedora are using "pti". Also
noticed some (like Fedora) are displaying "cpu_insecure" under the
bugs: heading of cpuinfo.
2006 Sep 19
5
VT 64bit kernel with >4Gb RAM
Hi there,
I have the lucky task to setup a Xen system.
my plateform is a dell 2950 with 16Gb of RAM.
I got as far as setting up debian sarge and xen following
http://www.debian-administration.org/articles/423
and overcoming some specific difficulties
(http://kmuto.jp/b.cgi/debian/d-i-2615.htm &
http://wiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround)
But, my concern now, while
2011 Jul 20
1
"xm dmesg" shows SVM but not /proc/cpuinfo
Ah, thank you for pointing that out. I forgot to include a subject, my
bad.
On Thu, Jul 21, 2011 at 12:46 AM, Larry Ing <larry@lwi3.net> wrote:
> Earlier I posed this question:
>
> "My Dom0 kernel is having issues detecting the SVM capabilities of my
> CPU. Non-Xen kernels are able to see the capability just fine and I
> can''t figure out why the Dom0 cannot. I
2005 Dec 13
6
compaq r4000 /proc/cpuinfo reports 997 and should be 2400
Hi
I have a compaq R4000 with the 2.4GIG AMD 64 bit. 4000+ rated.
proc cpuinfo reports
cpu Mhz as 997.481
Do I have to run the 64 bit version to have things run correctly?
I just have the normal 4.2 loaded at this time.
The laptop seems slow for 4000+ as reflected by the cpu Mhz also.
Any thoughts on running the 32 bit version of 4.2 vs the 64 bit version
of 4.2?
Jerry
2017 Jan 28
2
libvirt does not show same CPU Model as /proc/cpuinfo for CPU Model info.
Hi ,
Created new thread .
Environment:
Bare Metal server + CentOs with qemu/KVM +libvirt for virtualization
Guest Instantiated with virt-install with forced CPU model like below
virt-install --virt-type kvm --name compute-0 --cpu
Haswell,+fma,+movbe,+fsgsbase,+bmi1,+hle,+avx2,+smep,+bmi2,+erms,+invpcid,+rtm
--ram=61440 --vcpus=20 --os-type=linux --os-variant=generic
After guest installation
2008 Sep 13
1
cpuinfo flags change under 3.2-testing?
Hi,
I''m building Xen on a 64bit machine, then using the xen.gz from that
on a 32bit host (so that it can boot 64bit guests). This works fine.
However I note that after booting xen.gz from 3.2-testing
/proc/cpuinfo has different flags. 3.2.1 is the same. I have not yet
tried 3.3.x.
3.2.0 results in:
flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov
pat pse36 clflush
2010 Jul 16
4
Installping puppet with kickstart -- Cannot find local fact /proc/cpuinfo
Hi
I have been trying to get puppet working with kickstart. I am
trying to install Hadoop on the nodes. Installing puppet from
kickstart work and when the machine restarts, certificates are pulled
down and hadoop user is created and files are extracted.
I want all the user creation etc to be done before the machine
reboots so that I can set up init.d scripts to do a start of hadoop .
So I
2018 Sep 30
1
libvirt reported capabilities doesn't match /proc/cpuinfo while the model does match
Hi,
According to virsh capabilities I only have the following cpu features:
<cpu>
<arch>x86_64</arch>
<model>IvyBridge-IBRS</model>
<vendor>Intel</vendor>
<microcode version='32'/>
<topology sockets='1' cores='4' threads='1'/>
<feature name='ds'/>
2008 Sep 18
0
domU cpuinfo shows only 16 KB ater upgrading to Xen-3.3.0!
Hi folks!
After upgrading my Xen-3.2.0 to new Xen-3.3.0/Linux-2.6.18.8-xen-3.3.0 my
domU /proc/cpuinfo shows only:
administrativo@vsrvXX:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Intel(R) Pentium(R) D CPU 3.40GHz
stepping : 4
cpu MHz : 3391.500
*cache size : 16 KB*
physical id : 0
siblings
2016 Mar 23
2
Re: /proc/meminfo
On 03/23/2016 09:19 AM, Cole Robinson wrote:
> On 03/23/2016 12:10 PM, Peter Steele wrote:
>> Has anyone seen this issue? We're running containers under CentOS 7.2 and some
>> of these containers are reporting incorrect memory allocation in
>> /proc/meminfo. The output below comes from a system with 32G of memory and
>> 84GB of swap. The values reported are
2019 Sep 15
3
virsh -c lxc:/// setvcpus and <vcpu> configuration fails
Hi folks!
i created a server with this XML file:
<domain type='lxc'>
<name>lxctest1</name>
<uuid>227bd347-dd1d-4bfd-81e1-01052e91ffe2</uuid>
<metadata>
<libosinfo:libosinfo
xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
<libosinfo:os id="http://centos.org/centos/6.9"/>
2016 Mar 23
7
/proc/meminfo
Has anyone seen this issue? We're running containers under CentOS 7.2
and some of these containers are reporting incorrect memory allocation
in /proc/meminfo. The output below comes from a system with 32G of
memory and 84GB of swap. The values reported are completely wrong.
# cat /proc/meminfo
MemTotal: 9007199254740991 kB
MemFree: 9007199224543267 kB
MemAvailable: 12985680
2008 Nov 19
0
amd mobile on 1 cpu listed in /proc/cpuinfo
I just noticed that my Dual core mobile AMD ZM-82 is only showing
one processor in /proc/cpuinfo and not two.
Is there a reason? I am running centos 5.2 x86_64.
uname -a
Linux demobox.msgnet.com 2.6.18-92.el5 #1 SMP Tue Jun 10 18:51:06 EDT
2008 x86_64 x86_64 x86_64 GNU/Linux
Jerry
--------------
more /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 17
model
2006 Jun 01
5
Moved from Xen 2 to Xen 3... some questions..
Hi,
Ive been using Xen2 for ages, and it great, but ive decided to go to Xen 3.
Ive got it working, but I want to ask a couple of questions about it.
1. There no longer seems to be a seperate DomU and Dom0 built when I build
from source. Is this the new policy? this would suit me, as I always used
Xen0 kernels in my guest domains anyway.
2. Ive got me a vmx (vanderpool / intel virtualization
2017 Jan 30
0
Re: libvirt does not show same CPU Model as /proc/cpuinfo for CPU Model info.
On Sat, Jan 28, 2017 at 09:29:11PM +0530, akhilesh rawat wrote:
>Hi ,
>
>Created new thread .
>
>
>Environment:
>Bare Metal server + CentOs with qemu/KVM +libvirt for virtualization
>Guest Instantiated with virt-install with forced CPU model like below
> virt-install --virt-type kvm --name compute-0 --cpu
2016 Mar 25
2
Re: /proc/meminfo
>> The latest version available for CentOS/RHEL is version 1.2.17. What
>> site are you using to get the rpm for version 1.3.2?
build from source rpm's
> I found a download for this version and tried it out but we ran into a
> different set of problems when running our software in containers under
> this environment. Unfortunately we're out of time to address these
2016 Apr 11
4
meminfo
Dear All
As far as I know , to check for the amount of installed RAM on my
centos server I checked it as:
#more /proc/meminfo
Can you please let me know how can I check for the instantaneous
occupied amount of my RAM the similar way the task manager shows it on
my Win server ?
Thank you in advance
2008 Jul 01
6
OpenVZ configuration of networking with puppet - big crash
I am trying to streamline the current distribution specific setup and
creation of VE''s within OpenVZ with puppet. My first attempt has gone
horribly wrong as you will see below. Here''s the script I wrote to
replace the redhat specific setup that OpenVZ used:
[jleggett@lxp6d15m3 scripts]$ cat redhat-add_ip.sh
#!/bin/bash
#
# Debug - take out later
set -x