The file being present doesn't necessarily mean anything these
days, as it's created independently of whether the kvm module
has been loaded; moreover, we're already gathering all the
information we need through QMP, so poking the filesystem at
all is entirely unnecessary.
[1]
https://github.com/systemd/systemd/commit/d35d6249d5a7ed3228
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
src/qemu/qemu_capabilities.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/src/qemu/qemu_capabilities.c b/src/qemu/qemu_capabilities.c
index 348b478159..3d99c95a6a 100644
--- a/src/qemu/qemu_capabilities.c
+++ b/src/qemu/qemu_capabilities.c
@@ -834,9 +834,8 @@ virQEMUCapsInitGuestFromBinary(virCapsPtr caps,
if (!binary)
return 0;
- if (virFileExists("/dev/kvm") &&
- (virQEMUCapsGet(qemubinCaps, QEMU_CAPS_KVM) ||
- kvmbin))
+ if (virQEMUCapsGet(qemubinCaps, QEMU_CAPS_KVM) ||
+ kvmbin)
haskvm = true;
if (virQEMUCapsGetMachineTypesCaps(qemubinCaps, &nmachines, &machines) <
0)
--
2.17.1