similar to: Why Guest does not retain Host CPU flags

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

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

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

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

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

On 05/11/2017 12:45 PM, Leon Fauster wrote: >> 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 >>> >>>

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

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

> Here's mine. Interesting differences: If you disable Intel Speedstep in the BIOS it should lock the CPU to its fastest speed, but you lose power saving during idle. On Thu, May 11, 2017 at 3:48 PM, ken <gebser at mousecar.com> wrote: > On 05/11/2017 12:45 PM, Leon Fauster wrote: > >> Am 11.05.2017 um 16:29 schrieb Leon Fauster <leonfauster at googlemail.com>:

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

On 04.02.2015 22:32, Dennis Jacobfeuerborn wrote: > 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

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,

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 > >>>> >

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 @

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

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

On 12/06/2016 06:06 AM, Blair Bethwaite wrote: > Hi Roberto, Hi Blair > What is the cpu and memory configuration of your guest? I've set to copy host configuration (16 cores) and memory is set to 24GB, host has 64GB. Guest is Windows 2012 64bits version Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 16

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'/>

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

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,