|author||Samuel Thibault <email@example.com>||2016-08-28 22:08:26 +0200|
|committer||Samuel Thibault <firstname.lastname@example.org>||2016-08-28 22:08:26 +0200|
Complete commit 1f6eff (Drop -no-kvm-irqchip)
we don't have the issue without it any more, and it actually seems to pose other problems
2 files changed, 2 insertions, 16 deletions
diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn
index ef89ec1..369ceab 100644
@@ -95,21 +95,7 @@ Check that the kvm module is loaded:
More info on kvm at: http://www.linux-kvm.org/page/FAQ
-If your machine supports hardware acceleration, you should really use the kvm variant of qemu, as it speeds things quite a lot. Note however that kvm tends to make assumptions when accelerating things in the linux kernel, you may need some -no-kvm-something option. At the moment in Debian you need to pass
-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
- <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
+If your machine supports hardware acceleration, you should really use the kvm variant of qemu, as it speeds things quite a lot.
# HAP/EPT/NPT acceleration
diff --git a/open_issues/libpthread.mdwn b/open_issues/libpthread.mdwn
index 0294b00..274e7e3 100644
@@ -1061,7 +1061,7 @@ Most of the issues raised on this page has been resolved, a few remain.
<gnu_srs> kvm -m 1024 -net nic,model=rtl8139 -net
cache=writeback,index=0,media=disk,file=hurd-experimental.img -vnc :6
- -cdrom isos/netinst_2012-07-15.iso -no-kvm-irqchip
+ -cdrom isos/netinst_2012-07-15.iso
<braunr> what is the file system type where your disk image is stored ?
<braunr> and how much physical memory on the host ?