[haiku-bugs] Re: [Haiku] #8052: Haiku works very poorly as a guest under the Linux Kernel Virtual Machine QEMU KVM
- From: "Don Quixote" <trac@xxxxxxxxxxxx>
- Date: Wed, 26 Oct 2011 13:57:39 -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
Blocked By: | Blocking:
Has a Patch: 0 | Platform: x86
-------------------------+-------------------------------------------------
Comment (by Don Quixote):
mmlr, when my untar of buildtools completes I will try using just one
core. But the whole reason I tried KVM at all was that I hoped to speed
up builds by using both cores in my computer.
KVM allows one to configure how any storage unit appears to the guest. In
every case the real sorage unit on the host is my Micro Center USB stick.
W
When the guest sees the storage as USB passthrough or IDE, it works but is
slow. IDE seems to be faster than USB passthrough. I expect this is
because the implementation of USB passthrough in KVM is slow.
When the guest sees the storage as SCSI it cannot find the boot device.
This panic occurs very early on.
When the guest sees the storage as a USB disk it panics late in the boot,
but before the screen turns blue. This is 100% reproducible. I would
have thought this option would work the best. I will file a bug
specifically for this. I have a saved serial output log.
There is a cascading series of errors before it tries to enter KDL in this
case. The very last message is that it cannot enter the debugger, but the
actual problem occurs much earlier. It should be possible to enter KDL
early one, set a breakpoint to just before the first complaint, then look
at where the problem first begins to occur.
A gzip compressed tarball of yesterday's builtools SVN is 210805 kb. The
untar process has been running for about nine hours now. I don't want to
stop it until it completes, which I hope will be soon.
However it has been running without grinding completely to a halt as
always happened when I tried to check out from Subversion running Haiku.
While the filesystem performance is slow under KVM, it does seem to work
reliably. Perhaps my worst problem was accessing the network under KVM.
Is there a way to configure the build so that one does not build the
buildtools as well? That is not documented on the Haiku build
instructions page.
In any case, I think it is helpful to build from buildtools I built
myself, just to make sure that the latest buildtools SVN actually still
works right.
--
Ticket URL: <http://dev.haiku-os.org/ticket/8052#comment:4>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
