Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Libvirt log: internal error: unknown CPU feature

Enver
in VM Engine (KVM)

Featured Replies

Hi Guys,

 

I have an Intel i7 5960x CPU and from day one of using KVM within UNRAID I have seen the following errors. Its as if KVM doesn't know which CPU is being passed through or doesn't fully support it?

 

UNRAID Version: 6.3.4

QEMU Version: 2.7.1

Lirbvirt Version: 2.4.0 <- I think is a pretty old version of Lirbvirt and the bug may lie here.

 

Can someone shed light on the below please?

 

 

2017-05-24 19:05:36.598+0000: 10747: info : libvirt version: 2.4.0
2017-05-24 19:05:36.598+0000: 10747: info : hostname: Tower
2017-05-24 19:05:36.598+0000: 10747: warning : qemuDomainObjTaint:3885 : Domain id=1 name='Windows Server 2016 ADFS' uuid=194da13b-d655-a808-28c2-a4931269853f is tainted: high-privileges
2017-05-24 19:05:36.598+0000: 10747: warning : qemuDomainObjTaint:3885 : Domain id=1 name='Windows Server 2016 ADFS' uuid=194da13b-d655-a808-28c2-a4931269853f is tainted: host-cpu
2017-05-24 19:05:36.662+0000: 10747: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2017-05-24 19:05:36.662+0000: 10747: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id
2017-05-24 19:05:36.787+0000: 10747: warning : qemuDomainObjTaint:3885 : Domain id=2 name='Windows Server 2016 Core DC' uuid=f160aecc-ac0f-c8da-2c9a-65476c1fbc06 is tainted: high-privileges
2017-05-24 19:05:36.787+0000: 10747: warning : qemuDomainObjTaint:3885 : Domain id=2 name='Windows Server 2016 Core DC' uuid=f160aecc-ac0f-c8da-2c9a-65476c1fbc06 is tainted: host-cpu
2017-05-24 19:05:36.847+0000: 10747: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2017-05-24 19:05:36.847+0000: 10747: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id
2017-05-24 19:05:36.983+0000: 10747: warning : qemuDomainObjTaint:3885 : Domain id=3 name='Windows 10 Pro' uuid=6cdeacc6-d49b-da2b-a62c-f948822dec92 is tainted: high-privileges
2017-05-24 19:05:36.983+0000: 10747: warning : qemuDomainObjTaint:3885 : Domain id=3 name='Windows 10 Pro' uuid=6cdeacc6-d49b-da2b-a62c-f948822dec92 is tainted: host-cpu
2017-05-24 19:05:42.791+0000: 10747: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2017-05-24 19:05:42.791+0000: 10747: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id

Edited by Enver

  • Quote

    I have nothing of value to add, other than i get that with every VM boot. Running a pair of Xeon 5650's, quite a bit older than your CPU's

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.