Displaying 20 results from an estimated 2000 matches similar to: "libvirt does not show same CPU Model as /proc/cpuinfo for CPU Model info."
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
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:
2013 Jun 13
3
Haswell 4770 misidentified as Sandy Bridge
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: guest and host CPU are
not compatible: Host CPU does not provide required features: rtm,
2017 Jan 27
3
Re: LibVirt query CPU Model support and restore operation
hello ,
thanks for comments .
I tried now with force options for CPU flag which were not supported . Now
the command with non fully supported CPU model gets executed , But i am
surprised to see that still Guest cpu model is not changed and still same
as host cpu model(SAndy Bridge)
Why don't i see the model as HAswell now , could you please comment.
Command used :
virt-install
2015 Feb 04
2
CPU model and missing AES-NI extension
Hi,
today I tried to configure a guest using Virt-Manager and used the "copy
host cpu configuration" option which resultet in a "Sandy Bridge" model.
What I noticed is that for example the "aes" extension is not available
in the guest even though it is available on the host cpu.
This is what the host cpu looks like:
model name : Intel(R) Xeon(R) CPU E5-2650 v3 @
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
2017 May 11
2
CentOS 6 / Intel CPU support
> Am 11.05.2017 um 16:29 schrieb Leon Fauster <leonfauster at googlemail.com>:
>
>> Am 11.05.2017 um 14:48 schrieb Leon Fauster <leonfauster at googlemail.com>:
>>
>> https://access.redhat.com/support/policy/intel
>>
>> shows mainly Xeon CPUs. What about
>>
>> Intel Core i7-6700 Quad-Core Skylake
>>
>> has the current EL6
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
2017 Jan 24
3
Re: LibVirt query CPU Model support and restore operation
hi,
yes we are talking about same host here.
You could've just used -cpu host-model-only
>> I dont want to host model ( it is working with host model) .
AS KVM seems to allow support Haswell with native commands . Does this mean
in my case KVM is allowing software emulated cpu model.
Can libvirt allow software-emulated for non host model ? if yes how .
thanks
On Tue, Jan 24,
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
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:
>>>>
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'/>
2013 Jun 17
0
Re: Fwd: Haswell 4770 misidentified as Sandy Bridge
Kashyap: I have not tried integrating your guest xml but I will look over
it today when I get a chance. Thank you.
Martin: Below is the output from /proc/cpuinfo. Let me know if there is
anything else that would be helpful in debugging this. Thank you,
Michael Giardino
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
stepping
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:
2016 Sep 13
0
Error doing PCI passthrough on CentOS 7.2
Hi all,
I am trying to configure a kvm guest using pci passthrough to pass it a wireless pci adapter (host is my personal laptop). But when I try to start it:
error: Failed to start domain obsdfw
error: unsupported configuration: host doesn't support passthrough of host PCI devices
PCI passthrough is enabled:
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.10.0-327.28.3.el7.x86_64
2017 Feb 16
9
[Bug 99841] New: Switching to VT freezes X only on a dual screen
https://bugs.freedesktop.org/show_bug.cgi?id=99841
Bug ID: 99841
Summary: Switching to VT freezes X only on a dual screen
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at
2017 Feb 28
2
NUMA placement failed, performance might be affected
I just did a yum update on a CentOS 7 / Xen 4.6 server which took me from kernel-3.18.34-20.el7.x86_64 -> kernel-3.18.44-20.el7.x86_64
After rebooting, the following notice is printed immediately upon xl create'ing a domain: libxl: notice: libxl_numa.c:499:libxl__get_numa_candidate: NUMA placement failed, performance might be affected
Indeed performance is significantly degraded. This
2017 Feb 06
2
Why Guest does not retain Host CPU flags
hi ,
I am creating Guest by Libvirt tool " virt-install" with cpu model as
host.
After Guest creation i see Guest Missing quite no of flags which Host was
having .
What could be the reason for this ? I am expecting all flags of Host to e
present in Guest as well when choosing cpu model as host .
Guest :
processor : 19
vendor_id : GenuineIntel
cpu family : 6
model
2013 Apr 10
5
How to determine 64 vs 32 bit processor
I have been tied up with other work and Holidays. Now back to some
server work that is long overdue. I lost an old server yesterday so it
is crunch time.
I believe my new platform is suppose to be an x86_64. The order form
says 64 bit.
I booted Centos 6.3 i386 liveCD to check the system out before an install.
uname -i
reports i386
dmidecode -t processor
reports Characteristics of 64
2017 Jun 29
2
Way to detect virtual machine cpu features
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