virtualbox-kvm icon indicating copy to clipboard operation
virtualbox-kvm copied to clipboard

Required capability 'KVM_CAP_KVM_CAP_XCRS' is missing!

Open jschwartzenberg opened this issue 1 year ago • 5 comments

Bug Description

When I try to run a VM, I get the following message: Required capability 'KVM_CAP_KVM_CAP_XCRS' is missing! (VERR_NEM_MISSING_FEATURE).

How to Reproduce

Compile and try to run a VM on an Intel Core2 Duo.

VM configuration

Guest OS configuration details:

Host OS details:

  • Trisquel 11.0 (Based on Ubuntu 22.04)
  • 5.15.0-92-generic

Logs

Following logs are required:

jschwartzenberg avatar Feb 08 '24 19:02 jschwartzenberg

Unfortunately, your Intel P8600 CPU does not support the XSAVE instruction which is currently a requirement to run VirtualBox with our KVM backend.

tpressure avatar Feb 09 '24 09:02 tpressure

Thanks a lot for the quick response!

I tried it also on another laptop I have, but I'm getting the same error with an Intel Core i5 M 460 CPU. dmesg.txt test-2024-02-09-21-22-43.log

It would be great if more CPUs could be supported in the future!

jschwartzenberg avatar Feb 09 '24 20:02 jschwartzenberg

Intel Core i5 M 460 is Nehalem (microarchitecture) which also does not support XSAVE.

Currently, you need at least Sandy Bridge (2nd generation Core Processors) in order to use VirtualBox with KVM. Supporting older systems without XSAVE is certainly possible, but it's not on our agenda right now.

tpressure avatar Feb 09 '24 21:02 tpressure

Alright, thanks for the info! It seems you are politely saying all my CPUs are old.. :)

Is XSAVE indeed the one and only thing that prevents all these older CPUs from working?

jschwartzenberg avatar Feb 10 '24 13:02 jschwartzenberg

Alright, thanks for the info! It seems you are politely saying all my CPUs are old.. :)

:smile:

XSAVE should be the only thing ... can't give you 100% on this though since I've never tested anything older than Ivy Bridge (3rd Gen Core).

tpressure avatar Feb 11 '24 14:02 tpressure

Just to let everyone know, we have now included more information in the readme. Feel free to have a look and let us know if that clarifies things!

parthy avatar Feb 21 '24 15:02 parthy

Closing this because the limitation has been added to the readme.

tpressure avatar Feb 23 '24 14:02 tpressure

Just to let everyone know, we have now included more information in the readme. Feel free to have a look and let us know if that clarifies things!

I think the main issue is Intel's marketing. Now this is written "This implies a 2nd Gen Core processor or newer.", but Intel Core2 Duo is not a 2nd gen core processor despite the 2 and the Duo :) If nobody else will bring this up, I think everything's fine, otherwise I hope there can be other ways to describe this better to prevent you from getting asked about this over and over.

(Myself I'm in the category that believes i7 is always faster than i5. When somebody would talk about Haswell i5 versus Sandy or Ivy, I presume an i5 could be faster than an i7 if they are from different generations, but I'd have no clue.)

jschwartzenberg avatar Feb 23 '24 15:02 jschwartzenberg