The message when failing to connect can be misleading as package names
will differ per Distribution as well as not apply for e.g. self built
binaries.
This changes the message in a way to be more generic not implying literal
package names.
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@xxxxxxxxxxxxx>
---
virtManager/engine.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/virtManager/engine.py b/virtManager/engine.py
index 644a42a..262375e 100644
--- a/virtManager/engine.py
+++ b/virtManager/engine.py
@@ -217,8 +217,8 @@ class vmmEngine(vmmGObject):
# Manager fail message
msg = _("Could not detect a default hypervisor. Make\n"
"sure the appropriate virtualization packages\n"
- "are installed (kvm, qemu, libvirt, etc.), and\n"
- "that libvirtd is running.\n\n"
+ "containing kvm, qemu, libvirt, etc. are\n"
+ "installed, and that libvirtd is running.\n\n"
"A hypervisor connection can be manually\n"
"added via File->Add Connection")
--
2.7.4
_______________________________________________
virt-tools-list mailing list
virt-tools-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/virt-tools-list
