1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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
License|/fdl]]."]]"""]]
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. jenkins.debian.net 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
https://www.mail-archive.com/kvm@vger.kernel.org/msg109570.html
|
