similar to: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)

Displaying 20 results from an estimated 1000 matches similar to: "'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)"

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
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: >>>>
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:
2014 Mar 03
0
Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
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 fxsr sse sse2 ss ht tm pbe syscall > nx pdpe1gb rdtscp lm constant_tsc
2014 Mar 03
0
Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
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: > >> > >> # grep ^flags /proc/cpuinfo | sort -u > >> flags
2014 Mar 03
0
Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
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: > >>>> Hi Martin > >>>> >
2014 Mar 03
0
Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
On Fri, Feb 28, 2014 at 03:45:01PM +0000, Struan Bartlett wrote: > 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
2014 Mar 03
0
Re: 'virsh capabilities' on Debian Wheezy-amd64 reports different cpu to Wheezy-i386 (on same hardware)
On Mon, Mar 03, 2014 at 02:15:43PM +0000, Struan Bartlett wrote: > > > 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
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:
2017 Jul 06
2
Live Migration and LibVirt CPU Mode
Hi All, First time mailing here, I hope someone can help. We?re running a OpenStack Newton environment on top of CentOS-7.3, LibVirt and Qemu-KVM-EV. We are encountered an issue live migrating a VM between 2 hosts with different CPUs and LibVirt throws the following error: libvirtError: unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features:
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 @
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 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
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
2015 Mar 13
6
Re: Processor usage of qemu process.
On Fri, Mar 13, 2015 at 12:35 PM, Daniel P. Berrange <berrange@redhat.com> wrote: > On Fri, Mar 13, 2015 at 10:32:14AM +0100, Dominique Ramaekers wrote: >> Dear Daniel, my XML's: >> >> Note: It seems I was to quick, the Windows 8.1 isn't fixed... >> >> Windows Server 2015 R2 >> >> <domain type='kvm' id='146'> >>
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
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'/>
2015 Mar 13
2
Re: Processor usage of qemu process.
Dear Daniel, my XML's: Note: It seems I was to quick, the Windows 8.1 isn't fixed... Windows Server 2015 R2 <domain type='kvm' id='146'> <name>CmsrvAPP2</name> <uuid>02c5daef-662a-85ba-7291-485118badc64</uuid> <memory unit='KiB'>3149824</memory> <currentMemory unit='KiB'>3149824</currentMemory>
2013 Nov 11
0
Error in snapshot create in libvirt 1.1.4
Hi list, i currently have the following issue: I did a test upgrade to libvirt 1.1.4 and now i cannot create new snapshots which can be reverted. Following Situation: Virtualization: kvm Disktype: qcow2 qemu XML: <cpu mode='host-passthrough'> </cpu> Creating of snapshot: virsh snapshot-create-as <guest> <name> <description> --atomic Now i craete