From linimon at FreeBSD.org Sat Aug 1 18:26:00 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sat Aug 1 18:26:13 2009 Subject: ports/137332: add caution messages to some adobe products Message-ID: <200908011825.n71IPxWg099873@freefall.freebsd.org> Synopsis: add caution messages to some adobe products Responsible-Changed-From-To: freebsd-ports-bugs->emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sat Aug 1 18:24:15 UTC 2009 Responsible-Changed-Why: Over to maintainer of www/linux-flashplugin9. Someone there will have to figure out the maintainership of the various ports involved. http://www.freebsd.org/cgi/query-pr.cgi?pr=137332 From nox at jelal.kn-bremen.de Sun Aug 2 18:36:54 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun Aug 2 18:37:06 2009 Subject: ports/137281: update www/linux-f8-flashplugin10 In-Reply-To: <45094083@serv3.int.kfs.ru> References: <200907302340.n6UNeFYx057448@freefall.freebsd.org> <45094083@serv3.int.kfs.ru> Message-ID: <20090802181834.GA12442@triton.kn-bremen.de> On Fri, Jul 31, 2009 at 03:35:08PM +0400, Boris Samorodov wrote: >[...] > Can someone test the patch and report back? And it will be > good to create a patch for www/linux-f10-flashplugin10. Seems to be working here on 7-stable; and I just tested the following patch for www/linux-f10-flashplugin10 on head: Index: Makefile =================================================================== RCS file: /home/pcvs/ports/www/linux-f10-flashplugin10/Makefile,v retrieving revision 1.3 diff -u -p -r1.3 Makefile --- Makefile 3 Jul 2009 20:59:10 -0000 1.3 +++ Makefile 2 Aug 2009 17:43:29 -0000 @@ -7,7 +7,7 @@ # PORTNAME= flashplugin -PORTVERSION= 10.0r22 +PORTVERSION= 10.0r32 CATEGORIES= www multimedia linux MASTER_SITES= http://fpdownload.macromedia.com/get/flashplayer/current/:plugin \ ftp://ftp.ipt.ru/pub/download/:suplib @@ -27,7 +27,7 @@ RESTRICTED= Redistribution not allowed RESTRICTED_FILES= ${DISTFILES:Nlinux-f10-flashsupport*:C/:[^:]+$//} NO_BUILD= yes -WRKSRC= ${WRKDIR}/install_flash_player_10_linux +WRKSRC= ${WRKDIR} USE_NPAPI= linux-* NPAPI_FILES= libflashplayer.so Index: distinfo =================================================================== RCS file: /home/pcvs/ports/www/linux-f10-flashplugin10/distinfo,v retrieving revision 1.3 diff -u -p -r1.3 distinfo --- distinfo 3 Jul 2009 20:59:10 -0000 1.3 +++ distinfo 2 Aug 2009 17:43:29 -0000 @@ -1,6 +1,6 @@ -MD5 (flashplugin/10.0r22/install_flash_player_10_linux.tar.gz) = 23e4c2b844db0f87ff62084178aa2b1f -SHA256 (flashplugin/10.0r22/install_flash_player_10_linux.tar.gz) = cd29f166c87fecc943e88fe951bb61c56728fab12b4bf343badafa73ea95394e -SIZE (flashplugin/10.0r22/install_flash_player_10_linux.tar.gz) = 3994294 -MD5 (flashplugin/10.0r22/linux-f10-flashsupport-9.0.1.i386.tar.gz) = 6e416c81497f65065d78dae1e0acad0d -SHA256 (flashplugin/10.0r22/linux-f10-flashsupport-9.0.1.i386.tar.gz) = 4a309b1a326bd2212cc72480628659e5a7fd61d9e0572cb7350c206f030955bf -SIZE (flashplugin/10.0r22/linux-f10-flashsupport-9.0.1.i386.tar.gz) = 3455 +MD5 (flashplugin/10.0r32/install_flash_player_10_linux.tar.gz) = 6306980e40a3266b4b6c173bfcfdc946 +SHA256 (flashplugin/10.0r32/install_flash_player_10_linux.tar.gz) = 88aea5d73c5be37328a388630f8b89c256235c4f8337eef15ed523bbe3e5dada +SIZE (flashplugin/10.0r32/install_flash_player_10_linux.tar.gz) = 4044751 +MD5 (flashplugin/10.0r32/linux-f10-flashsupport-9.0.1.i386.tar.gz) = 6e416c81497f65065d78dae1e0acad0d +SHA256 (flashplugin/10.0r32/linux-f10-flashsupport-9.0.1.i386.tar.gz) = 4a309b1a326bd2212cc72480628659e5a7fd61d9e0572cb7350c206f030955bf +SIZE (flashplugin/10.0r32/linux-f10-flashsupport-9.0.1.i386.tar.gz) = 3455 From bsam at FreeBSD.org Mon Aug 3 09:37:56 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Mon Aug 3 09:38:02 2009 Subject: ports/137281: update www/linux-f8-flashplugin10 Message-ID: <200908030937.n739btDF080024@freefall.freebsd.org> Synopsis: update www/linux-f8-flashplugin10 State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Mon Aug 3 09:37:46 UTC 2009 State-Changed-Why: Committed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=137281 From dfilter at FreeBSD.ORG Mon Aug 3 09:40:04 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Mon Aug 3 09:40:10 2009 Subject: ports/137281: commit references a PR Message-ID: <200908030940.n739e3np080101@freefall.freebsd.org> The following reply was made to PR ports/137281; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/137281: commit references a PR Date: Mon, 3 Aug 2009 09:34:21 +0000 (UTC) bsam 2009-08-03 09:34:11 UTC FreeBSD ports repository Modified files: www/linux-f8-flashplugin10 Makefile distinfo Log: Update to version 10.0r32. PR: ports/137281 Submitted by: Tsurutani Naoki Tested by: nox Revision Changes Path 1.2 +2 -2 ports/www/linux-f8-flashplugin10/Makefile 1.2 +6 -6 ports/www/linux-f8-flashplugin10/distinfo _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From bsam at ipt.ru Mon Aug 3 09:56:04 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Aug 3 09:56:11 2009 Subject: ports/137281: update www/linux-f8-flashplugin10 In-Reply-To: <20090802181834.GA12442@triton.kn-bremen.de> (Juergen Lock's message of "Sun\, 2 Aug 2009 20\:18\:34 +0200") References: <200907302340.n6UNeFYx057448@freefall.freebsd.org> <45094083@serv3.int.kfs.ru> <20090802181834.GA12442@triton.kn-bremen.de> Message-ID: <12898677@bb.ipt.ru> On Sun, 2 Aug 2009 20:18:34 +0200 Juergen Lock wrote: > Seems to be working here on 7-stable; and I just tested the following > patch for www/linux-f10-flashplugin10 on head: Thanks for testing and the patch! Just has been committed. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From bugmaster at FreeBSD.org Mon Aug 3 11:06:48 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 3 11:07:26 2009 Subject: Current problem reports assigned to emulation@FreeBSD.org Message-ID: <200908031106.n73B6lSY088424@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/137332 emulation add caution messages to some adobe products 1 problem total. From bugmaster at FreeBSD.org Mon Aug 3 11:06:55 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 3 11:08:09 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200908031106.n73B6std088558@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135341 emulation [PATCH] linux-f10 ports that install manpages: add NOM o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o ports/135322 emulation Port graphics/linux_dri has incorrect packaging list c o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/97326 emulation [linux] file descriptor leakage in linux emulation o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 18 problems total. From linimon at FreeBSD.org Mon Aug 3 15:11:57 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon Aug 3 15:12:08 2009 Subject: ports/137332: add caution messages to some adobe products Message-ID: <200908031511.n73FBu8q085041@freefall.freebsd.org> Synopsis: add caution messages to some adobe products Responsible-Changed-From-To: emulation->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Aug 3 15:11:45 UTC 2009 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=137332 From linimon at FreeBSD.org Mon Aug 3 15:11:57 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon Aug 3 15:12:08 2009 Subject: ports/137332: add caution messages to some adobe products Message-ID: <200908031511.n73FBu8q085041@freefall.freebsd.org> Synopsis: add caution messages to some adobe products Responsible-Changed-From-To: emulation->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Aug 3 15:11:45 UTC 2009 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=137332 From lwindschuh at googlemail.com Wed Aug 5 23:17:46 2009 From: lwindschuh at googlemail.com (Lucius Windschuh) Date: Wed Aug 5 23:17:53 2009 Subject: Linuxolator panic: Lock (rw) Name Cache exclusively locked Message-ID: <90a5caac0908051556j27e721e2m25a949ade16848c1@mail.gmail.com> Hi. I tried to install CA Wily Introscope 8.1, an enterprise application performance monitoring framework, on FreeBSD. It is Java-based and works, if installed. Unfortunately, the installer panics my machine reproducably when it exits after the installation: panic: Lock (rw) Name Cache exclusively locked @ /usr/src/sys/kern/vfs_cache.c:589 I'm using -CURRENT r196074 (i386) at the moment. Kernel config: http://sites.google.com/site/lwfreebsd/Home/files/kernelconfig-CURRENT.txt?attredirects=0 I have a kernel dump for further analysis (the installation archive may not be published, I suppose): $ kgdb ... vmcore.12 (kgdb) bt #0 doadump () at pcpu.h:246 #1 0xc063cd1e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:419 #2 0xc063cff2 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:575 #3 0xc067e515 in witness_assert (lock=0xc0b160fc, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/subr_witness.c:2235 #4 0xc063a1d5 in _rw_assert (rw=0xc0b160fc, what=Variable "what" is not available. ) at /usr/src/sys/kern/kern_rwlock.c:1020 #5 0xc063a80b in _rw_runlock (rw=0xc0b160fc, file=0xc0905c58 "/usr/src/sys/kern/vfs_cache.c", line=589) at /usr/src/sys/kern/kern_rwlock.c:526 #6 0xc06b8297 in cache_lookup (dvp=0xc733c218, vpp=0xf63fcc70, cnp=0xf63fcc00) at /usr/src/sys/kern/vfs_cache.c:589 #7 0xc06b837d in vfs_cache_lookup (ap=0xf63fcc48) at /usr/src/sys/kern/vfs_cache.c:881 #8 0xc08a79c2 in VOP_LOOKUP_APV (vop=0xc65ec880, a=0xf63fcc48) at vnode_if.c:123 #9 0xc0de7547 in linux_getcwd (td=0xc718e240, args=0xf63fccf8) at vnode_if.h:54 #10 0xc0898567 in syscall (frame=0xf63fcd38) at /usr/src/sys/i386/i386/trap.c:1073 #11 0xc087b8c0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:261 #12 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) Panicing the kernel with getcwd() is strange. :-D Lucius From tijl at ulyssis.org Thu Aug 6 09:31:11 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Thu Aug 6 09:31:17 2009 Subject: nspluginwrapper patch for testing (was: Re: flash10 vs f10) In-Reply-To: <20090630184146.GA39346@triton.kn-bremen.de> References: <20090628082701.GA34665@triton.kn-bremen.de> <20090630163841.GA28338@triton.kn-bremen.de> <20090630184146.GA39346@triton.kn-bremen.de> Message-ID: <200908061059.22997.tijl@ulyssis.org> On Tuesday 30 June 2009 20:41:46 Juergen Lock wrote: > New version that redirects possible error messages to /dev/null: > (in case limit is already lower than 32M...) > > Index: Makefile > =================================================================== > RCS file: /home/pcvs/ports/www/nspluginwrapper/Makefile,v > retrieving revision 1.13 > diff -u -p -r1.13 Makefile > --- Makefile 19 Mar 2009 17:28:49 -0000 1.13 > +++ Makefile 30 Jun 2009 16:31:29 -0000 > @@ -7,7 +7,7 @@ > > PORTNAME= nspluginwrapper > PORTVERSION= 1.2.2 > -PORTREVISION= 2 > +PORTREVISION= 3 > CATEGORIES= www linux emulators > MASTER_SITES= http://gwenole.beauchesne.info/projects/nspluginwrapper/files/ > DISTFILES= ${DISTNAME}${EXTRACT_SUFX} ${RPMFILE} > @@ -53,6 +53,8 @@ post-extract: > post-patch: > @${REINPLACE_CMD} -e 's,/usr/X11R6,${LOCALBASE},g' \ > ${WRKSRC}/src/npw-config.c > + ${RM} ${WRKSRC}/usr/lib/nspluginwrapper/i386/linux/npviewer.orig > + > post-install: > ${MKDIR} ${LIBDIR}/i386/linux > ${INSTALL_SCRIPT} ${WRKSRC}/usr/lib/nspluginwrapper/i386/linux/* \ > Index: files/patch-ulimit > @@ -0,0 +1,7 @@ > +Index: usr/lib/nspluginwrapper/i386/linux/npviewer > +@@ -1,4 +1,5 @@ > + #!/bin/sh > + TARGET_OS=linux > + TARGET_ARCH=i386 > ++ulimit -s 32768 2>/dev/null > + . /usr/local/lib/nspluginwrapper/noarch/npviewer Can this be committed before the 8.0 ports freeze? From bsam at ipt.ru Thu Aug 6 10:14:14 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Thu Aug 6 10:14:24 2009 Subject: nspluginwrapper patch for testing In-Reply-To: <200908061059.22997.tijl@ulyssis.org> (Tijl Coosemans's message of "Thu\, 6 Aug 2009 10\:59\:21 +0200") References: <20090628082701.GA34665@triton.kn-bremen.de> <20090630163841.GA28338@triton.kn-bremen.de> <20090630184146.GA39346@triton.kn-bremen.de> <200908061059.22997.tijl@ulyssis.org> Message-ID: <00375901@h30.sp.ipt.ru> On Thu, 6 Aug 2009 10:59:21 +0200 Tijl Coosemans wrote: > Can this be committed before the 8.0 ports freeze? According to the list this solution appears to be helpful, so the answer is "yes" (or rather "should"). Can you provide a commit log? -- WBR, bsam From lwindschuh at googlemail.com Thu Aug 6 11:31:14 2009 From: lwindschuh at googlemail.com (Lucius Windschuh) Date: Thu Aug 6 11:31:20 2009 Subject: Linuxolator panic: Lock (rw) Name Cache exclusively locked In-Reply-To: <20090806110335.GP1884@deviant.kiev.zoral.com.ua> References: <90a5caac0908051556j27e721e2m25a949ade16848c1@mail.gmail.com> <20090806110335.GP1884@deviant.kiev.zoral.com.ua> Message-ID: <90a5caac0908060431p3a18c5b7ra675a87f36473fe0@mail.gmail.com> Hi Kostik. 2009/8/6 Kostik Belousov : > On Thu, Aug 06, 2009 at 12:56:08AM +0200, Lucius Windschuh wrote: >> Hi. >> I tried to install CA Wily Introscope 8.1, an enterprise application >> performance monitoring framework, on FreeBSD. >> It is Java-based and works, if installed. >> Unfortunately, the installer panics my machine reproducably when it >> exits after the installation: >> panic: Lock (rw) Name Cache exclusively locked @ >> /usr/src/sys/kern/vfs_cache.c:589 >> [...] > Please try this patch. > > diff --git a/sys/kern/vfs_cache.c b/sys/kern/vfs_cache.c > index f21f4af..7854803 100644 > --- a/sys/kern/vfs_cache.c > +++ b/sys/kern/vfs_cache.c > @@ -416,7 +416,8 @@ retry_wlocked: > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?if (dvp->v_cache_dd->nc_flag & NCF_ISDOTDOT) > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?cache_zap(dvp->v_cache_dd); > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?dvp->v_cache_dd = NULL; > - ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? goto unlock; > + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? CACHE_WUNLOCK(); > + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? return (0); > ? ? ? ? ? ? ? ? ? ? ? ?} > ? ? ? ? ? ? ? ? ? ? ? ?if (dvp->v_cache_dd->nc_flag & NCF_ISDOTDOT) > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?*vpp = dvp->v_cache_dd->nc_vp; > This lets me install Introscope without a panic. Thank you for the fast response. Lucius From kostikbel at gmail.com Thu Aug 6 11:43:46 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Thu Aug 6 11:43:52 2009 Subject: Linuxolator panic: Lock (rw) Name Cache exclusively locked In-Reply-To: <90a5caac0908051556j27e721e2m25a949ade16848c1@mail.gmail.com> References: <90a5caac0908051556j27e721e2m25a949ade16848c1@mail.gmail.com> Message-ID: <20090806110335.GP1884@deviant.kiev.zoral.com.ua> On Thu, Aug 06, 2009 at 12:56:08AM +0200, Lucius Windschuh wrote: > Hi. > I tried to install CA Wily Introscope 8.1, an enterprise application > performance monitoring framework, on FreeBSD. > It is Java-based and works, if installed. > Unfortunately, the installer panics my machine reproducably when it > exits after the installation: > panic: Lock (rw) Name Cache exclusively locked @ > /usr/src/sys/kern/vfs_cache.c:589 > > I'm using -CURRENT r196074 (i386) at the moment. > Kernel config: http://sites.google.com/site/lwfreebsd/Home/files/kernelconfig-CURRENT.txt?attredirects=0 > > I have a kernel dump for further analysis (the installation archive > may not be published, I suppose): > > $ kgdb ... vmcore.12 > (kgdb) bt > #0 doadump () at pcpu.h:246 > #1 0xc063cd1e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:419 > #2 0xc063cff2 in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:575 > #3 0xc067e515 in witness_assert (lock=0xc0b160fc, flags=Variable > "flags" is not available. > ) > at /usr/src/sys/kern/subr_witness.c:2235 > #4 0xc063a1d5 in _rw_assert (rw=0xc0b160fc, what=Variable "what" is > not available. > ) > at /usr/src/sys/kern/kern_rwlock.c:1020 > #5 0xc063a80b in _rw_runlock (rw=0xc0b160fc, > file=0xc0905c58 "/usr/src/sys/kern/vfs_cache.c", line=589) > at /usr/src/sys/kern/kern_rwlock.c:526 > #6 0xc06b8297 in cache_lookup (dvp=0xc733c218, vpp=0xf63fcc70, cnp=0xf63fcc00) > at /usr/src/sys/kern/vfs_cache.c:589 > #7 0xc06b837d in vfs_cache_lookup (ap=0xf63fcc48) > at /usr/src/sys/kern/vfs_cache.c:881 > #8 0xc08a79c2 in VOP_LOOKUP_APV (vop=0xc65ec880, a=0xf63fcc48) > at vnode_if.c:123 > #9 0xc0de7547 in linux_getcwd (td=0xc718e240, args=0xf63fccf8) > at vnode_if.h:54 > #10 0xc0898567 in syscall (frame=0xf63fcd38) > at /usr/src/sys/i386/i386/trap.c:1073 > #11 0xc087b8c0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:261 > #12 0x00000033 in ?? () > Previous frame inner to this frame (corrupt stack?) > > Panicing the kernel with getcwd() is strange. :-D Please try this patch. diff --git a/sys/kern/vfs_cache.c b/sys/kern/vfs_cache.c index f21f4af..7854803 100644 --- a/sys/kern/vfs_cache.c +++ b/sys/kern/vfs_cache.c @@ -416,7 +416,8 @@ retry_wlocked: if (dvp->v_cache_dd->nc_flag & NCF_ISDOTDOT) cache_zap(dvp->v_cache_dd); dvp->v_cache_dd = NULL; - goto unlock; + CACHE_WUNLOCK(); + return (0); } if (dvp->v_cache_dd->nc_flag & NCF_ISDOTDOT) *vpp = dvp->v_cache_dd->nc_vp; -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090806/3bb9f4a4/attachment.pgp From tijl at ulyssis.org Thu Aug 6 12:21:10 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Thu Aug 6 12:21:17 2009 Subject: nspluginwrapper patch for testing In-Reply-To: <00375901@h30.sp.ipt.ru> References: <20090628082701.GA34665@triton.kn-bremen.de> <200908061059.22997.tijl@ulyssis.org> <00375901@h30.sp.ipt.ru> Message-ID: <200908061418.36989.tijl@ulyssis.org> On Thursday 06 August 2009 12:14:10 Boris Samorodov wrote: > On Thu, 6 Aug 2009 10:59:21 +0200 Tijl Coosemans wrote: >> Can this be committed before the 8.0 ports freeze? > > According to the list this solution appears to be helpful, > so the answer is "yes" (or rather "should"). > > Can you provide a commit log? Limit the stack size for plugins. Linux glibc threading behaves slightly differently with a smaller stack size and the Flash plugins rely on this behaviour. Suggested by: dchagin Patch by: nox From scf at FreeBSD.org Thu Aug 6 14:15:14 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Thu Aug 6 14:15:22 2009 Subject: nspluginwrapper patch for testing In-Reply-To: <200908061418.36989.tijl@ulyssis.org> References: <20090628082701.GA34665@triton.kn-bremen.de> <200908061059.22997.tijl@ulyssis.org> <00375901@h30.sp.ipt.ru> <200908061418.36989.tijl@ulyssis.org> Message-ID: On Thu, 6 Aug 2009, Tijl Coosemans wrote: > On Thursday 06 August 2009 12:14:10 Boris Samorodov wrote: >> On Thu, 6 Aug 2009 10:59:21 +0200 Tijl Coosemans wrote: >>> Can this be committed before the 8.0 ports freeze? >> >> According to the list this solution appears to be helpful, >> so the answer is "yes" (or rather "should"). >> >> Can you provide a commit log? > > Limit the stack size for plugins. Linux glibc threading behaves > slightly differently with a smaller stack size and the Flash plugins > rely on this behaviour. > > Suggested by: dchagin > Patch by: nox Also, it helps for running Google Earth. Until I limited the stack size for it, it would crash if I zoomed in too close to the Earth. It still crashes for me when exiting Google Earth, but I am able to live with that. This is when running on i386 7-STABLE with the Nvidia driver v185.18.29. Sean -- scf@FreeBSD.org From tijl at ulyssis.org Thu Aug 6 15:13:13 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Thu Aug 6 15:13:20 2009 Subject: nspluginwrapper patch for testing In-Reply-To: References: <20090628082701.GA34665@triton.kn-bremen.de> <200908061418.36989.tijl@ulyssis.org> Message-ID: <200908061710.39039.tijl@ulyssis.org> On Thursday 06 August 2009 15:15:10 Sean C. Farley wrote: > On Thu, 6 Aug 2009, Tijl Coosemans wrote: >> On Thursday 06 August 2009 12:14:10 Boris Samorodov wrote: >>> On Thu, 6 Aug 2009 10:59:21 +0200 Tijl Coosemans wrote: >>>> Can this be committed before the 8.0 ports freeze? >>> >>> According to the list this solution appears to be helpful, >>> so the answer is "yes" (or rather "should"). >>> >>> Can you provide a commit log? >> >> Limit the stack size for plugins. Linux glibc threading behaves >> slightly differently with a smaller stack size and the Flash plugins >> rely on this behaviour. >> >> Suggested by: dchagin >> Patch by: nox > > Also, it helps for running Google Earth. Until I limited the stack size > for it, it would crash if I zoomed in too close to the Earth. It still > crashes for me when exiting Google Earth, but I am able to live with > that. This is when running on i386 7-STABLE with the Nvidia driver > v185.18.29. You mean a similar patch should applied to the google-earth port? From bsam at ipt.ru Thu Aug 6 16:00:14 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Thu Aug 6 16:00:37 2009 Subject: nspluginwrapper patch for testing In-Reply-To: <200908061418.36989.tijl@ulyssis.org> (Tijl Coosemans's message of "Thu\, 6 Aug 2009 14\:18\:35 +0200") References: <20090628082701.GA34665@triton.kn-bremen.de> <200908061059.22997.tijl@ulyssis.org> <00375901@h30.sp.ipt.ru> <200908061418.36989.tijl@ulyssis.org> Message-ID: <98610852@bb.ipt.ru> On Thu, 6 Aug 2009 14:18:35 +0200 Tijl Coosemans wrote: > On Thursday 06 August 2009 12:14:10 Boris Samorodov wrote: > > Can you provide a commit log? > Limit the stack size for plugins. Linux glibc threading behaves > slightly differently with a smaller stack size and the Flash plugins > rely on this behaviour. > Suggested by: dchagin > Patch by: nox Committed, thanks! -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From scf at FreeBSD.org Thu Aug 6 16:14:23 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Thu Aug 6 16:14:30 2009 Subject: nspluginwrapper patch for testing In-Reply-To: <200908061710.39039.tijl@ulyssis.org> References: <20090628082701.GA34665@triton.kn-bremen.de> <200908061418.36989.tijl@ulyssis.org> <200908061710.39039.tijl@ulyssis.org> Message-ID: On Thu, 6 Aug 2009, Tijl Coosemans wrote: > On Thursday 06 August 2009 15:15:10 Sean C. Farley wrote: >> On Thu, 6 Aug 2009, Tijl Coosemans wrote: >>> On Thursday 06 August 2009 12:14:10 Boris Samorodov wrote: >>>> On Thu, 6 Aug 2009 10:59:21 +0200 Tijl Coosemans wrote: >>>>> Can this be committed before the 8.0 ports freeze? >>>> >>>> According to the list this solution appears to be helpful, >>>> so the answer is "yes" (or rather "should"). >>>> >>>> Can you provide a commit log? >>> >>> Limit the stack size for plugins. Linux glibc threading behaves >>> slightly differently with a smaller stack size and the Flash plugins >>> rely on this behaviour. >>> >>> Suggested by: dchagin >>> Patch by: nox >> >> Also, it helps for running Google Earth. Until I limited the stack >> size for it, it would crash if I zoomed in too close to the Earth. >> It still crashes for me when exiting Google Earth, but I am able to >> live with that. This is when running on i386 7-STABLE with the >> Nvidia driver v185.18.29. > > You mean a similar patch should applied to the google-earth port? I am not sure. It helps me, but I do not know if my case is peculiar. I do not have this problem on an amd64 7-STABLE (same revision as above) using the radeonhd driver. However, on the amd64 system, the RV610 chip does not have hardware acceleration at this time. Can anyone replicate my problem? Sean -- scf@FreeBSD.org From nox at jelal.kn-bremen.de Thu Aug 6 16:52:59 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Thu Aug 6 16:53:05 2009 Subject: nspluginwrapper patch for testing In-Reply-To: <200908061710.39039.tijl@ulyssis.org> References: <20090628082701.GA34665@triton.kn-bremen.de> <200908061418.36989.tijl@ulyssis.org> <200908061710.39039.tijl@ulyssis.org> Message-ID: <20090806164652.GA9854@triton.kn-bremen.de> On Thu, Aug 06, 2009 at 05:10:37PM +0200, Tijl Coosemans wrote: > On Thursday 06 August 2009 15:15:10 Sean C. Farley wrote: > > On Thu, 6 Aug 2009, Tijl Coosemans wrote: > >> On Thursday 06 August 2009 12:14:10 Boris Samorodov wrote: > >>> On Thu, 6 Aug 2009 10:59:21 +0200 Tijl Coosemans wrote: > >>>> Can this be committed before the 8.0 ports freeze? > >>> > >>> According to the list this solution appears to be helpful, > >>> so the answer is "yes" (or rather "should"). > >>> > >>> Can you provide a commit log? > >> > >> Limit the stack size for plugins. Linux glibc threading behaves > >> slightly differently with a smaller stack size and the Flash plugins > >> rely on this behaviour. > >> > >> Suggested by: dchagin > >> Patch by: nox > > > > Also, it helps for running Google Earth. Until I limited the stack size > > for it, it would crash if I zoomed in too close to the Earth. It still > > crashes for me when exiting Google Earth, but I am able to live with > > that. This is when running on i386 7-STABLE with the Nvidia driver > > v185.18.29. > > You mean a similar patch should applied to the google-earth port? Yup, helps here too (I no longer need the cpuset -l 0 I reported here, http://docs.freebsd.org/cgi/mid.cgi?20090412201428.GA67309 ), so I committed it: http://www.freebsd.org/cgi/cvsweb.cgi/ports/astro/google-earth/files/patch-stacksize Thanx! :) Juergen From nox at jelal.kn-bremen.de Thu Aug 6 17:07:38 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Thu Aug 6 17:07:44 2009 Subject: nspluginwrapper patch for testing In-Reply-To: References: <20090628082701.GA34665@triton.kn-bremen.de> <200908061418.36989.tijl@ulyssis.org> <200908061710.39039.tijl@ulyssis.org> Message-ID: <20090806170526.GA10971@triton.kn-bremen.de> On Thu, Aug 06, 2009 at 11:14:22AM -0500, Sean C. Farley wrote: > On Thu, 6 Aug 2009, Tijl Coosemans wrote: > > > On Thursday 06 August 2009 15:15:10 Sean C. Farley wrote: > >> On Thu, 6 Aug 2009, Tijl Coosemans wrote: > >>> On Thursday 06 August 2009 12:14:10 Boris Samorodov wrote: > >>>> On Thu, 6 Aug 2009 10:59:21 +0200 Tijl Coosemans wrote: > >>>>> Can this be committed before the 8.0 ports freeze? > >>>> > >>>> According to the list this solution appears to be helpful, > >>>> so the answer is "yes" (or rather "should"). > >>>> > >>>> Can you provide a commit log? > >>> > >>> Limit the stack size for plugins. Linux glibc threading behaves > >>> slightly differently with a smaller stack size and the Flash plugins > >>> rely on this behaviour. > >>> > >>> Suggested by: dchagin > >>> Patch by: nox > >> > >> Also, it helps for running Google Earth. Until I limited the stack > >> size for it, it would crash if I zoomed in too close to the Earth. > >> It still crashes for me when exiting Google Earth, but I am able to > >> live with that. This is when running on i386 7-STABLE with the > >> Nvidia driver v185.18.29. > > > > You mean a similar patch should applied to the google-earth port? > > I am not sure. It helps me, but I do not know if my case is peculiar. > I do not have this problem on an amd64 7-STABLE (same revision as above) > using the radeonhd driver. However, on the amd64 system, the RV610 chip > does not have hardware acceleration at this time. Can anyone replicate > my problem? Already committed. :) (As Linux has a smaller stack by default iiuc its unlikely to hurt, and it _seems_ to help against the hangs/deadlocks I got which I used to work around by forcing googleearth onto a single cpu too.) Thanx, Juergen From scf at FreeBSD.org Thu Aug 6 17:20:11 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Thu Aug 6 17:20:19 2009 Subject: nspluginwrapper patch for testing In-Reply-To: <20090806170526.GA10971@triton.kn-bremen.de> References: <20090628082701.GA34665@triton.kn-bremen.de> <200908061418.36989.tijl@ulyssis.org> <200908061710.39039.tijl@ulyssis.org> <20090806170526.GA10971@triton.kn-bremen.de> Message-ID: On Thu, 6 Aug 2009, Juergen Lock wrote: > On Thu, Aug 06, 2009 at 11:14:22AM -0500, Sean C. Farley wrote: >> On Thu, 6 Aug 2009, Tijl Coosemans wrote: >>> On Thursday 06 August 2009 15:15:10 Sean C. Farley wrote: >>>> On Thu, 6 Aug 2009, Tijl Coosemans wrote: >>>>> On Thursday 06 August 2009 12:14:10 Boris Samorodov wrote: >>>>>> On Thu, 6 Aug 2009 10:59:21 +0200 Tijl Coosemans wrote: >>>>>>> Can this be committed before the 8.0 ports freeze? >>>>>> >>>>>> According to the list this solution appears to be helpful, >>>>>> so the answer is "yes" (or rather "should"). >>>>>> >>>>>> Can you provide a commit log? >>>>> >>>>> Limit the stack size for plugins. Linux glibc threading behaves >>>>> slightly differently with a smaller stack size and the Flash plugins >>>>> rely on this behaviour. >>>>> >>>>> Suggested by: dchagin >>>>> Patch by: nox >>>> >>>> Also, it helps for running Google Earth. Until I limited the stack >>>> size for it, it would crash if I zoomed in too close to the Earth. >>>> It still crashes for me when exiting Google Earth, but I am able to >>>> live with that. This is when running on i386 7-STABLE with the >>>> Nvidia driver v185.18.29. >>> >>> You mean a similar patch should applied to the google-earth port? >> >> I am not sure. It helps me, but I do not know if my case is >> peculiar. I do not have this problem on an amd64 7-STABLE (same >> revision as above) using the radeonhd driver. However, on the amd64 >> system, the RV610 chip does not have hardware acceleration at this >> time. Can anyone replicate my problem? > > Already committed. :) Thank you. > (As Linux has a smaller stack by default iiuc its unlikely to hurt, > and it _seems_ to help against the hangs/deadlocks I got which I used > to work around by forcing googleearth onto a single cpu too.) I am glad it helps. I wonder what other applications would benefit from this and if there is a more global way to set the default for Linux applications to a stack size of 32MB. Sean -- scf@FreeBSD.org From tijl at ulyssis.org Thu Aug 6 18:20:22 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Thu Aug 6 18:20:28 2009 Subject: nspluginwrapper patch for testing In-Reply-To: References: <20090628082701.GA34665@triton.kn-bremen.de> <20090806170526.GA10971@triton.kn-bremen.de> Message-ID: <200908062017.49082.tijl@ulyssis.org> On Thursday 06 August 2009 19:20:08 Sean C. Farley wrote: > I am glad it helps. I wonder what other applications would benefit > from this and if there is a more global way to set the default for > Linux applications to a stack size of 32MB. On amd64 you can add this to /etc/sysctl.conf (linux32 only) compat.linux32.maxssiz=33554432 On i386 you can add this to /boot/loader.conf (system wide) kern.maxssiz=33554432 From aus129 at gmail.com Fri Aug 7 00:01:54 2009 From: aus129 at gmail.com (Wesley Dyk) Date: Fri Aug 7 00:02:06 2009 Subject: How to Install Python 2.5 with Linux (2.6) ABI and linux_base-f8 Message-ID: <81739ca0908061629m207e3a93s66b9e5172ce3b0fd@mail.gmail.com> Has anyone installed a linux version of python 2.5 on FreeBSD? I need the Linux version to connect to Oracle via cx_Oracle. I have FreeBSD 7.2 installed with compat.linux.osrelease=2.6.16 in sysctl.conf, linux_base-f8 installed via ports and need to install a Linux version of Python 2.5. I have tried to install a compiled version from a fedora10 rpm with the command: rpm -i --ignoreos --root /compat/linux without success. I also tried to make python 2.5.4 on ubuntu jaunty, then copy the working folder to FreeBSD and install from there. The other option I have heard of is to compile python for the Linux ABI in FreeBSD, but I don't know if there is a specific port I need additionally to be able to do that. Thanks for the help! Aus From sfourman at gmail.com Fri Aug 7 06:53:01 2009 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Fri Aug 7 06:53:06 2009 Subject: nspluginwrapper patch for testing In-Reply-To: <200908062017.49082.tijl@ulyssis.org> References: <20090628082701.GA34665@triton.kn-bremen.de> <20090806170526.GA10971@triton.kn-bremen.de> <200908062017.49082.tijl@ulyssis.org> Message-ID: <11167f520908062352w62b4622ck681f9d7a59611c4c@mail.gmail.com> On Thu, Aug 6, 2009 at 1:17 PM, Tijl Coosemans wrote: > On Thursday 06 August 2009 19:20:08 Sean C. Farley wrote: >> I am glad it helps. ?I wonder what other applications would benefit >> from this and if there is a more global way to set the default for >> Linux applications to a stack size of 32MB. > > On amd64 you can add this to /etc/sysctl.conf (linux32 only) > compat.linux32.maxssiz=33554432 > > On i386 you can add this to /boot/loader.conf (system wide) > kern.maxssiz=33554432 is this flash tourtorial still reasonably up to date? for FreeBSD 8 of course use Fedora 10 linux emulation and flash 10. but I cant seem to get native firefox 3.5 to see teh flash 10 plugin. even after todays nspluginwrapper patch. Sam Fourman Jr. From bsam at ipt.ru Fri Aug 7 09:46:49 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri Aug 7 09:46:56 2009 Subject: How to Install Python 2.5 with Linux (2.6) ABI and linux_base-f8 In-Reply-To: <81739ca0908061629m207e3a93s66b9e5172ce3b0fd@mail.gmail.com> (Wesley Dyk's message of "Thu\, 6 Aug 2009 17\:29\:48 -0600") References: <81739ca0908061629m207e3a93s66b9e5172ce3b0fd@mail.gmail.com> Message-ID: <12842216@h30.sp.ipt.ru> (trim freebsd-python@, the topic is freebsd-emulation@ specific) On Thu, 6 Aug 2009 17:29:48 -0600 Wesley Dyk wrote: > I have tried to install a compiled version from a > fedora10 rpm with the command: > rpm -i --ignoreos --root /compat/linux To extract an rpm file to a current directory use: % rpm2cpio < /path/to/rpm/file | cpio -id Note: you should brandelf(1) any binary executable file extracted from a distro). -- WBR, bsam From bsam at ipt.ru Fri Aug 7 09:51:53 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri Aug 7 09:52:15 2009 Subject: [patch] www/linux-flashplugin9: new version Message-ID: <46761912@h30.sp.ipt.ru> Hi! Adobe released a new flashplugin9 version. I don't use it so I can suggest (a tinderbox tested) patch. Please, give it a try and submit a followup. Thanks! ----- Index: Makefile =================================================================== RCS file: /home/pcvs/ports/www/linux-flashplugin9/Makefile,v retrieving revision 1.34 diff -u -r1.34 Makefile --- Makefile 28 Apr 2009 00:18:42 -0000 1.34 +++ Makefile 7 Aug 2009 09:27:21 -0000 @@ -6,7 +6,7 @@ # PORTNAME= flashplugin -PORTVERSION= 9.0r159 +PORTVERSION= 9.0r246 CATEGORIES= www multimedia linux MASTER_SITES= http://download.macromedia.com/pub/flashplayer/installers/current/9/:plugin \ http://tijl.ulyssis.be/mirror/:suplib Index: distinfo =================================================================== RCS file: /home/pcvs/ports/www/linux-flashplugin9/distinfo,v retrieving revision 1.21 diff -u -r1.21 distinfo --- distinfo 2 Mar 2009 21:38:17 -0000 1.21 +++ distinfo 7 Aug 2009 09:27:21 -0000 @@ -1,6 +1,6 @@ -MD5 (flashplugin/9.0r159/install_flash_player_9.tar.gz) = 10f06f6a7aac488f4ce6a06f18e3d107 -SHA256 (flashplugin/9.0r159/install_flash_player_9.tar.gz) = fe7a55f86faf663b36befa19848ddd28f808666d5cf7b14311599128c6d85fb7 -SIZE (flashplugin/9.0r159/install_flash_player_9.tar.gz) = 3057882 -MD5 (flashplugin/9.0r159/libflashsupport.so) = c034ff03c92f94b2938062b6bbc02669 -SHA256 (flashplugin/9.0r159/libflashsupport.so) = d5c943e5a59016dcfeab5016d701e1e5e08fb30e8780d239053fec175b89d1e1 -SIZE (flashplugin/9.0r159/libflashsupport.so) = 44752 +MD5 (flashplugin/9.0r246/install_flash_player_9.tar.gz) = 47c0823400c2c711b8eefe67ad7efb20 +SHA256 (flashplugin/9.0r246/install_flash_player_9.tar.gz) = c2581cf5034a9adb9393acfd646d50608ab3a6a229c6f36a77ca9a8d8c5c6f07 +SIZE (flashplugin/9.0r246/install_flash_player_9.tar.gz) = 3057910 +MD5 (flashplugin/9.0r246/libflashsupport.so) = c034ff03c92f94b2938062b6bbc02669 +SHA256 (flashplugin/9.0r246/libflashsupport.so) = d5c943e5a59016dcfeab5016d701e1e5e08fb30e8780d239053fec175b89d1e1 +SIZE (flashplugin/9.0r246/libflashsupport.so) = 44752 ----- -- WBR, bsam From me at janh.de Fri Aug 7 11:48:46 2009 From: me at janh.de (Jan Henrik Sylvester) Date: Fri Aug 7 11:48:55 2009 Subject: [patch] www/linux-flashplugin9: new version Message-ID: <4A7C10BD.1070802@janh.de> Boris Samorodov wrote: > Adobe released a new flashplugin9 version. I don't use it > so I can suggest (a tinderbox tested) patch. Please, give > it a try and submit a followup. Thanks! > > ----- > Index: Makefile > =================================================================== > RCS file: /home/pcvs/ports/www/linux-flashplugin9/Makefile,v > retrieving revision 1.34 > diff -u -r1.34 Makefile > --- Makefile 28 Apr 2009 00:18:42 -0000 1.34 > +++ Makefile 7 Aug 2009 09:27:21 -0000 > @@ -6,7 +6,7 @@ > # > > PORTNAME= flashplugin > -PORTVERSION= 9.0r159 > +PORTVERSION= 9.0r246 I just tried with nspluginwrapper in native firefox35 on i386/7.2-RELEASE with linux_base-fc-4_14 and it works. Something is weird, tough, I have opened and closed three different pages with flash and still cannot find a core dump in my home directory... must be the latest patch to nspluginwrapper doing its job. :-) Please commit, Jan Henrik From bsam at ipt.ru Fri Aug 7 12:08:42 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri Aug 7 12:08:49 2009 Subject: [patch] www/linux-flashplugin9: new version In-Reply-To: <4A7C10BD.1070802@janh.de> (Jan Henrik Sylvester's message of "Fri\, 07 Aug 2009 13\:32\:13 +0200") References: <4A7C10BD.1070802@janh.de> Message-ID: <09312630@bb.ipt.ru> On Fri, 07 Aug 2009 13:32:13 +0200 Jan Henrik Sylvester wrote: > Boris Samorodov wrote: > > Adobe released a new flashplugin9 version. I don't use it > > so I can suggest (a tinderbox tested) patch. Please, give > > it a try and submit a followup. Thanks! > I just tried with nspluginwrapper in native firefox35 on > i386/7.2-RELEASE with linux_base-fc-4_14 and it works. Committed, thanks for the feedback! > Something is weird, tough, I have opened and closed three different > pages with flash and still cannot find a core dump in my home > directory... must be the latest patch to nspluginwrapper doing its > job. :-) :-) Good to know. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From blackend at freebsd.org Fri Aug 7 20:28:14 2009 From: blackend at freebsd.org (Marc Fonvieille) Date: Fri Aug 7 20:28:25 2009 Subject: [patch] www/linux-flashplugin9: new version In-Reply-To: <09312630@bb.ipt.ru> References: <4A7C10BD.1070802@janh.de> <09312630@bb.ipt.ru> Message-ID: <20090807201437.GA20151@abigail.blackend.org> On Fri, Aug 07, 2009 at 04:08:41PM +0400, Boris Samorodov wrote: > On Fri, 07 Aug 2009 13:32:13 +0200 Jan Henrik Sylvester wrote: > > Boris Samorodov wrote: > > > > Adobe released a new flashplugin9 version. I don't use it > > > so I can suggest (a tinderbox tested) patch. Please, give > > > it a try and submit a followup. Thanks! > > > I just tried with nspluginwrapper in native firefox35 on > > i386/7.2-RELEASE with linux_base-fc-4_14 and it works. > > Committed, thanks for the feedback! > Same here, it works on 7-STABLE, with fc4 and firefox2 . -- Marc From edwin at FreeBSD.org Sat Aug 8 02:40:13 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Sat Aug 8 02:40:20 2009 Subject: ports/137554: port upgrade: ftp/linux-f10-curl Message-ID: <200908080240.n782eDxJ052216@freefall.freebsd.org> Synopsis: port upgrade: ftp/linux-f10-curl Responsible-Changed-From-To: freebsd-ports-bugs->emulation Responsible-Changed-By: edwin Responsible-Changed-When: Sat Aug 8 02:40:12 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=137554 From dougb at FreeBSD.org Sat Aug 8 05:34:06 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sat Aug 8 05:34:12 2009 Subject: virtualbox not building on -current Message-ID: <4A7D0804.5010408@FreeBSD.org> I have up to date -current and ports, and got the following errors trying to build virtualbox tonight: cd /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457 && /bin/sh env.sh && VBOX_LIBPATH_X11=/usr/local VBOX_FREEBSD_SRC=/sys /usr/local/bin/kmk BUILD_TYPE=debug Config.kmk:1666: /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/emulators/virtualbox/out/freebsd.x86/debug/GCCConfig.kmk: No such file or directory Config.kmk:3799: /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/emulators/virtualbox/out/freebsd.x86/debug/revision.kmk: No such file or directory /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/VBox/Devices/Makefile.kmk:37: /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/VBox/Devices/Storage/VBoxHDDFormats/Makefile.kmk: No such file or directory /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/VBox/Devices/Makefile.kmk:43: /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/VBox/Devices/PC/PXE/Makefile.kmk: No such file or directory /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/VBox/Makefile.kmk:60: /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/VBox/Debugger/Makefile.kmk: No such file or directory /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/VBox/Makefile.kmk:64: /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/VBox/RDP/Makefile.kmk: No such file or directory /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/libs/Makefile.kmk:51: /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/libs/curl-7.19.4/Makefile.kmk: No such file or directory /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/libs/Makefile.kmk:62: /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/libs/openssl-0.9.8k/Makefile.kmk: No such file or directory kmk: *** No rule to make target `/usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-2.2.51r20457/src/libs/openssl-0.9.8k/Makefile.kmk'. Stop. *** Error code 2 -- This .signature sanitized for your protection From bsam at FreeBSD.org Sat Aug 8 12:55:15 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Sat Aug 8 12:55:20 2009 Subject: ports/137554: port upgrade: ftp/linux-f10-curl Message-ID: <200908081255.n78CtEek072142@freefall.freebsd.org> Synopsis: port upgrade: ftp/linux-f10-curl State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Sat Aug 8 12:48:22 UTC 2009 State-Changed-Why: Committed with some changes. Your distfile was not correct. To create a correct one you should fetch a linux port and makesum with an option PACKAGE_BUILDING=YES. One more hint: a shar archieve is good for new ports (BTW, the base should not be a / file system -- the committers ports will be overwritten). For good patch one may checkout a port from cvs, apply changes and send a unified diff. Anyway thanks for the report and the patch, much appreciated! http://www.freebsd.org/cgi/query-pr.cgi?pr=137554 From dfilter at FreeBSD.ORG Sat Aug 8 13:00:13 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sat Aug 8 13:00:19 2009 Subject: ports/137554: commit references a PR Message-ID: <200908081300.n78D0CZq072265@freefall.freebsd.org> The following reply was made to PR ports/137554; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/137554: commit references a PR Date: Sat, 8 Aug 2009 12:48:17 +0000 (UTC) bsam 2009-08-08 12:48:01 UTC FreeBSD ports repository Modified files: ftp/linux-f10-curl Makefile distinfo.i386 Log: Update to version 7.19.4-6.fc10. PR: ports/137554 (based on) Submitted by: codebloc Revision Changes Path 1.10 +2 -2 ports/ftp/linux-f10-curl/Makefile 1.7 +9 -9 ports/ftp/linux-f10-curl/distinfo.i386 _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From bsam at FreeBSD.org Sat Aug 8 13:10:56 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Sat Aug 8 13:11:03 2009 Subject: ports/136321: x11-toolkits/linux-pango: please update linux based port of pango Message-ID: <200908081310.n78DAtuQ086015@freefall.freebsd.org> Synopsis: x11-toolkits/linux-pango: please update linux based port of pango State-Changed-From-To: open->feedback State-Changed-By: bsam State-Changed-When: Sat Aug 8 13:09:43 UTC 2009 State-Changed-Why: Sure we'll do it if you provide an URL for an updated rpm files, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=136321 From bsam at FreeBSD.org Sat Aug 8 14:16:38 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Sat Aug 8 14:16:44 2009 Subject: ports/135341: [PATCH] linux-f10 ports that install manpages: add NOMANCOMPRESS Message-ID: <200908081416.n78EGb8T035295@freefall.freebsd.org> Synopsis: [PATCH] linux-f10 ports that install manpages: add NOMANCOMPRESS State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Sat Aug 8 14:16:01 UTC 2009 State-Changed-Why: Fixes has been committed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=135341 From dfilter at FreeBSD.ORG Sat Aug 8 14:20:03 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sat Aug 8 14:20:09 2009 Subject: ports/135341: commit references a PR Message-ID: <200908081420.n78EK2km035398@freefall.freebsd.org> The following reply was made to PR ports/135341; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/135341: commit references a PR Date: Sat, 8 Aug 2009 14:15:41 +0000 (UTC) bsam 2009-08-08 14:15:32 UTC FreeBSD ports repository Modified files: databases/linux-f10-sqlite3 Makefile databases/linux-f8-sqlite3 Makefile ftp/linux-f10-curl Makefile ftp/linux-f8-curl Makefile textproc/linux-f10-libxml2 Makefile textproc/linux-f8-libxml2 Makefile Log: . LINUX_RPM ports install compressed manpages, so set MANCOMPRESSED=yes; . bump PORTREVISIONs. PR: ports/135341 Submitted by: amdmi3 Revision Changes Path 1.6 +2 -0 ports/databases/linux-f10-sqlite3/Makefile 1.5 +2 -1 ports/databases/linux-f8-sqlite3/Makefile 1.11 +2 -1 ports/ftp/linux-f10-curl/Makefile 1.7 +2 -1 ports/ftp/linux-f8-curl/Makefile 1.23 +2 -1 ports/textproc/linux-f10-libxml2/Makefile 1.21 +2 -1 ports/textproc/linux-f8-libxml2/Makefile _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From bsam at ipt.ru Sat Aug 8 14:50:02 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Sat Aug 8 14:50:59 2009 Subject: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Message-ID: <200908081450.n78Eo2ZP060610@freefall.freebsd.org> The following reply was made to PR ports/135337; it has been noted by GNATS. From: Boris Samorodov To: bug-followup@FreeBSD.org,amdmi3@amdmi3.ru Cc: Subject: Re: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Date: Sat, 08 Aug 2009 18:48:29 +0400 Yep, the first suggestion won't work at chroot. Your second workaround should be added with "... and create a link /usr/local/bin/bash -> /bin/bash". Not good either. The third one does not work. :-( The best I can advice here is to use linux interpreter at command line (so it won't be evaluated while running the script): ----- % /compat/linux/bin/sh /compat/linux/usr/bin/ldd /compat/linux/lib/libz.so.1 libc.so.6 => /lib/libc.so.6 (0x2bc39000) /lib/ld-linux.so.2 (0x00000000) ----- If anyone knows/suggests a better solution/patches -- I'm all ears. Thanks! -- WBR, bsam From nox at jelal.kn-bremen.de Sat Aug 8 16:19:10 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sat Aug 8 16:19:19 2009 Subject: virtualbox not building on -current In-Reply-To: <4A7D0804.5010408@FreeBSD.org> Message-ID: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> In article <4A7D0804.5010408@FreeBSD.org> you write: >I have up to date -current and ports, and got the following errors >trying to build virtualbox tonight: Yeah the port failed to build on head for me too, had to use the development vbox port svn that uses a later vbox snapshot: svn co http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox Rumor has it the official port should get an update at least before the 8.0-R ports freeze... HTH, Juergen From nox at jelal.kn-bremen.de Sat Aug 8 16:52:24 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sat Aug 8 16:52:30 2009 Subject: VirtualBox NAT network works or not? In-Reply-To: References: Message-ID: <200908081651.n78GpDjV004629@triton8.kn-bremen.de> In article you write: >On Tue, July 28, 2009 00:39, Jeremy Messenger wrote: >> Hello, >> >> I have installed VirtualBox and very surpised about that it's very fast. >> Very nice! >> >> But I have a problem with NAT network and uses DHCP in guest. It does not >> work. The host is yesterday -CURRENT and very latest installed ports with >> libtool 2.2. I don't know how I can debug it. I have decided to install >> VirtualBox in Windows 7 and I have setup very same exactly how I do with >> guest of FreeBSD 6.4. It works perfect. The only difference is that >> VirtualBox version is 3.x in Windows and 2.x in -CURRENT. It is either bug >> or not ready? I have tried to disable VT-x and it makes no difference. I >> have tried all network adapter and no difference. > I've had nat mode problems too (guests randomly failing to dhcp on the first attempt, have to manually run `dhclient eth0' a second time in the guest), and the official vbox changelog, http://www.virtualbox.org/wiki/Changelog mentions NAT: fixed network communication corruptions (bugs #4499, #4540, #4591, #4604) for their 3.0.4 release too, so maybe we just need to wait for these fixes to reach the FreeBSD port... >I've been using Vbox 3 in FreeBSD for a bit more of a week now, and it is >doing what I want it to. > >the svn > >svn co >http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox > >I can use nat, but still trying to figure out how to reach the vm using >network. if anyone has any leads. so far, the best thing I think is to >make a reverse tunnel using ssh. > vbox' nat mode, like qemu's, can map individual guest ports to ones on the host (port forwarding), see here for details: http://www.virtualbox.org/manual/UserManual.html#networking-nat >matheus > >ps: I can't use my amd64 vm's if not from 7.2-STABLE. -CURRENT is no good >in here, tested three diff machines by now. I have problems parsing this, :) you mean amd64 guests stopped working on -current? Guess I should test that here... HTH, Juergen From matheus at eternamente.info Sat Aug 8 17:27:24 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Sat Aug 8 17:27:33 2009 Subject: VirtualBox NAT network works or not? In-Reply-To: <200908081651.n78GpDjV004629@triton8.kn-bremen.de> References: <200908081651.n78GpDjV004629@triton8.kn-bremen.de> Message-ID: On Sat, August 8, 2009 13:51, Juergen Lock wrote: > In article you > write: >>On Tue, July 28, 2009 00:39, Jeremy Messenger wrote: >>> Hello, >>> >>> I have installed VirtualBox and very surpised about that it's very >>> fast. >>> Very nice! >>> >>> But I have a problem with NAT network and uses DHCP in guest. It does >>> not >>> work. The host is yesterday -CURRENT and very latest installed ports >>> with >>> libtool 2.2. I don't know how I can debug it. I have decided to install >>> VirtualBox in Windows 7 and I have setup very same exactly how I do >>> with >>> guest of FreeBSD 6.4. It works perfect. The only difference is that >>> VirtualBox version is 3.x in Windows and 2.x in -CURRENT. It is either >>> bug >>> or not ready? I have tried to disable VT-x and it makes no difference. >>> I >>> have tried all network adapter and no difference. >> > I've had nat mode problems too (guests randomly failing to dhcp on the > first attempt, have to manually run `dhclient eth0' a second time > in the guest), and the official vbox changelog, > http://www.virtualbox.org/wiki/Changelog > mentions > NAT: fixed network communication corruptions (bugs #4499, #4540, #4591, > #4604) > for their 3.0.4 release too, so maybe we just need to wait for these > fixes to reach the FreeBSD port... I had problems in a work box where ssh portforwarding was not good. the box has no firewall at all. the same thing worked here at home ok. >>I've been using Vbox 3 in FreeBSD for a bit more of a week now, and it is >>doing what I want it to. >> >>the svn >> >>svn co >>http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox >> >>I can use nat, but still trying to figure out how to reach the vm using >>network. if anyone has any leads. so far, the best thing I think is to >>make a reverse tunnel using ssh. >> > vbox' nat mode, like qemu's, can map individual guest ports to > ones on the host (port forwarding), see here for details: > http://www.virtualbox.org/manual/UserManual.html#networking-nat good to hear that, will read asap. thanks :) >>matheus >> >>ps: I can't use my amd64 vm's if not from 7.2-STABLE. -CURRENT is no good >>in here, tested three diff machines by now. > > I have problems parsing this, :) you mean amd64 guests stopped > working on -current? Guess I should test that here... I have two machines (real ones) running FreeBSD 7.2-STABLE (one from late July, other mid June) and using vbox from this svn port ok. I have amd64 vm's (one each) and VT-x is enabled in both (if is really working I can't tell, but I can use both cores in the vm and folding at home performance is paired to the real native linux) and it is quite stable. I'd really like to do this in 8.0 (now in beta state), but I'm unable to do so as I get errors from vbox or machine crashes. so 7.2-STABLE is ok but the soon to be born 8.0 is not :( thanks, matheus > HTH, > Juergen > -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From segnetusers at gmail.com Sat Aug 8 18:58:17 2009 From: segnetusers at gmail.com (Segnet Webmail) Date: Sat Aug 8 18:58:24 2009 Subject: Upgrade your Account now!! Message-ID: Dear subcriber, This message is from segnet.com Internet webmail messaging center to all segnet.com Internet webmail account owners. We are currently upgrading our data base and e-mail account center. We are deleting all un-used segnet.com Internet webmail email account to create more space for new accounts. To prevent your account from closing you will have to update it below so that we will know that it's a present used account. PLEASE CONFIRM YOUR segnet.com Internet webmail EMAIL ACCOUNT IDENTITY BELOW NOW Email Username : .......... ..... EMAIL Password : ................ Date of Birth : ................. Country or Territory : .......... Warning!!! Account owner that refuses to update his or her account within three working days of receiving this warning will lose his or her account permanently. Thank you for using "segnet.com" segnet.com Internet webmail COMMUNICATION UNIIT From dougb at FreeBSD.org Sat Aug 8 19:01:08 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sat Aug 8 19:01:14 2009 Subject: virtualbox not building on -current In-Reply-To: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> References: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> Message-ID: <4A7DC528.4070306@FreeBSD.org> Juergen Lock wrote: > In article <4A7D0804.5010408@FreeBSD.org> you write: >> I have up to date -current and ports, and got the following errors >> trying to build virtualbox tonight: > > Yeah the port failed to build on head for me too, had to use the > development vbox port svn that uses a later vbox snapshot: > svn co http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox > > Rumor has it the official port should get an update at least before > the 8.0-R ports freeze... It would be really nice if we could get a working version of this for 8.0-RELEASE. Frankly I'm getting a little frustrated that this has never worked in HEAD for a lot of users, including me, and it doesn't seem to be getting any attention. Doug -- This .signature sanitized for your protection From beat at FreeBSD.org Sat Aug 8 19:47:42 2009 From: beat at FreeBSD.org (Beat Gaetzi) Date: Sat Aug 8 19:48:14 2009 Subject: virtualbox not building on -current In-Reply-To: <4A7DC528.4070306@FreeBSD.org> References: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> <4A7DC528.4070306@FreeBSD.org> Message-ID: <26f6c7210908081217u6935fedeobd936ccdfed63697@mail.gmail.com> 2009/8/8 Doug Barton : > Juergen Lock wrote: >> In article <4A7D0804.5010408@FreeBSD.org> you write: >>> I have up to date -current and ports, and got the following errors >>> trying to build virtualbox tonight: >> >> Yeah the port failed to build on head for me too, had to use the >> development vbox port svn that uses a later vbox snapshot: >> ? ? ? svn co http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox >> >> ?Rumor has it the official port should get an update at least before >> the 8.0-R ports freeze... > > It would be really nice if we could get a working version of this for > 8.0-RELEASE. Frankly I'm getting a little frustrated that this has > never worked in HEAD for a lot of users, including me, and it doesn't > seem to be getting any attention. The current svn port fixes a lot of known problems (also for HEAD) so I hope we could update the port before the port freeze. But there are still two issues which should be looked at first: - Patch files/patch-include-iprt-stdint.h fixes build on amd64. It works but I think it is not fixed the right way. This patch needs some review. - Some users reported problems updating virtualbox with portmaster (same problem with devel/kBuild). Unfortunately I hadn't time to verify this yet. Beat From bsam at ipt.ru Sat Aug 8 19:50:13 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Sat Aug 8 19:50:19 2009 Subject: virtualbox not building on -current In-Reply-To: <4A7DC528.4070306@FreeBSD.org> (Doug Barton's message of "Sat\, 08 Aug 2009 11\:34\:16 -0700") References: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> <4A7DC528.4070306@FreeBSD.org> Message-ID: <21782108@h30.sp.ipt.ru> On Sat, 08 Aug 2009 11:34:16 -0700 Doug Barton wrote: > Frankly I'm getting a little frustrated that this has > never worked in HEAD for a lot of users, Well, I've had just an opposite experience. Virtual box works for me even when it was not at ports. I've seen many reports from users and answers from both vitrualbox developer and our porters... > including me, and it doesn't > seem to be getting any attention. Maybe bad luck? Or was it my good luck? Anyway I have been using with success: ----- % uname -a FreeBSD bb.ipt.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Thu Jul 2 19:24:05 MSD 2009 root@bb.ipt.ru:/usr/obj/usr/src/sys/BB i386 [~]bsam@bb% pkg_info -Ix virtualbox virtualbox-2.2.51.r20457_3 A general-purpose full virtualizer for x86 hardware ----- -- WBR, bsam From dougb at FreeBSD.org Sat Aug 8 20:02:56 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sat Aug 8 20:03:03 2009 Subject: virtualbox not building on -current In-Reply-To: <26f6c7210908081217u6935fedeobd936ccdfed63697@mail.gmail.com> References: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> <4A7DC528.4070306@FreeBSD.org> <26f6c7210908081217u6935fedeobd936ccdfed63697@mail.gmail.com> Message-ID: <4A7DD9E4.3000900@FreeBSD.org> Beat Gaetzi wrote: > The current svn port fixes a lot of known problems (also for HEAD) so > I hope we could update the port before the port freeze. Can you post a patch to the existing port so that I can give it a try? > - Some users reported problems updating virtualbox with portmaster > (same problem with devel/kBuild). Unfortunately I hadn't time to > verify this yet. Yes, this is a known issue, and the problem is in kBuild. Portmaster uses a number of environment variables to do its work and they seem to be overflowing kBuild's stack. Doug -- This .signature sanitized for your protection From beat at FreeBSD.org Sat Aug 8 20:18:52 2009 From: beat at FreeBSD.org (Beat Gaetzi) Date: Sat Aug 8 20:18:59 2009 Subject: virtualbox not building on -current In-Reply-To: <4A7DD9E4.3000900@FreeBSD.org> References: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> <4A7DC528.4070306@FreeBSD.org> <26f6c7210908081217u6935fedeobd936ccdfed63697@mail.gmail.com> <4A7DD9E4.3000900@FreeBSD.org> Message-ID: <26f6c7210908081318p7b29d299yb27c826fba1438ff@mail.gmail.com> 2009/8/8 Doug Barton : > Beat Gaetzi wrote: > >> The current svn port fixes a lot of known problems (also for HEAD) so >> I hope we could update the port before the port freeze. > > Can you post a patch to the existing port so that I can give it a try? Please try this patch: http://people.freebsd.org/~beat/vbox/virtualbox-cvs-3.0.51r22072.patch >> - Some users reported problems updating virtualbox with portmaster >> (same problem with devel/kBuild). Unfortunately I hadn't time to >> verify this yet. > > Yes, this is a known issue, and the problem is in kBuild. Portmaster > uses a number of environment variables to do its work and they seem to > be overflowing kBuild's stack. I see. Thanks for the information. Beat From dougb at FreeBSD.org Sat Aug 8 23:08:31 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sat Aug 8 23:08:38 2009 Subject: virtualbox not building on -current In-Reply-To: <26f6c7210908081318p7b29d299yb27c826fba1438ff@mail.gmail.com> References: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> <4A7DC528.4070306@FreeBSD.org> <26f6c7210908081217u6935fedeobd936ccdfed63697@mail.gmail.com> <4A7DD9E4.3000900@FreeBSD.org> <26f6c7210908081318p7b29d299yb27c826fba1438ff@mail.gmail.com> Message-ID: <4A7E0565.4070002@FreeBSD.org> Beat Gaetzi wrote: > 2009/8/8 Doug Barton : >> Beat Gaetzi wrote: >> >>> The current svn port fixes a lot of known problems (also for HEAD) so >>> I hope we could update the port before the port freeze. >> Can you post a patch to the existing port so that I can give it a try? > > Please try this patch: > http://people.freebsd.org/~beat/vbox/virtualbox-cvs-3.0.51r22072.patch Ok, with that patch it builds, runs, and I can start installing WinXP. Unfortunately it panic'ed early in the process. I put the full core.txt.4 file in my home directory on freefall, but here is the first bit: panic: blockable sleep lock (sleep mutex) IPRT Event Semaphore @ /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22072/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:127 (kgdb) #0 doadump () at pcpu.h:246 #1 0xc05f11ae in boot (howto=260) at /usr/local/src/sys/kern/kern_shutdown.c:419 #2 0xc05f1482 in panic (fmt=Variable "fmt" is not available. ) at /usr/local/src/sys/kern/kern_shutdown.c:575 #3 0xc0631d90 in witness_checkorder (lock=0xc6249a20, flags=9, file=0xc619ff60 "/usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22072/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c", line=127, interlock=0x0) at /usr/local/src/sys/kern/subr_witness.c:1063 #4 0xc05e20e4 in _mtx_lock_flags (m=0xc6249a20, opts=0, file=0xc619ff60 "/usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22072/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c", line=127) at /usr/local/src/sys/kern/kern_mutex.c:200 #5 0xc618d45c in RTSemEventSignal (EventSem=0xc6249a10) at /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22072/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:127 #6 0xc61769b4 in SUPSemEventSignal (pSession=0xc593e410, hEvent=0x1) at /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22072/src/VBox/HostDrivers/Support/SUPDrv.c:3417 Then a whole bunch of stuff that looks like this: #124 0x00000000 in ?? () #125 0xe7d73280 in ?? () Then: #146 0xc05e1984 in _mtx_unlock_spin_flags (m=0x0, opts=731913140, file=0x1
, line=13944) at /usr/local/src/sys/kern/kern_mutex.c:267 Previous frame inner to this frame (corrupt stack?) (kgdb) -- This .signature sanitized for your protection From lumiwa at gmail.com Sun Aug 9 17:03:09 2009 From: lumiwa at gmail.com (ajtiM) Date: Sun Aug 9 17:03:16 2009 Subject: qlscribe Message-ID: <200908091135.52103.lumiwa@gmail.com> Hi! I try to run Lacie software for Lightscribe labeling but I am not lucky - there are no drive. Than I search on the Internet and found two applications which are under GNU Licences: http://sourceforge.net/projects/qlscribe/ and http://sourceforge.net/projects/qscribe/ I don't know if someone try this under linux emulation, please? I have no luck again.. Is it possible to ported for freebsd? Thanks in advance. -- Mitja ----- http://starikarp.redbubble.com From beat at FreeBSD.org Sun Aug 9 17:35:06 2009 From: beat at FreeBSD.org (Beat Gaetzi) Date: Sun Aug 9 17:35:12 2009 Subject: virtualbox not building on -current In-Reply-To: <4A7E0565.4070002@FreeBSD.org> References: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> <4A7DC528.4070306@FreeBSD.org> <26f6c7210908081217u6935fedeobd936ccdfed63697@mail.gmail.com> <4A7DD9E4.3000900@FreeBSD.org> <26f6c7210908081318p7b29d299yb27c826fba1438ff@mail.gmail.com> <4A7E0565.4070002@FreeBSD.org> Message-ID: <26f6c7210908091035y64099cb8i1a1860547d03fc83@mail.gmail.com> 2009/8/9 Doug Barton : > Beat Gaetzi wrote: >> 2009/8/8 Doug Barton : >>> Beat Gaetzi wrote: >>> >>>> The current svn port fixes a lot of known problems (also for HEAD) so >>>> I hope we could update the port before the port freeze. >>> Can you post a patch to the existing port so that I can give it a try? >> >> Please try this patch: >> http://people.freebsd.org/~beat/vbox/virtualbox-cvs-3.0.51r22072.patch > > Ok, with that patch it builds, runs, and I can start installing WinXP. > Unfortunately it panic'ed early in the process. Thanks for testing. This looks like a new problem so far. Is this panic reproducible? If yes, could you please add this patch to the port: http://people.freebsd.org/~beat/vbox/patch-src-VBox-Runtime-r0drv-semevent-r0drv-freebsd.c Beat From nox at jelal.kn-bremen.de Sun Aug 9 18:54:20 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun Aug 9 18:54:27 2009 Subject: experimental FreeBSD qemu 0.11.0-rc1 port update up for testing; unstable guest timer irqs and more Message-ID: <20090809185150.GA2688@triton8.kn-bremen.de> As qemu upstream has cut a new rc from its new 0.11 stable branch, http://lists.gnu.org/archive/html/qemu-devel/2009-07/msg02521.html I thought its time to start testing on FreeBSD and made a preliminary update for our qemu-devel port: http://people.freebsd.org/~nox/qemu/qemu-devel-0.11.0r1.patch I don't plan to commit this as it is, its just so we can test the new branch on FreeBSD easier... Some notes: 1. kqemu still works, but is disabled by default now so you'll have to pass -enable-kqemu (or -kernel-kqemu as with the previous versions) if you want to use it. 2. guest timer irqs seem to be even less stable when running qemu on FreeBSD 8 than they were on 7, I now regularly have to pass `no_timer_check' to linux guest kernels or they'd hang at boot after saying something like this: [...] Getting LVT1: 10000 enabled ExtINT on CPU#0 ENABLING IO-APIC IRQs ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 ..MP-BIOS bug: 8254 timer not connected to IO-APIC ...trying to set up timer (IRQ0) through the 8259A ... ..... (found apic 0 pin 2) ... ....... failed. ...trying to set up timer as Virtual Wire IRQ... I see reports of this on the net for qemu running on Linux hosts too tho, so this doesn't seem to be specific to FreeBSD. (And it has nothing to do with the new qemu branch, it happens here with 0.10.6 too, I just was testing qemu on FreeBSD 7 before only.) 3. The binutils in FreeBSD base are too old for as(1) to understand constructs used in multiboot.bin's asm source, so this port now depends on the new devel/binutils port and patches qemu/pc-bios/optionrom/Makefile to invoke the new as for the file in question. (see files/patch-pc-bios-optionrom-Makefile at the end of the patch; the same problem has been reported for OpenBSD on the qemu list before.) 4. There's a bug in qemu/osdep.c:kqemu_vmalloc(), it doesn't round its size arg up to full pages before calling mmap on the BSDs. Here is the patch: (files/patch-osdep.c in the port.) Index: qemu/osdep.c @@ -179,7 +179,9 @@ } unlink(phys_ram_file); } +#endif /* !(__OpenBSD__ || __FreeBSD__ || __DragonFly__) */ size = (size + 4095) & ~4095; +#if !defined(__OpenBSD__) && !defined(__FreeBSD__) && !defined(__DragonFly__) ftruncate(phys_ram_fd, phys_ram_size + size); #endif /* !(__OpenBSD__ || __FreeBSD__ || __DragonFly__) */ ptr = mmap(NULL, Ok I guess thats it for now. Happy testing... :) Juergen From josh.carroll at gmail.com Mon Aug 10 03:34:18 2009 From: josh.carroll at gmail.com (Josh Carroll) Date: Mon Aug 10 03:34:24 2009 Subject: VirtualBox 3 and VT-x support Message-ID: <8cb6106e0908092011t1d7a6cf8w7d45f52ddeb18055@mail.gmail.com> Hi, First of all, thanks to everyone involved for the terrific work in bringing VirtualBox to FreeBSD! It's great to have a viable virtual machine solution. I'm currently using the virtualbox-cvs-3.0.51r22072.patch patch and Vbox is running great for 32-bit guests on my 8.0-BETA2/amd64 system. However, I'm interested in running some 64-bit guests, and as I have an Intel CPU (core 2 quad 9550), I'm wondering if there is a rough timeline for when VT-x support may be available. Both to allow for 64-bit guests as well as the (I'm guessing) performance increases by using VT-x and of course support for > 1 CPU in the VM guest. If there's any help I can provide as far as testing, I'd be glad to help. Thanks! Josh From dougb at FreeBSD.org Mon Aug 10 04:10:38 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Mon Aug 10 04:10:45 2009 Subject: virtualbox not building on -current In-Reply-To: <26f6c7210908091035y64099cb8i1a1860547d03fc83@mail.gmail.com> References: <200908081617.n78GHUOW003735@triton8.kn-bremen.de> <4A7DC528.4070306@FreeBSD.org> <26f6c7210908081217u6935fedeobd936ccdfed63697@mail.gmail.com> <4A7DD9E4.3000900@FreeBSD.org> <26f6c7210908081318p7b29d299yb27c826fba1438ff@mail.gmail.com> <4A7E0565.4070002@FreeBSD.org> <26f6c7210908091035y64099cb8i1a1860547d03fc83@mail.gmail.com> Message-ID: <4A7F9DB5.503@FreeBSD.org> Beat Gaetzi wrote: > 2009/8/9 Doug Barton : >> Beat Gaetzi wrote: >>> 2009/8/8 Doug Barton : >>>> Beat Gaetzi wrote: >>>> >>>>> The current svn port fixes a lot of known problems (also for HEAD) so >>>>> I hope we could update the port before the port freeze. >>>> Can you post a patch to the existing port so that I can give it a try? >>> Please try this patch: >>> http://people.freebsd.org/~beat/vbox/virtualbox-cvs-3.0.51r22072.patch >> Ok, with that patch it builds, runs, and I can start installing WinXP. >> Unfortunately it panic'ed early in the process. > > Thanks for testing. This looks like a new problem so far. Well I'm not sure about that, it's never worked for me. I probably should have pointed out in the last message that I have a plain-vanilla -current running i386 SMP on an Intel C2D. I do have witness in my kernel which might be why some of these problems are showing up. > Is this > panic reproducible? If yes, could you please add this patch to the > port: > http://people.freebsd.org/~beat/vbox/patch-src-VBox-Runtime-r0drv-semevent-r0drv-freebsd.c With that patch I get an instant panic when I kldload vboxdrv: Unread portion of the kernel message buffer: VBoxDrvFreeBSDLoad: 6/0: off=10bc 5/0: off=54230 supdrvDetermineAsyncTsc: iCpu=0 cLoops=3 CurTsc=55fe8f3a692 PrevTsc=56146f4ffa6 supdrvDetermineAsyncTsc: returns 1; iLastCpu=31 rc=0 offMin=15e015914 offMax=15e015914 vboxdrv: fAsync=1 offMin=0x5e015914 offMax=0x5e015914 supdrvGipCreate: omni timer not supported, falling back to synchronous mode supdrvGipCreate: 10000000 nps ainnteirvcal:. sleeping without a lock VBoxDrvFreeBSDLoad: returns successfully cpuid = 1 (kgdb) #0 doadump () at pcpu.h:246 #1 0xc05f11ae in boot (howto=260) at /usr/local/src/sys/kern/kern_shutdown.c:419 #2 0xc05f1482 in panic (fmt=Variable "fmt" is not available. ) at /usr/local/src/sys/kern/kern_shutdown.c:575 #3 0xc05f9e28 in _sleep (ident=0xc7e6e910, lock=0x0, priority=84, wmesg=0xc91d6eee "iprtev", timo=0) at /usr/local/src/sys/kern/kern_synch.c:149 #4 0xc91c4175 in rtSemEventWait (EventSem=0xc7e6e910, cMillies=4294967295, fInterruptible=false) at /usr/local/home/dougb/virtualbox/work/virtualbox-3.0.51r22072/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:185 #5 0xc91c6617 in rtTimerThread (Thread=0xc7eff310, pvUser=0xc9004d10) at /usr/local/home/dougb/virtualbox/work/virtualbox-3.0.51r22072/src/VBox/Runtime/generic/timer-generic.cpp:244 #6 0xc91c3479 in rtThreadMain (pThread=0xc7eff310, NativeThread=3323851328, pszThreadName=0xc7eff350 "TIMER") at /usr/local/home/dougb/virtualbox/work/virtualbox-3.0.51r22072/src/VBox/Runtime/common/misc/thread.cpp:637 #7 0xc91c5d03 in rtThreadNativeMain (pvThreadInt=0xc7eff310) at /usr/local/home/dougb/virtualbox/work/virtualbox-3.0.51r22072/src/VBox/Runtime/r0drv/freebsd/thread2-r0drv-freebsd.c:112 #8 0xc05c7fa8 in fork_exit (callout=0xc91c5ce0 , arg=0xc7eff310, frame=0xe7decd38) at /usr/local/src/sys/kern/kern_fork.c:838 #9 0xc083e9c0 in fork_trampoline () at /usr/local/src/sys/i386/i386/exception.s:270 Full core.txt.5 is in my freefall home directory. Doug -- This .signature sanitized for your protection From blackend at FreeBSD.org Mon Aug 10 07:18:11 2009 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Mon Aug 10 07:18:18 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <00339944@bb.ipt.ru> References: <20090725013500.GC62402@onelab2.iet.unipi.it> <20090725073805.GA11455@abigail.blackend.org> <20090806211401.GB2546@pollux.local.net> <68208453@h30.sp.ipt.ru> <20090809160121.GA1621@pollux.local.net> <00339944@bb.ipt.ru> Message-ID: <20090810071850.GB1238@gothic.blackend.org> [moved to emulation@] On Sun, Aug 09, 2009 at 08:22:47PM +0400, Boris Samorodov wrote: > > Well, as for fc4 ports, Fedora Core 4 is unmaintained for > a long time and there is no hope to get an updated version. > The same seems to happen with f8 port. This is annoying cause it means default linux_base under 7.X is a "no way" in future: I mean when some linux apps will be updated people using 7.X and default linux_base may face up to issues. And on another hand I understood that some missing sysctl calls etc. prevents the switch to f10 under 7.X. So what is the good solution for the future? -- Marc From jochen.keil at gmail.com Mon Aug 10 10:30:59 2009 From: jochen.keil at gmail.com (Jochen Keil) Date: Mon Aug 10 10:31:06 2009 Subject: virtualbox-2.2.51.r20457_3 from ports Message-ID: <4A7FF1F3.8070506@gmail.com> Hello, After installing virtualbox from emulators ports i noticed several issues: * kldloading vboxdrv.ko crashed my box, loading on boot via loader.conf works with problems though * /usr/local/lib/virtualbox is only readable by root: $ ls -ld /usr/local/lib/virtualbox drwx------ 3 root wheel 1024 10 Aug 03:32 /usr/local/lib/virtualbox which means: $ ls -ld /usr/local/lib/virtualbox/VirtualBox ls: /usr/local/lib/virtualbox/VirtualBox: Permission denied i can start virtualbox as root though: $ sudo ls -ld /usr/local/lib/virtualbox/VirtualBox -r-s--x--x 1 root vboxusers 19236 10 Aug 03:32 /usr/local/lib/virtualbox/VirtualBox my user (that is me :) is a member of the vboxusers group. * /usr/local/lib seems a bit odd as an installation location for a freebsd user although somebody mentioned to me that this is/was common on system v and solaris. $ uname -a FreeBSD monolith.lokal.lan 7.2-STABLE FreeBSD 7.2-STABLE #0: Wed Aug 5 10:11:22 CEST 2009 root@monolith.lokal.lan:/usr/obj/usr/src/sys/MONOLITH i386 Regards, Jochen Keil P.S. Please add me to CC if you answer, since i did not subscribe to emulation@freebsd.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090810/a0265aae/signature.pgp From bugmaster at FreeBSD.org Mon Aug 10 11:06:54 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 10 11:07:48 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200908101106.n7AB6rHO025105@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/137332 emulation add caution messages to some adobe products f ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o ports/135322 emulation Port graphics/linux_dri has incorrect packaging list c o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/97326 emulation [linux] file descriptor leakage in linux emulation o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 18 problems total. From amdmi3 at amdmi3.ru Mon Aug 10 15:00:14 2009 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Mon Aug 10 15:00:20 2009 Subject: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Message-ID: <200908101500.n7AF0DbX014716@freefall.freebsd.org> The following reply was made to PR ports/135337; it has been noted by GNATS. From: Dmitry Marakasov To: Boris Samorodov Cc: bug-followup@FreeBSD.org Subject: Re: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Date: Mon, 10 Aug 2009 18:51:22 +0400 * Boris Samorodov (bsam@ipt.ru) wrote: > If anyone knows/suggests a better solution/patches -- I'm all ears. /usr/bin/env bash, perhaps? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From scf at FreeBSD.org Mon Aug 10 15:02:45 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Mon Aug 10 15:02:51 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <20090810071850.GB1238@gothic.blackend.org> References: <20090725013500.GC62402@onelab2.iet.unipi.it> <20090725073805.GA11455@abigail.blackend.org> <20090806211401.GB2546@pollux.local.net> <68208453@h30.sp.ipt.ru> <20090809160121.GA1621@pollux.local.net> <00339944@bb.ipt.ru> <20090810071850.GB1238@gothic.blackend.org> Message-ID: On Mon, 10 Aug 2009, Marc Fonvieille wrote: > On Sun, Aug 09, 2009 at 08:22:47PM +0400, Boris Samorodov wrote: >> >> Well, as for fc4 ports, Fedora Core 4 is unmaintained for a long time >> and there is no hope to get an updated version. The same seems to >> happen with f8 port. > > This is annoying cause it means default linux_base under 7.X is a "no > way" in future: I mean when some linux apps will be updated people > using 7.X and default linux_base may face up to issues. And on > another hand I understood that some missing sysctl calls etc. prevents > the switch to f10 under 7.X. So what is the good solution for the > future? I think at some point (MFC) after 7.2-RELEASE 7.x began working well enough to use F10 as the base. At least, GoogleEarth, UT99, Skype, Adobe Reader 8 (nspluginwrapper and standalone) and Flash (nspluginwrapper) work for me. There are some missing system calls, but I am not sure what applications will have trouble (not work as opposed to make warnings) without them. Sean -- scf@FreeBSD.org From bsam at ipt.ru Mon Aug 10 16:53:55 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Aug 10 16:54:03 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <20090810071850.GB1238@gothic.blackend.org> (Marc Fonvieille's message of "Mon\, 10 Aug 2009 09\:18\:50 +0200") References: <20090725013500.GC62402@onelab2.iet.unipi.it> <20090725073805.GA11455@abigail.blackend.org> <20090806211401.GB2546@pollux.local.net> <68208453@h30.sp.ipt.ru> <20090809160121.GA1621@pollux.local.net> <00339944@bb.ipt.ru> <20090810071850.GB1238@gothic.blackend.org> Message-ID: <78871850@bb.ipt.ru> On Mon, 10 Aug 2009 09:18:50 +0200 Marc Fonvieille wrote: > On Sun, Aug 09, 2009 at 08:22:47PM +0400, Boris Samorodov wrote: > > > > Well, as for fc4 ports, Fedora Core 4 is unmaintained for > > a long time and there is no hope to get an updated version. > > The same seems to happen with f8 port. > This is annoying cause it means default linux_base under 7.X is a "no > way" in future: I mean when some linux apps will be updated people using > 7.X and default linux_base may face up to issues. And on another hand I > understood that some missing sysctl calls etc. prevents the switch to > f10 under 7.X. So what is the good solution for the future? As Sean has said 7-STABLE is in a good state to use -f10- ports. However, even Fedora 10 distros have not been updated so far... If you need a workstation with modern linuxulator consider trying 8.x. Write here what is not working and we'll try to overcome it. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From bsam at ipt.ru Mon Aug 10 17:10:04 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Aug 10 17:10:10 2009 Subject: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Message-ID: <200908101710.n7AHA3wo014408@freefall.freebsd.org> The following reply was made to PR ports/135337; it has been noted by GNATS. From: Boris Samorodov To: Dmitry Marakasov Cc: bug-followup@FreeBSD.org Subject: Re: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Date: Mon, 10 Aug 2009 21:05:35 +0400 On Mon, 10 Aug 2009 18:51:22 +0400 Dmitry Marakasov wrote: > * Boris Samorodov (bsam@ipt.ru) wrote: > > If anyone knows/suggests a better solution/patches -- I'm all ears. > /usr/bin/env bash, perhaps? Whithout chroot the script will run as native FreeBSD script and won't look for linux paths. -- WBR, Boris Samorodov (bsam) From amdmi3 at amdmi3.ru Mon Aug 10 17:40:04 2009 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Mon Aug 10 17:40:11 2009 Subject: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Message-ID: <200908101740.n7AHe3xc038394@freefall.freebsd.org> The following reply was made to PR ports/135337; it has been noted by GNATS. From: Dmitry Marakasov To: Boris Samorodov Cc: bug-followup@FreeBSD.org Subject: Re: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Date: Mon, 10 Aug 2009 21:36:11 +0400 * Boris Samorodov (bsam@ipt.ru) wrote: > Whithout chroot the script will run as native FreeBSD script > and won't look for linux paths. Yes. Why is that bad? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From Carlos.Paniago at cnptia.embrapa.br Mon Aug 10 18:01:11 2009 From: Carlos.Paniago at cnptia.embrapa.br (Carlos Fernando Assis Paniago) Date: Mon Aug 10 18:01:18 2009 Subject: VirtualBox 3.0.4 Message-ID: <4A805C22.3070505@cnptia.embrapa.br> People: the virtualbox release the new version 3.0.4. Someone is trying to port this new version to freebsd? Paniago From bsam at ipt.ru Mon Aug 10 19:20:06 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Aug 10 19:20:21 2009 Subject: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Message-ID: <200908101920.n7AJK5R3013610@freefall.freebsd.org> The following reply was made to PR ports/135337; it has been noted by GNATS. From: Boris Samorodov To: Dmitry Marakasov Cc: bug-followup@FreeBSD.org Subject: Re: ports/135337: [PATCH] emulators/linux_base-f10: incorrect bash usage Date: Mon, 10 Aug 2009 23:15:58 +0400 On Mon, 10 Aug 2009 21:36:11 +0400 Dmitry Marakasov wrote: > * Boris Samorodov (bsam@ipt.ru) wrote: > > Whithout chroot the script will run as native FreeBSD script > > and won't look for linux paths. > Yes. Why is that bad? It just doesn't help! ;-) Well, at least not always. So it can't be a solution, just a new workaround. ----- % bash --version GNU bash, version 4.0.24(0)-release (i386-portbld-freebsd8.0) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. % ls file.1 file.2 % cat /compat/linux/usr/bin/test-ls #!/usr/bin/env bash listing=`dir $1` echo $listing % LANG=C /compat/linux/usr/bin/test-ls /compat/linux/usr/bin/test-ls: line 3: dir: command not found % /compat/linux/bin/bash /compat/linux/usr/bin/test-ls file.1 file.2 ----- -- WBR, bsam From decke at bluelife.at Mon Aug 10 19:45:19 2009 From: decke at bluelife.at (Bernhard =?iso-8859-1?Q?Fr=F6hlich?=) Date: Mon Aug 10 19:45:26 2009 Subject: VirtualBox 3.0.4 In-Reply-To: <4A805C22.3070505@cnptia.embrapa.br> References: <4A805C22.3070505@cnptia.embrapa.br> Message-ID: <0e7670d67d850c84034a53be5c7d6ad2.squirrel@webmail.itac.at> On Mon, August 10, 2009 7:42 pm, Carlos Fernando Assis Paniago wrote: > People: the virtualbox release the new version 3.0.4. Someone is trying > to port this new version to freebsd? > We're working on it. -- Bernhard Fr?hlich http://www.bluelife.at/ From rich at math.missouri.edu Mon Aug 10 20:18:16 2009 From: rich at math.missouri.edu (Rich Winkel) Date: Mon Aug 10 20:18:22 2009 Subject: Mathematica 7 license manager Message-ID: <20090810201815.GA48620@pencil.math.missouri.edu> I'm trying to run mathlm for mathematica version 7 under linux_base-fc-4_13 on freebsd 7.1-release-p7. It demonizes and appears to be happy until I try to run mathematica, then it crashes with signal 11. Even running monitorlm causes it to crash. Maxing out the loglevel doesn't produce any more info. Looking at the last access times in /compat/linux/etc, it opens host.conf, ld.so.cache and nsswitch.conf before dying. Has anyone seen this before? Any help would be much appreciated!! Rich From beat at FreeBSD.org Mon Aug 10 20:26:51 2009 From: beat at FreeBSD.org (Beat Gaetzi) Date: Mon Aug 10 20:26:57 2009 Subject: virtualbox-2.2.51.r20457_3 from ports In-Reply-To: <4A7FF1F3.8070506@gmail.com> References: <4A7FF1F3.8070506@gmail.com> Message-ID: <4A807ADB.6010104@FreeBSD.org> Hi, Jochen Keil wrote: > * kldloading vboxdrv.ko crashed my box, loading on boot via loader.conf > works with problems though This is a known problem. All known problems are documented on our wiki page: http://wiki.freebsd.org/VirtualBox > * /usr/local/lib/virtualbox is only readable by root: > $ ls -ld /usr/local/lib/virtualbox > drwx------ 3 root wheel 1024 10 Aug 03:32 /usr/local/lib/virtualbox Unfortunately I could not reproduce this problem here. What umask does your root user use? > * /usr/local/lib seems a bit odd as an installation location for a > freebsd user although somebody mentioned to me that this is/was common > on system v and solaris. Do to the virtualbox hardening we are forced to use this installation location. Beat From jochen.keil at gmail.com Mon Aug 10 20:59:48 2009 From: jochen.keil at gmail.com (Jochen Keil) Date: Mon Aug 10 20:59:54 2009 Subject: UNS: Re: virtualbox-2.2.51.r20457_3 from ports In-Reply-To: <4A807ADB.6010104@FreeBSD.org> (sfid-20090810_21550_4BA1DB1A) References: <4A7FF1F3.8070506@gmail.com> <4A807ADB.6010104@FreeBSD.org> (sfid-20090810_21550_4BA1DB1A) Message-ID: <4A8089C6.5040703@gmail.com> Hi, Beat Gaetzi wrote: >> * /usr/local/lib/virtualbox is only readable by root: >> $ ls -ld /usr/local/lib/virtualbox >> drwx------ 3 root wheel 1024 10 Aug 03:32 /usr/local/lib/virtualbox > > Unfortunately I could not reproduce this problem here. What umask does > your root user use? The umask is 022. But that's quite odd: i unpacked the .tbz from the port build (make package) to /tmp and took a look at the directories. The file permission were ok there. So i did a pkg_delete and performed a pkg_add with the same package. Now everything is fine in /usr/local too. The only difference is that i installed the package from ports first and now i installed the package (which was built by the ports system).. However, i am able run virtualbox as user now. Thanks and regards, Jochen -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090810/3eab8c24/signature.pgp From blackend at FreeBSD.org Tue Aug 11 07:02:09 2009 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Tue Aug 11 07:02:17 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <78871850@bb.ipt.ru> References: <20090725013500.GC62402@onelab2.iet.unipi.it> <20090725073805.GA11455@abigail.blackend.org> <20090806211401.GB2546@pollux.local.net> <68208453@h30.sp.ipt.ru> <20090809160121.GA1621@pollux.local.net> <00339944@bb.ipt.ru> <20090810071850.GB1238@gothic.blackend.org> <78871850@bb.ipt.ru> Message-ID: <20090811070254.GA1247@gothic.blackend.org> On Mon, Aug 10, 2009 at 08:53:57PM +0400, Boris Samorodov wrote: > On Mon, 10 Aug 2009 09:18:50 +0200 Marc Fonvieille wrote: > > On Sun, Aug 09, 2009 at 08:22:47PM +0400, Boris Samorodov wrote: > > > > > > Well, as for fc4 ports, Fedora Core 4 is unmaintained for > > > a long time and there is no hope to get an updated version. > > > The same seems to happen with f8 port. > > > This is annoying cause it means default linux_base under 7.X is a "no > > way" in future: I mean when some linux apps will be updated people using > > 7.X and default linux_base may face up to issues. And on another hand I > > understood that some missing sysctl calls etc. prevents the switch to > > f10 under 7.X. So what is the good solution for the future? > > As Sean has said 7-STABLE is in a good state to use -f10- ports. > However, even Fedora 10 distros have not been updated so far... > If you need a workstation with modern linuxulator consider trying > 8.x. Write here what is not working and we'll try to overcome it. > Well I'm not thinking about me but more about people who don't want to struggle with various fc4, f8 and f10 bits to make their apps working. In fact I'd like to have one "official" voice regarding this problem and follow it for example in our Handbook. Is there any project in switching linux-base from fc4 to f10 on 7.X branches? -- Marc From gary.jennejohn at freenet.de Tue Aug 11 09:41:19 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Tue Aug 11 09:41:25 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <78871850@bb.ipt.ru> References: <20090725013500.GC62402@onelab2.iet.unipi.it> <20090725073805.GA11455@abigail.blackend.org> <20090806211401.GB2546@pollux.local.net> <68208453@h30.sp.ipt.ru> <20090809160121.GA1621@pollux.local.net> <00339944@bb.ipt.ru> <20090810071850.GB1238@gothic.blackend.org> <78871850@bb.ipt.ru> Message-ID: <20090811114116.71e72ebb@ernst.jennejohn.org> On Mon, 10 Aug 2009 20:53:57 +0400 Boris Samorodov wrote: > On Mon, 10 Aug 2009 09:18:50 +0200 Marc Fonvieille wrote: > > On Sun, Aug 09, 2009 at 08:22:47PM +0400, Boris Samorodov wrote: > > > > > > Well, as for fc4 ports, Fedora Core 4 is unmaintained for > > > a long time and there is no hope to get an updated version. > > > The same seems to happen with f8 port. > > > This is annoying cause it means default linux_base under 7.X is a "no > > way" in future: I mean when some linux apps will be updated people using > > 7.X and default linux_base may face up to issues. And on another hand I > > understood that some missing sysctl calls etc. prevents the switch to > > f10 under 7.X. So what is the good solution for the future? > > As Sean has said 7-STABLE is in a good state to use -f10- ports. > However, even Fedora 10 distros have not been updated so far... > If you need a workstation with modern linuxulator consider trying > 8.x. Write here what is not working and we'll try to overcome it. > Well, I'm running an 8-current AMD64 installation. I installed nspluginwrapper-1.2.2_4 and linux-f10-flashplugin-10.0r32 today and now it's back to core dump city again. Older versions of these ports worked. I have compat.linux32.maxssiz=4194304 in /etc/sysctl.conf, which used to be all that was required for flash to work :( I've now deleted both ports. I can live without flash - just a report of my experience. --- Gary Jennejohn From rick-freebsd2008 at kiwi-computer.com Tue Aug 11 17:48:00 2009 From: rick-freebsd2008 at kiwi-computer.com (Rick C. Petty) Date: Tue Aug 11 17:48:07 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <20090811114116.71e72ebb@ernst.jennejohn.org> References: <20090725013500.GC62402@onelab2.iet.unipi.it> <20090725073805.GA11455@abigail.blackend.org> <20090806211401.GB2546@pollux.local.net> <68208453@h30.sp.ipt.ru> <20090809160121.GA1621@pollux.local.net> <00339944@bb.ipt.ru> <20090810071850.GB1238@gothic.blackend.org> <78871850@bb.ipt.ru> <20090811114116.71e72ebb@ernst.jennejohn.org> Message-ID: <20090811172117.GA66530@keira.kiwi-computer.com> On Tue, Aug 11, 2009 at 11:41:16AM +0200, Gary Jennejohn wrote: > > Well, I'm running an 8-current AMD64 installation. > > I installed nspluginwrapper-1.2.2_4 and linux-f10-flashplugin-10.0r32 > > today and now it's back to core dump city again. Older versions of these > ports worked. I am not having these problems. It just works perfectly. For the first time in a long time, audio and video seem sync'd. > I have compat.linux32.maxssiz=4194304 in /etc/sysctl.conf, which used to > be all that was required for flash to work :( Which version of linux_base do you have? Just for the record I have: amd64, r196088 of svn://svn.freebsd.org/base/stable/8 % pkg_info | grep -E '(firefox|linux_base|flashplugin|pluginwrapper)' firefox-3.0.13,1 Web browser based on the browser portion of Mozilla linux-f10-flashplugin-10.0r32 Adobe Flash Player NPAPI Plugin linux_base-f10-10_1 Base set of packages needed in Linux mode for i386/amd64 (L nspluginwrapper-1.2.2_4 A compatibility plugin for Netscape 4 (NPAPI) plugins % sysctl -a | grep compat.linux hw.snd.compat_linux_mmap: 0 compat.linux.oss_version: 198144 compat.linux.osrelease: 2.6.16 compat.linux.osname: Linux compat.linux32.maxvmem: 0 compat.linux32.maxssiz: 4194304 compat.linux32.maxdsiz: 536870912 % nspluginwrapper -l /home/rick/.mozilla/plugins/npwrapper.libflashplayer.so Original plugin: /usr/local/lib/firefox3/plugins/libflashplayer.so Wrapper version string: 1.2.2 -- Rick C. Petty From daichi at ongs.co.jp Wed Aug 12 00:56:27 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Wed Aug 12 00:56:35 2009 Subject: Flash10 on BETA2, by f10 / f8 Message-ID: <4A821338.5030301@ongs.co.jp> I have quick checked follow two flash10 behavior. 1) FreeBSD 8-BETA2/amd64 linux-f10-flashplugin-10.0r32 linux_base-f10 2) FreeBSD 8-BETA2/i386 linux-f10-flashplugin-10.0r32 linux_base-f8 Both look working well. I couldn't encounter a bug around playing movie. Great :) But in case 1), flash player cannot print Japanese font. In case 2), flash10 player displays Japaense text well. Anyone has any ideas? -- ONGS Inc. CEO, Daichi GOTO (daichi@ongs.co.jp) TEL: 81-42-316-7945 FAX: 81-42-316-7946 WWW: http://www.ongs.co.jp/ From gary.jennejohn at freenet.de Wed Aug 12 09:18:41 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Wed Aug 12 09:18:48 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <20090811172117.GA66530@keira.kiwi-computer.com> References: <20090725013500.GC62402@onelab2.iet.unipi.it> <20090725073805.GA11455@abigail.blackend.org> <20090806211401.GB2546@pollux.local.net> <68208453@h30.sp.ipt.ru> <20090809160121.GA1621@pollux.local.net> <00339944@bb.ipt.ru> <20090810071850.GB1238@gothic.blackend.org> <78871850@bb.ipt.ru> <20090811114116.71e72ebb@ernst.jennejohn.org> <20090811172117.GA66530@keira.kiwi-computer.com> Message-ID: <20090812111836.4413bbd4@ernst.jennejohn.org> On Tue, 11 Aug 2009 12:21:17 -0500 "Rick C. Petty" wrote: > Which version of linux_base do you have? Just for the record I have: > > amd64, r196088 of svn://svn.freebsd.org/base/stable/8 > My kernel is a little older, from July 25. I use cvsup to keep my sources up to date. I have linux_base-f10-10 installed, along with a slew of other f10-based ports. Looks like my Linux base is a little older than yours. With the old version of flash support I had a mixture of f10 and f8 ports installed. I'm using firefox35, but flash was working with this version before. Maybe I should just reinstall /compat/linux from scratch with the latest ports. --- Gary Jennejohn From chat95 at mac.com Wed Aug 12 09:49:24 2009 From: chat95 at mac.com (Maho NAKATA) Date: Wed Aug 12 09:49:30 2009 Subject: Flash10 on BETA2, by f10 / f8 In-Reply-To: <4A821338.5030301@ongs.co.jp> References: <4A821338.5030301@ongs.co.jp> Message-ID: <20090812.182131.4959786962467610.chat95@mac.com> Hi Just I'd like to know how you tested ;) thanks From: Daichi GOTO Subject: Flash10 on BETA2, by f10 / f8 Date: Wed, 12 Aug 2009 09:56:24 +0900 > I have quick checked follow two flash10 behavior. > > 1) > FreeBSD 8-BETA2/amd64 > linux-f10-flashplugin-10.0r32 > linux_base-f10 > > 2) > FreeBSD 8-BETA2/i386 > linux-f10-flashplugin-10.0r32 > linux_base-f8 > > Both look working well. I couldn't encounter a bug > around playing movie. Great :) > > But in case 1), flash player cannot print Japanese > font. In case 2), flash10 player displays Japaense > text well. > > Anyone has any ideas? > > -- > ONGS Inc. > CEO, Daichi GOTO (daichi@ongs.co.jp) > TEL: 81-42-316-7945 FAX: 81-42-316-7946 > WWW: http://www.ongs.co.jp/ > _______________________________________________ > 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" > From bsam at ipt.ru Wed Aug 12 11:51:18 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed Aug 12 11:51:25 2009 Subject: Flash10 on BETA2, by f10 / f8 In-Reply-To: <4A821338.5030301@ongs.co.jp> (Daichi GOTO's message of "Wed\, 12 Aug 2009 09\:56\:24 +0900") References: <4A821338.5030301@ongs.co.jp> Message-ID: <68130604@serv3.int.kfs.ru> Hi, Daichi GOTO writes: > I have quick checked follow two flash10 behavior. > > 1) > FreeBSD 8-BETA2/amd64 > linux-f10-flashplugin-10.0r32 > linux_base-f10 > > 2) > FreeBSD 8-BETA2/i386 > linux-f10-flashplugin-10.0r32 > linux_base-f8 There is a specail linux flashplugin port for linux_base-f8. It is www/linux-f8-flashplugin10. > Both look working well. I couldn't encounter a bug > around playing movie. Great :) > > But in case 1), flash player cannot print Japanese > font. In case 2), flash10 player displays Japaense > text well. Hm, I'd expect right the opposite with the latest ports (both linux-* and X11). The problem (I'm referring to) is with the fontconfig version. Only x11-fonts/linux-f10-fontconfig has a configuration file compatible with current X11 versions. > Anyone has any ideas? None for now, but can you post an output for: ----- % pkg_info | grep -E '(linux|fontconfig)' ----- -- WBR, bsam From bsam at ipt.ru Wed Aug 12 11:56:56 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Wed Aug 12 11:57:02 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <20090812111836.4413bbd4@ernst.jennejohn.org> (Gary Jennejohn's message of "Wed\, 12 Aug 2009 11\:18\:36 +0200") References: <20090725013500.GC62402@onelab2.iet.unipi.it> <20090725073805.GA11455@abigail.blackend.org> <20090806211401.GB2546@pollux.local.net> <68208453@h30.sp.ipt.ru> <20090809160121.GA1621@pollux.local.net> <00339944@bb.ipt.ru> <20090810071850.GB1238@gothic.blackend.org> <78871850@bb.ipt.ru> <20090811114116.71e72ebb@ernst.jennejohn.org> <20090811172117.GA66530@keira.kiwi-computer.com> <20090812111836.4413bbd4@ernst.jennejohn.org> Message-ID: <34211562@serv3.int.kfs.ru> Gary Jennejohn writes: > On Tue, 11 Aug 2009 12:21:17 -0500 > "Rick C. Petty" wrote: > >> Which version of linux_base do you have? Just for the record I have: >> >> amd64, r196088 of svn://svn.freebsd.org/base/stable/8 > > My kernel is a little older, from July 25. I use cvsup to keep my > sources up to date. > > I have linux_base-f10-10 installed, along with a slew of other f10-based > ports. Looks like my Linux base is a little older than yours. That should not be a problem imo... > With the old version of flash support I had a mixture of f10 and f8 ports > installed. ...while that may definitely be (inspite of the fact that sometime something works). > I'm using firefox35, but flash was working with this version before. > > Maybe I should just reinstall /compat/linux from scratch with the latest > ports. That is the best way. Please, report back your results. Thanks. -- WBR, bsam From daichi at ongs.co.jp Wed Aug 12 12:57:17 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Wed Aug 12 12:57:24 2009 Subject: Flash10 on BETA2, by f10 / f8 In-Reply-To: <20090812.182131.4959786962467610.chat95@mac.com> References: <4A821338.5030301@ongs.co.jp> <20090812.182131.4959786962467610.chat95@mac.com> Message-ID: <4A82BC2C.80904@ongs.co.jp> Maho NAKATA wrote: > Hi > > Just I'd like to know how you tested ;) > thanks I guess that nico nico douga is one of the best test beds web service for Flash behavior, movie playing, Japaense test displaying/inputing, locale checking and timezone checking. Or do you mean how to setup using flash10 and f10 base? > From: Daichi GOTO > Subject: Flash10 on BETA2, by f10 / f8 > Date: Wed, 12 Aug 2009 09:56:24 +0900 > >> I have quick checked follow two flash10 behavior. >> >> 1) >> FreeBSD 8-BETA2/amd64 >> linux-f10-flashplugin-10.0r32 >> linux_base-f10 >> >> 2) >> FreeBSD 8-BETA2/i386 >> linux-f10-flashplugin-10.0r32 >> linux_base-f8 >> >> Both look working well. I couldn't encounter a bug >> around playing movie. Great :) >> >> But in case 1), flash player cannot print Japanese >> font. In case 2), flash10 player displays Japaense >> text well. >> >> Anyone has any ideas? >> >> -- >> ONGS Inc. >> CEO, Daichi GOTO (daichi@ongs.co.jp) >> TEL: 81-42-316-7945 FAX: 81-42-316-7946 >> WWW: http://www.ongs.co.jp/ >> _______________________________________________ >> 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" -- ONGS Inc. CEO, Daichi GOTO (daichi@ongs.co.jp) TEL: 81-42-316-7945 FAX: 81-42-316-7946 WWW: http://www.ongs.co.jp/ From gary.jennejohn at freenet.de Wed Aug 12 14:31:16 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Wed Aug 12 14:31:29 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <34211562@serv3.int.kfs.ru> References: <20090725013500.GC62402@onelab2.iet.unipi.it> <20090725073805.GA11455@abigail.blackend.org> <20090806211401.GB2546@pollux.local.net> <68208453@h30.sp.ipt.ru> <20090809160121.GA1621@pollux.local.net> <00339944@bb.ipt.ru> <20090810071850.GB1238@gothic.blackend.org> <78871850@bb.ipt.ru> <20090811114116.71e72ebb@ernst.jennejohn.org> <20090811172117.GA66530@keira.kiwi-computer.com> <20090812111836.4413bbd4@ernst.jennejohn.org> <34211562@serv3.int.kfs.ru> Message-ID: <20090812163112.092df46c@ernst.jennejohn.org> On Wed, 12 Aug 2009 15:35:17 +0400 Boris Samorodov wrote: > Gary Jennejohn writes: > > Maybe I should just reinstall /compat/linux from scratch with the latest > > ports. > > That is the best way. Please, report back your results. Thanks. > Ok, I've now reinstalled all Linux-based ports, including nspluginwrapper and linux-f10-flashplugin-10.0r32. Here's the output from nspluginwrapper -v -a -i as a normal user: Auto-install plugins from /home/garyj/.mozilla/plugins Looking for plugins in /home/garyj/.mozilla/plugins Hmm. Nothing happens? ~/.mozilla/plugins is and remains empty. --- Gary Jennejohn From tijl at ulyssis.org Wed Aug 12 16:20:13 2009 From: tijl at ulyssis.org (Tijl Coosemans) Date: Wed Aug 12 16:20:19 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <20090812163112.092df46c@ernst.jennejohn.org> References: <20090725013500.GC62402@onelab2.iet.unipi.it> <34211562@serv3.int.kfs.ru> <20090812163112.092df46c@ernst.jennejohn.org> Message-ID: <200908121817.39708.tijl@ulyssis.org> On Wednesday 12 August 2009 16:31:12 Gary Jennejohn wrote: > Ok, I've now reinstalled all Linux-based ports, including > nspluginwrapper and linux-f10-flashplugin-10.0r32. > > Here's the output from nspluginwrapper -v -a -i as a normal user: > > Auto-install plugins from /home/garyj/.mozilla/plugins > Looking for plugins in /home/garyj/.mozilla/plugins > > Hmm. Nothing happens? ~/.mozilla/plugins is and remains empty. Did you create the link mentioned here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html#MOZ-FLASH-PLUGIN From blackend at freebsd.org Thu Aug 13 06:55:53 2009 From: blackend at freebsd.org (Marc Fonvieille) Date: Thu Aug 13 06:55:59 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <20090812163112.092df46c@ernst.jennejohn.org> References: <68208453@h30.sp.ipt.ru> <20090809160121.GA1621@pollux.local.net> <00339944@bb.ipt.ru> <20090810071850.GB1238@gothic.blackend.org> <78871850@bb.ipt.ru> <20090811114116.71e72ebb@ernst.jennejohn.org> <20090811172117.GA66530@keira.kiwi-computer.com> <20090812111836.4413bbd4@ernst.jennejohn.org> <34211562@serv3.int.kfs.ru> <20090812163112.092df46c@ernst.jennejohn.org> Message-ID: <20090813065638.GA1239@gothic.blackend.org> On Wed, Aug 12, 2009 at 04:31:12PM +0200, Gary Jennejohn wrote: > On Wed, 12 Aug 2009 15:35:17 +0400 > Boris Samorodov wrote: > > > Gary Jennejohn writes: > > > Maybe I should just reinstall /compat/linux from scratch with the latest > > > ports. > > > > That is the best way. Please, report back your results. Thanks. > > > > Ok, I've now reinstalled all Linux-based ports, including nspluginwrapper > and linux-f10-flashplugin-10.0r32. > > Here's the output from nspluginwrapper -v -a -i as a normal user: > > Auto-install plugins from /home/garyj/.mozilla/plugins > Looking for plugins in /home/garyj/.mozilla/plugins > > Hmm. Nothing happens? ~/.mozilla/plugins is and remains empty. > You have to # ln -s /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so \ /usr/local/lib/browser_plugins/ before using nspluginwrapper. -- Marc From gary.jennejohn at freenet.de Thu Aug 13 09:01:23 2009 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Thu Aug 13 09:01:29 2009 Subject: status of flash9/flash10 support in RELENG_7 ? In-Reply-To: <200908121817.39708.tijl@ulyssis.org> References: <20090725013500.GC62402@onelab2.iet.unipi.it> <34211562@serv3.int.kfs.ru> <20090812163112.092df46c@ernst.jennejohn.org> <200908121817.39708.tijl@ulyssis.org> Message-ID: <20090813110119.17bd36da@ernst.jennejohn.org> On Wed, 12 Aug 2009 18:17:10 +0200 Tijl Coosemans wrote: > On Wednesday 12 August 2009 16:31:12 Gary Jennejohn wrote: > > Ok, I've now reinstalled all Linux-based ports, including > > nspluginwrapper and linux-f10-flashplugin-10.0r32. > > > > Here's the output from nspluginwrapper -v -a -i as a normal user: > > > > Auto-install plugins from /home/garyj/.mozilla/plugins > > Looking for plugins in /home/garyj/.mozilla/plugins > > > > Hmm. Nothing happens? ~/.mozilla/plugins is and remains empty. > > Did you create the link mentioned here: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html#MOZ-FLASH-PLUGIN Thanks. With the symbolic link nspluginwrapper found and installed the flash plugin and flash seems to work. There are definitely some problems with the nspluginwrapper port! The directory /usr/local/lib/browser_plugins didn't exist and I had to create it myself. It seems like this directory and the symbolic link into it should be created by the port and not be left up to the user to take care of. --- Gary Jennejohn From bsam at ipt.ru Thu Aug 13 10:04:54 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Thu Aug 13 10:05:00 2009 Subject: Flash10 on BETA2, by f10 / f8 In-Reply-To: <68130604@serv3.int.kfs.ru> (Boris Samorodov's message of "Wed\, 12 Aug 2009 15\:51\:15 +0400") References: <4A821338.5030301@ongs.co.jp> <68130604@serv3.int.kfs.ru> Message-ID: <98521399@ipt.ru> Boris Samorodov writes: > Hm, I'd expect right the opposite with the latest ports > (both linux-* and X11). The problem (I'm referring to) > is with the fontconfig version. Only x11-fonts/linux-f10-fontconfig > has a configuration file compatible with current X11 versions. Correction: s/configuration/cache ! Cache files are incompatible. -- WBR, bsam From bsam at ipt.ru Thu Aug 13 17:21:47 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Thu Aug 13 17:21:59 2009 Subject: Mathematica 7 license manager In-Reply-To: <20090812192421.GA88671@pencil.math.missouri.edu> (Rich Winkel's message of "Wed\, 12 Aug 2009 14\:24\:21 -0500") References: <20090812192421.GA88671@pencil.math.missouri.edu> Message-ID: <10995191@ipt.ru> (redirecting to freebsd-emulation@, please trim freebsd-questions@) Rich Winkel writes: > I'm trying to run mathlm for mathematica version 7 under linux_base-fc-4_13 on > freebsd 7.1-release-p7. > > It demonizes and appears to be happy until I try to run mathematica, > then it crashes with signal 11. Even running monitorlm causes it > to crash. Maxing out the loglevel doesn't produce any more info. > > Looking at the last access times in /compat/linux/etc, it opens host.conf, > ld.so.cache and nsswitch.conf before dying. > > Has anyone seen this before? Any help would be much appreciated!! As for me I can say that there were many changes to linuxulator not only at FreeBSD-7.2 but at 7-STABLE. Can you try it or even 8-BETA and report back? BTW, 8-BETA has linux_base-f10 as a default linux base port. -- WBR, bsam From bsam at ipt.ru Thu Aug 13 21:25:51 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Thu Aug 13 21:29:34 2009 Subject: Flash10 on BETA2, by f10 / f8 In-Reply-To: <4A847E7E.5010805@ongs.co.jp> (Daichi GOTO's message of "Fri\, 14 Aug 2009 05\:58\:38 +0900") References: <4A821338.5030301@ongs.co.jp> <68130604@serv3.int.kfs.ru> <4A847E7E.5010805@ongs.co.jp> Message-ID: <77075814@ipt.ru> Daichi GOTO writes: > 1) > FreeBSD 8-BETA2/amd64 > % pkg_info | grep -E '(linux|fontconfig)' > fontconfig-2.6.0,1 An XML-based font configuration API for X Windows > linux-f10-fontconfig-2.6.0 An XML-based font configuration API for X Windows (Linux Fe Those ports have compatible cache files... > 2) > FreeBSD 8-BETA2/i386 > % pkg_info | grep -E '(linux|fontconfig)' > fontconfig-2.6.0,1 An XML-based font configuration API for X Windows > linux-f8-fontconfig-2.4.2_1 An XML-based font configuration API for X Windows (Linux Fe ...while those don't. I'm out of ideas, sorry. I'd expect 1) TDRT, but not the 2). Anybody? -- WBR, bsam From daichi at ongs.co.jp Thu Aug 13 21:26:04 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Thu Aug 13 21:31:09 2009 Subject: Flash10 on BETA2, by f10 / f8 In-Reply-To: <68130604@serv3.int.kfs.ru> References: <4A821338.5030301@ongs.co.jp> <68130604@serv3.int.kfs.ru> Message-ID: <4A847E7E.5010805@ongs.co.jp> 1) FreeBSD 8-BETA2/amd64 % pkg_info | grep -E '(linux|fontconfig)' fontconfig-2.6.0,1 An XML-based font configuration API for X Windows linux-dri-7.4 Mesa-based DRI libraries, drivers and binaries (Linux Ubunt linux-f10-alsa-lib-1.0.19 The Advanced Linux Sound Architecture libraries (Linux Fedo linux-f10-atk-1.24.0 Accessibility Toolkit, Linux/i386 binary (Linux Fedora 10) linux-f10-cairo-1.8.0 Vector graphics library Cairo (Linux Fedora 10) linux-f10-curl-7.19.4_4 The command line tool for transferring files with URL synta linux-f10-cyrus-sasl2-2.1.22 RFC 2222 SASL (Simple Authentication and Security Layer) (L linux-f10-expat-2.0.1 Linux/i386 binary port of Expat XML-parsing library (Linux linux-f10-flashplugin-10.0r32 Adobe Flash Player NPAPI Plugin linux-f10-fontconfig-2.6.0 An XML-based font configuration API for X Windows (Linux Fe linux-f10-gdk-pixbuf-0.22.0 Image loading library for GTK+ (Linux Fedora 10) linux-f10-gtk2-2.14.7 GTK+ library, version 2.X (Linux Fedora 10) linux-f10-hicolor-icon-theme-0.5 A high-color icon theme shell from the FreeDesktop project linux-f10-jpeg-6b RPM of the JPEG lib (Linux Fedora 10) linux-f10-libsigc++20-2.2.2 Callback Framework for C++ (Linux Fedora 10) linux-f10-libssh2-0.18 The library implementing the SSH2 protocol (Linux Fedora 10 linux-f10-libxml2-2.7.3_2 Library providing XML and HTML support (Linux Fedora 10) linux-f10-nspr-4.7.3 Netscape Portable Runtime (Linux Fedora 10) linux-f10-nss-3.12.2.0 Network Security Services (Linux Fedora 10) linux-f10-openldap-2.4.12_1 Lightweight Directory Access Protocol libraries (Linux Fedo linux-f10-openssl-0.9.8g The OpenSSL toolkit (Linux Fedora 10) linux-f10-pango-1.22.3 The pango library (Linux Fedora 10) linux-f10-png-1.2.35 RPM of the PNG lib (Linux Fedora 10) linux-f10-sqlite3-3.5.9_1 The library that implements an embeddable SQL database engi linux-f10-tiff-3.8.2 The TIFF library, Linux/i386 binary (Linux Fedora 10) linux-f10-xorg-libs-7.4 Xorg libraries (Linux Fedora 10) linux-nvu-1.0_1 A complete Web Authoring System linux_base-f10-10_1 Base set of packages needed in Linux mode for i386/amd64 (L 2) FreeBSD 8-BETA2/i386 % pkg_info | grep -E '(linux|fontconfig)' fontconfig-2.6.0,1 An XML-based font configuration API for X Windows linux-f8-atk-1.20.0_1 Accessibility Toolkit, Linux/i386 binary (Linux Fedora linux-f8-cairo-1.4.14_1 Vector graphics library Cairo (Linux Fedora linux-f8-curl-7.18.2_2 The command line tool for transferring files with URL synta linux-f8-expat-2.0.1_1 Linux/i386 binary port of Expat XML-parsing library (Linux linux-f8-fontconfig-2.4.2_1 An XML-based font configuration API for X Windows (Linux Fe linux-f8-gtk2-2.12.8_1 GTK+ library, version 2.X (Linux Fedora linux-f8-hicolor-icon-theme-0.5_1 A high-color icon theme shell from the FreeDesktop project linux-f8-jpeg-6b_1 RPM of the JPEG lib (Linux Fedora linux-f8-libidn-0.6.14_1 Internationalized Domain Name support library (Linux Fedora linux-f8-libssh2-0.18_1 The library implementing the SSH2 protocol (Linux Fedora linux-f8-libxml2-2.7.2_2 Library providing XML and HTML support (Linux Fedora linux-f8-nspr-4.7.3_1 Netscape Portable Runtime (Linux Fedora linux-f8-nss-3.12.2.0_1 Network Security Services (Linux Fedora linux-f8-openssl-0.9.8b_1 The OpenSSL toolkit (Linux Fedora linux-f8-pango-1.18.4_1 The pango library (Linux Fedora linux-f8-png-1.2.22_1 RPM of the PNG lib (Linux Fedora linux-f8-scim-gtk-1.4.7_1 Smart Common Input Method platform, gtk module, (Linux Fedo linux-f8-scim-libs-1.4.7_1 Smart Common Input Method libraries (Linux Fedora linux-f8-sqlite3-3.4.2_3 The library that implements an embeddable SQL database engi linux-f8-tiff-3.8.2_1 The TIFF library, Linux/i386 binary (Linux Fedora linux-f8-xorg-libs-7.3_3 Xorg libraries (Linux Fedora linux-flashplugin-10.0r32 Adobe Flash Player NPAPI Plugin linux-nvu-1.0_1 A complete Web Authoring System linux-realplayer-10.0.9.809.20070726 Linux RealPlayer 10 from RealNetworks linux-sun-jdk-1.6.0.15 Sun Java Development Kit 1.6 for Linux linux_base-f8-8_11 Base set of packages needed in Linux mode (for i386/amd64) Boris Samorodov wrote: > Hi, > > Daichi GOTO writes: > >> I have quick checked follow two flash10 behavior. >> >> 1) >> FreeBSD 8-BETA2/amd64 >> linux-f10-flashplugin-10.0r32 >> linux_base-f10 >> >> 2) >> FreeBSD 8-BETA2/i386 >> linux-f10-flashplugin-10.0r32 >> linux_base-f8 > > There is a specail linux flashplugin port for linux_base-f8. > It is www/linux-f8-flashplugin10. > >> Both look working well. I couldn't encounter a bug >> around playing movie. Great :) >> >> But in case 1), flash player cannot print Japanese >> font. In case 2), flash10 player displays Japaense >> text well. > > Hm, I'd expect right the opposite with the latest ports > (both linux-* and X11). The problem (I'm referring to) > is with the fontconfig version. Only x11-fonts/linux-f10-fontconfig > has a configuration file compatible with current X11 versions. > >> Anyone has any ideas? > > None for now, but can you post an output for: > ----- > % pkg_info | grep -E '(linux|fontconfig)' > ----- -- ONGS Inc. CEO, Daichi GOTO (daichi@ongs.co.jp) TEL: 81-42-316-7945 FAX: 81-42-316-7946 WWW: http://www.ongs.co.jp/ From daichi at ongs.co.jp Fri Aug 14 03:10:17 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Fri Aug 14 03:10:24 2009 Subject: Flash10 on BETA2, by f10 / f8 (solved) In-Reply-To: <77075814@ipt.ru> References: <4A821338.5030301@ongs.co.jp> <68130604@serv3.int.kfs.ru> <4A847E7E.5010805@ongs.co.jp> <77075814@ipt.ru> Message-ID: <4A84D596.9000104@ongs.co.jp> Boris Samorodov wrote: > Daichi GOTO writes: > >> 1) >> FreeBSD 8-BETA2/amd64 >> % pkg_info | grep -E '(linux|fontconfig)' >> fontconfig-2.6.0,1 An XML-based font configuration API for X Windows >> linux-f10-fontconfig-2.6.0 An XML-based font configuration API for X Windows (Linux Fe > > Those ports have compatible cache files... > >> 2) >> FreeBSD 8-BETA2/i386 >> % pkg_info | grep -E '(linux|fontconfig)' >> fontconfig-2.6.0,1 An XML-based font configuration API for X Windows >> linux-f8-fontconfig-2.4.2_1 An XML-based font configuration API for X Windows (Linux Fe > > ...while those don't. > > I'm out of ideas, sorry. I'd expect 1) TDRT, but not the 2). > Anybody? Thanks Boris! At last I have found the cause of this problem and now it can display Japanese text well. Your description has given me some lights ;-) I have thought that ~/.fonts.conf maybe has effects because you said fontconfig of linux_base-f10 has compatibility with FreeBSD's fontconfig. So I had created a new user without some config files, and Firefox+flash10 of new user can display Japanese text. I am using ~/.fonts.conf including lines as follow: sans-serif Bitstream Vera Sans IPAUIGothic IPAPGothic IPAGothic VL PGothic VL Gothic Sazanami Gothic Kochi Gothic "Bitstream Vera Sans" first line and others from second line, thats order is very important. With above config, applications use "Bitstream Vera Sans" font for Alphabet text and other text are displayed with "IPAUIGothic" or something other listed Japanese font first matched. But flash10 uses "Bitstream Vera Sans" for all kind of text including Japanese. So flash10/f10 fails to display Japanese text. Is it correct to remove "Bitstream Vera Sans" line from ~/.fonts.conf? Maybe.... But I dislike Japanese font for all Alphabet, it's very bold to use. "Bitstream Vera Sans" and IPA fonts mixing using is better I guess, of course JIMO. So I have created home directory under /compat/linux and deploy customized .fonts.conf file under that for flash10. # mkdir -p /compat/linux/home/daichi # cp ~daichi/.fonts.conf /compat/linux/home/daichi/ # vi /compat/linux/home/daichi/.fonts.conf <-- rid of bitstream line Firefox refers to ~daichi/.fonts.conf including bitsteam line and flash10 refers to /compat/linux/home/daichi/.fonts.conf not including bitsteam line. Working well. Of course in this way, other Linux Applications (Acrobat Reader, Skype or something) are affected. But it's better than all applications are affected. -- ONGS Inc. CEO, Daichi GOTO (daichi@ongs.co.jp) TEL: 81-42-316-7945 FAX: 81-42-316-7946 WWW: http://www.ongs.co.jp/ From rich at math.missouri.edu Fri Aug 14 03:38:08 2009 From: rich at math.missouri.edu (Rich Winkel) Date: Fri Aug 14 03:38:21 2009 Subject: Mathematica 7 license manager In-Reply-To: <10995191@ipt.ru> References: <20090812192421.GA88671@pencil.math.missouri.edu> <10995191@ipt.ru> Message-ID: <20090814033806.GC72730@pencil.math.missouri.edu> On Thu, Aug 13, 2009 at 09:23:04PM +0400, Boris Samorodov wrote: > Rich Winkel writes: > > I'm trying to run mathlm for mathematica version 7 under linux_base-fc-4_13 on > > freebsd 7.1-release-p7. > > > > It demonizes and appears to be happy until I try to run mathematica, > > then it crashes with signal 11. Even running monitorlm causes it > > to crash. Maxing out the loglevel doesn't produce any more info. > > > > Looking at the last access times in /compat/linux/etc, it opens host.conf, > > ld.so.cache and nsswitch.conf before dying. > > > > Has anyone seen this before? Any help would be much appreciated!! > > As for me I can say that there were many changes to linuxulator > not only at FreeBSD-7.2 but at 7-STABLE. Can you try it or even > 8-BETA and report back? BTW, 8-BETA has linux_base-f10 as a default > linux base port. I talked to their tech support today. It turns out it made assumptions about the availability of IP6, which I don't have enabled. Version 7.01 works fine. Rich From bsam at ipt.ru Fri Aug 14 08:22:12 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Fri Aug 14 08:22:20 2009 Subject: Flash10 on BETA2, by f10 / f8 (solved) In-Reply-To: <4A84D596.9000104@ongs.co.jp> (Daichi GOTO's message of "Fri\, 14 Aug 2009 12\:10\:14 +0900") References: <4A821338.5030301@ongs.co.jp> <68130604@serv3.int.kfs.ru> <4A847E7E.5010805@ongs.co.jp> <77075814@ipt.ru> <4A84D596.9000104@ongs.co.jp> Message-ID: <80582407@ipt.ru> Hi Daichi-san, Daichi GOTO writes: > Firefox refers to ~daichi/.fonts.conf including bitsteam line and > flash10 refers to /compat/linux/home/daichi/.fonts.conf not including > bitsteam line. Working well. I'm glad that you have found a way to have Japanese at flash10. But it'a bug at flash10, isn't it? Maybe future versions won't suffer from it. -- WBR, bsam From dougb at FreeBSD.org Fri Aug 14 19:44:26 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Fri Aug 14 19:44:33 2009 Subject: virtualbox-3.0.51r22226 still panic'ing Message-ID: <4A85BE8E.5000505@FreeBSD.org> I'm using a core2duo on i386 SMP and the latest virtualbox port is still panic'ing for me: panic: blockable sleep lock (sleep mutex) IPRT Event Semaphore @ /usr/local/tmp/ usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runti me/r0drv/freebsd/semevent-r0drv-freebsdT?^]FreeBSD Kernel Dump #0 doadump () at pcpu.h:246 246 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:246 #1 0xc05f11de in boot (howto=260) at /usr/local/src/sys/kern/kern_shutdown.c:416 #2 0xc05f14b2 in panic (fmt=Variable "fmt" is not available. ) at /usr/local/src/sys/kern/kern_shutdown.c:579 #3 0xc0631eb0 in witness_checkorder (lock=0xc627c720, flags=9, file=0xc61a7a40 "/usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c", line=127, interlock=0x0) at /usr/local/src/sys/kern/subr_witness.c:1063 #4 0xc05e2114 in _mtx_lock_flags (m=0xc627c720, opts=0, file=0xc61a7a40 "/usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c", line=127) at /usr/local/src/sys/kern/kern_mutex.c:200 #5 0xc6194e7c in RTSemEventSignal (EventSem=0xc627c710) at /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:127 #6 0xc617e3d4 in SUPSemEventSignal (pSession=0xc5683410, hEvent=0x1) at /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/Support/SUPDrv.c:3417 #7 0xc62df4db in ?? () [bunch more like #7 above] #139 0xc08677f4 in __qdivrem (uq=Unhandled dwarf expression opcode 0x93) at /usr/local/src/sys/libkern/qdivrem.c:186 Previous frame inner to this frame (corrupt stack?) Doug -- This .signature sanitized for your protection From scf at FreeBSD.org Fri Aug 14 20:18:54 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Fri Aug 14 20:19:00 2009 Subject: virtualbox-3.0.51r22226 still panic'ing In-Reply-To: <4A85BE8E.5000505@FreeBSD.org> References: <4A85BE8E.5000505@FreeBSD.org> Message-ID: On Fri, 14 Aug 2009, Doug Barton wrote: > I'm using a core2duo on i386 SMP and the latest virtualbox port is > still panic'ing for me: > > panic: blockable sleep lock (sleep mutex) IPRT Event Semaphore @ > /usr/local/tmp/ > usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runti > me/r0drv/freebsd/semevent-r0drv-freebsdT?^]FreeBSD Kernel Dump Is this while loading the kernel module? I am not having problems with this version on i386 or amd64 with 7-STABLE when loaded via /boot/loader.conf. I remember having panics if attempting to load the module while the system was running, but I do not know if those have been fixed. Sean -- scf@FreeBSD.org From dougb at FreeBSD.org Fri Aug 14 20:22:31 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Fri Aug 14 20:22:37 2009 Subject: virtualbox-3.0.51r22226 still panic'ing In-Reply-To: References: <4A85BE8E.5000505@FreeBSD.org> Message-ID: <4A85C77C.9050600@FreeBSD.org> Sean C. Farley wrote: > On Fri, 14 Aug 2009, Doug Barton wrote: > >> I'm using a core2duo on i386 SMP and the latest virtualbox port is >> still panic'ing for me: >> >> panic: blockable sleep lock (sleep mutex) IPRT Event Semaphore @ >> /usr/local/tmp/ >> usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runti >> >> me/r0drv/freebsd/semevent-r0drv-freebsdT?^]FreeBSD Kernel Dump > > Is this while loading the kernel module? The first time I loaded the module (in X) it locked up hard without panicing. After reboot I was able to kldload it at the console ok. This panic happened after starting the vm which booted from the winxp ISO just fine, but paniced in the process of formatting the disk. I also forgot to mention that core.txt.6 is on my home directory on freefall. Doug -- This .signature sanitized for your protection From miwi at FreeBSD.org Fri Aug 14 21:37:02 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Fri Aug 14 21:37:09 2009 Subject: virtualbox-3.0.51r22226 still panic'ing In-Reply-To: <4A85BE8E.5000505@FreeBSD.org> References: <4A85BE8E.5000505@FreeBSD.org> Message-ID: <20090814211745.GX5272@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I can't confirm that, any special kernel hacks? On Fri, Aug 14, 2009 at 12:44:14PM -0700, Doug Barton wrote: > I'm using a core2duo on i386 SMP and the latest virtualbox port is > still panic'ing for me: > > panic: blockable sleep lock (sleep mutex) IPRT Event Semaphore @ > /usr/local/tmp/ > usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runti > me/r0drv/freebsd/semevent-r0drv-freebsdT?^]FreeBSD Kernel Dump > > #0 doadump () at pcpu.h:246 > 246 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump () at pcpu.h:246 > #1 0xc05f11de in boot (howto=260) > at /usr/local/src/sys/kern/kern_shutdown.c:416 > #2 0xc05f14b2 in panic (fmt=Variable "fmt" is not available. > ) at /usr/local/src/sys/kern/kern_shutdown.c:579 > #3 0xc0631eb0 in witness_checkorder (lock=0xc627c720, flags=9, > file=0xc61a7a40 > "/usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c", > line=127, interlock=0x0) at /usr/local/src/sys/kern/subr_witness.c:1063 > #4 0xc05e2114 in _mtx_lock_flags (m=0xc627c720, opts=0, > file=0xc61a7a40 > "/usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c", > line=127) at /usr/local/src/sys/kern/kern_mutex.c:200 > #5 0xc6194e7c in RTSemEventSignal (EventSem=0xc627c710) > at > /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:127 > #6 0xc617e3d4 in SUPSemEventSignal (pSession=0xc5683410, hEvent=0x1) > at > /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/Support/SUPDrv.c:3417 > #7 0xc62df4db in ?? () > [bunch more like #7 above] > #139 0xc08677f4 in __qdivrem (uq=Unhandled dwarf expression opcode > 0x93) at /usr/local/src/sys/libkern/qdivrem.c:186 > Previous frame inner to this frame (corrupt stack?) > > Doug > > -- > > This .signature sanitized for your protection > > _______________________________________________ > 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" > - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkqF1HkACgkQdLJIhLHm/Ok42wCeKrOnc4W9Sa50M59XEv25FlqA GTIAoMgAesH/q+K8feEArEkJlXZau3KO =+ViP -----END PGP SIGNATURE----- From dougb at FreeBSD.org Fri Aug 14 23:36:17 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Fri Aug 14 23:36:24 2009 Subject: virtualbox-3.0.51r22226 still panic'ing In-Reply-To: <4A85C77C.9050600@FreeBSD.org> References: <4A85BE8E.5000505@FreeBSD.org> <4A85C77C.9050600@FreeBSD.org> Message-ID: <4A85F4E5.2030606@FreeBSD.org> Hey, good news! Turns out there was a BIOS setting to enable the "Virtual Machine Manager functions" of my CPU that I had enabled. Turning that OFF actually allows virtualbox to run! I'm very excited, thanks to all those who followed up, and my apologies if I tripped over a known issue. Doug -- This .signature sanitized for your protection From matheus at eternamente.info Sat Aug 15 00:44:01 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Sat Aug 15 00:44:07 2009 Subject: virtualbox-3.0.51 In-Reply-To: <20090814211745.GX5272@bsdcrew.de> References: <4A85BE8E.5000505@FreeBSD.org> <20090814211745.GX5272@bsdcrew.de> Message-ID: <2c9042e5025c9819dfa4be1c8cc25082.squirrel@cygnus.homeunix.com> Hi, just changed the subject as the version stands, just not shure about the rev. I just found that this 3.0.51 rev 428 works great in running F@H for some time (some hours, maybe more than one day), and then what was running in two cpu's get to run in just one. Out of nothing. when I restart the vm, all get back to normal again. anyone also have seen this ? thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From chat95 at mac.com Mon Aug 17 01:17:24 2009 From: chat95 at mac.com (Maho NAKATA) Date: Mon Aug 17 01:17:31 2009 Subject: Flash10 on BETA2, by f10 / f8 In-Reply-To: <4A82BC2C.80904@ongs.co.jp> References: <4A821338.5030301@ongs.co.jp> <20090812.182131.4959786962467610.chat95@mac.com> <4A82BC2C.80904@ongs.co.jp> Message-ID: <20090817.101713.519459540419587513.chat95@mac.com> From: Daichi GOTO Subject: Re: Flash10 on BETA2, by f10 / f8 Date: Wed, 12 Aug 2009 21:57:16 +0900 > Maho NAKATA wrote: >> Hi >> Just I'd like to know how you tested ;) >> thanks > > I guess that nico nico douga is one of the best > test beds web service for Flash behavior, movie playing, > Japaense test displaying/inputing, locale checking and > timezone checking. Ok. Very good testbed! This is what I know. I'm using gtk-gnash. YouTube is okay but it doesn't work for nico nico. > Or do you mean how to setup using flash10 and f10 base? Thanks -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt From daichi at ongs.co.jp Mon Aug 17 09:06:45 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Mon Aug 17 09:06:52 2009 Subject: Flash10 on BETA2, by f10 / f8 (solved) In-Reply-To: <80582407@ipt.ru> References: <4A821338.5030301@ongs.co.jp> <68130604@serv3.int.kfs.ru> <4A847E7E.5010805@ongs.co.jp> <77075814@ipt.ru> <4A84D596.9000104@ongs.co.jp> <80582407@ipt.ru> Message-ID: <4A891DA3.5050203@ongs.co.jp> Boris Samorodov wrote: > Hi Daichi-san, > > Daichi GOTO writes: > >> Firefox refers to ~daichi/.fonts.conf including bitsteam line and >> flash10 refers to /compat/linux/home/daichi/.fonts.conf not including >> bitsteam line. Working well. > > I'm glad that you have found a way to have Japanese at flash10. > But it'a bug at flash10, isn't it? Maybe future versions won't > suffer from it. Yeah, I am thinking it's a bug of flash10 :) -- ONGS Inc. CEO, Daichi GOTO (daichi@ongs.co.jp) TEL: 81-42-316-7945 FAX: 81-42-316-7946 WWW: http://www.ongs.co.jp/ From bugmaster at FreeBSD.org Mon Aug 17 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 17 11:07:47 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200908171106.n7HB6qku075748@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/137332 emulation add caution messages to some adobe products f ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o ports/135322 emulation Port graphics/linux_dri has incorrect packaging list c o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/97326 emulation [linux] file descriptor leakage in linux emulation o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 18 problems total. From nox at jelal.kn-bremen.de Wed Aug 19 17:16:48 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Wed Aug 19 17:16:57 2009 Subject: virtualbox-3.0.51r22226 still panic'ing In-Reply-To: <20090814211745.GX5272@bsdcrew.de> References: <4A85BE8E.5000505@FreeBSD.org> Message-ID: <200908191713.n7JHDTtF008046@triton8.kn-bremen.de> In article <20090814211745.GX5272@bsdcrew.de> you write: >I can't confirm that, > >any special kernel hacks? > >On Fri, Aug 14, 2009 at 12:44:14PM -0700, Doug Barton wrote: >> I'm using a core2duo on i386 SMP and the latest virtualbox port is >> still panic'ing for me: >> >> panic: blockable sleep lock (sleep mutex) IPRT Event Semaphore @ >> /usr/local/tmp/ >> usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runti >> me/r0drv/freebsd/semevent-r0drv-freebsdT?^]FreeBSD Kernel Dump >> >> #0 doadump () at pcpu.h:246 >> 246 pcpu.h: No such file or directory. >> in pcpu.h >> (kgdb) #0 doadump () at pcpu.h:246 >> #1 0xc05f11de in boot (howto=260) >> at /usr/local/src/sys/kern/kern_shutdown.c:416 >> #2 0xc05f14b2 in panic (fmt=Variable "fmt" is not available. >> ) at /usr/local/src/sys/kern/kern_shutdown.c:579 >> #3 0xc0631eb0 in witness_checkorder (lock=0xc627c720, flags=9, >> file=0xc61a7a40 >> "/usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c", >> line=127, interlock=0x0) at /usr/local/src/sys/kern/subr_witness.c:1063 >> #4 0xc05e2114 in _mtx_lock_flags (m=0xc627c720, opts=0, >> file=0xc61a7a40 >> "/usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c", >> line=127) at /usr/local/src/sys/kern/kern_mutex.c:200 >> #5 0xc6194e7c in RTSemEventSignal (EventSem=0xc627c710) >> at >> /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c:127 >> #6 0xc617e3d4 in SUPSemEventSignal (pSession=0xc5683410, hEvent=0x1) >> at >> /usr/local/tmp/usr/local/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/Support/SUPDrv.c:3417 >> #7 0xc62df4db in ?? () >> [bunch more like #7 above] >> #139 0xc08677f4 in __qdivrem (uq=Unhandled dwarf expression opcode >> 0x93) at /usr/local/src/sys/libkern/qdivrem.c:186 >> Previous frame inner to this frame (corrupt stack?) I just got (probably) the same panic while testing tuntap networking (more about that in a bit :) with a linux/amd64 guest running with svm and npt enabled - it was scp'ing a file out of the guest at about 16 MBytes/sec when the panic happened. I say `probably' the same because I don't have witness enabled and I also don't have debug symbols for vboxdrv.ko so the backtrace looks a bit different: .. Unread portion of the kernel message buffer: panic: mi_switch: switch in a critical section cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x182 mi_switch() at mi_switch+0x341 turnstile_wait() at turnstile_wait+0x234 _mtx_lock_sleep() at _mtx_lock_sleep+0xd6 _mtx_lock_flags() at _mtx_lock_flags+0x7e RTSemEventSignal() at RTSemEventSignal+0x9d SUPSemEventSignal() at SUPSemEventSignal+0xba g_iRTPowerGeneration() at 0xffffffff811f7bd1 g_iRTPowerGeneration() at 0xffffffff8122ca62 g_iRTPowerGeneration() at 0xffffffff811d5535 g_iRTPowerGeneration() at 0xffffffff811c20eb g_iRTPowerGeneration() at 0xffffffff811bcc41 g_iRTPowerGeneration() at 0xffffffff8124f8e1 g_iRTPowerGeneration() at 0xffffffff811d8605 supdrvIOCtlFast() at supdrvIOCtlFast+0x5a VBoxDrvFreeBSDIOCtl() at VBoxDrvFreeBSDIOCtl+0xe1 devfs_ioctl_f() at devfs_ioctl_f+0x76 kern_ioctl() at kern_ioctl+0xc5 ioctl() at ioctl+0xfd syscall() at syscall+0x1af Xfast_syscall() at Xfast_syscall+0xe1 --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800c8bf7c, rsp = 0x7fffffabaa98, rbp = 0x7fffffabaad0 --- Uptime: 1d0h11m30s Physical memory: 8175 MB Dumping 2431 MB: 2416 2400 2384 (CTRL-C to abort) 2368 2352 2336 2320 2304 2288 2272 2256 2240 2224 2208 2192 2176 2160 2144 2128 2112 2096 2080 2064 2048 2032 2016 2000 1984 1968 1952 1936 1920 1904 1888 1872 1856 1840 1824 1808 1792 1776 1760 1744 1728 1712 1696 1680 1664 1648 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 1456 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 1216 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 976 960 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 656 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 Reading symbols from /boot/kernel/amdtemp.ko...Reading symbols from /boot/kernel/amdtemp.ko.symbols...done. done. Loaded symbols for /boot/kernel/amdtemp.ko Reading symbols from /boot/kernel/ahci.ko...Reading symbols from /boot/kernel/ahci.ko.symbols...done. done. Loaded symbols for /boot/kernel/ahci.ko Reading symbols from /boot/kernel/siis.ko...Reading symbols from /boot/kernel/siis.ko.symbols...done. done. Loaded symbols for /boot/kernel/siis.ko Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/linprocfs.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from /boot/kernel/netgraph.ko.symbols...done. done. Loaded symbols for /boot/kernel/netgraph.ko Reading symbols from /boot/kernel/ng_ether.ko...Reading symbols from /boot/kernel/ng_ether.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_ether.ko Reading symbols from /boot/kernel/ng_pppoe.ko...Reading symbols from /boot/kernel/ng_pppoe.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_pppoe.ko Reading symbols from /boot/kernel/ng_socket.ko...Reading symbols from /boot/kernel/ng_socket.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_socket.ko Reading symbols from /boot/kernel/green_saver.ko...Reading symbols from /boot/kernel/green_saver.ko.symbols...done. done. Loaded symbols for /boot/kernel/green_saver.ko Reading symbols from /boot/kernel/radeon.ko...Reading symbols from /boot/kernel/radeon.ko.symbols...done. done. Loaded symbols for /boot/kernel/radeon.ko Reading symbols from /boot/kernel/drm.ko...Reading symbols from /boot/kernel/drm.ko.symbols...done. done. Loaded symbols for /boot/kernel/drm.ko Reading symbols from /boot/modules/cx88video.ko...done. Loaded symbols for /boot/modules/cx88video.ko Reading symbols from /boot/modules/iicdev.ko...done. Loaded symbols for /boot/modules/iicdev.ko Reading symbols from /boot/kernel/iicbus.ko...Reading symbols from /boot/kernel/iicbus.ko.symbols...done. done. Loaded symbols for /boot/kernel/iicbus.ko Reading symbols from /boot/modules/cx88i2c.ko...done. Loaded symbols for /boot/modules/cx88i2c.ko Reading symbols from /boot/modules/cx88.ko...done. Loaded symbols for /boot/modules/cx88.ko Reading symbols from /boot/kernel/snd_hda.ko...Reading symbols from /boot/kernel/snd_hda.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_hda.ko Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. Loaded symbols for /boot/kernel/sound.ko Reading symbols from /boot/kernel/if_tap.ko...Reading symbols from /boot/kernel/if_tap.ko.symbols...done. done. Loaded symbols for /boot/kernel/if_tap.ko Reading symbols from /boot/kernel/if_bridge.ko...Reading symbols from /boot/kernel/if_bridge.ko.symbols...done. done. Loaded symbols for /boot/kernel/if_bridge.ko Reading symbols from /boot/kernel/bridgestp.ko...Reading symbols from /boot/kernel/bridgestp.ko.symbols...done. done. Loaded symbols for /boot/kernel/bridgestp.ko Reading symbols from /boot/modules/kqemu.ko...done. Loaded symbols for /boot/modules/kqemu.ko Reading symbols from /boot/modules/vboxdrv.ko...done. Loaded symbols for /boot/modules/vboxdrv.ko #0 doadump () at pcpu.h:223 223 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:223 #1 0xffffffff805ba723 in boot (howto=260) at /usr/home/nox/src-r8/src/sys/kern/kern_shutdown.c:419 #2 0xffffffff805bab7c in panic (fmt=Variable "fmt" is not available. ) at /usr/home/nox/src-r8/src/sys/kern/kern_shutdown.c:575 #3 0xffffffff805c2b01 in mi_switch (flags=259, newtd=0x0) at /usr/home/nox/src-r8/src/sys/kern/kern_synch.c:403 #4 0xffffffff805f9374 in turnstile_wait (ts=0xffffff018569ba80, owner=0xffffff018569f000, queue=Variable "queue" is not available. ) at /usr/home/nox/src-r8/src/sys/kern/subr_turnstile.c:745 #5 0xffffffff805ac316 in _mtx_lock_sleep (m=0xffffff0185ac8b20, tid=18446742976608033456, opts=Variable "opts" is not available. ) at /usr/home/nox/src-r8/src/sys/kern/kern_mutex.c:447 #6 0xffffffff805ac41e in _mtx_lock_flags (m=Variable "m" is not available. ) at /usr/home/nox/src-r8/src/sys/kern/kern_mutex.c:203 #7 0xffffffff8119140d in RTSemEventSignal () from /boot/modules/vboxdrv.ko #8 0x0000000805fffac0 in ?? () #9 0xffffff80f0633690 in ?? () #10 0xffffffff8117a4ba in SUPSemEventSignal () from /boot/modules/vboxdrv.ko #11 0xffffff80f063f330 in ?? () #12 0x0000000805fffac0 in ?? () #13 0x0000000805fffac0 in ?? () #14 0xffffff80f06336c0 in ?? () ---Type to continue, or q to quit--- #15 0xffffffff811f7bd1 in ?? () [...more `... in ??'] #472 0x0000000100000008 in ?? () #473 0x0000000000000000 in ?? () ---Type to continue, or q to quit---q Quit (kgdb) fr 3 #3 0xffffffff805c2b01 in mi_switch (flags=259, newtd=0x0) at /usr/home/nox/src-r8/src/sys/kern/kern_synch.c:403 403 KASSERT(td->td_critnest == 1 || (td->td_critnest == 2 && (kgdb) l 398 KASSERT(!TD_ON_RUNQ(td), ("mi_switch: called by old code")); 399 #ifdef INVARIANTS 400 if (!TD_ON_LOCK(td) && !TD_IS_RUNNING(td)) 401 mtx_assert(&Giant, MA_NOTOWNED); 402 #endif 403 KASSERT(td->td_critnest == 1 || (td->td_critnest == 2 && 404 (td->td_owepreempt) && (flags & SW_INVOL) != 0 && 405 newtd == NULL) || panicstr, 406 ("mi_switch: switch in a critical section")); 407 KASSERT((flags & (SW_INVOL | SW_VOL)) != 0, (kgdb) p td->td_critnest $1 = 2 (kgdb) p td->td_owepreempt $2 = 0 '\0' (kgdb) p flags $3 = 259 (kgdb) p newtd $4 = (struct thread *) 0x0 (kgdb) p panicstr $5 = 0xffffffff80c52080 "mi_switch: switch in a critical section" (kgdb) q From nox at jelal.kn-bremen.de Wed Aug 19 18:58:46 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Wed Aug 19 18:58:52 2009 Subject: tuntap hacks for FreeBSD vbox hosts (bandaid till vbox-net driver...) Message-ID: <20090819185448.GA8386@triton8.kn-bremen.de> Hi! After inquiring on the #vbox-dev channel whether the tuntap code could be resurrected for hosts that don't have vbox net/bridge drivers yet (like FreeBSD :) I now got it working - except the config gui and ifup/down scripts, the code for at least the latter seems to have been ripped out for good indeed... So for now you have to use VBoxManage something like this, VBoxManage modifyvm --nic1 bridged --bridgeadapter1 tap0 and manually configure your tap interface and (optionally) add it to a bridge before the VM starts. If you already have setup your host system to use tuntap networking with qemu you probably can just chown/chmod /dev/tap0 (or whichever one you use) to 660 root:vboxusers and then run your /usr/local/etc/qemu-ifup script with the same tap interface as arg, otherwise do something like... kldload if_tap if_bridge sysctl net.link.tap.user_open=1 chown root:vboxusers /dev/tap0 chmod 660 /dev/tap0 ifconfig bridge0 create ifconfig bridge0 addm ifconfig tap0 netmask ifconfig bridge0 addm tap0 and then start the guest. (You'll have to rerun the `ifconfig tap0 ...' each time before you start the guest again.) Tested on the stable/8 FreeBSD branch with the vbox version currently in ports. (which btw today seems to have hit the same FreeBSD vboxdrv bug with svm and npt here while scp'ing a big file out of a guest that I previously thought only plagued intel vt-x users, see this post for details... http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006692.html ) Anyway, here comes the patch, enjoy! :) Index: Config.kmk @@ -490,7 +490,7 @@ endif endif # Use VBoxNetFlt for host interface networking. -if1of ($(KBUILD_TARGET), darwin linux solaris win freebsd) +if1of ($(KBUILD_TARGET), darwin linux solaris win) VBOX_WITH_NETFLT = 1 VBOX_SOLARIS_NSL_RESOLVED = 1 if1of ($(KBUILD_TARGET), darwin solaris linux) Index: src/VBox/Devices/Makefile.kmk @@ -802,7 +802,8 @@ Storage/DrvHostFloppy% \ , $(Drivers_SOURCES)) \ Audio/ossaudio.c -Drivers_SOURCES.freebsd = +Drivers_SOURCES.freebsd = \ + Network/DrvTAP.cpp endif # freebsd Index: src/VBox/Main/include/ConsoleImpl.h @@ -573,7 +573,7 @@ PPDMLED mapNetworkLeds[SchemaDefs::NetworkAdapterCount]; PPDMLED mapSharedFolderLed; PPDMLED mapUSBLed[2]; -#if !defined(VBOX_WITH_NETFLT) && defined(RT_OS_LINUX) +#if !defined(VBOX_WITH_NETFLT) && (defined(RT_OS_LINUX) || defined(RT_OS_FREEBSD)) Utf8Str maTAPDeviceName[8]; RTFILE maTapFD[8]; #endif Index: src/VBox/Devices/Builtins.h @@ -100,7 +100,7 @@ extern const PDMDRVREG g_DrvRawImage; extern const PDMDRVREG g_DrvISCSI; extern const PDMDRVREG g_DrvISCSITransportTcp; -#ifdef RT_OS_LINUX +#if defined(RT_OS_LINUX) || defined(RT_OS_FREEBSD) extern const PDMDRVREG g_DrvHostInterface; #endif extern const PDMDRVREG g_DrvIntNet; Index: src/VBox/Devices/Builtins.cpp @@ -227,7 +227,7 @@ if (RT_FAILURE(rc)) return rc; #endif -#if defined(RT_OS_LINUX) +#if defined(RT_OS_LINUX) || defined(RT_OS_FREEBSD) rc = pCallbacks->pfnRegister(pCallbacks, &g_DrvHostInterface); if (RT_FAILURE(rc)) return rc; Index: src/VBox/Frontends/VBoxBFE/NetworkAdapterImpl.h @@ -61,7 +61,7 @@ BOOL mCableConnected; BOOL mTraceEnabled; Bstr mHostInterface; -#ifdef RT_OS_LINUX +#if defined(RT_OS_LINUX) || defined(RT_OS_FREEBSD) Bstr mTAPSetupApplication; Bstr mTAPTerminateApplication; RTFILE mTAPFD; @@ -89,7 +89,7 @@ // STDMETHOD(COMGETTER(AttachmentType))(NetworkAttachmentType_T *attachmentType); STDMETHOD(COMGETTER(HostInterface))(BSTR *hostInterface); STDMETHOD(COMSETTER(HostInterface))(INPTR BSTR hostInterface); -#ifdef RT_OS_LINUX +#if defined(RT_OS_LINUX) || defined(RT_OS_FREEBSD) STDMETHOD(COMGETTER(TAPFileDescriptor))(LONG *tapFileDescriptor); STDMETHOD(COMSETTER(TAPFileDescriptor))(LONG tapFileDescriptor); STDMETHOD(COMGETTER(TAPSetupApplication))(BSTR *tapSetupApplication); Index: src/VBox/Main/ConsoleImpl.cpp @@ -34,6 +34,16 @@ # include # include # include +#elif defined(RT_OS_FREEBSD) +# include +# include +# include +# include +# include +# include +# include +# include +# include #endif #include "ConsoleImpl.h" @@ -6023,7 +6033,7 @@ */ HRESULT Console::attachToBridgedInterface(INetworkAdapter *networkAdapter) { -#if !defined(RT_OS_LINUX) || defined(VBOX_WITH_NETFLT) +#if (!defined(RT_OS_LINUX) && !defined(RT_OS_FREEBSD)) || defined(VBOX_WITH_NETFLT) /* * Nothing to do here. * @@ -6033,7 +6043,7 @@ NOREF(networkAdapter); return S_OK; -#else /* RT_OS_LINUX && !VBOX_WITH_NETFLT */ +#else /* (RT_OS_LINUX || RT_OS_FREEBSD) && !VBOX_WITH_NETFLT */ LogFlowThisFunc(("\n")); /* sanity check */ @@ -6055,6 +6065,7 @@ /* * Allocate a host interface device */ +#ifdef RT_OS_LINUX int rcVBox = RTFileOpen(&maTapFD[slot], "/dev/net/tun", RTFILE_O_READWRITE | RTFILE_O_OPEN | RTFILE_O_DENY_NONE | RTFILE_O_INHERIT); if (VBOX_SUCCESS(rcVBox)) @@ -6133,6 +6144,48 @@ break; } } +#elif RT_OS_FREEBSD + /* + * Set/obtain the tap interface. + */ + /* The name of the TAP interface we are using */ + Bstr tapDeviceName; + rc = networkAdapter->COMGETTER(HostInterface)(tapDeviceName.asOutParam()); + if (FAILED(rc)) + tapDeviceName.setNull(); /* Is this necessary? */ + if (tapDeviceName.isEmpty()) + { + LogRel(("No TAP device name was supplied.\n")); + rc = setError(E_FAIL, tr ("No TAP device name was supplied for the host networking interface")); + } + char szTapdev[1024] = "/dev/"; + /* If we are using a static TAP device then try to open it. */ + Utf8Str str(tapDeviceName); + if (str.length() + strlen(szTapdev) <= sizeof(szTapdev)) + strcat(szTapdev, str.raw()); + else + memcpy(szTapdev + strlen(szTapdev), str.raw(), sizeof(szTapdev) - strlen(szTapdev) - 1); /** @todo bitch about names which are too long... */ + int rcVBox = RTFileOpen(&maTapFD[slot], szTapdev, + RTFILE_O_READWRITE | RTFILE_O_OPEN | RTFILE_O_DENY_NONE | RTFILE_O_INHERIT | RTFILE_O_NON_BLOCK); + + if (VBOX_SUCCESS(rcVBox)) + { + maTAPDeviceName[slot] = tapDeviceName; + rcVBox = VINF_SUCCESS; + } else { + switch (rcVBox) + { + case VERR_ACCESS_DENIED: + /* will be handled by our caller */ + rc = rcVBox; + break; + default: + rc = setError(E_FAIL, tr ("Failed to open the host network interface %ls"), + tapDeviceName.raw()); + break; + } + } +#endif /* RT_OS_FREEBSD */ /* in case of failure, cleanup. */ if (VBOX_FAILURE(rcVBox) && SUCCEEDED(rc)) { @@ -6141,7 +6194,7 @@ } LogFlowThisFunc(("rc=%d\n", rc)); return rc; -#endif /* RT_OS_LINUX */ +#endif /* RT_OS_LINUX || RT_OS_FREEBSD */ } /** @@ -6154,7 +6207,7 @@ */ HRESULT Console::detachFromBridgedInterface(INetworkAdapter *networkAdapter) { -#if !defined(RT_OS_LINUX) || defined(VBOX_WITH_NETFLT) +#if (!defined(RT_OS_LINUX) && !defined(RT_OS_FREEBSD)) || defined(VBOX_WITH_NETFLT) /* * Nothing to do here. */ @@ -6211,7 +6264,7 @@ } LogFlowThisFunc(("returning %d\n", rc)); return rc; -#endif /* RT_OS_LINUX */ +#endif /* RT_OS_LINUX || RT_OS_FREEBSD */ } Index: src/VBox/Main/ConsoleImpl2.cpp @@ -2182,7 +2182,13 @@ case NetworkAttachmentType_Bridged: { -#if !defined(VBOX_WITH_NETFLT) && defined(RT_OS_LINUX) +#if !defined(VBOX_WITH_NETFLT) && (defined(RT_OS_LINUX) || defined(RT_OS_FREEBSD)) + hrc = pThis->attachToBridgedInterface(aNetworkAdapter); + if (FAILED(hrc)) + { + LogRel(("NetworkAttachmentType_Bridged: attachToBridgedInterface failed, hrc (0x%x)", hrc)); + H(); + } Assert ((int)pThis->maTapFD[uInstance] >= 0); if ((int)pThis->maTapFD[uInstance] >= 0) { PS: error handling can probably be improved... From shuriku at shurik.kiev.ua Thu Aug 20 09:12:35 2009 From: shuriku at shurik.kiev.ua (Alexandr Krivulya) Date: Thu Aug 20 09:12:47 2009 Subject: virtualbox port forwarding Message-ID: <4A8D0EC4.8030105@shurik.kiev.ua> Hello, I have host with FreeBSD 7.2-RELEASE-p3 running Win2K3 under virtualbox-3.0.51.r22226 with cofigured terminal service. I configured port forwarding to get access terminal service on win2k3 outside of a virtual machine, but it doesn't work :( shurik@shurik-nb:~> VBoxManage getextradata WIN2003STD enumerate VirtualBox Command Line Management Interface Version 3.0.51_OSE (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. Key: GUI/AutoresizeGuest, Value: on Key: GUI/Fullscreen, Value: off Key: GUI/LastCloseAction, Value: powerOff Key: GUI/LastWindowPostion, Value: 297,74,800,647 Key: GUI/MiniToolBarAlignment, Value: bottom Key: GUI/MiniToolBarAutoHide, Value: on Key: GUI/SaveMountedAtRuntime, Value: yes Key: GUI/Seamless, Value: off Key: GUI/ShowMiniToolBar, Value: yes Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/RDP/GuestPort, Value: 3389 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/RDP/HostPort, Value: 53389 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/RDP/Protocol, Value: TCP sockstat shows listening port 53389: shurik@shurik-nb:~> sockstat -l -4|grep 3389 shurik VirtualBox 9553 42 tcp4 *:53389 *:* Network inside of virtual machine works good. P.S. Sorry for my english. From scf at FreeBSD.org Thu Aug 20 14:46:12 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Thu Aug 20 14:46:18 2009 Subject: virtualbox port forwarding In-Reply-To: <4A8D0EC4.8030105@shurik.kiev.ua> References: <4A8D0EC4.8030105@shurik.kiev.ua> Message-ID: On Thu, 20 Aug 2009, Alexandr Krivulya wrote: > Hello, > > I have host with FreeBSD 7.2-RELEASE-p3 running Win2K3 under > virtualbox-3.0.51.r22226 with cofigured terminal service. I configured > port forwarding to get access terminal service on win2k3 outside of a > virtual machine, but it doesn't work :( > > shurik@shurik-nb:~> VBoxManage getextradata WIN2003STD enumerate > VirtualBox Command Line Management Interface Version 3.0.51_OSE > (C) 2005-2009 Sun Microsystems, Inc. > All rights reserved. > > Key: GUI/AutoresizeGuest, Value: on > Key: GUI/Fullscreen, Value: off > Key: GUI/LastCloseAction, Value: powerOff > Key: GUI/LastWindowPostion, Value: 297,74,800,647 > Key: GUI/MiniToolBarAlignment, Value: bottom > Key: GUI/MiniToolBarAutoHide, Value: on > Key: GUI/SaveMountedAtRuntime, Value: yes > Key: GUI/Seamless, Value: off > Key: GUI/ShowMiniToolBar, Value: yes > Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/RDP/GuestPort, Value: 3389 > Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/RDP/HostPort, Value: 53389 > Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/RDP/Protocol, Value: TCP > > sockstat shows listening port 53389: > > shurik@shurik-nb:~> sockstat -l -4|grep 3389 > shurik VirtualBox 9553 42 tcp4 *:53389 *:* > > Network inside of virtual machine works good. Your configuration looks correct. I had something similar to use ssh with a guest that did work: Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/CentOS/GuestPort, Value: 22 Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/CentOS/HostPort, Value: 30022 Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/CentOS/Protocol, Value: TCP Here are my thoughts: 1. Is the guest configured to allow remote desktop? Ah. I see you already have it configured. 2. Is the guest configured to allow remote desktop through its firewall? 3. Is there a firewall on the host that could interfere with the connection? This is even if you are trying to communicate from the host. 4. You could run tcpdump -n -i lo0 port 53389 on the host to see if any packets are coming out of the guest. This is assuming you are connecting from the host to localhost. 5. Are you attempting to connect with rdesktop such as: rdesktop localhost:53389 6. You could try the patch posted on this list yesterday from Juergen Lock to allow the use of tap devices (requires manual setup) and avoid having to use port forwarding. Sean -- scf@FreeBSD.org From uqs at spoerlein.net Thu Aug 20 19:49:34 2009 From: uqs at spoerlein.net (Ulrich =?utf-8?B?U3DDtnJsZWlu?=) Date: Thu Aug 20 19:49:41 2009 Subject: acquiring duplicate lock of same type: "ftlk" Message-ID: <20090820194932.GA66475@acme.spoerlein.net> Hi, I'm on RELENG_8/amd64 now and while using flash inside FF3 I observed the following acquiring duplicate lock of same type: "ftlk" 1st ftlk @ /data/freebsd-head/sys/modules/linux/../../compat/linux/linux_futex.c:177 2nd ftlk @ /data/freebsd-head/sys/modules/linux/../../compat/linux/linux_futex.c:203 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x8ef _sx_xlock() at _sx_xlock+0x55 futex_get0() at futex_get0+0xfe linux_sys_futex() at linux_sys_futex+0x96 ia32_syscall() at ia32_syscall+0x19c Xint0x80_syscall() at Xint0x80_syscall+0x95 --- syscall (240, Linux ELF32, linux_sys_futex), rip = 0x287d89b3, rsp = 0xffffaa8c, rbp = 0x4000001 --- I'm running with linux-f8 (f10 gave me trouble last time I tried on CURRENT) and flash10. Is this a known problem? Is someone working on this or shall I file a PR? Regards, Uli PS: please keep me CC'ed. thx. From scf at FreeBSD.org Thu Aug 20 20:19:38 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Thu Aug 20 20:19:44 2009 Subject: tuntap hacks for FreeBSD vbox hosts (bandaid till vbox-net driver...) In-Reply-To: <20090819185448.GA8386@triton8.kn-bremen.de> References: <20090819185448.GA8386@triton8.kn-bremen.de> Message-ID: On Wed, 19 Aug 2009, Juergen Lock wrote: > Hi! > > After inquiring on the #vbox-dev channel whether the tuntap code could > be resurrected for hosts that don't have vbox net/bridge drivers yet > (like FreeBSD :) I now got it working - except the config gui and > ifup/down scripts, the code for at least the latter seems to have been > ripped out for good indeed... So for now you have to use VBoxManage > something like this, > VBoxManage modifyvm --nic1 bridged --bridgeadapter1 tap0 > and manually configure your tap interface and (optionally) add it to a > bridge before the VM starts. If you already have setup your host > system to use tuntap networking with qemu you probably can just > chown/chmod /dev/tap0 (or whichever one you use) to 660 root:vboxusers > and then run your /usr/local/etc/qemu-ifup script with the same tap > interface as arg, otherwise do something like... > kldload if_tap if_bridge > sysctl net.link.tap.user_open=1 > chown root:vboxusers /dev/tap0 > chmod 660 /dev/tap0 > ifconfig bridge0 create > ifconfig bridge0 addm > ifconfig tap0 netmask > ifconfig bridge0 addm tap0 > and then start the guest. (You'll have to rerun the `ifconfig tap0 > ...' each time before you start the guest again.) Thank you! I had started looking at the code to try to figure out why I could not force the use of a tap device via VBoxManage. This patch works for me with FreeBSD 7-STABLE. BTW, you should not need the ifconfig tap0 line above since the VM is getting or setting its own IP. Is there a reason to do it? If you want it to have it look even more authenticate, you can always rename the tap device to vboxnet0 with ifconfig. :) Sean -- scf@FreeBSD.org From kostikbel at gmail.com Thu Aug 20 20:29:26 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Thu Aug 20 20:29:32 2009 Subject: acquiring duplicate lock of same type: "ftlk" In-Reply-To: <20090820194932.GA66475@acme.spoerlein.net> References: <20090820194932.GA66475@acme.spoerlein.net> Message-ID: <20090820200101.GW9623@deviant.kiev.zoral.com.ua> On Thu, Aug 20, 2009 at 09:49:32PM +0200, Ulrich Sp??rlein wrote: > Hi, I'm on RELENG_8/amd64 now and while using flash inside FF3 I > observed the following > > acquiring duplicate lock of same type: "ftlk" > 1st ftlk @ /data/freebsd-head/sys/modules/linux/../../compat/linux/linux_futex.c:177 > 2nd ftlk @ /data/freebsd-head/sys/modules/linux/../../compat/linux/linux_futex.c:203 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > _witness_debugger() at _witness_debugger+0x2e > witness_checkorder() at witness_checkorder+0x8ef > _sx_xlock() at _sx_xlock+0x55 > futex_get0() at futex_get0+0xfe > linux_sys_futex() at linux_sys_futex+0x96 > ia32_syscall() at ia32_syscall+0x19c > Xint0x80_syscall() at Xint0x80_syscall+0x95 > --- syscall (240, Linux ELF32, linux_sys_futex), rip = 0x287d89b3, rsp = 0xffffaa8c, rbp = 0x4000001 --- > > I'm running with linux-f8 (f10 gave me trouble last time I tried on CURRENT) and flash10. > > Is this a known problem? Is someone working on this or shall I file a PR? > > Regards, > Uli > > PS: please keep me CC'ed. thx. This is a known and harmless issue. We need sx_xlock_flags(). -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090820/2366b4da/attachment.pgp From shuriku at shurik.kiev.ua Fri Aug 21 06:06:31 2009 From: shuriku at shurik.kiev.ua (Alexandr Krivulya) Date: Fri Aug 21 06:06:38 2009 Subject: virtualbox port forwarding In-Reply-To: References: <4A8D0EC4.8030105@shurik.kiev.ua> Message-ID: <4A8E3969.9030203@shurik.kiev.ua> Thx for your reply, Sean. My problem was solved by changing "TCP" to "tcp" in "VBoxInternal/Devices/pcnet/0/LUN#0/Config/RDP/Protocol, Value: TCP" Sean C. Farley ?????: > On Thu, 20 Aug 2009, Alexandr Krivulya wrote: > >> Hello, >> >> I have host with FreeBSD 7.2-RELEASE-p3 running Win2K3 under >> virtualbox-3.0.51.r22226 with cofigured terminal service. I configured >> port forwarding to get access terminal service on win2k3 outside of a >> virtual machine, but it doesn't work :( >> >> shurik@shurik-nb:~> VBoxManage getextradata WIN2003STD enumerate >> VirtualBox Command Line Management Interface Version 3.0.51_OSE >> (C) 2005-2009 Sun Microsystems, Inc. >> All rights reserved. >> >> Key: GUI/AutoresizeGuest, Value: on >> Key: GUI/Fullscreen, Value: off >> Key: GUI/LastCloseAction, Value: powerOff >> Key: GUI/LastWindowPostion, Value: 297,74,800,647 >> Key: GUI/MiniToolBarAlignment, Value: bottom >> Key: GUI/MiniToolBarAutoHide, Value: on >> Key: GUI/SaveMountedAtRuntime, Value: yes >> Key: GUI/Seamless, Value: off >> Key: GUI/ShowMiniToolBar, Value: yes >> Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/RDP/GuestPort, Value: 3389 >> Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/RDP/HostPort, Value: 53389 >> Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/RDP/Protocol, Value: TCP >> >> sockstat shows listening port 53389: >> >> shurik@shurik-nb:~> sockstat -l -4|grep 3389 >> shurik VirtualBox 9553 42 tcp4 *:53389 *:* >> >> Network inside of virtual machine works good. > > Your configuration looks correct. I had something similar to use ssh > with a guest that did work: > Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/CentOS/GuestPort, Value: 22 > Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/CentOS/HostPort, Value: > 30022 > Key: VBoxInternal/Devices/e1000/0/LUN#0/Config/CentOS/Protocol, Value: TCP > > Here are my thoughts: > 1. Is the guest configured to allow remote desktop? Ah. I see you > already have it configured. > 2. Is the guest configured to allow remote desktop through its firewall? > 3. Is there a firewall on the host that could interfere with the > connection? This is even if you are trying to communicate from the > host. > 4. You could run tcpdump -n -i lo0 port 53389 on the host to see if any > packets are coming out of the guest. This is assuming you are > connecting from the host to localhost. > 5. Are you attempting to connect with rdesktop such as: > rdesktop localhost:53389 > 6. You could try the patch posted on this list yesterday from Juergen > Lock to allow the use of tap devices (requires manual setup) and > avoid having to use port forwarding. > > Sean From gamato at users.sf.net Fri Aug 21 14:05:55 2009 From: gamato at users.sf.net (martinko) Date: Fri Aug 21 14:06:02 2009 Subject: Automagic bridged networking with QEMU (tap) Message-ID: Hallo list, I spent a good portion of yesterday trying to find out how to change from using user mode to bridged networking with QEMU on FreeBSD 7.2. As I found a few how-to's of differing quality and I couldn't manage to make it work for some time, I decided to share the final results of my journey with you as I believe it may save someone a few hours or hair. The proposed solution does not need any manual steps and is fully transparent to users (like user mode networking is). It does not even permanently bridge your real NIC, only when necessary, which is good because of some performance penalties when bridging. And you can run as many guests as you want and it's all set up automagically. :-) OK, enough words, here's what to do: /boot/loader.conf[.local]: if_bridge_load="YES" if_tap_load="YES" /etc/sysctl.conf: net.link.tap.up_on_open=1 net.link.tap.user_open=1 /etc/devfs.rules: [localrules=10] add path 'tap*' mode 0660 /etc/rc.conf[.local]: devfs_system_ruleset="localrules" kqemu_enable="YES" /usr/local/etc/qemu-ifup -- custom script /usr/local/etc/qemu-ifdown -- custom script --- /usr/local/etc/qemu-ifup #!/bin/sh # # /usr/local/etc/qemu-ifup : martinko [20-aug-2009] # IFNAME=re0 for BRIDGE in $(ifconfig -a | grep '^bridge' | cut -d: -f1) do if [ -n "$(ifconfig "$BRIDGE" | grep -w "member: $IFNAME")" ] then echo "${0##*/}: Adding $1 as a member of $BRIDGE" sudo /sbin/ifconfig "$BRIDGE" addm "$1" up exit fi done BRIDGE="$(sudo /sbin/ifconfig bridge create)" sudo /sbin/ifconfig "$BRIDGE" addm "$IFNAME" addm "$1" up echo "${0##*/}: Created $BRIDGE and added $1 as a member" --- /usr/local/etc/qemu-ifdown #!/bin/sh # # /usr/local/etc/qemu-ifdown : martinko [20-aug-2009] # for BRIDGE in $(ifconfig -a | grep '^bridge' | cut -d: -f1) do if [ -n "$(ifconfig "$BRIDGE" | grep -w "member: $1")" ] then if [ "$(ifconfig "$BRIDGE" | grep -c -w "member:")" -le 2 ] then echo "${0##*/}: Destroying $BRIDGE" sudo /sbin/ifconfig "$BRIDGE" destroy fi echo "${0##*/}: Destroying $1" sudo /sbin/ifconfig "$1" destroy fi done --- And that's all, folks! :) Enjoy and if you find a better solution please let me/us know. Cheers, Martin PS1: Of course change IFNAME in qemu-ifup according to your setup. PS2: You man want/need to change the group in devfs.rules as well. From fli at shapeshifter.se Fri Aug 21 14:48:55 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Fri Aug 21 14:49:02 2009 Subject: VirtualBox bridged adapter (vboxnetflt) Message-ID: <4A8EB3D2.7010109@shapeshifter.se> Hi I've started working on the missing bits of the FreeBSD network implementation in VirtualBox. I now have a working vboxnetflt.ko driver that allows automatic bridged networking in VirtualBox (probably what most people want). This allows guests to automatically bridge with your existing network adapter providing seamless network access. Work on host-only adapter mode is in progress (this should not be confused with host-interface in previous vbox 2.x releases). The patch can be found at http://www.shapeshifter.se/pub/patches/vbox-freebsd-network.patch Additional patch for emulators/virtualbox/Makefile http://www.shapeshifter.se/pub/patches/virtualbox-Makefile.patch You'll have to rebuild VirtualBox to make it work, the following lines should do the trick. cd /usr/ports/emulators/virtualbox make clean patch mkdir work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd patch -d work/virtualbox-3.0.51r22226 < vbox-freebsd-network.patch patch < virtualbox-Makefile.patch make install In addition to vboxdrv.ko you'll need to load vboxnetflt.ko too. kldload /boot/modules/vboxnetflt.ko In VirtualBox network settings, under "Bridged Adapter" you should now see your available network interfaces. Select the one connected to your network and boot your virtual machine. It should now be connected to your local network as any other machine. Please note that this is just the first iteration of the patch and it should by no means be considered complete. It has only been tested on FreeBSD 8/i386. Slippery when wet :) The kld is also a bit hackish at the moment regarding to how it interfaces with the network stack to avoid kernel code modifications. Fredrik From dnaeon at gmail.com Fri Aug 21 18:36:39 2009 From: dnaeon at gmail.com (Marin Atanasov) Date: Fri Aug 21 18:37:11 2009 Subject: VirtualBox permissions issue Message-ID: <717f7a3e0908211112l493d33daia38df89dca83ffc3@mail.gmail.com> Hello, mates! First, I'd like to thank all of you that managed to port VirtualBox to FreeBSD! Thanks so much! :) Today I've installed VirtualBox on my FreeBSD 7.2 system and I can tell you it works like a charm! :) However I've noticed a very small issue - permissions. Installing VirtualBox from ports results in incorrect permissions set - this actually does not allow normal users to run VirtualBox, even if they are in the `vboxusers' group. Here's the incorrect permissions set by the default installation: drwx------ 4 root wheel 1536 Aug 19 15:58 /usr/local/lib/virtualbox/ So, in order to run VirtualBox as normal user one have to change the permissions for /usr/local/lib/virtualbox. Can I ask you to make the permissions for the next release of VirtualBox for /usr/local/lib/virtualbox 0750 for example, or just update the Handbook and mentioned that little part of allowing normal users to run VirtualBox? :) Best regards, D From edwin at FreeBSD.org Sat Aug 22 02:10:12 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Sat Aug 22 02:10:24 2009 Subject: ports/138058: Update Port: audio/linux-f10-alsa-lib Message-ID: <200908220210.n7M2ACbm092311@freefall.freebsd.org> Synopsis: Update Port: audio/linux-f10-alsa-lib Responsible-Changed-From-To: freebsd-ports-bugs->emulation Responsible-Changed-By: edwin Responsible-Changed-When: Sat Aug 22 02:10:12 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=138058 From vbox-devel-l at jelal.kn-bremen.de Sat Aug 22 12:55:02 2009 From: vbox-devel-l at jelal.kn-bremen.de (Juergen Lock) Date: Sat Aug 22 12:55:11 2009 Subject: tuntap hacks for FreeBSD vbox hosts (bandaid till vbox-net driver...) In-Reply-To: References: <20090819185448.GA8386@triton8.kn-bremen.de> Message-ID: <20090822123611.GA8594@triton8.kn-bremen.de> On Thu, Aug 20, 2009 at 03:19:36PM -0500, Sean C. Farley wrote: > On Wed, 19 Aug 2009, Juergen Lock wrote: > > > Hi! > > > > After inquiring on the #vbox-dev channel whether the tuntap code could > > be resurrected for hosts that don't have vbox net/bridge drivers yet > > (like FreeBSD :) I now got it working - except the config gui and > > ifup/down scripts, the code for at least the latter seems to have been > > ripped out for good indeed... So for now you have to use VBoxManage > > something like this, > > VBoxManage modifyvm --nic1 bridged --bridgeadapter1 tap0 > > and manually configure your tap interface and (optionally) add it to a > > bridge before the VM starts. If you already have setup your host > > system to use tuntap networking with qemu you probably can just > > chown/chmod /dev/tap0 (or whichever one you use) to 660 root:vboxusers > > and then run your /usr/local/etc/qemu-ifup script with the same tap > > interface as arg, otherwise do something like... > > kldload if_tap if_bridge > > sysctl net.link.tap.user_open=1 > > chown root:vboxusers /dev/tap0 > > chmod 660 /dev/tap0 > > ifconfig bridge0 create > > ifconfig bridge0 addm > > ifconfig tap0 netmask > > ifconfig bridge0 addm tap0 > > and then start the guest. (You'll have to rerun the `ifconfig tap0 > > ...' each time before you start the guest again.) > > Thank you! I had started looking at the code to try to figure out why I > could not force the use of a tap device via VBoxManage. This patch > works for me with FreeBSD 7-STABLE. > > BTW, you should not need the ifconfig tap0 line above since the VM is > getting or setting its own IP. Is there a reason to do it? > I was about to explain how I needed it for the guest to be able to talk to the host here, but - turns out this was just due to me using pf on this box and the rules were a little broken. So yes it is not really necessary... > If you want it to have it look even more authenticate, you can always > rename the tap device to vboxnet0 with ifconfig. :) > Haha! :) Btw, seems my patch has reached its ultimate goal much more quickly than I expected: Motivating someone to implement `proper' FreeBSD vbox net drivers: http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006701.html Thank you Fredrik!! :) Juergen From nox at jelal.kn-bremen.de Sat Aug 22 15:31:04 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sat Aug 22 15:31:11 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: <4A8EB3D2.7010109@shapeshifter.se> Message-ID: <200908221527.n7MFRx4K006005@triton8.kn-bremen.de> In article <4A8EB3D2.7010109@shapeshifter.se> you write: >Hi > >I've started working on the missing bits of the FreeBSD network >implementation in VirtualBox. > >I now have a working vboxnetflt.ko driver that allows automatic >bridged networking in VirtualBox (probably what most people want). >This allows guests to automatically bridge with your existing >network adapter providing seamless network access. > >Work on host-only adapter mode is in progress (this should not >be confused with host-interface in previous vbox 2.x releases). > >The patch can be found at >http://www.shapeshifter.se/pub/patches/vbox-freebsd-network.patch > >Additional patch for emulators/virtualbox/Makefile >http://www.shapeshifter.se/pub/patches/virtualbox-Makefile.patch > > >You'll have to rebuild VirtualBox to make it work, the following lines >should do the trick. > >cd /usr/ports/emulators/virtualbox >make clean patch >mkdir work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd > >patch -d work/virtualbox-3.0.51r22226 < vbox-freebsd-network.patch >patch < virtualbox-Makefile.patch >make install > >In addition to vboxdrv.ko you'll need to load vboxnetflt.ko too. > >kldload /boot/modules/vboxnetflt.ko > >In VirtualBox network settings, under "Bridged Adapter" you should now >see your available network interfaces. Select the one connected to your >network and boot your virtual machine. It should now be connected to >your local network as any other machine. > > >Please note that this is just the first iteration of the patch and it >should by no means be considered complete. It has only been tested >on FreeBSD 8/i386. Slippery when wet :) > > >The kld is also a bit hackish at the moment regarding to how it >interfaces with the network stack to avoid kernel code modifications. This is cool! :) I just did a quick test on stable/8/amd64: (its a little older checkout) The good news is it builds and the guest can ping the host, also pinging another box on the lan that I wasn't sure was up (it was down) from the guest failed as expected, but pinging the same box from the host to verify while the guest was still running then panic'd the host: triton8.kn-bremen.de dumped core - see /var/crash/vmcore.3 Sat Aug 22 16:59:18 CEST 2009 FreeBSD triton8.kn-bremen.de 8.0-BETA2 FreeBSD 8.0-BETA2 #3: Wed Aug 12 21:38:39 CEST 2009 nox@triton8.kn-bremen.de:/usr/obj/usr/home/nox/src-r8/src/sys/TRITON8 amd64 panic: general protection fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 9: general protection fault while in kernel mode cpuid = 1; apic id = 01 instruction pointer = 0x20:0xffffffff80614c05 stack pointer = 0x28:0xffffff8000055ac0 frame pointer = 0x28:0xffffff8000055ae0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (swi4: clock) trap number = 9 panic: general protection fault cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x182 trap_fatal() at trap_fatal+0x2ad trap() at trap+0xe4 calltrap() at calltrap+0x8 --- trap 0x9, rip = 0xffffffff80614c05, rsp = 0xffffff8000055ac0, rbp = 0xffffff8000055ae0 --- m_freem() at m_freem+0x25 llentry_free() at llentry_free+0x5c arptimer() at arptimer+0xd8 softclock() at softclock+0x291 intr_event_execute_handlers() at intr_event_execute_handlers+0x68 ithread_loop() at ithread_loop+0xb2 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff8000055d30, rbp = 0 --- Uptime: 2h34m56s Physical memory: 8175 MB Dumping 2353 MB: 2338 2322 2306 2290 2274 2258 2242 2226 2210 2194 2178 2162 2146 2130 2114 2098 2082 2066 2050 2034 2018 2002 1986 1970 1954 1938 1922 1906 1890 1874 1858 1842 1826 1810 1794 1778 1762 1746 1730 1714 1698 1682 1666 1650 1634 1618 1602 1586 1570 1554 1538 1522 1506 1490 1474 1458 1442 1426 1410 1394 1378 1362 1346 1330 1314 1298 1282 1266 1250 1234 1218 1202 1186 1170 1154 1138 1122 1106 1090 1074 1058 1042 1026 1010 994 978 962 946 930 914 898 882 866 850 834 818 802 786 770 754 738 722 706 690 674 658 642 626 610 594 578 562 546 530 514 498 482 466 450 434 418 402 386 370 354 338 322 306 290 274 258 242 226 210 194 178 162 146 130 114 98 82 66 50 34 18 2 Reading symbols from /boot/kernel/amdtemp.ko...Reading symbols from /boot/kernel/amdtemp.ko.symbols...done. done. Loaded symbols for /boot/kernel/amdtemp.ko Reading symbols from /boot/kernel/ahci.ko...Reading symbols from /boot/kernel/ahci.ko.symbols...done. done. Loaded symbols for /boot/kernel/ahci.ko Reading symbols from /boot/kernel/siis.ko...Reading symbols from /boot/kernel/siis.ko.symbols...done. done. Loaded symbols for /boot/kernel/siis.ko Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/linprocfs.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from /boot/kernel/netgraph.ko.symbols...done. done. Loaded symbols for /boot/kernel/netgraph.ko Reading symbols from /boot/kernel/ng_ether.ko...Reading symbols from /boot/kernel/ng_ether.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_ether.ko Reading symbols from /boot/kernel/ng_pppoe.ko...Reading symbols from /boot/kernel/ng_pppoe.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_pppoe.ko Reading symbols from /boot/kernel/ng_socket.ko...Reading symbols from /boot/kernel/ng_socket.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_socket.ko Reading symbols from /boot/kernel/green_saver.ko...Reading symbols from /boot/kernel/green_saver.ko.symbols...done. done. Loaded symbols for /boot/kernel/green_saver.ko Reading symbols from /boot/kernel/radeon.ko...Reading symbols from /boot/kernel/radeon.ko.symbols...done. done. Loaded symbols for /boot/kernel/radeon.ko Reading symbols from /boot/kernel/drm.ko...Reading symbols from /boot/kernel/drm.ko.symbols...done. done. Loaded symbols for /boot/kernel/drm.ko Reading symbols from /boot/modules/vboxdrv.ko...done. Loaded symbols for /boot/modules/vboxdrv.ko Reading symbols from /boot/modules/vboxnetflt.ko...done. Loaded symbols for /boot/modules/vboxnetflt.ko Reading symbols from /boot/kernel/snd_hda.ko...Reading symbols from /boot/kernel/snd_hda.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_hda.ko Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. Loaded symbols for /boot/kernel/sound.ko #0 doadump () at pcpu.h:223 223 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:223 #1 0xffffffff805ba723 in boot (howto=260) at /usr/home/nox/src-r8/src/sys/kern/kern_shutdown.c:419 #2 0xffffffff805bab7c in panic (fmt=Variable "fmt" is not available. ) at /usr/home/nox/src-r8/src/sys/kern/kern_shutdown.c:575 #3 0xffffffff8089653d in trap_fatal (frame=0x9, eva=Variable "eva" is not available. ) at /usr/home/nox/src-r8/src/sys/amd64/amd64/trap.c:852 #4 0xffffffff80896fc4 in trap (frame=0xffffff8000055a10) at /usr/home/nox/src-r8/src/sys/amd64/amd64/trap.c:639 #5 0xffffffff8087cd63 in calltrap () at /usr/home/nox/src-r8/src/sys/amd64/amd64/exception.S:224 #6 0xffffffff80614c05 in m_freem (mb=0xdeadc0dedeadc0de) at /usr/home/nox/src-r8/src/sys/kern/uipc_mbuf.c:160 #7 0xffffffff8066851c in llentry_free (lle=0xffffff01f0e35400) at /usr/home/nox/src-r8/src/sys/net/if_llatbl.c:101 #8 0xffffffff806adbb8 in arptimer (arg=0xffffff01f0e35400) at /usr/home/nox/src-r8/src/sys/netinet/if_ether.c:172 #9 0xffffffff805ccd41 in softclock (arg=Variable "arg" is not available. ) at /usr/home/nox/src-r8/src/sys/kern/kern_timeout.c:411 #10 0xffffffff80594f78 in intr_event_execute_handlers (p=Variable "p" is not available. ) at /usr/home/nox/src-r8/src/sys/kern/kern_intr.c:1165 #11 0xffffffff80595bd2 in ithread_loop (arg=0xffffff000187f840) at /usr/home/nox/src-r8/src/sys/kern/kern_intr.c:1178 #12 0xffffffff80592eca in fork_exit ( callout=0xffffffff80595b20 , arg=0xffffff000187f840, frame=0xffffff8000055c80) at /usr/home/nox/src-r8/src/sys/kern/kern_fork.c:838 #13 0xffffffff8087d23e in fork_trampoline () at /usr/home/nox/src-r8/src/sys/amd64/amd64/exception.S:561 #14 0x0000000000000000 in ?? () #15 0x0000000000000000 in ?? () #16 0x0000000000000001 in ?? () #17 0x0000000000000000 in ?? () #18 0x0000000000000000 in ?? () #19 0x0000000000000000 in ?? () #20 0x0000000000000000 in ?? () #21 0x0000000000000000 in ?? () #22 0x0000000000000000 in ?? () #23 0x0000000000000000 in ?? () #24 0x0000000000000000 in ?? () #25 0x0000000000000000 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000000 in ?? () #30 0x0000000000000000 in ?? () #31 0x0000000000000000 in ?? () #32 0x0000000000000000 in ?? () #33 0x0000000000000000 in ?? () #34 0x0000000000000000 in ?? () #35 0x0000000000000000 in ?? () #36 0x0000000000000000 in ?? () #37 0x0000000000000000 in ?? () #38 0x0000000000ed5000 in ?? () #39 0x0000000000000000 in ?? () #40 0xffffffff80c58ec0 in affinity () #41 0xffffffff80c58ec0 in affinity () #42 0xffffff00019ff720 in ?? () #43 0xffffff8000054ee0 in ?? () #44 0xffffff8000054e98 in ?? () #45 0xffffff0001890390 in ?? () #46 0xffffffff805dd5c0 in sched_switch (td=0xffffff000187f840, newtd=0xffffffff80595b20, flags=Variable "flags" is not available. ) at /usr/home/nox/src-r8/src/sys/kern/sched_ule.c:1858 Previous frame inner to this frame (corrupt stack?) (kgdb) Oh and the plist is now wrong too, vboxnetflt.ko is missing at least... Thanx, Juergen From Alexander.Eichner at Sun.COM Sun Aug 23 09:16:30 2009 From: Alexander.Eichner at Sun.COM (Alexander Eichner) Date: Sun Aug 23 09:16:36 2009 Subject: [vbox-dev] tuntap hacks for FreeBSD vbox hosts (bandaid till vbox-net driver...) In-Reply-To: <20090822123611.GA8594@triton8.kn-bremen.de> References: <20090819185448.GA8386@triton8.kn-bremen.de> <20090822123611.GA8594@triton8.kn-bremen.de> Message-ID: <1251018964.4475.10.camel@Hatak> Hi Juergen, thank for you very much for the tuntap patch. I would like to integrate it in the in the main VirtualBox repository but you didn't specified the license the patch is under. To integrate it you either need to sign the SCA or put it under the MIT license. More information regarding the SCA is here http://www.virtualbox.org/wiki/ICA . The above is valid for the vboxnetflt driver too :) Regards, Alexander Eichner Am Samstag, den 22.08.2009, 14:36 +0200 schrieb Juergen Lock: > On Thu, Aug 20, 2009 at 03:19:36PM -0500, Sean C. Farley wrote: > > On Wed, 19 Aug 2009, Juergen Lock wrote: > > > > > Hi! > > > > > > After inquiring on the #vbox-dev channel whether the tuntap code could > > > be resurrected for hosts that don't have vbox net/bridge drivers yet > > > (like FreeBSD :) I now got it working - except the config gui and > > > ifup/down scripts, the code for at least the latter seems to have been > > > ripped out for good indeed... So for now you have to use VBoxManage > > > something like this, > > > VBoxManage modifyvm --nic1 bridged --bridgeadapter1 tap0 > > > and manually configure your tap interface and (optionally) add it to a > > > bridge before the VM starts. If you already have setup your host > > > system to use tuntap networking with qemu you probably can just > > > chown/chmod /dev/tap0 (or whichever one you use) to 660 root:vboxusers > > > and then run your /usr/local/etc/qemu-ifup script with the same tap > > > interface as arg, otherwise do something like... > > > kldload if_tap if_bridge > > > sysctl net.link.tap.user_open=1 > > > chown root:vboxusers /dev/tap0 > > > chmod 660 /dev/tap0 > > > ifconfig bridge0 create > > > ifconfig bridge0 addm > > > ifconfig tap0 netmask > > > ifconfig bridge0 addm tap0 > > > and then start the guest. (You'll have to rerun the `ifconfig tap0 > > > ...' each time before you start the guest again.) > > > > Thank you! I had started looking at the code to try to figure out why I > > could not force the use of a tap device via VBoxManage. This patch > > works for me with FreeBSD 7-STABLE. > > > > BTW, you should not need the ifconfig tap0 line above since the VM is > > getting or setting its own IP. Is there a reason to do it? > > > I was about to explain how I needed it for the guest to be able > to talk to the host here, but - turns out this was just due to me > using pf on this box and the rules were a little broken. So yes it is > not really necessary... > > > If you want it to have it look even more authenticate, you can always > > rename the tap device to vboxnet0 with ifconfig. :) > > > Haha! :) > > Btw, seems my patch has reached its ultimate goal much more quickly > than I expected: Motivating someone to implement `proper' FreeBSD vbox > net drivers: > http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006701.html > > Thank you Fredrik!! :) > > Juergen > > _______________________________________________ > vbox-dev mailing list > vbox-dev@virtualbox.org > http://vbox.innotek.de/mailman/listinfo/vbox-dev From vbox-devel-l at jelal.kn-bremen.de Sun Aug 23 13:47:23 2009 From: vbox-devel-l at jelal.kn-bremen.de (Juergen Lock) Date: Sun Aug 23 13:47:30 2009 Subject: [vbox-dev] tuntap hacks for FreeBSD vbox hosts (bandaid till vbox-net driver...) In-Reply-To: <1251018964.4475.10.camel@Hatak> References: <20090819185448.GA8386@triton8.kn-bremen.de> <20090822123611.GA8594@triton8.kn-bremen.de> <1251018964.4475.10.camel@Hatak> Message-ID: <20090823134158.GB96781@triton8.kn-bremen.de> On Sun, Aug 23, 2009 at 11:16:04AM +0200, Alexander Eichner wrote: > Hi Juergen, Hi! > > thank for you very much for the tuntap patch. I would like to integrate > it in the in the main VirtualBox repository but you didn't specified the > license the patch is under. > To integrate it you either need to sign the SCA or put it under the MIT > license. More information regarding the SCA is here > http://www.virtualbox.org/wiki/ICA . > Oh, I'm fine with the MIT license. Do need to repost the patch? > The above is valid for the vboxnetflt driver too :) Btw there seems to be another FreeBSD host patch still pending wrt raw vmdk creation: http://vbox.innotek.de/pipermail/vbox-dev/2009-June/001477.html (And I later found out there is a ticket with a similar patch too: http://www.virtualbox.org/ticket/4269 ) Just thought I'd mention... :) Juergen From mlobo at digiart.art.br Sun Aug 23 15:56:38 2009 From: mlobo at digiart.art.br (Mario Lobo) Date: Sun Aug 23 15:56:44 2009 Subject: [vbox-dev] tuntap hacks for FreeBSD vbox hosts (bandaid till vbox-net driver...) In-Reply-To: <1251018964.4475.10.camel@Hatak> References: <20090819185448.GA8386@triton8.kn-bremen.de> <20090822123611.GA8594@triton8.kn-bremen.de> <1251018964.4475.10.camel@Hatak> Message-ID: <200908231257.09375.mlobo@digiart.art.br> On Sunday 23 August 2009 06:16:04 Alexander Eichner wrote: > Hi Juergen, > > thank for you very much for the tuntap patch. I would like to integrate > it in the in the main VirtualBox repository but you didn't specified the > license the patch is under. > To integrate it you either need to sign the SCA or put it under the MIT > license. More information regarding the SCA is here > http://www.virtualbox.org/wiki/ICA . > > The above is valid for the vboxnetflt driver too :) > > Regards, > Alexander Eichner May I suggest that Juergen's patch be added as a 6th "attached to:" type on the interface and VBoxManage? Maybe like: Attached to: Not Attached NAT Bridge Adapter Internal Network Host-only Network TAP Adapter TUN Adapter or TAP/TUN Adapter -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winedows FREE) From bsam at FreeBSD.org Sun Aug 23 16:45:50 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Sun Aug 23 16:45:56 2009 Subject: ports/138058: Update Port: audio/linux-f10-alsa-lib Message-ID: <200908231645.n7NGjoXM008637@freefall.freebsd.org> Synopsis: Update Port: audio/linux-f10-alsa-lib State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Sun Aug 23 16:43:23 UTC 2009 State-Changed-Why: Committed, thanks! Some changes were needed as well: 1) Fix pkg-plist. 2) Update distinfo for sources (one need to fetch and makesum with PACKAGE_BUILDING=YES). http://www.freebsd.org/cgi/query-pr.cgi?pr=138058 From dfilter at FreeBSD.ORG Sun Aug 23 16:50:09 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sun Aug 23 16:50:37 2009 Subject: ports/138058: commit references a PR Message-ID: <200908231650.n7NGo9Fh008745@freefall.freebsd.org> The following reply was made to PR ports/138058; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/138058: commit references a PR Date: Sun, 23 Aug 2009 16:43:12 +0000 (UTC) bsam 2009-08-23 16:43:03 UTC FreeBSD ports repository Modified files: audio/linux-f10-alsa-lib Makefile distinfo.i386 pkg-plist Log: . update to version 1.0.20-1.fc10; [1] . update distinfo for sources as well; . fix pkg-plist. PR: ports/138058 [1] Submitted by: Rick Elrod [1] Revision Changes Path 1.13 +2 -2 ports/audio/linux-f10-alsa-lib/Makefile 1.8 +6 -6 ports/audio/linux-f10-alsa-lib/distinfo.i386 1.4 +5 -5 ports/audio/linux-f10-alsa-lib/pkg-plist _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From nox at jelal.kn-bremen.de Sun Aug 23 22:19:43 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun Aug 23 22:19:50 2009 Subject: Automagic bridged networking with QEMU (tap) In-Reply-To: Message-ID: <200908232215.n7NMFqkK007704@triton8.kn-bremen.de> In article you write: >Hallo list, Hi! > >I spent a good portion of yesterday trying to find out how to change >from using user mode to bridged networking with QEMU on FreeBSD 7.2. >As I found a few how-to's of differing quality and I couldn't manage to >make it work for some time, I decided to share the final results of my >journey with you as I believe it may save someone a few hours or hair. > >The proposed solution does not need any manual steps and is fully >transparent to users (like user mode networking is). It does not even >permanently bridge your real NIC, only when necessary, which is good >because of some performance penalties when bridging. And you can run as >many guests as you want and it's all set up automagically. :-) > >OK, enough words, here's what to do: > >/boot/loader.conf[.local]: > if_bridge_load="YES" > if_tap_load="YES" > >/etc/sysctl.conf: > net.link.tap.up_on_open=1 > net.link.tap.user_open=1 > >/etc/devfs.rules: > [localrules=10] > add path 'tap*' mode 0660 > >/etc/rc.conf[.local]: > devfs_system_ruleset="localrules" > kqemu_enable="YES" > >/usr/local/etc/qemu-ifup -- custom script >/usr/local/etc/qemu-ifdown -- custom script > >--- /usr/local/etc/qemu-ifup > >#!/bin/sh ># ># /usr/local/etc/qemu-ifup : martinko [20-aug-2009] ># > >IFNAME=re0 > >for BRIDGE in $(ifconfig -a | grep '^bridge' | cut -d: -f1) >do > if [ -n "$(ifconfig "$BRIDGE" | grep -w "member: $IFNAME")" ] > then > echo "${0##*/}: Adding $1 as a member of $BRIDGE" > sudo /sbin/ifconfig "$BRIDGE" addm "$1" up > exit > fi >done > >BRIDGE="$(sudo /sbin/ifconfig bridge create)" >sudo /sbin/ifconfig "$BRIDGE" addm "$IFNAME" addm "$1" up >echo "${0##*/}: Created $BRIDGE and added $1 as a member" > >--- /usr/local/etc/qemu-ifdown > >#!/bin/sh ># ># /usr/local/etc/qemu-ifdown : martinko [20-aug-2009] ># > >for BRIDGE in $(ifconfig -a | grep '^bridge' | cut -d: -f1) >do > if [ -n "$(ifconfig "$BRIDGE" | grep -w "member: $1")" ] > then > if [ "$(ifconfig "$BRIDGE" | grep -c -w "member:")" -le 2 ] > then > echo "${0##*/}: Destroying $BRIDGE" > sudo /sbin/ifconfig "$BRIDGE" destroy > fi > echo "${0##*/}: Destroying $1" > sudo /sbin/ifconfig "$1" destroy > fi >done > >--- > >And that's all, folks! :) > >Enjoy and if you find a better solution please let me/us know. > >Cheers, > >Martin > >PS1: Of course change IFNAME in qemu-ifup according to your setup. >PS2: You man want/need to change the group in devfs.rules as well. I like the idea, but found it needs a patch to qemu or otherwise a KASSERT gets triggered in the tap driver (sys/net/if_tap.c:tap_destroy(), causing a `tapX flags is out of sync' panic if the driver is built with INVARIANTS) because the tap interface gets destroyed before its /dev/tap fd is closed: Index: qemu/net.c @@ -961,11 +961,12 @@ { TAPState *s = vc->opaque; - if (s->down_script[0]) - launch_script(s->down_script, s->down_script_arg, s->fd); - qemu_set_fd_handler(s->fd, NULL, NULL, NULL); close(s->fd); + + if (s->down_script[0]) + launch_script(s->down_script, s->down_script_arg, -1); + qemu_free(s); } I guess the driver could handle this condition more gracefully, but until then... Oh and I also found the ifdown script doesn't get called in all cases, like when you quit qemu via the monitor. Btw, can someone test this on 6.3? I'm wondering if we could ship these ifup/down scripts in the qemu port(s) by default, maybe with an rcvar added to enable them or something like that. (and the other config instructions in the pkg-message file.) If you don't mind... :) Thanx, Juergen From bakul at bitblocks.com Sun Aug 23 23:49:49 2009 From: bakul at bitblocks.com (Bakul Shah) Date: Sun Aug 23 23:49:55 2009 Subject: Automagic bridged networking with QEMU (tap) In-Reply-To: Your message of "Mon, 24 Aug 2009 00:15:52 +0200." <200908232215.n7NMFqkK007704@triton8.kn-bremen.de> References: <200908232215.n7NMFqkK007704@triton8.kn-bremen.de> Message-ID: <20090823233419.790325B2E@mail.bitblocks.com> I use something simpler that is perhaps less flexible but I find my machines don't have enough oomph to handle more than 3 or 4 qemu VMs! /boot/loader.conf if_tap_load="YES" # if_bridge will be autoloaded later /etc/rc.conf cloned_interfaces="bridge0" # create these interfaces on bootup autobridge_interfaces="bridge0" # autoconfigure these bridges autobridge_bridge0="tap* $eth" # $eth = eth interface you want bridged # if your machine has static ip address $ipaddr, with prefix length $len ifconfig_bridge0="inet $ipaddr/$len # if your machine is given a dynamic ip address #ifconfig_bridge0="DHCP" /etc/devfs.conf # create as many as you are likely to use own tap0 $user:$group # set to user/group of person invoking qemu own tap1 $user:$group own tap2 $user:$group own tap3 $user:$group /etc/sysctl.conf net.link.tap.user_open=1 net.link.tap.up_on_open=1 ln -s /usr/bin/true /etc/qemu-ifup ln -s /usr/bin/true /etc/qemu-ifdown Note that on a wifi only machine you are only allowed one mac address for the wifi link so bridging with VMs won't work and you need NAT but you can still bridge all your tap interfaces together. Also note that each qemu VM will need a unique mac address. On Mon, 24 Aug 2009 00:15:52 +0200 Juergen Lock wrote: > In article you write: > >Hallo list, > Hi! > > > >I spent a good portion of yesterday trying to find out how to change > >from using user mode to bridged networking with QEMU on FreeBSD 7.2. > >As I found a few how-to's of differing quality and I couldn't manage to > >make it work for some time, I decided to share the final results of my > >journey with you as I believe it may save someone a few hours or hair. > > > >The proposed solution does not need any manual steps and is fully > >transparent to users (like user mode networking is). It does not even > >permanently bridge your real NIC, only when necessary, which is good > >because of some performance penalties when bridging. And you can run as > >many guests as you want and it's all set up automagically. :-) > > > >OK, enough words, here's what to do: > > > >/boot/loader.conf[.local]: > > if_bridge_load="YES" > > if_tap_load="YES" > > > >/etc/sysctl.conf: > > net.link.tap.up_on_open=1 > > net.link.tap.user_open=1 > > > >/etc/devfs.rules: > > [localrules=10] > > add path 'tap*' mode 0660 > > > >/etc/rc.conf[.local]: > > devfs_system_ruleset="localrules" > > kqemu_enable="YES" > > > >/usr/local/etc/qemu-ifup -- custom script > >/usr/local/etc/qemu-ifdown -- custom script > > > >--- /usr/local/etc/qemu-ifup > > > >#!/bin/sh > ># > ># /usr/local/etc/qemu-ifup : martinko [20-aug-2009] > ># > > > >IFNAME=re0 > > > >for BRIDGE in $(ifconfig -a | grep '^bridge' | cut -d: -f1) > >do > > if [ -n "$(ifconfig "$BRIDGE" | grep -w "member: $IFNAME")" ] > > then > > echo "${0##*/}: Adding $1 as a member of $BRIDGE" > > sudo /sbin/ifconfig "$BRIDGE" addm "$1" up > > exit > > fi > >done > > > >BRIDGE="$(sudo /sbin/ifconfig bridge create)" > >sudo /sbin/ifconfig "$BRIDGE" addm "$IFNAME" addm "$1" up > >echo "${0##*/}: Created $BRIDGE and added $1 as a member" > > > >--- /usr/local/etc/qemu-ifdown > > > >#!/bin/sh > ># > ># /usr/local/etc/qemu-ifdown : martinko [20-aug-2009] > ># > > > >for BRIDGE in $(ifconfig -a | grep '^bridge' | cut -d: -f1) > >do > > if [ -n "$(ifconfig "$BRIDGE" | grep -w "member: $1")" ] > > then > > if [ "$(ifconfig "$BRIDGE" | grep -c -w "member:")" -le 2 ] > > then > > echo "${0##*/}: Destroying $BRIDGE" > > sudo /sbin/ifconfig "$BRIDGE" destroy > > fi > > echo "${0##*/}: Destroying $1" > > sudo /sbin/ifconfig "$1" destroy > > fi > >done > > > >--- > > > >And that's all, folks! :) > > > >Enjoy and if you find a better solution please let me/us know. > > > >Cheers, > > > >Martin > > > >PS1: Of course change IFNAME in qemu-ifup according to your setup. > >PS2: You man want/need to change the group in devfs.rules as well. > > I like the idea, but found it needs a patch to qemu or otherwise a > KASSERT gets triggered in the tap driver (sys/net/if_tap.c:tap_destroy(), > causing a `tapX flags is out of sync' panic if the driver is built with > INVARIANTS) because the tap interface gets destroyed before its /dev/tap > fd is closed: > > Index: qemu/net.c > @@ -961,11 +961,12 @@ > { > TAPState *s = vc->opaque; > > - if (s->down_script[0]) > - launch_script(s->down_script, s->down_script_arg, s->fd); > - > qemu_set_fd_handler(s->fd, NULL, NULL, NULL); > close(s->fd); > + > + if (s->down_script[0]) > + launch_script(s->down_script, s->down_script_arg, -1); > + > qemu_free(s); > } > > I guess the driver could handle this condition more gracefully, but > until then... Oh and I also found the ifdown script doesn't get called > in all cases, like when you quit qemu via the monitor. > > Btw, can someone test this on 6.3? I'm wondering if we could ship > these ifup/down scripts in the qemu port(s) by default, maybe with an > rcvar added to enable them or something like that. (and the other > config instructions in the pkg-message file.) If you don't mind... :) From gamato at users.sf.net Mon Aug 24 06:58:33 2009 From: gamato at users.sf.net (martinko) Date: Mon Aug 24 06:58:41 2009 Subject: Automagic bridged networking with QEMU (tap) In-Reply-To: <200908232215.n7NMFqkK007704@triton8.kn-bremen.de> References: <200908232215.n7NMFqkK007704@triton8.kn-bremen.de> Message-ID: Juergen Lock wrote: > > I like the idea, but found it needs a patch to qemu or otherwise a > KASSERT gets triggered in the tap driver (sys/net/if_tap.c:tap_destroy(), > causing a `tapX flags is out of sync' panic if the driver is built with > INVARIANTS) because the tap interface gets destroyed before its /dev/tap > fd is closed: > > Index: qemu/net.c > @@ -961,11 +961,12 @@ > { > TAPState *s = vc->opaque; > > - if (s->down_script[0]) > - launch_script(s->down_script, s->down_script_arg, s->fd); > - > qemu_set_fd_handler(s->fd, NULL, NULL, NULL); > close(s->fd); > + > + if (s->down_script[0]) > + launch_script(s->down_script, s->down_script_arg, -1); > + > qemu_free(s); > } > > I guess the driver could handle this condition more gracefully, but > until then... Oh and I also found the ifdown script doesn't get called > in all cases, like when you quit qemu via the monitor. > > Btw, can someone test this on 6.3? I'm wondering if we could ship > these ifup/down scripts in the qemu port(s) by default, maybe with an > rcvar added to enable them or something like that. (and the other > config instructions in the pkg-message file.) If you don't mind... :) Hallo Juergen, I certainly don't mind shipping those scripts of mine. Thank you for the patch, I wasn't aware of any panics, though I was thinking along the lines if it's ok to destroy a tap while Qemu apparently has got it open. I don't use Qemu monitor but I quess quitting from there should behave the same way and it's a Qemu bug if the scripts are not called, imho. Regards and thank you for all the work on Qemu port. Martin From gamato at users.sf.net Mon Aug 24 07:35:03 2009 From: gamato at users.sf.net (martinko) Date: Mon Aug 24 07:35:13 2009 Subject: Automagic bridged networking with QEMU (tap) In-Reply-To: <20090823233419.790325B2E@mail.bitblocks.com> References: <200908232215.n7NMFqkK007704@triton8.kn-bremen.de> <20090823233419.790325B2E@mail.bitblocks.com> Message-ID: Bakul Shah wrote: > I use something simpler that is perhaps less flexible but I > find my machines don't have enough oomph to handle more than > 3 or 4 qemu VMs! > > /boot/loader.conf > if_tap_load="YES" # if_bridge will be autoloaded later > > /etc/rc.conf > cloned_interfaces="bridge0" # create these interfaces on bootup > autobridge_interfaces="bridge0" # autoconfigure these bridges > autobridge_bridge0="tap* $eth" # $eth = eth interface you want bridged > > # if your machine has static ip address $ipaddr, with prefix length $len > ifconfig_bridge0="inet $ipaddr/$len > > # if your machine is given a dynamic ip address > #ifconfig_bridge0="DHCP" > > /etc/devfs.conf > # create as many as you are likely to use > own tap0 $user:$group # set to user/group of person invoking qemu > own tap1 $user:$group > own tap2 $user:$group > own tap3 $user:$group > > /etc/sysctl.conf > net.link.tap.user_open=1 > net.link.tap.up_on_open=1 > > ln -s /usr/bin/true /etc/qemu-ifup > ln -s /usr/bin/true /etc/qemu-ifdown Hi, I was thinking of using autobridge but eventually decided not to because: - Putting an interface into bridge has certain drawbacks like disabling checksum offloading. So I'd prefer not to bridge until I have to. - I'm not sure whether it's generally acceptable to autobridge all tap* devices. I might be OK with it now but I may not in the future and/or other users may have different uses of tap* devices. Problem with your devfs.conf is that it's static and thus the solution is sort of halfway between not using autobridging at all (precreating a few tap? devices and bridging them in rc.conf, like I found in many examples on the internet). Again, it may be OK for you and me but I was trying to find a more general solution. Also, I'm not sure how is it possible that it works for you at all. I tried "perm tap* 0660" but it did not work and then I learned devfs.conf is only good for interfaces available at boot. That's why I had to use /etc/devfs.rules config file. > Note that on a wifi only machine you are only allowed one mac > address for the wifi link so bridging with VMs won't work and > you need NAT but you can still bridge all your tap interfaces > together. Thanks for the note, I wasn't aware of this. Although I guess that if people run VMs on wifi connected machines they would be happy with user mode networking. > Also note that each qemu VM will need a unique mac address. Yes, this is true and I wrote another script to help me automate it. And MAC generation is "stolen" from you -- thank you for publishing! :-) Well, the script is not that general and polished but here it is: --- #!/bin/sh # # ~/bin/qemu_tap : mato [21-aug-2009] # # 1st parameter must be number of bridged NICs to create (tap interface) # 3rd parameter should be primary / boot disk (MACs are generated based on it) # [ "$1" -ge 0 ] || { echo "usage: ${0##*/} number_of_nics [qemu_options]" >&2 ; exit 1 ; } nics="$1" shift opts="$*" vlan=0 macaddr() { echo "52:54:00:$(echo "$1" | md5 | cut -c1-6 | sed 's/\(..\)\(..\)/\1:\2:/')" } while [ $vlan -lt "$nics" ] do opts="$opts -net nic,vlan=$vlan,macaddr=$(macaddr "$(realpath $2)-$vlan") -net tap,vlan=$vlan" vlan="$(expr $vlan + 1)" done exec qemu $opts --- I create a runscript for each VM I want to bridge as follows: $ cat img/matoqemu #!/bin/sh qemu_tap 1 -hda ~/img/matoqemu_winxp-pro-en-vlp.raw.img -name matoqemu/192.168.11.201 -alt-grab -kernel-kqemu -localtime -soundhw es1370 -m 256 "$@" For ad hoc VMs and ones I do not require to be bridged I happily use qemu-launcher (though I haven't tried anything else and I would certainly welcome port of qemuctl). With regards, Martin From bugmaster at FreeBSD.org Mon Aug 24 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 24 11:07:52 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200908241106.n7OB6qP6048530@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/137332 emulation add caution messages to some adobe products f ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o ports/135322 emulation Port graphics/linux_dri has incorrect packaging list c o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/97326 emulation [linux] file descriptor leakage in linux emulation o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 18 problems total. From bakul at bitblocks.com Mon Aug 24 15:59:04 2009 From: bakul at bitblocks.com (Bakul Shah) Date: Mon Aug 24 15:59:10 2009 Subject: Automagic bridged networking with QEMU (tap) In-Reply-To: Your message of "Mon, 24 Aug 2009 09:34:39 +0200." References: <200908232215.n7NMFqkK007704@triton8.kn-bremen.de> <20090823233419.790325B2E@mail.bitblocks.com> Message-ID: <20090824155902.0C9675B30@mail.bitblocks.com> On Mon, 24 Aug 2009 09:34:39 +0200 martinko wrote: > > I was thinking of using autobridge but eventually decided not to because: > - Putting an interface into bridge has certain drawbacks like disabling > checksum offloading. So I'd prefer not to bridge until I have to. > - I'm not sure whether it's generally acceptable to autobridge all tap* > devices. I might be OK with it now but I may not in the future and/or > other users may have different uses of tap* devices. > > Problem with your devfs.conf is that it's static and thus the solution > is sort of halfway between not using autobridging at all (precreating a > few tap? devices and bridging them in rc.conf, like I found in many > examples on the internet). Again, it may be OK for you and me but I was > trying to find a more general solution. There is no one solution that works for all. In any case we have to touch too many files and things like devfs.conf and devfs.rules are confusing so what would be most useful is a "wizard" script that asks some questions and modifies appropriate files to configure qemu. > Also, I'm not sure how is it possible that it works for you at all. I > tried "perm tap* 0660" but it did not work and then I learned > devfs.conf is only good for interfaces available at boot. It works fine for me. I think you have to use specific tap devices and not tap*. If you want the same behavior for additional tap devices created at run time, devfs.conf won't do. From doconnor at gsoft.com.au Tue Aug 25 14:30:01 2009 From: doconnor at gsoft.com.au (Daniel O'Connor) Date: Tue Aug 25 14:30:07 2009 Subject: virtualbox port bug Message-ID: <200908252327.00701.doconnor@gsoft.com.au> Hi, The Virtualbox port works fine except that the permissions on /usr/local/lib/virtualbox appear to be too restrictive. I think it should be 755 (or 555, or perhaps 550 :vboxusers), but when I install it, it's 700 and hence no-one except root can use it. Please CC me, I'm not on the list. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: This is a digitally signed message part. Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090825/9100b869/attachment.pgp From rwatson at FreeBSD.org Tue Aug 25 16:39:00 2009 From: rwatson at FreeBSD.org (Robert Watson) Date: Tue Aug 25 16:39:29 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: <4A8EB3D2.7010109@shapeshifter.se> References: <4A8EB3D2.7010109@shapeshifter.se> Message-ID: On Fri, 21 Aug 2009, Fredrik Lindberg wrote: > I've started working on the missing bits of the FreeBSD network > implementation in VirtualBox. > > I now have a working vboxnetflt.ko driver that allows automatic bridged > networking in VirtualBox (probably what most people want). This allows > guests to automatically bridge with your existing network adapter providing > seamless network access. > > Work on host-only adapter mode is in progress (this should not be confused > with host-interface in previous vbox 2.x releases). Hi Fredrik: The technical approach you've taken here is a bit unusual and potentially quite fragile -- replacing the method pointers on struct ifnet's maintained by other drivers and "borrowing" spare fields is likely going to prove problematic in the future (and, in fact, already). It looks like a lot of what the driver is trying to accomplish can already be done entirely from userspace using bpf(4): taking a tee of incoming frames arriving at the NIC, perhaps selecting down to ones to specific ethernet addresses, taking the card into and out of promiscuous mode, and injecting frames into the output path, are exactly what BPF is designed to support. I was wondering if you'd looked at this approach as an alternative to a custom kernel driver? Robert > > The patch can be found at > http://www.shapeshifter.se/pub/patches/vbox-freebsd-network.patch > > Additional patch for emulators/virtualbox/Makefile > http://www.shapeshifter.se/pub/patches/virtualbox-Makefile.patch > > > You'll have to rebuild VirtualBox to make it work, the following lines > should do the trick. > > cd /usr/ports/emulators/virtualbox > make clean patch > mkdir work/virtualbox-3.0.51r22226/src/VBox/HostDrivers/VBoxNetFlt/freebsd > > patch -d work/virtualbox-3.0.51r22226 < vbox-freebsd-network.patch > patch < virtualbox-Makefile.patch > make install > > In addition to vboxdrv.ko you'll need to load vboxnetflt.ko too. > > kldload /boot/modules/vboxnetflt.ko > > In VirtualBox network settings, under "Bridged Adapter" you should now > see your available network interfaces. Select the one connected to your > network and boot your virtual machine. It should now be connected to > your local network as any other machine. > > > Please note that this is just the first iteration of the patch and it > should by no means be considered complete. It has only been tested > on FreeBSD 8/i386. Slippery when wet :) > > > The kld is also a bit hackish at the moment regarding to how it > interfaces with the network stack to avoid kernel code modifications. > > Fredrik > _______________________________________________ > 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" > From fli at shapeshifter.se Tue Aug 25 18:00:34 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Tue Aug 25 18:00:40 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: References: <4A8EB3D2.7010109@shapeshifter.se> Message-ID: <4A9426BD.1050503@shapeshifter.se> Robert Watson wrote: > > On Fri, 21 Aug 2009, Fredrik Lindberg wrote: > >> I've started working on the missing bits of the FreeBSD network >> implementation in VirtualBox. >> >> I now have a working vboxnetflt.ko driver that allows automatic >> bridged networking in VirtualBox (probably what most people want). >> This allows guests to automatically bridge with your existing network >> adapter providing seamless network access. >> >> Work on host-only adapter mode is in progress (this should not be >> confused with host-interface in previous vbox 2.x releases). > > Hi Fredrik: > > The technical approach you've taken here is a bit unusual and > potentially quite fragile -- replacing the method pointers on struct > ifnet's maintained by other drivers and "borrowing" spare fields is > likely going to prove problematic in the future (and, in fact, already). > > It looks like a lot of what the driver is trying to accomplish can > already be done entirely from userspace using bpf(4): taking a tee of > incoming frames arriving at the NIC, perhaps selecting down to ones to > specific ethernet addresses, taking the card into and out of promiscuous > mode, and injecting frames into the output path, are exactly what BPF is > designed to support. I was wondering if you'd looked at this approach > as an alternative to a custom kernel driver? > > Robert > That's why I ended my mail by saying it's "hackish" (which usually mean fragile) :) vboxnetflt is a driver that exists for all operating systems capable of running in virtualbox host mode. It consists of both operating system independent code and operating system dependent code. This together forms a kernel module (on all host OS) which in turn depend on symbols in the other kernel support driver (vboxdrv.ko). So, unless we re-write a lot of the generic code in VBox, this have to be done in the kernel (disclaimer, I haven't really looked on what would have to be changed, but it's not very attractive to start messing with their generic code). I've actually looked at BPF..but didn't find a clean API from the kernel (maybe I just don't know where to look). (Opening /dev/bpf from the kernel seemed just as fragile as the current approach if it's even possible). The third approach is to add vbox glue to ifnet and ether_output, but that is just as bad (accounting for third party software in the kernel is just ugly). At least Darwin seems to have a "filtering" mechanism that allows you to manipulate mbufs before they are sent to the interface. Linux seems to have a similar mechanism, but not as flexible as the one in Darwin. I was thinking along the same lines for FreeBSD. Implementing generic hooks in the input/output path that could be used for vbox, if_bridge, carp, etc, instead of the current hard coded calls in ether_{output,input}. This could also have the effect of removing module specific glue from struct ifnet. Anything worth pursuing ? Fredrik Lindberg From julian at elischer.org Wed Aug 26 17:46:57 2009 From: julian at elischer.org (Julian Elischer) Date: Wed Aug 26 17:47:03 2009 Subject: freebsd-emulation Digest, Vol 330, Issue 3 In-Reply-To: <20090826120020.27CAE106570D@hub.freebsd.org> References: <20090826120020.27CAE106570D@hub.freebsd.org> Message-ID: <4A9571F3.1010605@elischer.org> ----- Robert said: > Hi Fredrik: > > The technical approach you've taken here is a bit unusual > and potentially quite fragile -- replacing the method pointers > on struct ifnet's maintained by other drivers and "borrowing" > spare fields is likely going to prove problematic in the future > (and, in fact, already). > > It looks like a lot of what the driver is trying to accomplish > can already be one entirely from userspace using bpf(4): taking > a tee of incoming frames arriving at the NIC, perhaps selecting > down to ones to specific ethernet addresses, taking the card into > and out of promiscuous mode, and injecting frames into the > output path, are exactly what BPF is designed to support. I > was wondering if you'd looked at this approach as an alternative > to a custom kernel driver? > > Robert -------------End quote---------- BPF is pretty lousy for that job.. Take a look at the netgraph hooks at interface level to divert packets to other destinations. From matheus at eternamente.info Wed Aug 26 20:56:32 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Wed Aug 26 20:56:39 2009 Subject: vbox 3.0.51 and 8-beta3 Message-ID: <72dfada5029c91e5704436ec501297e7.squirrel@cygnus.homeunix.com> hail, this same machine runs on in 7.2-stable. I get instant machine (just guest) crash. there was a message to send this files. if any further help needed. by the way, has anyone ever got this scenario to work ? amd64 guest running two cpu on 8-betaX. thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From pluknet at gmail.com Thu Aug 27 09:29:48 2009 From: pluknet at gmail.com (pluknet) Date: Thu Aug 27 09:29:55 2009 Subject: acquiring duplicate lock of same type: "ftlk" Message-ID: Hi. Got it on FreeBSD 9.0-CURRENT while been running in Xorg, don't know where exactly. Acquiring duplicate lock of same type: "ftlk" 1st ftlk @ /usr/src/sys/modules/linux/../../compat/linux/linux_futex.c:177 2nd ftlk @ /usr/src/sys/modules/linux/../../compat/linux/linux_futex.c:203 KDB: stack backtrace: db_trace_self_wrapper(c07fd8ea,ea393b58,c060a145,c05fac1b,c08007b2,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c05fac1b,c08007b2,c0b49757,c58ead20,ea393bb4,...) at kdb_backtrace+0x29 _witness_debugger(c08007b2,c0b49793,c0b49757,cb,0,...) at _witness_debugger+0x25 witness_checkorder(c9bba780,9,c0b49757,cb,0,...) at witness_checkorder+0x469 _sx_xlock(c9bba780,0,c0b49757,cb,0,...) at _sx_xlock+0x85 futex_get0(c0609f8c,c09cc7a8,c9ac7764,c09cc7a8,c084df3c,...) at futex_get0+0x116 linux_sys_futex(c9ac76c0,ea393cf8,ea393d18,ea393d1c,c0b4cf40,...) at linux_sys_futex+0x6f syscall(ea393d38) at syscall+0x2b4 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (240, Linux ELF, linux_sys_futex), eip = 0x28799533, esp = 0xbfbfc0cc, ebp = 0x4000001 --- -- wbr, pluknet From rwatson at FreeBSD.org Fri Aug 28 21:25:27 2009 From: rwatson at FreeBSD.org (Robert Watson) Date: Fri Aug 28 21:25:34 2009 Subject: VirtualBox bridged adapter (vboxnetflt) In-Reply-To: <4A9426BD.1050503@shapeshifter.se> References: <4A8EB3D2.7010109@shapeshifter.se> <4A9426BD.1050503@shapeshifter.se> Message-ID: On Tue, 25 Aug 2009, Fredrik Lindberg wrote: > That's why I ended my mail by saying it's "hackish" (which usually mean > fragile) :) > > vboxnetflt is a driver that exists for all operating systems capable of > running in virtualbox host mode. It consists of both operating system > independent code and operating system dependent code. This together forms a > kernel module (on all host OS) which in turn depend on symbols in the other > kernel support driver (vboxdrv.ko). > > So, unless we re-write a lot of the generic code in VBox, this have to be > done in the kernel (disclaimer, I haven't really looked on what would have > to be changed, but it's not very attractive to start messing with their > generic code). > > I've actually looked at BPF..but didn't find a clean API from the kernel > (maybe I just don't know where to look). (Opening /dev/bpf from the kernel > seemed just as fragile as the current approach if it's even possible). > > The third approach is to add vbox glue to ifnet and ether_output, but that > is just as bad (accounting for third party software in the kernel is just > ugly). > > At least Darwin seems to have a "filtering" mechanism that allows you to > manipulate mbufs before they are sent to the interface. Linux seems to have > a similar mechanism, but not as flexible as the one in Darwin. > > I was thinking along the same lines for FreeBSD. Implementing generic hooks > in the input/output path that could be used for vbox, if_bridge, carp, etc, > instead of the current hard coded calls in ether_{output,input}. This could > also have the effect of removing module specific glue from struct ifnet. > Anything worth pursuing ? In the past, we've talked about adding PFIL hooks for interface input/output paths, and in fact there's already a PFIL constant for it, it's just not hooked up to anything: PFIL_TYPE_IFNET. I think it would be a useful to flesh this out, but we'll need to decide where to place them. I think the right spot is probably in the link layer input/output routines - ether_{input,output} in particular, but also at other layers, such as in the VLAN code. Not for 8.0, obviously. :-) You'll still need to use an m_tag so you can mark traffic you've generated and ignore it when it gets picked up by a hook, of course. Robert N M Watson Computer Laboratory University of Cambridge From nox at jelal.kn-bremen.de Sat Aug 29 22:27:52 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sat Aug 29 22:27:59 2009 Subject: experimental FreeBSD qemu-devel git head port update for testing Message-ID: <20090829222339.GA93608@triton8.kn-bremen.de> Hi! Jan Kiszka asked me if the unstable guest timer irq problem still exists on qemu git head, so I made an update for that today: http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch (and found out it does.) The bad news (for FreeBSD users anyway) is kqemu support has now been removed as `promised' (by the upstream qemu developers), so testing this version is probably less interesting for many FreeBSD users than the qemu 0.11 stable branch snapshot I posted about here, http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006646.html but e.g. users of non-x86 targets probably will still be interested. Also the pcap patch stopped working in this snapshot and I don't yet know why. (I think the original version of that patch was submitted by Jung-uk Kim, maybe he has an idea; Cc'd.) Other misc notes: 1. I had to replace the line CFLAGS += $(call cc-option, $(CFLAGS), -fno-stack-protector,"") by CFLAGS += -fno-stack-protector in qemu/pc-bios/optionrom/Makefile because now make complained about recursive use of CFLAGS (in addition to forcing use of a newer as(1) for multiboot.S as already mentioned for the 0.11 rc, see files/patch-pc-bios-optionrom-Makefile in the update.) 2. vl.c references __FreeBSD_version in a few places but still didn't #include to get the definition: Index: qemu/vl.c @@ -57,6 +57,7 @@ #include #if defined(__FreeBSD__) || defined(__DragonFly__) #include +#include #else #include #endif 3. Do you guys think the posix timer patch is ready to be committed now? It _might_ cause -lrt to end up in $LIBS twice now tho. (not on FreeBSD since clock_gettime() is in libc there.) Btw it (-clock dynticks) also does't help the mentioned timer irq problems... Index: qemu/configure @@ -1538,6 +1538,20 @@ LIBS="-lrt $LIBS" fi +########################################## +# posix timer probe +cat > $TMPC < +int main(void) { timer_create(CLOCK_REALTIME, (struct sigevent *)NULL, (timer_t *)NULL); return 0; } +EOF +posixtimer=no +if compile_prog "" "" ; then + posixtimer=yes +elif compile_prog "" "-lrt" ; then + posixtimer=yes + LIBS="-lrt $LIBS" +fi + # Determine what linker flags to use to force archive inclusion check_linker_flags() { @@ -1872,6 +1886,9 @@ if test "$fdt" = "yes" ; then echo "CONFIG_FDT=y" >> $config_host_mak fi +if test "$posixtimer" = "yes" ; then + echo "CONFIG_POSIX_TIMER=y" >> $config_host_mak +fi # XXX: suppress that if [ "$bsd" = "yes" ] ; then Index: qemu/vl.c @@ -918,12 +918,16 @@ static int unix_start_timer(struct qemu_alarm_timer *t); static void unix_stop_timer(struct qemu_alarm_timer *t); -#ifdef __linux__ +#ifdef CONFIG_POSIX_TIMER static int dynticks_start_timer(struct qemu_alarm_timer *t); static void dynticks_stop_timer(struct qemu_alarm_timer *t); static void dynticks_rearm_timer(struct qemu_alarm_timer *t); +#endif + +#ifdef __linux__ + static int hpet_start_timer(struct qemu_alarm_timer *t); static void hpet_stop_timer(struct qemu_alarm_timer *t); @@ -1001,9 +1005,11 @@ static struct qemu_alarm_timer alarm_timers[] = { #ifndef _WIN32 -#ifdef __linux__ +#ifdef CONFIG_POSIX_TIMER {"dynticks", ALARM_FLAG_DYNTICKS, dynticks_start_timer, dynticks_stop_timer, dynticks_rearm_timer, NULL}, +#endif +#ifdef __linux__ /* HPET - if available - is preferred */ {"hpet", 0, hpet_start_timer, hpet_stop_timer, NULL, NULL}, /* ...otherwise try RTC */ @@ -1361,7 +1367,7 @@ return delta; } -#if defined(__linux__) || defined(_WIN32) +#if defined(CONFIG_POSIX_TIMER) || defined(_WIN32) static uint64_t qemu_next_deadline_dyntick(void) { int64_t delta; @@ -1506,6 +1512,10 @@ close(rtc_fd); } +#endif /* defined(__linux__) */ + +#ifdef CONFIG_POSIX_TIMER + static int dynticks_start_timer(struct qemu_alarm_timer *t) { struct sigevent ev; @@ -1577,7 +1587,7 @@ } } -#endif /* defined(__linux__) */ +#endif /* defined(CONFIG_POSIX_TIMER) */ static int unix_start_timer(struct qemu_alarm_timer *t) { Signed-off-by: Juergen Lock From av1474 at comtv.ru Sun Aug 30 00:49:21 2009 From: av1474 at comtv.ru (malc) Date: Sun Aug 30 00:49:28 2009 Subject: [Qemu-devel] experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: <20090829222339.GA93608@triton8.kn-bremen.de> References: <20090829222339.GA93608@triton8.kn-bremen.de> Message-ID: On Sun, 30 Aug 2009, Juergen Lock wrote: > Hi! > > Jan Kiszka asked me if the unstable guest timer irq problem still > exists on qemu git head, so I made an update for that today: > http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch > (and found out it does.) > > The bad news (for FreeBSD users anyway) is kqemu support has now been > removed as `promised' (by the upstream qemu developers), so testing this > version is probably less interesting for many FreeBSD users than the > qemu 0.11 stable branch snapshot I posted about here, > http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006646.html > but e.g. users of non-x86 targets probably will still be interested. > > Also the pcap patch stopped working in this snapshot and I don't yet > know why. (I think the original version of that patch was submitted by > Jung-uk Kim, maybe he has an idea; Cc'd.) > > Other misc notes: > > 1. I had to replace the line > CFLAGS += $(call cc-option, $(CFLAGS), -fno-stack-protector,"") > by > CFLAGS += -fno-stack-protector > in qemu/pc-bios/optionrom/Makefile because now make complained about > recursive use of CFLAGS (in addition to forcing use of a newer as(1) > for multiboot.S as already mentioned for the 0.11 rc, see > files/patch-pc-bios-optionrom-Makefile in the update.) Less violent way to have it is: CFLAGS := $(CFLAGS) $(call cc-option, $(CFLAGS), -fno-stack-protector,"") [..snip..] -- mailto:av1474@comtv.ru From nox at jelal.kn-bremen.de Sun Aug 30 19:12:10 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun Aug 30 19:12:17 2009 Subject: [Qemu-devel] experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: References: <20090829222339.GA93608@triton8.kn-bremen.de> Message-ID: <20090830190902.GA40977@triton8.kn-bremen.de> On Sun, Aug 30, 2009 at 03:49:17AM +0400, malc wrote: > On Sun, 30 Aug 2009, Juergen Lock wrote: > > > Hi! > > > > Jan Kiszka asked me if the unstable guest timer irq problem still > > exists on qemu git head, so I made an update for that today: > > http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch > > (and found out it does.) > > > > The bad news (for FreeBSD users anyway) is kqemu support has now been > > removed as `promised' (by the upstream qemu developers), so testing this > > version is probably less interesting for many FreeBSD users than the > > qemu 0.11 stable branch snapshot I posted about here, > > http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006646.html > > but e.g. users of non-x86 targets probably will still be interested. > > > > Also the pcap patch stopped working in this snapshot and I don't yet > > know why. (I think the original version of that patch was submitted by > > Jung-uk Kim, maybe he has an idea; Cc'd.) > > > > Other misc notes: > > > > 1. I had to replace the line > > CFLAGS += $(call cc-option, $(CFLAGS), -fno-stack-protector,"") > > by > > CFLAGS += -fno-stack-protector > > in qemu/pc-bios/optionrom/Makefile because now make complained about > > recursive use of CFLAGS (in addition to forcing use of a newer as(1) > > for multiboot.S as already mentioned for the 0.11 rc, see > > files/patch-pc-bios-optionrom-Makefile in the update.) > > Less violent way to have it is: > > CFLAGS := $(CFLAGS) $(call cc-option, $(CFLAGS), -fno-stack-protector,"") > > [..snip..] Thanx, that seems to work as well. Juergen From ivoras at freebsd.org Mon Aug 31 08:26:19 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Mon Aug 31 08:26:25 2009 Subject: experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: <20090829222339.GA93608@triton8.kn-bremen.de> References: <20090829222339.GA93608@triton8.kn-bremen.de> Message-ID: Juergen Lock wrote: > The bad news (for FreeBSD users anyway) is kqemu support has now been > removed as `promised' (by the upstream qemu developers), so testing this > version is probably less interesting for many FreeBSD users than the Why was kqemu support removed? Lack of interest and testing? From bugmaster at FreeBSD.org Mon Aug 31 11:07:04 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 31 11:07:51 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200908311107.n7VB73wY070515@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/137332 emulation add caution messages to some adobe products f ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o ports/135322 emulation Port graphics/linux_dri has incorrect packaging list c o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/97326 emulation [linux] file descriptor leakage in linux emulation o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 18 problems total. From uqs at spoerlein.net Mon Aug 31 21:12:19 2009 From: uqs at spoerlein.net (Ulrich =?utf-8?B?U3DDtnJsZWlu?=) Date: Mon Aug 31 21:12:26 2009 Subject: Thanks to wine developers/porters Message-ID: <20090831211217.GR50352@acme.spoerlein.net> Hi, just wanted to thank those who made it possible to run an i386 wine binary on amd64 and have it just work. I wrote the steps down in the wiki wine article, for those to whom they are not obvious. Again, thanks! Uli From nox at jelal.kn-bremen.de Mon Aug 31 22:20:13 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Mon Aug 31 22:20:23 2009 Subject: experimental FreeBSD qemu-devel git head port update for testing In-Reply-To: References: <20090829222339.GA93608@triton8.kn-bremen.de> Message-ID: <200908312217.n7VMH6Zk033623@triton8.kn-bremen.de> In article you write: >Juergen Lock wrote: > >> The bad news (for FreeBSD users anyway) is kqemu support has now been >> removed as `promised' (by the upstream qemu developers), so testing this >> version is probably less interesting for many FreeBSD users than the > >Why was kqemu support removed? Lack of interest and testing? In a way... Linux has moved on to kvm now (and yes we could relly use an up to date and working port for that [1]!), the original kqemu author has left the project and so there was no real maintainer for that code anymore that would have removed limitations kqemu imposed on qemu like the ~2G guest ram limit, or even make kqemu ready for inclusion in the Linux kernel... (since Linux seems to have a policy of discouraging out-of-tree kernel modules; kvm btw is in there now.) [1] Links: kvm: http://www.linux-kvm.org/page/Main_Page older (gsoc 07) kvm porting project: http://wiki.freebsd.org/FabioChecconi/PortingLinuxKVMToFreeBSD another seemingly dormant kvm-like project: http://sp01.cs.rice.edu/comp521/index.php/fkvm