similar to: Error doing PCI passthrough on CentOS 7.2

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

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

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,

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

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

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

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

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:

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 @

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

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

On Wed 14.Sep'16 at 7:17:45 -0600, Alex Williamson wrote: > On Wed, 14 Sep 2016 15:00:37 +0200 > Paolo Bonzini <pbonzini at redhat.com> wrote: > > > On 14/09/2016 14:35, Sandro Bonazzola wrote: > > > FYI > > > > > > > > > ---------- Forwarded message ---------- > > > From: *C. L. Martinez* <carlopmart at gmail.com

Hi all, some nouveau users and developers have an issue with mmiotracing the nvidia driver. After some digging I think it might has something todo with hugepages and/or the tracing infrastructure in general, but generally I am still clueless what is causing this. Generally it can be triggered by starting a X server on the nvidia gpu with the nvidia kernel module loaded and mmiotracer active

> 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

Hi, On Sun, Jul 23, 2017 at 3:45 PM, Pavel Hrdina <phrdina@redhat.com> wrote: > On Sat, Jul 22, 2017 at 03:03:06PM -0400, Alex wrote: >> Hi, >> I have a fedora25 system with a Windows10 host and would like to use >> it for photoshop. However, it complains the video memory is too low. >> I'm using the QXL driver and it appears to be limited to 256MB? I've

I have syslinux 5.10 on a 32bit gentoo system. It boots fine. Now I installed another linux system in other partitions of the same drive (a 64 bit system), updated syslinux.cfg, setup the new system as default, and the new entry appears in the menu. Problem is: it doesn't boot. On timeout, it starts counting down again, and that's it. No error message whatsoever. Selecting the old system

On Mon, Sep 14, 2020 at 8:42 AM Yedidyah Bar David <didi@redhat.com> wrote: > > On Mon, Sep 14, 2020 at 12:28 AM wodel youchi <wodel.youchi@gmail.com> wrote: > > > > Hi, > > > > Thanks for the help, I think I found the solution using this link : https://www.berrange.com/posts/2018/06/29/cpu-model-configuration-for-qemu-kvm-on-x86-hosts/ > > > >

Solved. For the archives: Noticed in xl info output that only 1 core was recognised, even though nr_cpus should show 16 on this box. Tried rebooting and selecting the old .34 kernel, console printed "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1" and CentOS failed to boot. Powered down the box fully and started back up with the latest .44 kernel and everything is working fine

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