QEMU AND KVM PROBLEMS

I tried installing qemu, but I had to install kvm first, and I checked that my processor supports virtualization, so I don’t know why. Here is the error when I enter kvm.

open /dev/kvm: No such file or directory Could not initialize KVM, will disable KVM support 

And a new window appeared for qemu, but the download failed ... could not read the boot disk, could not read from the CDROM (code 0003)

What can I do?

+4
source share
4 answers

First check if your VMX or SVM processor supports viewing / proc / cpuinfo. If so, you need to load the KVM kernel modules:

 modprobe kvm-amd #if you have AMD modprobe kvm-intel #if you have Intel 

Then the Qemu / Kvm command should start without complaining about / dev / kvm. If you still have problems, virtualization may be disabled in the BIOS. I had some machines that reported virtualization support in / proc / cpuinfo, but were disabled in the BIOS.

Then, to download KVM from an ISO image:

 kvm -cdrom img.iso -hda disk.img -boot d 
+3
source

Try "dmesg | grep kvm" to find the reason

+1
source

Try using this command sudo modprobe kvm-intel . You were not privileged to insert KVM modules.

0
source

The first thing to check is that your CPU has virtualization extensions and that the extensions are included in the BIOS / EUFI menu. These extensions are required to run KVM. Almost all modern AMD 64-bit processors will have it. Some Intel senior / junior processes do not have it, but most will.

 egrep -o 'vmx|svm' /proc/cpuinfo 

'vmx' will appear for Intel. svm for AMD.

If your processor supports extensions, then the next thing to check is your BIOS / EUFI settings. Often these extensions are disabled by default. You might want to look at the settings of the “chipset” or “processor”, and something about “virtualization” should be mentioned in it. Make sure these settings are enabled.

After that, you should automatically insert KVM modules after reboot. If they do not, try "modprobe kvm-amd" or "modprobe kvm-intel" as suggested by Diego Voitasen. Check also the output of dmesg | grep kvm.

0
source

Source: https://habr.com/ru/post/1403283/


All Articles