similar to: "xm dmesg" shows SVM but not /proc/cpuinfo

Displaying 20 results from an estimated 6000 matches similar to: ""xm dmesg" shows SVM but not /proc/cpuinfo"

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'/>
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
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
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
2010 Jan 05
0
pv_ops dom0 kernel: /proc/cpuinfo shows 0.000 MHz
I just noticed something interesting with the pv_ops dom0 kernel that I built from Jeremy''s git tree. When I run ''cat /proc/cpuinfo'' the output shows the processors have 0.000 MHz. Everything runs fine I just thought it was interesting. processor : 3 vendor_id : AuthenticAMD cpu family : 16 model : 4 model name : AMD Phenom(tm) II X4
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 Jun 16
2
unable to access Linux HVM via xm console - Could not read tty from store: No such file or directory
Hi all I''m running CentOS 5.1 x64 + Xen 3.0 & I have setup a CentOS 5.1 x64 domU as a HMV. For the setup I used VNC, but I would prefer to be able to access it via "xm console cPanel" via SSH directly. Here''s the output cPanel HVM: [root@pc-00059 ~]# more /etc/xen/cPanel name = "cPanel" uuid = "ff940501-507d-04ca-e590-831e79ba0397" maxmem =
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
2010 Jan 29
2
support for hvm
my server has intel q9550 cpu (which supports intel-vt) and intel s3200 motherboard. BIOS has enabled intel virtualisation. centos 5.4, 64bit [root@localhost ~]# uname -a Linux localhost.localdomain 2.6.18-164.el5xen #1 SMP Thu Sep 3 04:03:03 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux [root@localhost ~]# grep vmx /proc/cpuinfo flags           : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36
2014 Feb 28
2
'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
Hi On a range of Dell servers containing Intel 64bit processors, 'virsh capabilities' reports the cpu differently on Debian Wheezy-amd64 and Wheezy-i386. The results given by the Wheezy-i386 version seem very wrong (since n270 is an Atom processor). Apart from architecture, the package versions of libvirt-bin are identical: 1.2.1-1~bpo70+1. /usr/share/libvirt/cpu_map.xml files are
2014 Mar 03
2
Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
Hi Martin Thanks for your response. Here's the output of that grep: # grep ^flags /proc/cpuinfo | sort -u flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
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
2013 Jun 17
2
Re: Fwd: Haswell 4770 misidentified as Sandy Bridge
On 06/13/2013 10:11 PM, Michael Giardino wrote: > Hi, > > I'm running libvert on a Debian 7 system. I have upgraded libvert and qemu > from source (v1.06 and 1.5.0 respectively) and the problem persists. The > guest OS is also a Debian 7 system running a non-SMP kernel. The error > message from virt-manager is > > Error starting domain: unsupported configuration:
2014 Mar 03
2
Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
On 03/03/2014 10:44, Martin Kletzander wrote: > On Mon, Mar 03, 2014 at 10:30:11AM +0000, Struan Bartlett wrote: >> Hi Martin >> >> Thanks for your response. Here's the output of that grep: >> >> # grep ^flags /proc/cpuinfo | sort -u >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca >> cmov pat pse36 clflush dts acpi mmx
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
2008 Jun 13
9
Xen shows single processor on a dual core system
Hi all, On dual core processor machine, I installed ubuntu-8.04 in which I installed xen-3.2. In ubuntu: # cat /proc/cpuinfo --> Shows two processors information. But in Xen on the same machine: # cat /proc/cpuinfo --> Shows only one processor information. Can anyone please explain what could be the reason behind this? Thanks Saravana
2014 Mar 03
2
Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
On 03/03/2014 10:55, Martin Kletzander wrote: > On Mon, Mar 03, 2014 at 10:47:03AM +0000, Struan Bartlett wrote: >> On 03/03/2014 10:44, Martin Kletzander wrote: >>> On Mon, Mar 03, 2014 at 10:30:11AM +0000, Struan Bartlett wrote: >>>> Hi Martin >>>> >>>> Thanks for your response. Here's the output of that grep: >>>>
2010 Mar 26
0
VT-x enabled but xm dmesg does not show anything about vmx info
VT is enabled in BIOS and ''xm info'' shows that hvm can be created like below: xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm -3.0-x86_64 Several Windows VMs have been created on this server and running perfectly. However, I wonder that it does not show anything when commands show VT-x availability such as ''xm dmesg | grep VMX(or
2014 Mar 03
2
Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
On 03/03/2014 13:42, Martin Kletzander wrote: > On Mon, Mar 03, 2014 at 11:15:51AM +0000, Struan Bartlett wrote: >> On 03/03/2014 10:55, Martin Kletzander wrote: >>> On Mon, Mar 03, 2014 at 10:47:03AM +0000, Struan Bartlett wrote: >>>> On 03/03/2014 10:44, Martin Kletzander wrote: >>>>> On Mon, Mar 03, 2014 at 10:30:11AM +0000, Struan Bartlett wrote:
2008 Jun 17
4
Re: unable to access Linux HVM via xm console - Couldnot read tty from store: No such file or directory
HVM = fully virtualized. The question is, why are you using fully virtualized domUs? Why not paravirtualized (PV)? >>> On 2008/06/16 at 16:07, Rudi Ahlers <Rudi@SoftDux.com> wrote: Itamar - IspBrasil wrote: > why you''re using hvm ? its slow > > > > Rudi Ahlers wrote: >> Hi all >> >> I''m running CentOS 5.1 x64 + Xen 3.0 & I