Re: experimental qemu-devel port update, please test!
On 07/13/07 15:46, Juergen Lock wrote: On Thu, Jul 12, 2007 at 01:07:50PM -0500, Craig Boston wrote: On Thu, Jul 12, 2007 at 12:52:52PM -0500, Craig Boston wrote: For some reason when the ioctl is issued, curproc points to a totally bogus proc structure. curthread seems to be sane as far as I can tell, but the process it claims to belong to is full of junk. Aha! The problem isn't that curproc is garbage, but rather that it's being interpreted wrong. struct proc has some extra fields when KSE is #defined. KSE recently became a kernel option and was put in the DEFAULTS file, so everyone's kernel has it defined. But kqemu is being compiled without it. I compiled with -DKSE and now kqemu works! Aaah-haah! Thanks for catching this one! :) This seems like it would be a common problem for modules compiled outside the kernel tree. Is there an established way to get the standard configuration options? Good q... I'm thinking also about other options like SMP, that for instance changes the way mutexes work. Craig Okay what do you guys think about the following patch for now: (the SMP thing might actually be the cause for ports/113430, can someone verify?) The patch applies cleanly, and it builds. It also *WORKS*! :) I can't say anything about that PR though. Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: experimental qemu-devel port update, please test!
Craig Boston wrote: On Thu, Jul 12, 2007 at 12:52:52PM -0500, Craig Boston wrote: For some reason when the ioctl is issued, curproc points to a totally bogus proc structure. curthread seems to be sane as far as I can tell, but the process it claims to belong to is full of junk. Aha! The problem isn't that curproc is garbage, but rather that it's being interpreted wrong. struct proc has some extra fields when KSE is #defined. KSE recently became a kernel option and was put in the DEFAULTS file, so everyone's kernel has it defined. But kqemu is being compiled without it. I compiled with -DKSE and now kqemu works! This seems like it would be a common problem for modules compiled outside the kernel tree. Is there an established way to get the standard configuration options? I'm thinking also about other options like SMP, that for instance changes the way mutexes work. Great work! Thanks for chugging on it.. Do you think this could affect nvidia kernel modules? I think there was an alternate thread about nvidia modules causing systems to panic/lock up. Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: experimental qemu-devel port update, please test!
On 07/09/07 08:00, Eric Anderson wrote: Juergen Lock wrote: On Sun, Jul 08, 2007 at 01:15:35PM -0500, Eric Anderson wrote: On 07/07/07 09:02, Juergen Lock wrote: In article <[EMAIL PROTECTED]> you write: On 07/05/07 22:31, Eric Anderson wrote: [...] Although now I have the issue where using kqemu-kmod causes my system to reboot or power off. :( Any ideas? This seems to be a -current issue, it doesn't happen for me at least (6.2 and previously also 6.1.) You could check if it is dependent on the version of the used qemu (the 0.9.0 port, the version of qemu-devel in ports, or the not-yet-committed updated I posted), but I doubt it. What may help is finding out which commit to -current started kqemu to break (find an older version that worked, then binary-search), or at least a backtrace from a kernel compiled without -fomit-frame-pointer (putting DDB in the config seems to do that for amd64 at least, but rebuild the entire kernel.) There also is an open issue for kqemu on amd64 smp, http://www.freebsd.org/cgi/query-pr.cgi?pr=113430 dunno if its related... Juergen My host is i386, SMP, and it also happens with the current qemu-devel port. It must have been something in -CURRENT that changed, probably since May15th-ish. I can't do a binary search anytime soon to find it. In the past, I've recompiled kqemu and that has done the trick. I have all the debugging built in, but that doesn't stop the system from rebooting or powering off. Hmm an UP kernel might be worth a try too... Juergen Hmm - with and without UP, I get a panic, but I managed to catch a panic in _vm_map_lock, something like: _vm_map_lock() vm_map_wire() kqemu_lock_user_page() mon_user_map() I'll try to get a real bt.. Eric Hmm - I suspect this commit or something near it is the issue: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/vm/vm_map.c.diff?r1=1.384;r2=1.385;sortby=date;f=h;f=u Or the 1.384 -> 1.385 change by attilio@ (cc'ed). Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: experimental qemu-devel port update, please test!
Juergen Lock wrote: On Sun, Jul 08, 2007 at 01:15:35PM -0500, Eric Anderson wrote: On 07/07/07 09:02, Juergen Lock wrote: In article <[EMAIL PROTECTED]> you write: On 07/05/07 22:31, Eric Anderson wrote: [...] Although now I have the issue where using kqemu-kmod causes my system to reboot or power off. :( Any ideas? This seems to be a -current issue, it doesn't happen for me at least (6.2 and previously also 6.1.) You could check if it is dependent on the version of the used qemu (the 0.9.0 port, the version of qemu-devel in ports, or the not-yet-committed updated I posted), but I doubt it. What may help is finding out which commit to -current started kqemu to break (find an older version that worked, then binary-search), or at least a backtrace from a kernel compiled without -fomit-frame-pointer (putting DDB in the config seems to do that for amd64 at least, but rebuild the entire kernel.) There also is an open issue for kqemu on amd64 smp, http://www.freebsd.org/cgi/query-pr.cgi?pr=113430 dunno if its related... Juergen My host is i386, SMP, and it also happens with the current qemu-devel port. It must have been something in -CURRENT that changed, probably since May15th-ish. I can't do a binary search anytime soon to find it. In the past, I've recompiled kqemu and that has done the trick. I have all the debugging built in, but that doesn't stop the system from rebooting or powering off. Hmm an UP kernel might be worth a try too... Juergen Hmm - with and without UP, I get a panic, but I managed to catch a panic in _vm_map_lock, something like: _vm_map_lock() vm_map_wire() kqemu_lock_user_page() mon_user_map() I'll try to get a real bt.. Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: experimental qemu-devel port update, please test!
On 07/07/07 09:02, Juergen Lock wrote: In article <[EMAIL PROTECTED]> you write: On 07/05/07 22:31, Eric Anderson wrote: On 07/02/07 15:30, Juergen Lock wrote: Looks like its time for this again... Many bugs have been fixed, some features have been added, like, qemu-system-arm has grown emulation of a few PDAs like some Zaurus models, etc. As always, please test now, before I commit this, so we won't be in for nasty surprises afterwards... Works great so far on -CURRENT, thanks! Did the vmwarevga thing ever settle down, and become stable? Although now I have the issue where using kqemu-kmod causes my system to reboot or power off. :( Any ideas? This seems to be a -current issue, it doesn't happen for me at least (6.2 and previously also 6.1.) You could check if it is dependent on the version of the used qemu (the 0.9.0 port, the version of qemu-devel in ports, or the not-yet-committed updated I posted), but I doubt it. What may help is finding out which commit to -current started kqemu to break (find an older version that worked, then binary-search), or at least a backtrace from a kernel compiled without -fomit-frame-pointer (putting DDB in the config seems to do that for amd64 at least, but rebuild the entire kernel.) There also is an open issue for kqemu on amd64 smp, http://www.freebsd.org/cgi/query-pr.cgi?pr=113430 dunno if its related... Juergen My host is i386, SMP, and it also happens with the current qemu-devel port. It must have been something in -CURRENT that changed, probably since May15th-ish. I can't do a binary search anytime soon to find it. In the past, I've recompiled kqemu and that has done the trick. I have all the debugging built in, but that doesn't stop the system from rebooting or powering off. Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: experimental qemu-devel port update, please test!
On 07/05/07 22:31, Eric Anderson wrote: On 07/02/07 15:30, Juergen Lock wrote: Looks like its time for this again... Many bugs have been fixed, some features have been added, like, qemu-system-arm has grown emulation of a few PDAs like some Zaurus models, etc. As always, please test now, before I commit this, so we won't be in for nasty surprises afterwards... Works great so far on -CURRENT, thanks! Did the vmwarevga thing ever settle down, and become stable? Although now I have the issue where using kqemu-kmod causes my system to reboot or power off. :( Any ideas? Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: experimental qemu-devel port update, please test!
On 07/02/07 15:30, Juergen Lock wrote: Looks like its time for this again... Many bugs have been fixed, some features have been added, like, qemu-system-arm has grown emulation of a few PDAs like some Zaurus models, etc. As always, please test now, before I commit this, so we won't be in for nasty surprises afterwards... Works great so far on -CURRENT, thanks! Did the vmwarevga thing ever settle down, and become stable? Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: another qemu-devel port update ready for testing
On 05/27/07 13:52, Juergen Lock wrote:
On Sun, May 27, 2007 at 12:32:18PM -0500, Eric Anderson wrote:
On 05/27/07 07:58, Juergen Lock wrote:
On Sat, May 26, 2007 at 06:02:06PM -0500, Eric Anderson wrote:
On a recent -CURRENT (with the new GCC):
# make
...
===> Configuring for qemu-devel-0.9.0s.20070526
WARNING: "cc" looks like gcc 4.x
QEMU is known to have problems when compiled with gcc 4.x
It is recommended that you use gcc 3.x to build QEMU
To use this compiler anyway, configure with --disable-gcc-check
===> Script "configure" failed unexpectedly.
Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the
"/usr/ports/emulators/qemu-devel/work/qemu-snapshot-2007-05-26_05/config.log"
including the output of the failure of your make command. Also, it might
be
a good idea to provide an overview of all packages installed on your
system
(e.g. an `ls /var/db/pkg`).
*** Error code 1
Stop in /usr/ports/emulators/qemu-devel.
*** Error code 1
Stop in /usr/ports/emulators/qemu-devel.
Hmm that should not happen... Do you have an old version of
bsd.gcc.mk maybe?
Juergen
# $FreeBSD: ports/Mk/bsd.gcc.mk,v 1.12 2007/05/19 22:06:14 pav Exp $
That the right one?
Yeah. Ok probably CONFIGURE_ARGS needs to come after the
bsd.port.pre.mk include for it to pick up the right ${CC}... try this:
Same thing..
===> Vulnerability check disabled, database not found
===> Found saved configuration for qemu-devel-0.9.0s.20070526
===> Extracting for qemu-devel-0.9.0s.20070526
=> MD5 Checksum OK for qemu/qemu-snapshot-2007-05-26_05.tar.bz2.
=> SHA256 Checksum OK for qemu/qemu-snapshot-2007-05-26_05.tar.bz2.
===> qemu-devel-0.9.0s.20070526 depends on file:
/usr/local/bin/perl5.8.8 - found
===> Patching for qemu-devel-0.9.0s.20070526
===> qemu-devel-0.9.0s.20070526 depends on file:
/usr/local/bin/perl5.8.8 - found
===> Applying FreeBSD patches for qemu-devel-0.9.0s.20070526
===> qemu-devel-0.9.0s.20070526 depends on package:
kqemu-kmod>=1.3.0pre5 - found
===> qemu-devel-0.9.0s.20070526 depends on executable in : texi2html -
found
===> qemu-devel-0.9.0s.20070526 depends on executable in : gmake - found
===> qemu-devel-0.9.0s.20070526 depends on file:
/usr/local/bin/perl5.8.8 - found
===> qemu-devel-0.9.0s.20070526 depends on file:
/usr/local/bin/sdl-config - found
===> qemu-devel-0.9.0s.20070526 depends on shared library: SDL.11 - found
===> Configuring for qemu-devel-0.9.0s.20070526
WARNING: "cc" looks like gcc 4.x
QEMU is known to have problems when compiled with gcc 4.x
It is recommended that you use gcc 3.x to build QEMU
To use this compiler anyway, configure with --disable-gcc-check
===> Script "configure" failed unexpectedly.
Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the
"/usr/ports/emulators/qemu-devel/work/qemu-snapshot-2007-05-26_05/config.log"
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. an `ls /var/db/pkg`).
*** Error code 1
Stop in /usr/ports/emulators/qemu-devel.
*** Error code 1
Stop in /usr/ports/emulators/qemu-devel.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: another qemu-devel port update ready for testing
On 05/27/07 07:58, Juergen Lock wrote: On Sat, May 26, 2007 at 06:02:06PM -0500, Eric Anderson wrote: On a recent -CURRENT (with the new GCC): # make ... ===> Configuring for qemu-devel-0.9.0s.20070526 WARNING: "cc" looks like gcc 4.x QEMU is known to have problems when compiled with gcc 4.x It is recommended that you use gcc 3.x to build QEMU To use this compiler anyway, configure with --disable-gcc-check ===> Script "configure" failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the "/usr/ports/emulators/qemu-devel/work/qemu-snapshot-2007-05-26_05/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/emulators/qemu-devel. *** Error code 1 Stop in /usr/ports/emulators/qemu-devel. Hmm that should not happen... Do you have an old version of bsd.gcc.mk maybe? Juergen # $FreeBSD: ports/Mk/bsd.gcc.mk,v 1.12 2007/05/19 22:06:14 pav Exp $ That the right one? Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: another qemu-devel port update ready for testing
On a recent -CURRENT (with the new GCC):
# make
===> Vulnerability check disabled, database not found
===> Found saved configuration for qemu-0.9.0
=> qemu-snapshot-2007-05-26_05.tar.bz2 doesn't seem to exist in
/usr/ports/distfiles/qemu.
=> Attempting to fetch from http://qemu-forum.ipi.fi/qemu-snapshots/.
qemu-snapshot-2007-05-26_05.tar.bz2 100% of 1918 kB 72 kBps
00m00s
===> Extracting for qemu-devel-0.9.0s.20070526
=> MD5 Checksum OK for qemu/qemu-snapshot-2007-05-26_05.tar.bz2.
=> SHA256 Checksum OK for qemu/qemu-snapshot-2007-05-26_05.tar.bz2.
===> qemu-devel-0.9.0s.20070526 depends on file:
/usr/local/bin/perl5.8.8 - found
===> Patching for qemu-devel-0.9.0s.20070526
===> qemu-devel-0.9.0s.20070526 depends on file:
/usr/local/bin/perl5.8.8 - found
===> Applying FreeBSD patches for qemu-devel-0.9.0s.20070526
===> qemu-devel-0.9.0s.20070526 depends on package:
kqemu-kmod>=1.3.0pre5 - found
===> qemu-devel-0.9.0s.20070526 depends on executable in : texi2html -
found
===> qemu-devel-0.9.0s.20070526 depends on executable in : gmake - found
===> qemu-devel-0.9.0s.20070526 depends on file:
/usr/local/bin/perl5.8.8 - found
===> qemu-devel-0.9.0s.20070526 depends on file:
/usr/local/bin/sdl-config - found
===> qemu-devel-0.9.0s.20070526 depends on shared library: SDL.11 - found
===> Configuring for qemu-devel-0.9.0s.20070526
WARNING: "cc" looks like gcc 4.x
QEMU is known to have problems when compiled with gcc 4.x
It is recommended that you use gcc 3.x to build QEMU
To use this compiler anyway, configure with --disable-gcc-check
===> Script "configure" failed unexpectedly.
Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the
"/usr/ports/emulators/qemu-devel/work/qemu-snapshot-2007-05-26_05/config.log"
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. an `ls /var/db/pkg`).
*** Error code 1
Stop in /usr/ports/emulators/qemu-devel.
*** Error code 1
Stop in /usr/ports/emulators/qemu-devel.
On 05/26/07 13:17, Juergen Lock wrote:
It's been a while since I last updated the qemu-devel port, and
among many arm/mips/ppc/sparc imporvements there were also vmwarevga
and some i386/amd64 bugs fixed in qemu cvs, so possibly a few more
guests run now (also i386 guests on qemu-system-x86_64, there was
an mmu emulation bug fixed that could affect those.) I also would
like you to test existing guests that did already run correctly,
in order to catch possible regressions before I commit this update.
Thanx, and enjoy!
Juergen
Index: Makefile
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/Makefile,v
retrieving revision 1.77
diff -u -r1.77 Makefile
--- Makefile19 May 2007 20:04:37 - 1.77
+++ Makefile26 May 2007 15:29:44 -
@@ -6,8 +6,7 @@
#
PORTNAME= qemu
-PORTVERSION= 0.9.0s.20070405
-PORTREVISION= 4
+PORTVERSION= 0.9.0s.20070526
CATEGORIES=emulators
MASTER_SITES= http://qemu.org/:release \
http://qemu-forum.ipi.fi/qemu-snapshots/:snapshot \
@@ -15,7 +14,7 @@
http://www.volny.cz/xnavara/qemu/:snapshot \
http://people.brandeis.edu/~jcoiner/qemu_idedma/:idedma \
http://people.freebsd.org/~maho/qemu/:misc
-DISTNAME= ${PORTNAME}-snapshot-2007-04-05_05
+DISTNAME= ${PORTNAME}-snapshot-2007-05-26_05
DISTFILES= ${DISTNAME}${EXTRACT_SUFX}:snapshot
DIST_SUBDIR= qemu
EXTRACT_ONLY= ${DISTNAME}${EXTRACT_SUFX}
Index: distinfo
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/distinfo,v
retrieving revision 1.45
diff -u -r1.45 distinfo
--- distinfo7 Apr 2007 19:14:42 - 1.45
+++ distinfo26 May 2007 14:06:06 -
@@ -1,6 +1,6 @@
-MD5 (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) =
48321d0997db88f09f01d38500c52807
-SHA256 (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) =
48835ca90ced5cba2230fc95502b648167b5ca7247f885ee398ba891dbbf4c1b
-SIZE (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) = 1721640
+MD5 (qemu/qemu-snapshot-2007-05-26_05.tar.bz2) =
3fe2cf8c5cb26431499056bd08bb5be8
+SHA256 (qemu/qemu-snapshot-2007-05-26_05.tar.bz2) =
55e73f0593c5d31ba3483e8034542c5ab33217cc3048995dd94edf9640e8411e
+SIZE (qemu/qemu-snapshot-2007-05-26_05.tar.bz2) = 1964534
MD5 (qemu/patch3_cirrus) = ebe7ed9fce804c49e024bc93bfdfc810
SHA256 (qemu/patch3_cirrus) =
e862371834b7d895a896fbdb84fd9f70d17b5729a6f6789a48a61504fc941e11
SIZE (qemu/patch3_cirrus) = 8817
Index: pkg-plist
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/pkg-plist,v
retrieving revision 1.21
diff -u -r1.21 pkg-plist
--- pkg-plist 9 Apr 2007 22:11:23 - 1.21
+++ pkg-plist 26 May 2007 14:32:52 -
@@ -1,6 +1,7 @@
bin/qemu
bin/qemu-img
bin/qemu-system-arm
+bin/q
Re: experimental qemu-devel port update, please test!
On 04/05/07 16:03, Juergen Lock wrote: Hi! There have been a few interesting commits to qemu cvs, like, a qcow2 corruption bugfix, vmware vga emulation (-vmwarevga), and several emulated eepro100 (fxp) nic variants (-net nic,model=i82557b -net user worked for me with FreeBSD and linux guests, and seemed even slightly faster than the rtl8139 that already outperforms the default ne2kpci), so I prepared another qemu-devel port update that I now want you all to test with your various guests before I commit it! TIA, and enjoy... Juergen So far so good. All previous features seem to work, and the vmwarevga option does too. I'll try it with more testing this weekend, but it should be ok to commit I believe. Thanks a ton!! (looking forward to playing with the eepro driver!), Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: experimental qemu-devel port update, please test!
On 04/05/07 16:03, Juergen Lock wrote:
Hi!
There have been a few interesting commits to qemu cvs, like,
a qcow2 corruption bugfix, vmware vga emulation (-vmwarevga), and
several emulated eepro100 (fxp) nic variants (-net nic,model=i82557b
-net user worked for me with FreeBSD and linux guests, and seemed even
slightly faster than the rtl8139 that already outperforms the default
ne2kpci), so I prepared another qemu-devel port update that I now want
you all to test with your various guests before I commit it!
TIA, and enjoy...
Juergen
Remove files: files/patch-audio::ossaudio.c files/patch-bh
Building it now. Quick question: why have some diffs below in the
patch, when you say remove those files? Just curious..
Eric
Index: Makefile
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/Makefile,v
retrieving revision 1.72
diff -u -r1.72 Makefile
--- Makefile25 Mar 2007 16:33:01 - 1.72
+++ Makefile5 Apr 2007 16:08:57 -
@@ -6,7 +6,7 @@
#
PORTNAME= qemu
-PORTVERSION= 0.9.0s.20070322
+PORTVERSION= 0.9.0s.20070405
CATEGORIES=emulators
MASTER_SITES= http://qemu.org/:release \
http://qemu-forum.ipi.fi/qemu-snapshots/:snapshot \
@@ -14,7 +14,7 @@
http://www.volny.cz/xnavara/qemu/:snapshot \
http://people.brandeis.edu/~jcoiner/qemu_idedma/:idedma \
http://people.freebsd.org/~maho/qemu/:misc
-DISTNAME= ${PORTNAME}-snapshot-2007-03-22_05
+DISTNAME= ${PORTNAME}-snapshot-2007-04-05_05
DISTFILES= ${DISTNAME}${EXTRACT_SUFX}:snapshot
DIST_SUBDIR= qemu
EXTRACT_ONLY= ${DISTNAME}${EXTRACT_SUFX}
Index: distinfo
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/distinfo,v
retrieving revision 1.44
diff -u -r1.44 distinfo
--- distinfo25 Mar 2007 16:33:01 - 1.44
+++ distinfo5 Apr 2007 16:09:15 -
@@ -1,6 +1,6 @@
-MD5 (qemu/qemu-snapshot-2007-03-22_05.tar.bz2) =
b1d9d1b68094a9679b77d8b08796a7e4
-SHA256 (qemu/qemu-snapshot-2007-03-22_05.tar.bz2) =
be19f224e83fd90064f26b8d09fe018c4de7d27663f11544d494ac52d03808fa
-SIZE (qemu/qemu-snapshot-2007-03-22_05.tar.bz2) = 1685829
+MD5 (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) =
48321d0997db88f09f01d38500c52807
+SHA256 (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) =
48835ca90ced5cba2230fc95502b648167b5ca7247f885ee398ba891dbbf4c1b
+SIZE (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) = 1721640
MD5 (qemu/patch3_cirrus) = ebe7ed9fce804c49e024bc93bfdfc810
SHA256 (qemu/patch3_cirrus) =
e862371834b7d895a896fbdb84fd9f70d17b5729a6f6789a48a61504fc941e11
SIZE (qemu/patch3_cirrus) = 8817
Index: files/patch-audio::ossaudio.c
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/files/patch-audio::ossaudio.c,v
retrieving revision 1.2
diff -u -r1.2 patch-audio::ossaudio.c
--- files/patch-audio::ossaudio.c 10 Mar 2007 17:03:05 - 1.2
+++ files/patch-audio::ossaudio.c 5 Apr 2007 16:10:24 -
@@ -1,11 +0,0 @@
-Index: qemu/audio/ossaudio.c
-@@ -21,8 +21,8 @@
- * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
- * THE SOFTWARE.
- */
--#include
- #include
-+#include
- #include
- #include
- #include
Index: files/patch-bh
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/files/patch-bh,v
retrieving revision 1.4
diff -u -r1.4 patch-bh
--- files/patch-bh 10 Mar 2007 17:03:05 - 1.4
+++ files/patch-bh 5 Apr 2007 16:32:18 -
@@ -1,26 +0,0 @@
-Index: qemu/dyngen-exec.h
-===
-RCS file: /cvsroot/qemu/qemu/dyngen-exec.h,v
-retrieving revision 1.12
-diff -w -u -d -r1.12 dyngen-exec.h
dyngen-exec.h 12 May 2004 19:32:15 - 1.12
-+++ dyngen-exec.h 21 May 2004 15:00:41 -
-@@ -21,6 +21,8 @@
- #define __DYNGEN_EXEC_H__
-
- #include
-+#include
-+#include "config.h"
-
- typedef unsigned char uint8_t;
- typedef unsigned short uint16_t;
-@@ -54,9 +56,6 @@
- #define UINT32_MAX(4294967295U)
- #define UINT64_MAX((uint64_t)(18446744073709551615))
-
--typedef struct FILE FILE;
--extern int fprintf(FILE *, const char *, ...);
--extern int printf(const char *, ...);
- #undef NULL
- #define NULL 0
- #ifdef _BSD
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: experimental qemu-devel port (update), please test!
On 03/03/07 13:32, Juergen Lock wrote: In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] (Eric Anderson)writes: On 02/24/07 13:27, Juergen Lock wrote: On Sat, Feb 24, 2007 at 08:17:23PM +0100, Juergen Lock wrote: In article <[EMAIL PROTECTED]> you write: Is anyone else experiencing a nearly useless qemu experience with the latest versions? I'm running -CURRENT from yesterday, and the latest qemu port (and kqemu). These combinations segfault: Anything with the -vnc option, when disconnecting the vnc viewer, will segfault: sudo qemu -hda /alt/images/fs.img -hdb /alt/images/swapfile -net nic -net tap -snapshot -vnc :1 -serial /dev/ttyv8 -kernel-kqemu This used to work nicely, now it dies when I connect to port : sudo qemu -hda /alt/images/fs.img -hdb /alt/images/swapfile -net nic -net tap -snapshot -serial telnet::,server,nowait -std-vga -monitor stdio -full-screen -kernel-kqemu Which, when it dies, ktrace shows me: ... Hmm I don't know much about the code in question, you may have more luck reposting this on the qemu list: http://lists.gnu.org/mailman/listinfo/qemu-devel And just when I posted this... There were just patches posted on that list that fix vnc disconnect segfaults, so I think the next port update will fix at least that problem. Thanks! I've been hoping to see the update, but still not there yet.. :( Oh well. Sorry things are going a little slow around here... But now I have the following update for you all to test: 1. copy the qemu port dir (/usr/ports/emulators/qemu) to emulators/qemu-devel 2. apply the patch below in emulators 3. deinstall qemu 3. run `make install' in the new qemu-devel port dir (you probably cannot use portinstall/portupgrade unless you add the new port to INDEX yourself, that is until it is committed...) 4. test! Should you want to go back, deinstall qemu-devel and then install the originall qemu port again. I wonder if that will also fix my telnet issue with qemu. Not sure, but now you should be able to check yourself. :) I can confirm, this patch fixes both the vnc problem *and* the telnet issue. Woohoo!!! Thanks a ton! The only issue I see with VNC is one I've had since I tried using it 5-6 months ago, is corrupt video (during FreeBSD kernel boots, and console output, etc). I've never really tried it with higher resolution stuff though. Not a big deal.. Thanks for the patch!! Eric -- ---- Eric AndersonSr. Systems AdministratorCentaur Technology An undefined problem has an infinite number of solutions. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
