Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

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
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2025 Red Hat