Works for me... systemd has nothing to do with this.

What does the following output?

$ modprobe -qaR -S 3.11.1-1-ARCH $(</sys/devices/system/cpu/modalias)

This *should* (and does for me) show kvm_intel, as well as other CPU specific modules.

Can you compare this to the output from the 3.10.X kernel where you say this works?

Hi,

it shows:

microcode
aesni_intel
ghash_clmulni_intel
crc32c_intel
crc32_pclmul
kvm_amd
acpi_cpufreq

But, when I'm going to start a virtual machine with: qemu-system-x86_64 -enable-kvm the following error message occurs:

Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory

This behavior occurs for the first time - after updating to the 3.11.1 kernel (sorry I can't provide any output from the old 3.10.X kernel)

After the error message I can type $ modprobe kvm_amd + start the virtual machine without any errors - so I'm just wondering why this kernel module error comes up.

So then...

$ udevadm test /sys/devices/system/cpu/cpu0

You should see a line that looks something like:

run: 'kmod load x86cpu:vendor:0000:family:0006:model:002C:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0075,0076,0078,007C,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0093,0094,0097,0099,00C0,00E0,00E1,00E3,00E7,0100,0101,0102,0103,0104'

...which is essentially the modprobe command you ran before, but loads the modules (not just resolving the alias to module names). The "x86cpu:..." mess should also be identical to the contents of /sys/devices/system/cpu/modalias

Nevermind. It works for me because I'm running a newer systemd.

This'll remain "broken" until systemd 207 moves to core.