summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJan Kiszka <jan.kiszka@web.de>2009-06-07 11:30:25 +0200
committerBlue Swirl <blauwirbel@gmail.com>2009-06-07 16:40:22 +0300
commit168ccc11c323af885de353d9e045c0c1f78f6f2f (patch)
treed75e9a932496d36c94f274aad5d0039f6df0f6a2 /kvm-all.c
parentFix generation of CONFIG_KVM (diff)
downloadqemu-kvm-168ccc11c323af885de353d9e045c0c1f78f6f2f.tar.gz
qemu-kvm-168ccc11c323af885de353d9e045c0c1f78f6f2f.tar.bz2
qemu-kvm-168ccc11c323af885de353d9e045c0c1f78f6f2f.zip
kvm: Improve upgrade notes when facing unsupported kernels
Users complained that it is not obvious what to do when kvm refuses to build or run due to an unsupported host kernel, so let's improve the hints. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Diffstat (limited to 'kvm-all.c')
-rw-r--r--kvm-all.c10
1 files changed, 7 insertions, 3 deletions
diff --git a/kvm-all.c b/kvm-all.c
index c89e3b1cf..b24d8766f 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@ -404,6 +404,9 @@ static void kvm_reset_vcpus(void *opaque)
int kvm_init(int smp_cpus)
{
+ static const char upgrade_note[] =
+ "Please upgrade to at least kernel 2.6.29 or recent kvm-kmod\n"
+ "(see http://sourceforge.net/projects/kvm).\n";
KVMState *s;
int ret;
int i;
@@ -454,7 +457,8 @@ int kvm_init(int smp_cpus)
*/
if (!kvm_check_extension(s, KVM_CAP_USER_MEMORY)) {
ret = -EINVAL;
- fprintf(stderr, "kvm does not support KVM_CAP_USER_MEMORY\n");
+ fprintf(stderr, "kvm does not support KVM_CAP_USER_MEMORY\n%s",
+ upgrade_note);
goto err;
}
@@ -465,8 +469,8 @@ int kvm_init(int smp_cpus)
ret = -EINVAL;
fprintf(stderr,
- "KVM kernel module broken (DESTROY_MEMORY_REGION)\n"
- "Please upgrade to at least kvm-81.\n");
+ "KVM kernel module broken (DESTROY_MEMORY_REGION).\n%s",
+ upgrade_note);
goto err;
}