Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

B.15. No Guest Virtual Machines are Present when libvirtd is Started

Symptom
The libvirt daemon is successfully started, but no guest virtual machines appear to be present. 
# virsh list --all
 Id    Name                           State
----------------------------------------------------
#
Copy to Clipboard Toggle word wrap
Investigation
There are various possible causes of this problem. Performing these tests will help to determine the cause of this situation:
Verify KVM kernel modules
Verify that KVM kernel modules are inserted in the kernel: 
# lsmod | grep kvm
kvm_intel             121346  0
kvm                   328927  1 kvm_intel
Copy to Clipboard Toggle word wrap
If you are using an AMD machine, verify the kvm_amd kernel modules are inserted in the kernel instead, using the similar command lsmod | grep kvm_amd in the root shell.
If the modules are not present, insert them using the modprobe <modulename> command.

Note

Although it is uncommon, KVM virtualization support may be compiled into the kernel. In this case, modules are not needed.
Verify virtualization extensions
Verify that virtualization extensions are supported and enabled on the host: 
# egrep "(vmx|svm)" /proc/cpuinfo
flags		: fpu vme de pse tsc ... svm ... skinit wdt npt lbrv svm_lock nrip_save
flags		: fpu vme de pse tsc ... svm ... skinit wdt npt lbrv svm_lock nrip_save
Copy to Clipboard Toggle word wrap
Enable virtualization extensions in your hardware's firmware configuration within the BIOS setup. Refer to your hardware documentation for further details on this.
Verify client URI configuration
Verify that the URI of the client is configured as desired: 
# virsh uri
vbox:///system
Copy to Clipboard Toggle word wrap
For example, this message shows the URI is connected to the VirtualBox hypervisor, not QEMU, and reveals a configuration error for a URI that is otherwise set to connect to a QEMU hypervisor. If the URI was correctly connecting to QEMU, the same message would appear instead as: 
# virsh uri
qemu:///system
Copy to Clipboard Toggle word wrap
This situation occurs when there are other hypervisors present, which libvirt may speak to by default.
Solution
After performing these tests, use the following command to view a list of guest virtual machines: 
# virsh list --all
Copy to Clipboard Toggle word wrap
Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2026 Red Hat