search for: lscpu

Don't get the CPU information from libvirt, because including libvirt and all dependencies in the virt-p2v ISO bloats everything. Instead get most of the information we need from the util-linux program 'lscpu'. Unfortunately the CPU model cannot be retrieved. Example output: $ ./run virt-p2v --cmdline="p2v.dump_config_and_exit" [...] cpu vendor . . . Intel cpu sockets . . 2 cpu cores . . . 8 cpu threads . . 1 flags . . . . . acpi apic pae This updates commit...

/dev/cpu is only available on x86 with certain modules (e.g. msr) enabled. Using lscpu to get processors count is more portable. Signed-off-by: Mike Rapoport <rppt at linux.vnet.ibm.com> --- v3: simplify by using lscpu -p=cpu v2: use lspcu instead of /proc/cpuinfo as per Cornelia's suggestion tools/virtio/ringtest/run-on-all.sh | 4 ++-- 1 file changed, 2 insertions(+),...

/dev/cpu is only available on x86 with certain modules (e.g. msr) enabled. Using lscpu to get processors count is more portable. Signed-off-by: Mike Rapoport <rppt at linux.vnet.ibm.com> --- v3: simplify by using lscpu -p=cpu v2: use lspcu instead of /proc/cpuinfo as per Cornelia's suggestion tools/virtio/ringtest/run-on-all.sh | 4 ++-- 1 file changed, 2 insertions(+),...

...Thursday, 23 March 2017 15:31:36 CET Richard W.M. Jones wrote: > Don't get the CPU information from libvirt, because including libvirt > and all dependencies in the virt-p2v ISO bloats everything. > > Instead get most of the information we need from the util-linux > program 'lscpu'. > > Unfortunately the CPU model cannot be retrieved. Theoretically, at least for Intel CPUs it could be mapped from the "Model" field; there's a table on the intel website: https://software.intel.com/en-us/articles/intel-architecture-and-processor-identification-with-cpu...

/dev/cpu is only available on x86 with certain modules (e.g. msr) enabled. Using lscpu to get processors count is more portable. Signed-off-by: Mike Rapoport <rppt at linux.vnet.ibm.com> --- v2: use lspcu instead of /proc/cpuinfo as per Cornelia's suggestion tools/virtio/ringtest/run-on-all.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/...

/dev/cpu is only available on x86 with certain modules (e.g. msr) enabled. Using lscpu to get processors count is more portable. Signed-off-by: Mike Rapoport <rppt at linux.vnet.ibm.com> --- v2: use lspcu instead of /proc/cpuinfo as per Cornelia's suggestion tools/virtio/ringtest/run-on-all.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/...

Hi all, Question : Can I install Centos7 32 Bits on a computer i386 32 bits little indian pentium III Copermine Model8 Cpufamily 6 CpuMhz 863.979 (lscpu) grep -i pae /proc/cpuinfo gives a flag pae . I am very curieus, Ger van Dijck. -- Using Opera's mail client: http://www.opera.com/mail/

...ngtest: fix run-on-all.sh to work without /dev/cpu") run-on-all.sh uses seq 0 $HOST_AFFINITY as the list of ids of the CPUs to run the command on (assuming ids of online CPUs are consecutive and start from 0), where $HOST_AFFINITY is the highest CPU id in the system previously determined using lscpu. This can fail on systems with offline CPUs. Instead let's use lscpu to determine the list of online CPUs. Signed-off-by: Halil Pasic <pasic at linux.vnet.ibm.com> Fixes: ef1b144d ("tools/virtio/ringtest: fix run-on-all.sh to work without /dev/cpu") Reviewed-by: Sascha Silbe...

On Wed, 4 May 2016 10:59:53 +0300 Mike Rapoport <rppt at linux.vnet.ibm.com> wrote: > /dev/cpu is only available on x86 with certain modules (e.g. msr) enabled. > Using lscpu to get processors count is more portable. > > Signed-off-by: Mike Rapoport <rppt at linux.vnet.ibm.com> > --- > v2: use lspcu instead of /proc/cpuinfo as per Cornelia's suggestion > > tools/virtio/ringtest/run-on-all.sh | 4 ++-- > 1 file changed, 2 insertions(+),...

Michael, Any updates on this? On Wed, May 04, 2016 at 01:15:50PM +0300, Mike Rapoport wrote: > /dev/cpu is only available on x86 with certain modules (e.g. msr) enabled. > Using lscpu to get processors count is more portable. > > Signed-off-by: Mike Rapoport <rppt at linux.vnet.ibm.com> > --- > v3: simplify by using lscpu -p=cpu > v2: use lspcu instead of /proc/cpuinfo as per Cornelia's suggestion > > tools/virtio/ringtest/run-on-all.sh | 4 ++-...

...6 at 03:41:33PM +0300, Mike Rapoport wrote: > > Michael, > > > > Any updates on this? > > > > On Wed, May 04, 2016 at 01:15:50PM +0300, Mike Rapoport wrote: > > > /dev/cpu is only available on x86 with certain modules (e.g. msr) enabled. > > > Using lscpu to get processors count is more portable. > > > > > > Signed-off-by: Mike Rapoport <rppt at linux.vnet.ibm.com> > > > --- > > > v3: simplify by using lscpu -p=cpu > > > v2: use lspcu instead of /proc/cpuinfo as per Cornelia's suggestion >...

Hello everyone I want to know how can I use libvirt to detect what cpu features a virtual machine will see. I guess I could do it in following way: 1. if cpu mode is 'custom', use 'virsh cpu-baseline --features' on the cpu model to get model features. 2. if cpu mode is 'host-passthrough' or 'host-model', do a 'virsh capabilities' to list cpu features of

...le: ``` <cpu mode='host-passthrough' check='none'> <feature policy='disable' name='3dnowprefetch'/> </cpu> ``` Created the instance, seemed this feature was not being disabled in my guest. (I was able to see '3dnowprefetch' in `lscpu` outputs) Anybody has idea on this? Does libvirt support this for Xen? Any help would be appreciated. Thank you in advance. Regards, Charles Charles Shih (史晨) Quality Engineer Red Hat, Platform QE, Virt QE, Section 1 Email: cheshi@redhat.com IRC: cheshi @ #eng-china, #hyperv ,#qa, #vir...

...a new EPYC Rome Server from Hetzner, but sensors does not show > > status of all cores in list, which is why I asked. > > Curious what "sensors" you are referring to.. > > Like this: > > $ cat /sys/devices/system/cpu/online > 0-63 > > or this: > > $ lscpu | grep CPU\(s\) > CPU(s): 64 > On-line CPU(s) list: 0-63 > NUMA node0 CPU(s): 0-15,32-47 > NUMA node1 CPU(s): 16-31,48-63 > > or what? > > /Peter K > Hi Peter, /usr/bin/sensors from the lm_sensors package I had run sensors-detect --auto befo...

...eaders-2.6.31.6-1.2.80.xendom0.fc12.i686 xen-hypervisor-3.4.1-1.fc12.i686 xen-runtime-3.4.1-1.fc12.i686 xen-doc-3.4.1-1.fc12.i686 xen-3.4.1-1.fc12.i686 kernel-PAE-2.6.31.6-1.2.80.xendom0.fc12.i686 xen-debuginfo-3.4.1-1.fc12.i686 kernel-PAE-devel-2.6.31.6-1.2.80.xendom0.fc12.i686 below is lspic and lscpu output, root@xen avinash]# lspci 00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contro...

...eaders-2.6.31.6-1.2.80.xendom0.fc12.i686 xen-hypervisor-3.4.1-1.fc12.i686 xen-runtime-3.4.1-1.fc12.i686 xen-doc-3.4.1-1.fc12.i686 xen-3.4.1-1.fc12.i686 kernel-PAE-2.6.31.6-1.2.80.xendom0.fc12.i686 xen-debuginfo-3.4.1-1.fc12.i686 kernel-PAE-devel-2.6.31.6-1.2.80.xendom0.fc12.i686 below is lspic and lscpu output, root@xen avinash]# lspci 00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contro...

/dev/cpu is only available on x86 with certain modules (e.g. msr) enabled. Using /proc/cpuinfo to get processors count is more portable. Signed-off-by: Mike Rapoport <rppt at linux.vnet.ibm.com> --- tools/virtio/ringtest/run-on-all.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/virtio/ringtest/run-on-all.sh b/tools/virtio/ringtest/run-on-all.sh index

On Tue, Mar 31, 2020 at 11:44 AM Johnny Hughes <johnny at centos.org> wrote: > On 3/30/20 11:20 PM, Thomas Stephen Lee wrote: > > Hi, > > > > I had a doubt regarding RHEL/CentOS Versions. > > > > https://access.redhat.com/support/policy/amd > > > > in the he Notes > > > > No (8) > > > > says > > > >

CentOS-6.2 What is the maximum number of cpus can I configure for a single vm guest running on a host with this hardware? # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 CPU socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU fa...

Michael, the following patches have all been posted in the past. I've collected them on top of your vhost branch -- please let me know whether this works for you. The following changes since commit 6bdf1e0efb04a1716373646cb6f35b73addca492: Makefile: drop -D__CHECK_ENDIAN__ from cflags (2016-12-16 00:13:43 +0200) are available in the git repository at: