From: Matt <datahead4@gmail.com>
To: qemu-devel@nongnu.org, freebsd-emulation@freebsd.org
Subject: Re: [Qemu-devel] testing qemu svn r6367 on FreeBSD - sigev_signo; vmmouse, -vga vmware broken, slirp...
Date: Tue, 20 Jan 2009 13:31:42 -0600 [thread overview]
Message-ID: <cd6b4a5b0901201131x6dfcdf95vd3b9dfe4206c91f@mail.gmail.com> (raw)
In-Reply-To: <a17ba0c70324e3b3afb8417274a50943@iem.pw.edu.pl>
On Tue, Jan 20, 2009 at 8:19 AM, Jędrzej Kalinowski
<kalinoj1@iem.pw.edu.pl> wrote:
>
> On Mon, 19 Jan 2009 00:14:36 +0100, Juergen Lock <nox@jelal.kn-bremen.de>
> wrote:
>> Hi!
>>
>> I've made another experimental FreeBSD qemu-devel port update,
>> http://people.freebsd.org/~nox/qemu/qemu-devel-20090118.patch
>> and of the few things I've tested so far I only found vmmouse and -vga
>> vmware
>> broken now, vmmouse leaves the mouse cursor stuck in the top left corner,
>> and -vga vmware causes a broken display at least with xorg's vmware
> driver.
>> (both of these worked at least with the r6082, 2008-12-18 snapshot as
>> posted in
>> http://lists.gnu.org/archive/html/qemu-devel/2008-12/msg01417.html
>> )
>>
>> virtio and hpet still seem to work, and slirp indeed seems to finally
> work
>> on amd64 hosts.
>>
>>
>> More tests welcome...
>>
>
> Hello, I succesfully built it on CURRENT, however i get a segmentation
> fault, when trying
> to enter qemu monitor or serial console (left Alt+2,3).
This snapshot is working well for me on an amd64 host (with
kqemu-kmod) running -CURRENT from 1/8/2009 with WinXP guests.
> Can you reproduce this behaviour? The problem does not appear on your
> previous snapshot from 2008-12-18.
I can't reproduce this problem, but I'm running in headless mode only
and accessing the monitor and console via VNC so that might be a
difference.
Matt
>> Enjoy,
>> Juergen
>
>
> Regards,
> Jedrzej Kalinowski
>
>
> _______________________________________________
> freebsd-emulation@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org"
>
next prev parent reply other threads:[~2009-01-20 19:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 23:14 [Qemu-devel] testing qemu svn r6367 on FreeBSD - sigev_signo; vmmouse, -vga vmware broken, slirp Juergen Lock
2009-01-20 14:19 ` Jędrzej Kalinowski
2009-01-20 19:31 ` Matt [this message]
2009-01-20 23:12 ` More displaystate fallout? (was: Re: [Qemu-devel] testing qemu svn r6367 on FreeBSD - sigev_signo; vmmouse, -vga vmware broken, slirp...) Juergen Lock
2009-01-21 11:15 ` [Qemu-devel] Re: More displaystate fallout? (was: Re: [Qemu- devel] testing qemu svn r6367 on FreeB SD - sigev_signo; vmmouse, -vga vmware broken , slirp...) Jędrzej Kalinowski
2009-01-21 12:28 ` [Qemu-devel] Re: More displaystate fallout? Stefano Stabellini
2009-01-21 17:46 ` Stefan Weil
2009-01-21 18:15 ` Stefano Stabellini
2009-01-21 21:34 ` Stefan Weil
2009-01-22 14:11 ` Stefano Stabellini
2009-01-27 14:23 ` Stefano Stabellini
2009-01-29 14:55 ` Stefano Stabellini
2009-01-24 11:55 ` [Qemu-devel] testing qemu svn r6367 on FreeBSD - sigev_signo; vmmouse, -vga vmware broken, slirp Blue Swirl
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=cd6b4a5b0901201131x6dfcdf95vd3b9dfe4206c91f@mail.gmail.com \
--to=datahead4@gmail.com \
--cc=freebsd-emulation@freebsd.org \
--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).