[haiku-bugs] Re: [Haiku] #8052: Haiku works very poorly as a guest under the Linux Kernel Virtual Machine QEMU KVM
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Wed, 26 Oct 2011 20:00:02 -0000
#8052: Haiku works very poorly as a guest under the Linux Kernel Virtual Machine
QEMU KVM
-------------------------+-------------------------------------------------
Reporter: Don | Owner: axeld
Quixote | Status: new
Type: bug | Milestone: R1
Priority: normal | Version: R1/Development
Component: | Keywords: kvm, kernel virtual machine, qemu,
System/Kernel | linux, ubuntu, virtualization, subversion,
Resolution: | signal, SIGKILL, bfs, filesystem, r42888
Blocked By: | Blocking:
Has a Patch: 0 | Platform: x86
-------------------------+-------------------------------------------------
Comment (by bonefish):
One question that comes to mind: Why do you want to punish yourself
building Haiku on an emulated Haiku? On your Linux host system Haiku can
be built a lot faster than on a Haiku installed on the same machine. And
an emulated Haiku is dramatically slower even. When you work on individual
libraries or applications, building on an emulated Haiku might make sense,
but the more has to be built the better are the turn-around times for
building on Linux. For kernel or driver work that doesn't need actual
hardware, it's the best option anyway.
Anyway, putting that many different issues into one ticket is really not a
good idea. Likely some get overlooked and the whole ticket gets really
bloated. Most developers don't like to have to read through a lot of text
and filter out the information that pertain to the problem they are
interested in.
Regarding the unkillable processes/threads, it's rather easy to see what
they are blocking at in the kernel debugger. If you follow the lock
holders recursively it's usually not that complicated to identify
deadlocks. From your description I'd guess there's something fishy with
the network driver and the thread is probably blocking on one of its
locking primitives and not being woken up. Please open a new ticket for
that and attach at least the stack trace for the thread in question and
the output of `thread -s <thread ID>`.
On a general note, virtualization support (particularly virtio) would be
very welcome. Please feel encouraged to work on it. :-)
--
Ticket URL: <http://dev.haiku-os.org/ticket/8052#comment:9>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
