path: root/open_issues/kvm.mdwn
diff options
authorSamuel Thibault <>2015-02-18 00:58:35 +0100
committerSamuel Thibault <>2015-02-18 00:58:35 +0100
commit49a086299e047b18280457b654790ef4a2e5abfa (patch)
treec2b29e0734d560ce4f58c6945390650b5cac8a1b /open_issues/kvm.mdwn
parente2b3602ea241cd0f6bc3db88bf055bee459028b6 (diff)
Revert "rename open_issues.mdwn to service_solahart_jakarta_selatan__082122541663.mdwn"
This reverts commit 95878586ec7611791f4001a4ee17abf943fae3c1.
Diffstat (limited to 'open_issues/kvm.mdwn')
1 files changed, 37 insertions, 0 deletions
diff --git a/open_issues/kvm.mdwn b/open_issues/kvm.mdwn
new file mode 100644
index 00000000..327f97ca
--- /dev/null
+++ b/open_issues/kvm.mdwn
@@ -0,0 +1,37 @@
+[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]]
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+Issues when running Hurd under KVM: un-synced filesystems, etc. No problems
+with Virtualbox.
+2010-07-28, #hurd
+ <youpi> pochu: you were the one reporting issues with qemu/kvm and hurd, right?
+ <youpi> is your machine somehow smp (like multicore for instance)
+ <youpi> ?
+ <pochu> youpi: yes, it's a Core 2 Duo
+ <pochu> so 2 cores
+ <youpi> ok, you might want to try to bind qemu/kvm
+ <youpi> e.g. install hwloc, and prepend "hwloc-bind 1 --" before the qemu/kvm command line
+ <pochu> ok, ty
+2010-07-31, GNU Mach commit 039176372b4271f370ef38eb2ee5d43923a5b28b.
+# KVM-on-KVM (nested KVM)
+This seems sluggish like hell. suffers badly from it: it
+takes like an hour to complete the "Loading additional components" step.
+It's actually slower than just running qemu-on-KVM.
+This doesn't happen with Linux L2 guests.
+Date: Tue, 11 Nov 2014