summaryrefslogtreecommitdiff
path: root/hurd/running/qemu.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2012-11-29 01:33:22 +0100
committerThomas Schwinge <tschwinge@gnu.org>2012-11-29 01:33:22 +0100
commit5bd36fdff16871eb7d06fc26cac07e7f2703432b (patch)
treeb430970a01dfc56b8d41979552999984be5c6dfd /hurd/running/qemu.mdwn
parent2603401fa1f899a8ff60ec6a134d5bd511073a9d (diff)
IRC.
Diffstat (limited to 'hurd/running/qemu.mdwn')
-rw-r--r--hurd/running/qemu.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn
index 512ea60..3648c7d 100644
--- a/hurd/running/qemu.mdwn
+++ b/hurd/running/qemu.mdwn
@@ -105,6 +105,16 @@ If your machine supports hardware acceleration, you should really use the kvm va
to the command line, see below, if you are running Linux kernels 2.6.37 or 2.6.38 else IRQs may hang sooner or later. The kvm irq problems will be solved in kernel 2.6.39.
+IRC, freenode, #hurd, 2012-08-29:
+
+ <braunr> youpi: do you remember which linux versions require the
+ -no-kvm-irqchip option ?
+ <braunr> your page indicates 2.6.37-38, but i'm seeing weird things on
+ 2.6.32
+ <braunr> looks like a good thing to use that option all the time actually
+ <gnu_srs> seems like kvm -h says: -no-kvm-irqchip and man kvm says:
+ -machine kernel_irqchip=off
+
/!\ Note that there are known performance issues with KVM on Linux 2.6.39
kernels, compared to 2.6.32: [[!debbug 634149]]. We're preparing on a change
on our side to work around this.