aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVagrant Cascadian <vagrant@freegeek.org>2011-11-14 14:06:23 -0800
committerStefan Hajnoczi <stefanha@linux.vnet.ibm.com>2011-11-17 12:57:41 +0000
commit126197214e24b51a76fa6b0559e45b025b77e752 (patch)
tree81f935941a13690e84fcc92869d173d4d35ef8c9
parent4238e26416c3b5ece9a823de9ab8f6cdfaff8f99 (diff)
downloadqemu-126197214e24b51a76fa6b0559e45b025b77e752.zip
qemu-126197214e24b51a76fa6b0559e45b025b77e752.tar.gz
qemu-126197214e24b51a76fa6b0559e45b025b77e752.tar.bz2
Fix typo: runnning -> running
One n too many for running, need we say more. Signed-Off-By: Vagrant Cascadian <vagrant@freegeek.org> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
-rw-r--r--target-i386/kvm.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index ddd115c..5bfc21f 100644
--- a/target-i386/kvm.c
+++ b/target-i386/kvm.c
@@ -1845,7 +1845,7 @@ int kvm_arch_handle_exit(CPUState *env, struct kvm_run *run)
code);
if (host_supports_vmx() && code == VMX_INVALID_GUEST_STATE) {
fprintf(stderr,
- "\nIf you're runnning a guest on an Intel machine without "
+ "\nIf you're running a guest on an Intel machine without "
"unrestricted mode\n"
"support, the failure can be most likely due to the guest "
"entering an invalid\n"