From: "Carlos A. M. dos Santos" <unixmania@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5313)
Date: Fri, 26 Sep 2008 12:52:20 -0300 [thread overview]
Message-ID: <e71790db0809260852r5fb2b7bcgf25b45e6241fd8c8@mail.gmail.com> (raw)
In-Reply-To: <48DCF9FC.2070708@codemonkey.ws>
On Fri, Sep 26, 2008 at 12:04 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> Matt wrote:
>>>
>>> Here is another experimental update that forces -lthr on 6.x, and
>>> also updates to qemu svn r5313:
>>> http://people.freebsd.org/~nox/qemu/qemu-devel-20080924.patch
>>>
>>
>> I just built this update and it seems to have fixed the issue. Host
>> CPU usage again tracks with guest CPU usage and all seems well. I'll
>> continue to use this build to see if anything else crops up.
>>
>> Please let me know if there is anything other information I can provide.
>>
>
> If ya'll have patches to make QEMU work on FreeBSD, please submit them. I'm
> about to commit a patch that's what it took for me to get SVN working on
> FreeBSD.
>
> The one thing that really tripped me up with the whole aio kld-module thing.
> Perhaps we should detect the presence of the module at run time and disable
> aio? I assume kldload can only be run as root?
Yes, only root can load kernel modules. I think the best approach for
QEMU would be showing a message instructing the user kldload aio
and/or include a line in /boot/loader.conf countaining
aio_load="YES"
--
cd /usr/ports/sysutils/life
make clean
next prev parent reply other threads:[~2008-09-26 15:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 20:40 [Qemu-devel] qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates Juergen Lock
2008-09-22 15:30 ` Anthony Liguori
2008-09-24 21:52 ` Juergen Lock
2008-09-23 13:39 ` [Qemu-devel] " Matt
2008-09-24 22:10 ` [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5313) Juergen Lock
2008-09-25 2:54 ` Matt
2008-09-26 15:04 ` Anthony Liguori
2008-09-26 15:52 ` Carlos A. M. dos Santos [this message]
2008-09-26 22:04 ` Juergen Lock
2008-09-27 15:33 ` Anthony Liguori
2008-09-27 22:52 ` Juergen Lock
2008-09-30 14:51 ` Anthony Liguori
2008-09-30 22:17 ` Juergen Lock
2008-09-27 20:47 ` [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5331) Juergen Lock
2008-09-28 4:04 ` Carlos A. M. dos Santos
2008-09-30 22:33 ` Juergen Lock
2008-10-11 21:41 ` [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5457) Juergen Lock
2008-10-18 20:46 ` [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5499) Juergen Lock
2008-09-30 14:52 ` [Qemu-devel] Re: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5331) Anthony Liguori
2008-09-30 22:35 ` Juergen Lock
2008-09-25 20:17 ` [Qemu-devel] [PATCH] preprocessor issue in qemu/patch-block-raw-posix.c (was: qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates... (now updated to r5313)) Juergen Lock
2008-09-25 20:39 ` [Qemu-devel] [PATCH] preprocessor issue in qemu/patch-block-raw-posix.c Anthony Liguori
2008-09-26 21:29 ` Juergen Lock
2008-09-27 15:27 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e71790db0809260852r5fb2b7bcgf25b45e6241fd8c8@mail.gmail.com \
--to=unixmania@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).