It's important to know what the guest configuration looks like when debugging
issues so print out important command line options at startup:
$ ./kvm run -k ../../arch/x86/boot/bzImage -m 512
# kvm run -k ../../arch/x86/boot/bzImage -m 512 -c 1
Suggested-by: Ingo Molnar <mi...@elte.hu>
Cc: Asias He <asias.he...@gmail.com>
Cc: Avi Kivity <a...@redhat.com>
Cc: Cyrill Gorcunov <gorcu...@gmail.com>
Cc: Ingo Molnar <mi...@elte.hu>
Cc: Prasad Joshi <prasadjoshi...@gmail.com>
Cc: Sasha Levin <levinsasha...@gmail.com>
Signed-off-by: Pekka Enberg <penb...@kernel.org>
---
tools/kvm/kvm-run.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/tools/kvm/kvm-run.c b/tools/kvm/kvm-run.c
index 9b5176f..5b56779 100644
--- a/tools/kvm/kvm-run.c
+++ b/tools/kvm/kvm-run.c
@@ -476,6 +476,8 @@ int kvm_cmd_run(int argc, const char **argv, const char
*prefix)
}
free(hi);
+ printf(" # kvm run -k %s -m %Lu -c %d\n", kernel_filename, ram_size /
1023 / 1024, nrcpus);
+
if (!kvm__load_kernel(kvm, kernel_filename, initrd_filename,
real_cmdline))
die("unable to load kernel %s", kernel_filename);
--
1.7.0.4
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
