From owner-freebsd-emulation@FreeBSD.ORG Sun Jul 15 23:30:23 2012 Return-Path: Delivered-To: emulation@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59E5C106564A; Sun, 15 Jul 2012 23:30:23 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2D0A58FC15; Sun, 15 Jul 2012 23:30:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6FNUNrL080177; Sun, 15 Jul 2012 23:30:23 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6FNUN5K080171; Sun, 15 Jul 2012 23:30:23 GMT (envelope-from edwin) Date: Sun, 15 Jul 2012 23:30:23 GMT Message-Id: <201207152330.q6FNUN5K080171@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, emulation@FreeBSD.org From: edwin@FreeBSD.org Cc: Subject: Re: ports/169896: [patch] audio/linux-f10-alsa-lib: use OSS plugin by default X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jul 2012 23:30:23 -0000 Synopsis: [patch] audio/linux-f10-alsa-lib: use OSS plugin by default Responsible-Changed-From-To: freebsd-ports-bugs->emulation Responsible-Changed-By: edwin Responsible-Changed-When: Sun Jul 15 23:30:22 UTC 2012 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=169896 From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 16 03:15:30 2012 Return-Path: Delivered-To: freebsd-emulation@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F25DD1065687; Mon, 16 Jul 2012 03:15:29 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C57FF8FC17; Mon, 16 Jul 2012 03:15:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6G3FTnI017358; Mon, 16 Jul 2012 03:15:29 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6G3FTHC017354; Mon, 16 Jul 2012 03:15:29 GMT (envelope-from linimon) Date: Mon, 16 Jul 2012 03:15:29 GMT Message-Id: <201207160315.q6G3FTHC017354@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-emulation@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/169814: [linux] ptrace is broken in Linux emulation X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2012 03:15:30 -0000 Old Synopsis: ptrace is broken in Linux emulation New Synopsis: [linux] ptrace is broken in Linux emulation Responsible-Changed-From-To: freebsd-bugs->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jul 16 03:15:13 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=169814 From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 16 04:34:19 2012 Return-Path: Delivered-To: freebsd-emulation@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF7C31065670; Mon, 16 Jul 2012 04:34:19 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B220E8FC12; Mon, 16 Jul 2012 04:34:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6G4YJKX028489; Mon, 16 Jul 2012 04:34:19 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6G4YJOa028484; Mon, 16 Jul 2012 04:34:19 GMT (envelope-from linimon) Date: Mon, 16 Jul 2012 04:34:19 GMT Message-Id: <201207160434.q6G4YJOa028484@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-emulation@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/169805: [linux] utime() syscall does not work in linuxulator X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2012 04:34:20 -0000 Old Synopsis: utime() syscall does not work in linuxulator New Synopsis: [linux] utime() syscall does not work in linuxulator Responsible-Changed-From-To: freebsd-i386->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jul 16 04:33:51 UTC 2012 Responsible-Changed-Why: reclassify http://www.freebsd.org/cgi/query-pr.cgi?pr=169805 From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 16 11:08:29 2012 Return-Path: Delivered-To: emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A0B971065670 for ; Mon, 16 Jul 2012 11:08:29 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7249B8FC15 for ; Mon, 16 Jul 2012 11:08:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6GB8Tcm093812 for ; Mon, 16 Jul 2012 11:08:29 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6GB8SKS093809 for emulation@FreeBSD.org; Mon, 16 Jul 2012 11:08:28 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Jul 2012 11:08:28 GMT Message-Id: <201207161108.q6GB8SKS093809@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: emulation@FreeBSD.org Cc: Subject: Current problem reports assigned to emulation@FreeBSD.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2012 11:08:29 -0000 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/169896 emulation [patch] audio/linux-f10-alsa-lib: use OSS plugin by de o ports/169702 emulation [patch] graphics/linux-f10-tiff: fix packing list 2 problems total. From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 16 11:08:49 2012 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C69B0106564A for ; Mon, 16 Jul 2012 11:08:49 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 972858FC0C for ; Mon, 16 Jul 2012 11:08:49 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6GB8nPJ093948 for ; Mon, 16 Jul 2012 11:08:49 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6GB8mdv093945 for freebsd-emulation@FreeBSD.org; Mon, 16 Jul 2012 11:08:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Jul 2012 11:08:48 GMT Message-Id: <201207161108.q6GB8mdv093945@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-emulation@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2012 11:08:49 -0000 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 kern/169814 emulation [linux] ptrace is broken in Linux emulation o kern/169805 emulation [linux] utime() syscall does not work in linuxulator o kern/159646 emulation [linux] [patch] bump Linux version in linuxulator f kern/156691 emulation [vmware] [panic] panic when using hard disks as RAW de o kern/156353 emulation [ibcs2] ibcs2 binaries that execute on 4.x not working o kern/155577 emulation [boot] BTX halted after install. Reboot during install o kern/155040 emulation [linux] [patch] Linux recvfrom doesn't handle proto fa o kern/153990 emulation [hyper-v]: Will not install into Hyper-V on Server 200 o kern/153887 emulation [linux] Linux emulator not understand STB_GNU_UNIQUE b o kern/153243 emulation [ibcs2] Seg fault whne running COFF binary using iBCS2 o kern/151714 emulation [linux] print/acroread9 not usable due to lack of supp a bin/150262 emulation [patch] truss(1) -f doesn't follow descendants of the a kern/150186 emulation [parallels] [panic] Parallels Desktop: CDROM disconnec o ports/148097 emulation [patch] suggested addition to linux_base-* packages to o ports/148096 emulation emulators/linux_base-* can not be built from ports on o kern/147793 emulation [vmware] [panic] cdrom handling, panic, possible race o kern/146237 emulation [linux] Linux binaries not reading directories mounted p kern/144584 emulation [linprocfs][patch] bogus values in linprocfs o ports/142837 emulation [patch] emulators/linux_base-* packages fails to insta o kern/140156 emulation [linux] cdparanoia fails to read drive data f kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage s kern/133144 emulation [linux] linuxulator 2.6 crashes with nvidias libGL.so. o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/86619 emulation [linux] linux emulator interacts oddly with cp a kern/72920 emulation [linux] path "prefixing" is not done on unix domain so o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/36952 emulation [patch] [linux] ldd(1) command of linux does not work o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 32 problems total. From owner-freebsd-emulation@FreeBSD.ORG Wed Jul 18 10:54:29 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E26E0106564A; Wed, 18 Jul 2012 10:54:29 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 4A6008FC1A; Wed, 18 Jul 2012 10:54:29 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so1216526wgb.31 for ; Wed, 18 Jul 2012 03:54:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:user-agent:cc:mime-version:content-type :content-transfer-encoding:message-id; bh=A7kfS8qCZWX7SvwVti+iaw+zE/ynvfd2eDKgCHaCy5A=; b=HK2m7NK1QJ28Kp8H1/r0VG34dWpGAK9DmMZiQTGKyQ/9WQhrhfRFfxK5pdadrV9mH5 gXDYuWLA22dAcz404ShIywta4fWPcs/KmEr4iuz8vZe/aVKALkLnnRcCPIXQEe5XUn99 SfkpZb/M5dpCtHps2jxlzW8g9RwOexeg2QiC3K87Eh/YPlYtaOyLGXusfCMWy4a+U6TY I0Jt2/1ZaxERBvPwoqQbALJVnSktm9VwdXz1FGYDm78FyNvusxFeBrl/g980l41NeWU8 hyu0K6tmErojXcz/g233/n6PJdchBIvnl4IavNcMAYh77XDEA9YX2Yz5yQkAYTIx/Ez3 M8KA== Received: by 10.180.84.104 with SMTP id x8mr5433629wiy.20.1342608868289; Wed, 18 Jul 2012 03:54:28 -0700 (PDT) Received: from dragon.dg (41-132-92-160.dsl.mweb.co.za. [41.132.92.160]) by mx.google.com with ESMTPS id de10sm2239753wib.7.2012.07.18.03.54.18 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 Jul 2012 03:54:27 -0700 (PDT) From: David Naylor To: freebsd-emulation@freebsd.org Date: Wed, 18 Jul 2012 12:53:22 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-STABLE; KDE/4.8.4; amd64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2813538.HCfZfKfS31"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201207181253.26704.naylor.b.david@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Wine-fbsd64 updated to 1.5.9 (32bit Wine for 64bit FreeBSD) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2012 10:54:30 -0000 --nextPart2813538.HCfZfKfS31 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Packages [1] for wine-fbsd64-1.5.9 have been uploaded to mediafire [2]. Th= e=20 packages for FreeBSD 10 use the pkgng* [3] format. =20 There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users= ). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.9,1.tbz) =3D=20 dddaceda7c0dedd03e5f8531d9826966 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.9,1.txz) =3D=20 aec8afccdd6ac6928662d3be5f537195 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.9,1.txz) =3D=20 9436b443844ac8bf52d9ead2de55cf33 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh * pkgng support for nVidia patching should be working properly and using a= =20 mixed mode between pkgng and pkg also works --nextPart2813538.HCfZfKfS31 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAlAGlaYACgkQUaaFgP9pFrL3YACfbxt75U2hW/giJDIKS1G5Hchz bI4An188GL7t65BhrJolkVPphBLIG+Jm =oKVC -----END PGP SIGNATURE----- --nextPart2813538.HCfZfKfS31-- From owner-freebsd-emulation@FreeBSD.ORG Thu Jul 19 03:20:54 2012 Return-Path: Delivered-To: emulation@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D7D33106564A; Thu, 19 Jul 2012 03:20:54 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AAE638FC12; Thu, 19 Jul 2012 03:20:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6J3KsMR055705; Thu, 19 Jul 2012 03:20:54 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6J3KsMa055701; Thu, 19 Jul 2012 03:20:54 GMT (envelope-from edwin) Date: Thu, 19 Jul 2012 03:20:54 GMT Message-Id: <201207190320.q6J3KsMa055701@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, emulation@FreeBSD.org From: edwin@FreeBSD.org Cc: Subject: Re: ports/169988: [PATCH] Update sysutils/linux-procps to 3.2.7; also update to FC10 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jul 2012 03:20:54 -0000 Synopsis: [PATCH] Update sysutils/linux-procps to 3.2.7; also update to FC10 Responsible-Changed-From-To: freebsd-ports-bugs->emulation Responsible-Changed-By: edwin Responsible-Changed-When: Thu Jul 19 03:20:54 UTC 2012 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=169988 From owner-freebsd-emulation@FreeBSD.ORG Fri Jul 20 01:13:44 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5011C106564A for ; Fri, 20 Jul 2012 01:13:44 +0000 (UTC) (envelope-from yiz5hwi@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id EF0788FC08 for ; Fri, 20 Jul 2012 01:13:43 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so476333vcb.13 for ; Thu, 19 Jul 2012 18:13:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=B2itnQ5+UelRPhhhLejqfC7hzPaYwYv3VYt9RKoxW00=; b=cSyPrVoTNCf7Jy4NxKsgaHRogOSu4wyLgvMaUiCfH9VSb4NP/t6WKpc2ErlGsBX/5N J6AhiT9nT3V/hB21C0QIW8P1JXBt3xEwNhR8DG83vVQZC6CsWx4Z39eLW0G71PMVnn0U L4vo3S+JQF5uXeN7RBDhe7gMZSW4AydTMel6k1JjAB4GlYX1Nv48BJAvYBqLzIDLyd5j ykMmMRnYYxgtsXH+Shca4Mhh1LEdOOs89Ly/h+EfaX4y7wG992WeHPeFmMIw8zsI1/fk TLoYoU/kaxlKMQkaSDowli8Eq1LD2XF2jo4Lcfxk8+vYZO2cPdVJ1NfACR3ifQtMM/hs ZHBg== MIME-Version: 1.0 Received: by 10.52.22.38 with SMTP id a6mr2469313vdf.37.1342746819805; Thu, 19 Jul 2012 18:13:39 -0700 (PDT) Received: by 10.52.115.134 with HTTP; Thu, 19 Jul 2012 18:13:39 -0700 (PDT) In-Reply-To: References: Date: Thu, 19 Jul 2012 21:13:39 -0400 Message-ID: From: Steve Tuts To: freebsd-emulation@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: become worse now - Re: one virtualbox vm disrupts all vms and entire network X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2012 01:13:44 -0000 On Fri, Jul 13, 2012 at 4:34 PM, Steve Tuts wrote: > > > On Mon, Jul 9, 2012 at 9:11 AM, Steve Tuts wrote: > >> >> >> On Tue, Jun 12, 2012 at 6:24 PM, Gary Palmer wrote: >> >>> On Thu, Jun 07, 2012 at 03:56:22PM -0400, Steve Tuts wrote: >>> > On Thu, Jun 7, 2012 at 3:54 AM, Steve Tuts wrote: >>> > >>> > > >>> > > >>> > > On Thu, Jun 7, 2012 at 2:58 AM, Bernhard Fr?hlich >> >wrote: >>> > > >>> > >> On Do., 7. Jun. 2012 01:07:52 CEST, Kevin Oberman < >>> kob6558@gmail.com> >>> > >> wrote: >>> > >> >>> > >> > On Wed, Jun 6, 2012 at 3:46 PM, Steve Tuts >>> wrote: >>> > >> > > On Wed, Jun 6, 2012 at 3:50 AM, Bernhard Froehlich >>> > >> > > wrote: >>> > >> > > >>> > >> > > > On 05.06.2012 20:16, Bernhard Froehlich wrote: >>> > >> > > > >>> > >> > > > > On 05.06.2012 19:05, Steve Tuts wrote: >>> > >> > > > > >>> > >> > > > > > On Mon, Jun 4, 2012 at 4:11 PM, Rusty Nejdl >>> > >> > > > > > wrote: >>> > >> > > > > > >>> > >> > > > > > On 2012-06-02 12:16, Steve Tuts wrote: >>> > >> > > > > > > >>> > >> > > > > > > Hi, we have a Dell poweredge server with a dozen >>> interfaces. >>> > >> > > > > > > It hosts >>> > >> > > > > > > > a >>> > >> > > > > > > > few guests of web app and email servers with >>> > >> > > > > > > > VirtualBox-4.0.14. The host >>> > >> > > > > > > > and all guests are FreeBSD 9.0 64bit. Each guest is >>> bridged >>> > >> > > > > > > > to a distinct >>> > >> > > > > > > > interface. The host and all guests are set to >>> 10.0.0.0 >>> > >> > > > > > > > network NAT'ed to >>> > >> > > > > > > > a >>> > >> > > > > > > > cicso router. >>> > >> > > > > > > > >>> > >> > > > > > > > This runs well for a couple months, until we added a >>> new >>> > >> > > > > > > > guest recently. >>> > >> > > > > > > > Every few hours, none of the guests can be connected. >>> We >>> > >> > > > > > > > can only connect >>> > >> > > > > > > > to the host from outside the router. We can also go >>> to the >>> > >> > > > > > > > console of the >>> > >> > > > > > > > guests (except the new guest), but from there we >>> can't ping >>> > >> > > > > > > > the gateway 10.0.0.1 any more. The new guest just >>> froze. >>> > >> > > > > > > > >>> > >> > > > > > > > Furthermore, on the host we can see a vboxheadless >>> process >>> > >> > > > > > > > for each guest, >>> > >> > > > > > > > including the new guest. But we can not kill it, not >>> even >>> > >> > > > > > > > with "kill -9". >>> > >> > > > > > > > We looked around the web and someone suggested we >>> should use >>> > >> > > > > > > > "kill -SIGCONT" first since the "ps" output has the >>> "T" flag >>> > >> > > > > > > > for that vboxheadless process for that new guest, but >>> that >>> > >> > > > > > > > doesn't help. We also >>> > >> > > > > > > > tried all the VBoxManager commands to poweroff/reset >>> etc >>> > >> > > > > > > > that new guest, >>> > >> > > > > > > > but they all failed complaining that vm is in Aborted >>> state. >>> > >> > > > > > > > We also tried >>> > >> > > > > > > > VBoxManager commands to disconnect the network cable >>> for >>> > >> > > > > > > > that new guest, >>> > >> > > > > > > > it >>> > >> > > > > > > > didn't complain, but there was no effect. >>> > >> > > > > > > > >>> > >> > > > > > > > For a couple times, on the host we disabled the >>> interface >>> > >> > > > > > > > bridging that new >>> > >> > > > > > > > guest, then that vboxheadless process for that new >>> guest >>> > >> > > > > > > > disappeared (we >>> > >> > > > > > > > attempted to kill it before that). And immediately >>> all >>> > >> > > > > > > > other vms regained >>> > >> > > > > > > > connection back to normal. >>> > >> > > > > > > > >>> > >> > > > > > > > But there is one time even the above didn't help - the >>> > >> > > > > > > > vboxheadless process >>> > >> > > > > > > > for that new guest stubbonly remains, and we had to >>> reboot >>> > >> > > > > > > > the host. >>> > >> > > > > > > > >>> > >> > > > > > > > This is already a production server, so we can't >>> upgrade >>> > >> > > > > > > > virtualbox to the >>> > >> > > > > > > > latest version until we obtain a test server. >>> > >> > > > > > > > >>> > >> > > > > > > > Would you advise: >>> > >> > > > > > > > >>> > >> > > > > > > > 1. is there any other way to kill that new guest >>> instead of >>> > >> > > > > > > > rebooting? 2. what might cause the problem? >>> > >> > > > > > > > 3. what setting and test I can do to analyze this >>> problem? >>> > >> > > > > > > > ______________________________****_________________ >>> > >> > > > > > > > >>> > >> > > > > > > > >>> > >> > > > > > > I haven't seen any comments on this and don't want you >>> to >>> > >> > > > > > > think you are being ignored but I haven't seen this but >>> also, >>> > >> > > > > > > the 4.0 branch was buggier >>> > >> > > > > > > for me than the 4.1 releases so yeah, upgrading is >>> probably >>> > >> > > > > > > what you are looking at. >>> > >> > > > > > > >>> > >> > > > > > > Rusty Nejdl >>> > >> > > > > > > ______________________________****_________________ >>> > >> > > > > > > >>> > >> > > > > > > >>> > >> > > > > > > sorry, just realize my reply yesterday didn't go to >>> the list, >>> > >> > > > > > > so am >>> > >> > > > > > re-sending with some updates. >>> > >> > > > > > >>> > >> > > > > > Yes, we upgraded all ports and fortunately everything >>> went back >>> > >> > > > > > and especially all vms has run peacefully for two days >>> now. So >>> > >> > > > > > upgrading to the latest virtualbox 4.1.16 solved that >>> problem. >>> > >> > > > > > >>> > >> > > > > > But now we got a new problem with this new version of >>> > >> virtualbox: >>> > >> > > > > > whenever >>> > >> > > > > > we try to vnc to any vm, that vm will go to Aborted state >>> > >> > > > > > immediately. Actually, merely telnet from within the host >>> to the >>> > >> > > > > > vnc port of that vm will immediately Abort that vm. This >>> > >> > > > > > prevents us from adding new vms. Also, when starting vm >>> with vnc >>> > >> > > > > > port, we got this message: >>> > >> > > > > > >>> > >> > > > > > rfbListenOnTCP6Port: error in bind IPv6 socket: Address >>> already >>> > >> > > > > > in use >>> > >> > > > > > >>> > >> > > > > > , which we found someone else provided a patch at >>> > >> > > > > > >>> > >> >>> http://permalink.gmane.org/**gmane.os.freebsd.devel.**emulation/10237< >>> > >> http://permalink.gmane.org/gmane.os.freebsd.devel.emulation/10237> >>> > >> > > > > > >>> > >> > > > > > So looks like when there are multiple vms on a ipv6 >>> system (we >>> > >> > > > > > have 64bit FreeBSD 9.0) will get this problem. >>> > >> > > > > > >>> > >> > > > > >>> > >> > > > > Glad to hear that 4.1.16 helps for the networking problem. >>> The VNC >>> > >> > > > > problem is also a known one but the mentioned patch does >>> not work >>> > >> > > > > at least for a few people. It seems the bug is somewhere in >>> > >> > > > > libvncserver so downgrading net/libvncserver to an earlier >>> version >>> > >> > > > > (and rebuilding virtualbox) should help until we come up >>> with a >>> > >> > > > > proper fix. >>> > >> > > > > >>> > >> > > > >>> > >> > > > You are right about the "Address already in use" problem and >>> the >>> > >> > > > patch for it so I will commit the fix in a few moments. >>> > >> > > > >>> > >> > > > I have also tried to reproduce the VNC crash but I couldn't. >>> > >> Probably >>> > >> > > > because >>> > >> > > > my system is IPv6 enabled. flo@ has seen the same crash and >>> has no >>> > >> > > > IPv6 in his kernel which lead him to find this commit in >>> > >> > > > libvncserver: >>> > >> > > > >>> > >> > > > >>> > >> > > > commit 66282f58000c8863e104666c30cb67**b1d5cbdee3 >>> > >> > > > Author: Kyle J. McKay >>> > >> > > > Date: Fri May 18 00:30:11 2012 -0700 >>> > >> > > > libvncserver/sockets.c: do not segfault when >>> > >> > > > listenSock/listen6Sock == -1 >>> > >> > > > >>> > >> > > > http://libvncserver.git.** >>> > >> sourceforge.net/git/gitweb.**cgi?p=libvncserver/ >>> > >> > > > **libvncserver;a=commit;h=**66282f5< >>> > >> >>> http://libvncserver.git.sourceforge.net/git/gitweb.cgi?p=libvncserver/libvncserver;a=commit;h=66282f5 >>> > >> > >>> > >> > > > >>> > >> > > > >>> > >> > > > It looks promising so please test this patch if you can >>> reproduce >>> > >> the >>> > >> > > > crash. >>> > >> > > > >>> > >> > > > >>> > >> > > > -- >>> > >> > > > Bernhard Froehlich >>> > >> > > > http://www.bluelife.at/ >>> > >> > > > >>> > >> > > >>> > >> > > Sorry, I tried to try this patch, but couldn't figure out how >>> to do >>> > >> > > that. I use ports to compile everything, and can see the file >>> is at >>> > >> > > >>> > >> >>> /usr/ports/net/libvncserver/work/LibVNCServer-0.9.9/libvncserver/sockets.c >>> > >> > > . However, if I edit this file and do make clean, this patch >>> is wiped >>> > >> > > out before I can do "make" out of it. How to apply this patch >>> in the >>> > >> > > ports? >>> > >> > >>> > >> > To apply patches to ports: >>> > >> > # make clean >>> > >> > # make patch >>> > >> > >>> > >> > # make >>> > >> > # make deinstall >>> > >> > # make reinstall >>> > >> > >>> > >> > Note that the final two steps assume a version of the port is >>> already >>> > >> > installed. If not: 'make install' >>> > >> > I you use portmaster, after applying the patch: 'portmaster -C >>> > >> > net/libvncserver' -- >>> > >> >>> > >> flo has already committed the patch to net/libvncserver so I guess >>> it >>> > >> fixes the problem. Please update your portstree and verify that it >>> works >>> > >> fine. >>> > >> >>> > > >>> > > I confirmed after upgrading all ports and noticing libvncserver >>> upgraded >>> > > to 0.99_1 and reboot, then I can vnc to the vms now. Also, starting >>> vms >>> > > with vnc doesn't have that error now, instead it issues the >>> following info, >>> > > so all problem are solved. >>> > > >>> > > 07/06/2012 03:49:14 Listening for VNC connections on TCP port 5903 >>> > > 07/06/2012 03:49:14 Listening for VNC connections on TCP6 port 5903 >>> > > >>> > > Thanks everyone for your great help! >>> > > >>> > >>> > Unfortunately, seems that the original problem of one vm disrupts all >>> vms >>> > and entire network appears to remain, albeit to less scope. After >>> running >>> > on virtualbox-ose-4.1.16_1 and libvncserver-0.9.9_1 for 12 hours, all >>> vms >>> > lost connection again. Also, phpvirtualbox stopped responding, and >>> > attempts to restart vboxwebsrv hanged. And trying to kill (-9) the >>> > vboxwebsrv process won't work. The following was the output of "ps >>> > aux|grep -i box" at that time: >>> > >>> > root 3322 78.7 16.9 4482936 4248180 ?? Is 3:42AM 126:00.53 >>> > /usr/local/bin/VBoxHeadless --startvm vm1 >>> > root 3377 0.2 4.3 1286200 1078728 ?? Is 3:42AM 15:39.40 >>> > /usr/local/bin/VBoxHeadless --startvm vm2 >>> > root 3388 0.1 4.3 1297592 1084676 ?? Is 3:42AM 15:06.97 >>> > /usr/local/bin/VBoxHeadless --startvm vm7 -n -m 5907 -o >>> jtlgjkrfyh9tpgjklfds >>> > root 2453 0.0 0.0 141684 7156 ?? Ts 3:38AM 4:14.09 >>> > /usr/local/bin/vboxwebsrv >>> > root 2478 0.0 0.0 45288 2528 ?? S 3:38AM 1:29.99 >>> > /usr/local/lib/virtualbox/VBoxXPCOMIPCD >>> > root 2494 0.0 0.0 121848 5380 ?? S 3:38AM 3:13.96 >>> > /usr/local/lib/virtualbox/VBoxSVC --auto-shutdown >>> > root 3333 0.0 4.3 1294712 1079608 ?? Is 3:42AM 19:35.09 >>> > /usr/local/bin/VBoxHeadless --startvm vm3 >>> > root 3355 0.0 4.3 1290424 1079332 ?? Is 3:42AM 16:43.05 >>> > /usr/local/bin/VBoxHeadless --startvm vm5 >>> > root 3366 0.0 8.5 2351436 2140076 ?? Is 3:42AM 17:32.35 >>> > /usr/local/bin/VBoxHeadless --startvm vm6 >>> > root 3598 0.0 4.3 1294520 1078664 ?? Ds 3:50AM 15:01.04 >>> > /usr/local/bin/VBoxHeadless --startvm vm4 -n -m 5904 -o >>> > u679y0uojlkdfsgkjtfds >>> > >>> > You can see the vboxwebsrv process has the "T" flag there, and the >>> > vboxheadless process for vm4 has "D" flag there. Both of such >>> processes I >>> > can never kill them, not even with "kill -9". So on the host I >>> disabled >>> > the interface bridged to vm4 and restarted network, and fortunately >>> both >>> > the vm4 and the vboxwebsrv processed disappeared. And at that point >>> all >>> > other vms regained network. >>> > >>> > There may be one hope that the "troublemaker" may be limited to one of >>> the >>> > vms that started with vnc, although there was no vnc connection at that >>> > time, and the other vm with vnc was fine. And this is just a hopeful >>> guess. >>> > >>> > Also I found no log or error message related to virtualbox in any log >>> > file. The VBoxSVC.log only had some information when started but never >>> > since. >>> >>> If this is still a problem then >>> >>> ps alxww | grep -i box >>> >>> may be more helpful as it will show the wait channel of processes stuck >>> in the kernel. >>> >>> Gary >>> >> >> We avoided this problem by running all vms without vnc. But forgot this >> problem and left one vm on with vnc, together with the other few running >> vms yesterday, and hit this problem again on virtualbox 4.1.16. Only the >> old trick of turning off the host interface corresponding to the vm with >> vnc and then restarting host network got us out of the problem. >> >> We then upgraded virtualbox to 4.1.18, turning off all vms, wait until >> "ps aux|grep -i box" reported nothing, then started all vms. And let no vm >> with vnc running. >> >> Still the problem hit us again. Here is the output of " ps alxww | grep >> -i box" as you suggested: >> >> 1011 42725 1 0 20 0 1289796 1081064 IPRT S >> Is ?? 30:53.24 VBoxHeadless --startvm vm5 >> >> after "kill -9 42725", the line changed to >> >> 1011 42725 1 0 20 0 1289796 1081064 keglim >> Ts ?? 30:53.24 VBoxHeadless --startvm vm5 >> >> after "kill -9" for another vm, the line changed to something like >> >> 1011 42754 1 0 20 0 1289796 1081064 - Ts >> ?? 30:53.24 VBoxHeadless --startvm vm7 >> >> and controlvm command don't work, and these command stuck there >> themselves. The following are their outputs: >> >> 0 89572 79180 0 21 0 44708 1644 select I+ >> v6 0:00.01 VBoxManage controlvm projects_outside acpipowerbutton >> 0 89605 89586 0 21 0 44708 2196 select I+ >> v7 0:00.01 VBoxManage controlvm projects_outside poweroff >> >> We now rebooted the host, and left no vm with vnc running. >> > > The problem has become more rampant now. After rebooting and running > virtualbox-ose-4.1.18, and no vm was started with console, the around 10 > vms, bridged to each of its own dedicated interface, get no network > connection a couple times a day. Most times it would recover itself after > about 10 minutes, sometimes we have to restart host network which > immediately restore all connections. > Looks like multiple people had similar problem, see the threads in http://lists.freebsd.org/pipermail/freebsd-emulation/2011-July/008957.html http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063197.html and http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063172.html http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/058708.html http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/thread.html#63221 http://lists.freebsd.org/pipermail/freebsd-emulation/2011-July/thread.html#8957 In all cases (including mine), the hardware is a beefy Dell, such as Dell R710, with multiple cores and multiple interfaces. Virtualbox is running on all machines. Some of them may also have ZFS running (like mine). My problem is, after some time, the entire network on the host stops working, so that one can't ssh to any guest or other machine, not even to itself. At such point, restarting network on the host will restore everything. My guests are bridged to its respective interfaces on the host. Those other people also reported that they can't scp large file from host to the guest. (Un)fortunately I also confirmed the same problem. When scp a 10G file from host to guest, it will get stalled sometimes afterwards. And at that time, the entire network is broken, as described in the paragraph above. I tried everything they described, including: 1. setting net.graph.maxdata and net.graph.maxalloc to 65536 in /boot/loader.conf 2. setting kern.ipc.maxsockbut, net.graph.maxdgram, net.graph.recvspaceto 8388608 in /etc/sysctl.conf 3. setting kern.maxdsiz in /boot/loader.conf . Although I don't know what else to set, since somehow the default value is somehow 34G on my 24G memory server. Unfortunately, none of them work, ie, scp from host to guest always stalls after some variable time (varying from dozens of MBs to 7GB). Scp from host to other machine appears to have no problem though. So appears that something is broken after scp from host to guest for some time. But I don't know what is broken. Still, this offers a reliable way to reproduce the problem. If you have any suggestion of checking what is broken or what change to fix, I'd be happy to comply. This is already in production so I can't leave the vms not running for more than a few minutes though. From owner-freebsd-emulation@FreeBSD.ORG Fri Jul 20 01:30:24 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7D1F106566B for ; Fri, 20 Jul 2012 01:30:24 +0000 (UTC) (envelope-from yiz5hwi@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7F11D8FC08 for ; Fri, 20 Jul 2012 01:30:24 +0000 (UTC) Received: by vbmv11 with SMTP id v11so3167264vbm.13 for ; Thu, 19 Jul 2012 18:30:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=CWxEx4nxGK56RvR0tH58IZGaPIkr+ksvx/gyV0QN7i0=; b=hx3DDEOuCPnn5iy73OFgKQQMCmVEHzwmvUGruZsEDLBz+DifBbIHRDMeAVGtAW0+zr 0LOrcKcpCzfdVoc71yTi990GJRC1ayDXtziaQZuR6oqRJ9gnWSYxuoYBs3YN6RHrFPdY ns6xuLkiMP11u7mfpib3H3ryfvd6lhFC6kf6Ssr7AA5jYnSqFWETAKDGg2DlYcoY1z0L iREtdld5pZE1yfT1e6NogEcxFh9GBScGXAB3AqzXNVXF+IbTIxSFkU3wiS/RqnvNE+iG 5GYbfDDJcVgv1reTq2PaYol/z9ZXFxcfUjeJ+QUjqepTDZJ2pVeCacZuk4eAsHMuxQd4 FdwA== MIME-Version: 1.0 Received: by 10.52.89.35 with SMTP id bl3mr2459453vdb.106.1342747823018; Thu, 19 Jul 2012 18:30:23 -0700 (PDT) Received: by 10.52.115.134 with HTTP; Thu, 19 Jul 2012 18:30:22 -0700 (PDT) In-Reply-To: References: Date: Thu, 19 Jul 2012 21:30:22 -0400 Message-ID: From: Steve Tuts To: freebsd-emulation@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: become worse now - Re: one virtualbox vm disrupts all vms and entire network X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2012 01:30:24 -0000 On Thu, Jul 19, 2012 at 9:13 PM, Steve Tuts wrote: > > > On Fri, Jul 13, 2012 at 4:34 PM, Steve Tuts wrote: > >> >> >> On Mon, Jul 9, 2012 at 9:11 AM, Steve Tuts wrote: >> >>> >>> >>> On Tue, Jun 12, 2012 at 6:24 PM, Gary Palmer wrote: >>> >>>> On Thu, Jun 07, 2012 at 03:56:22PM -0400, Steve Tuts wrote: >>>> > On Thu, Jun 7, 2012 at 3:54 AM, Steve Tuts wrote: >>>> > >>>> > > >>>> > > >>>> > > On Thu, Jun 7, 2012 at 2:58 AM, Bernhard Fr?hlich < >>>> decke@bluelife.at>wrote: >>>> > > >>>> > >> On Do., 7. Jun. 2012 01:07:52 CEST, Kevin Oberman < >>>> kob6558@gmail.com> >>>> > >> wrote: >>>> > >> >>>> > >> > On Wed, Jun 6, 2012 at 3:46 PM, Steve Tuts >>>> wrote: >>>> > >> > > On Wed, Jun 6, 2012 at 3:50 AM, Bernhard Froehlich >>>> > >> > > wrote: >>>> > >> > > >>>> > >> > > > On 05.06.2012 20:16, Bernhard Froehlich wrote: >>>> > >> > > > >>>> > >> > > > > On 05.06.2012 19:05, Steve Tuts wrote: >>>> > >> > > > > >>>> > >> > > > > > On Mon, Jun 4, 2012 at 4:11 PM, Rusty Nejdl >>>> > >> > > > > > wrote: >>>> > >> > > > > > >>>> > >> > > > > > On 2012-06-02 12:16, Steve Tuts wrote: >>>> > >> > > > > > > >>>> > >> > > > > > > Hi, we have a Dell poweredge server with a dozen >>>> interfaces. >>>> > >> > > > > > > It hosts >>>> > >> > > > > > > > a >>>> > >> > > > > > > > few guests of web app and email servers with >>>> > >> > > > > > > > VirtualBox-4.0.14. The host >>>> > >> > > > > > > > and all guests are FreeBSD 9.0 64bit. Each guest is >>>> bridged >>>> > >> > > > > > > > to a distinct >>>> > >> > > > > > > > interface. The host and all guests are set to >>>> 10.0.0.0 >>>> > >> > > > > > > > network NAT'ed to >>>> > >> > > > > > > > a >>>> > >> > > > > > > > cicso router. >>>> > >> > > > > > > > >>>> > >> > > > > > > > This runs well for a couple months, until we added a >>>> new >>>> > >> > > > > > > > guest recently. >>>> > >> > > > > > > > Every few hours, none of the guests can be >>>> connected. We >>>> > >> > > > > > > > can only connect >>>> > >> > > > > > > > to the host from outside the router. We can also go >>>> to the >>>> > >> > > > > > > > console of the >>>> > >> > > > > > > > guests (except the new guest), but from there we >>>> can't ping >>>> > >> > > > > > > > the gateway 10.0.0.1 any more. The new guest just >>>> froze. >>>> > >> > > > > > > > >>>> > >> > > > > > > > Furthermore, on the host we can see a vboxheadless >>>> process >>>> > >> > > > > > > > for each guest, >>>> > >> > > > > > > > including the new guest. But we can not kill it, >>>> not even >>>> > >> > > > > > > > with "kill -9". >>>> > >> > > > > > > > We looked around the web and someone suggested we >>>> should use >>>> > >> > > > > > > > "kill -SIGCONT" first since the "ps" output has the >>>> "T" flag >>>> > >> > > > > > > > for that vboxheadless process for that new guest, >>>> but that >>>> > >> > > > > > > > doesn't help. We also >>>> > >> > > > > > > > tried all the VBoxManager commands to poweroff/reset >>>> etc >>>> > >> > > > > > > > that new guest, >>>> > >> > > > > > > > but they all failed complaining that vm is in >>>> Aborted state. >>>> > >> > > > > > > > We also tried >>>> > >> > > > > > > > VBoxManager commands to disconnect the network cable >>>> for >>>> > >> > > > > > > > that new guest, >>>> > >> > > > > > > > it >>>> > >> > > > > > > > didn't complain, but there was no effect. >>>> > >> > > > > > > > >>>> > >> > > > > > > > For a couple times, on the host we disabled the >>>> interface >>>> > >> > > > > > > > bridging that new >>>> > >> > > > > > > > guest, then that vboxheadless process for that new >>>> guest >>>> > >> > > > > > > > disappeared (we >>>> > >> > > > > > > > attempted to kill it before that). And immediately >>>> all >>>> > >> > > > > > > > other vms regained >>>> > >> > > > > > > > connection back to normal. >>>> > >> > > > > > > > >>>> > >> > > > > > > > But there is one time even the above didn't help - >>>> the >>>> > >> > > > > > > > vboxheadless process >>>> > >> > > > > > > > for that new guest stubbonly remains, and we had to >>>> reboot >>>> > >> > > > > > > > the host. >>>> > >> > > > > > > > >>>> > >> > > > > > > > This is already a production server, so we can't >>>> upgrade >>>> > >> > > > > > > > virtualbox to the >>>> > >> > > > > > > > latest version until we obtain a test server. >>>> > >> > > > > > > > >>>> > >> > > > > > > > Would you advise: >>>> > >> > > > > > > > >>>> > >> > > > > > > > 1. is there any other way to kill that new guest >>>> instead of >>>> > >> > > > > > > > rebooting? 2. what might cause the problem? >>>> > >> > > > > > > > 3. what setting and test I can do to analyze this >>>> problem? >>>> > >> > > > > > > > ______________________________****_________________ >>>> > >> > > > > > > > >>>> > >> > > > > > > > >>>> > >> > > > > > > I haven't seen any comments on this and don't want you >>>> to >>>> > >> > > > > > > think you are being ignored but I haven't seen this >>>> but also, >>>> > >> > > > > > > the 4.0 branch was buggier >>>> > >> > > > > > > for me than the 4.1 releases so yeah, upgrading is >>>> probably >>>> > >> > > > > > > what you are looking at. >>>> > >> > > > > > > >>>> > >> > > > > > > Rusty Nejdl >>>> > >> > > > > > > ______________________________****_________________ >>>> > >> > > > > > > >>>> > >> > > > > > > >>>> > >> > > > > > > sorry, just realize my reply yesterday didn't go to >>>> the list, >>>> > >> > > > > > > so am >>>> > >> > > > > > re-sending with some updates. >>>> > >> > > > > > >>>> > >> > > > > > Yes, we upgraded all ports and fortunately everything >>>> went back >>>> > >> > > > > > and especially all vms has run peacefully for two days >>>> now. So >>>> > >> > > > > > upgrading to the latest virtualbox 4.1.16 solved that >>>> problem. >>>> > >> > > > > > >>>> > >> > > > > > But now we got a new problem with this new version of >>>> > >> virtualbox: >>>> > >> > > > > > whenever >>>> > >> > > > > > we try to vnc to any vm, that vm will go to Aborted state >>>> > >> > > > > > immediately. Actually, merely telnet from within the >>>> host to the >>>> > >> > > > > > vnc port of that vm will immediately Abort that vm. This >>>> > >> > > > > > prevents us from adding new vms. Also, when starting vm >>>> with vnc >>>> > >> > > > > > port, we got this message: >>>> > >> > > > > > >>>> > >> > > > > > rfbListenOnTCP6Port: error in bind IPv6 socket: Address >>>> already >>>> > >> > > > > > in use >>>> > >> > > > > > >>>> > >> > > > > > , which we found someone else provided a patch at >>>> > >> > > > > > >>>> > >> >>>> http://permalink.gmane.org/**gmane.os.freebsd.devel.**emulation/10237< >>>> > >> http://permalink.gmane.org/gmane.os.freebsd.devel.emulation/10237> >>>> > >> > > > > > >>>> > >> > > > > > So looks like when there are multiple vms on a ipv6 >>>> system (we >>>> > >> > > > > > have 64bit FreeBSD 9.0) will get this problem. >>>> > >> > > > > > >>>> > >> > > > > >>>> > >> > > > > Glad to hear that 4.1.16 helps for the networking problem. >>>> The VNC >>>> > >> > > > > problem is also a known one but the mentioned patch does >>>> not work >>>> > >> > > > > at least for a few people. It seems the bug is somewhere in >>>> > >> > > > > libvncserver so downgrading net/libvncserver to an earlier >>>> version >>>> > >> > > > > (and rebuilding virtualbox) should help until we come up >>>> with a >>>> > >> > > > > proper fix. >>>> > >> > > > > >>>> > >> > > > >>>> > >> > > > You are right about the "Address already in use" problem and >>>> the >>>> > >> > > > patch for it so I will commit the fix in a few moments. >>>> > >> > > > >>>> > >> > > > I have also tried to reproduce the VNC crash but I couldn't. >>>> > >> Probably >>>> > >> > > > because >>>> > >> > > > my system is IPv6 enabled. flo@ has seen the same crash and >>>> has no >>>> > >> > > > IPv6 in his kernel which lead him to find this commit in >>>> > >> > > > libvncserver: >>>> > >> > > > >>>> > >> > > > >>>> > >> > > > commit 66282f58000c8863e104666c30cb67**b1d5cbdee3 >>>> > >> > > > Author: Kyle J. McKay >>>> > >> > > > Date: Fri May 18 00:30:11 2012 -0700 >>>> > >> > > > libvncserver/sockets.c: do not segfault when >>>> > >> > > > listenSock/listen6Sock == -1 >>>> > >> > > > >>>> > >> > > > http://libvncserver.git.** >>>> > >> sourceforge.net/git/gitweb.**cgi?p=libvncserver/ >>>> > >> > > > **libvncserver;a=commit;h=**66282f5< >>>> > >> >>>> http://libvncserver.git.sourceforge.net/git/gitweb.cgi?p=libvncserver/libvncserver;a=commit;h=66282f5 >>>> > >> > >>>> > >> > > > >>>> > >> > > > >>>> > >> > > > It looks promising so please test this patch if you can >>>> reproduce >>>> > >> the >>>> > >> > > > crash. >>>> > >> > > > >>>> > >> > > > >>>> > >> > > > -- >>>> > >> > > > Bernhard Froehlich >>>> > >> > > > http://www.bluelife.at/ >>>> > >> > > > >>>> > >> > > >>>> > >> > > Sorry, I tried to try this patch, but couldn't figure out how >>>> to do >>>> > >> > > that. I use ports to compile everything, and can see the file >>>> is at >>>> > >> > > >>>> > >> >>>> /usr/ports/net/libvncserver/work/LibVNCServer-0.9.9/libvncserver/sockets.c >>>> > >> > > . However, if I edit this file and do make clean, this patch >>>> is wiped >>>> > >> > > out before I can do "make" out of it. How to apply this patch >>>> in the >>>> > >> > > ports? >>>> > >> > >>>> > >> > To apply patches to ports: >>>> > >> > # make clean >>>> > >> > # make patch >>>> > >> > >>>> > >> > # make >>>> > >> > # make deinstall >>>> > >> > # make reinstall >>>> > >> > >>>> > >> > Note that the final two steps assume a version of the port is >>>> already >>>> > >> > installed. If not: 'make install' >>>> > >> > I you use portmaster, after applying the patch: 'portmaster -C >>>> > >> > net/libvncserver' -- >>>> > >> >>>> > >> flo has already committed the patch to net/libvncserver so I guess >>>> it >>>> > >> fixes the problem. Please update your portstree and verify that it >>>> works >>>> > >> fine. >>>> > >> >>>> > > >>>> > > I confirmed after upgrading all ports and noticing libvncserver >>>> upgraded >>>> > > to 0.99_1 and reboot, then I can vnc to the vms now. Also, >>>> starting vms >>>> > > with vnc doesn't have that error now, instead it issues the >>>> following info, >>>> > > so all problem are solved. >>>> > > >>>> > > 07/06/2012 03:49:14 Listening for VNC connections on TCP port 5903 >>>> > > 07/06/2012 03:49:14 Listening for VNC connections on TCP6 port 5903 >>>> > > >>>> > > Thanks everyone for your great help! >>>> > > >>>> > >>>> > Unfortunately, seems that the original problem of one vm disrupts all >>>> vms >>>> > and entire network appears to remain, albeit to less scope. After >>>> running >>>> > on virtualbox-ose-4.1.16_1 and libvncserver-0.9.9_1 for 12 hours, all >>>> vms >>>> > lost connection again. Also, phpvirtualbox stopped responding, and >>>> > attempts to restart vboxwebsrv hanged. And trying to kill (-9) the >>>> > vboxwebsrv process won't work. The following was the output of "ps >>>> > aux|grep -i box" at that time: >>>> > >>>> > root 3322 78.7 16.9 4482936 4248180 ?? Is 3:42AM 126:00.53 >>>> > /usr/local/bin/VBoxHeadless --startvm vm1 >>>> > root 3377 0.2 4.3 1286200 1078728 ?? Is 3:42AM 15:39.40 >>>> > /usr/local/bin/VBoxHeadless --startvm vm2 >>>> > root 3388 0.1 4.3 1297592 1084676 ?? Is 3:42AM 15:06.97 >>>> > /usr/local/bin/VBoxHeadless --startvm vm7 -n -m 5907 -o >>>> jtlgjkrfyh9tpgjklfds >>>> > root 2453 0.0 0.0 141684 7156 ?? Ts 3:38AM 4:14.09 >>>> > /usr/local/bin/vboxwebsrv >>>> > root 2478 0.0 0.0 45288 2528 ?? S 3:38AM 1:29.99 >>>> > /usr/local/lib/virtualbox/VBoxXPCOMIPCD >>>> > root 2494 0.0 0.0 121848 5380 ?? S 3:38AM 3:13.96 >>>> > /usr/local/lib/virtualbox/VBoxSVC --auto-shutdown >>>> > root 3333 0.0 4.3 1294712 1079608 ?? Is 3:42AM 19:35.09 >>>> > /usr/local/bin/VBoxHeadless --startvm vm3 >>>> > root 3355 0.0 4.3 1290424 1079332 ?? Is 3:42AM 16:43.05 >>>> > /usr/local/bin/VBoxHeadless --startvm vm5 >>>> > root 3366 0.0 8.5 2351436 2140076 ?? Is 3:42AM 17:32.35 >>>> > /usr/local/bin/VBoxHeadless --startvm vm6 >>>> > root 3598 0.0 4.3 1294520 1078664 ?? Ds 3:50AM 15:01.04 >>>> > /usr/local/bin/VBoxHeadless --startvm vm4 -n -m 5904 -o >>>> > u679y0uojlkdfsgkjtfds >>>> > >>>> > You can see the vboxwebsrv process has the "T" flag there, and the >>>> > vboxheadless process for vm4 has "D" flag there. Both of such >>>> processes I >>>> > can never kill them, not even with "kill -9". So on the host I >>>> disabled >>>> > the interface bridged to vm4 and restarted network, and fortunately >>>> both >>>> > the vm4 and the vboxwebsrv processed disappeared. And at that point >>>> all >>>> > other vms regained network. >>>> > >>>> > There may be one hope that the "troublemaker" may be limited to one >>>> of the >>>> > vms that started with vnc, although there was no vnc connection at >>>> that >>>> > time, and the other vm with vnc was fine. And this is just a hopeful >>>> guess. >>>> > >>>> > Also I found no log or error message related to virtualbox in any log >>>> > file. The VBoxSVC.log only had some information when started but >>>> never >>>> > since. >>>> >>>> If this is still a problem then >>>> >>>> ps alxww | grep -i box >>>> >>>> may be more helpful as it will show the wait channel of processes stuck >>>> in the kernel. >>>> >>>> Gary >>>> >>> >>> We avoided this problem by running all vms without vnc. But forgot this >>> problem and left one vm on with vnc, together with the other few running >>> vms yesterday, and hit this problem again on virtualbox 4.1.16. Only the >>> old trick of turning off the host interface corresponding to the vm with >>> vnc and then restarting host network got us out of the problem. >>> >>> We then upgraded virtualbox to 4.1.18, turning off all vms, wait until >>> "ps aux|grep -i box" reported nothing, then started all vms. And let no vm >>> with vnc running. >>> >>> Still the problem hit us again. Here is the output of " ps alxww | grep >>> -i box" as you suggested: >>> >>> 1011 42725 1 0 20 0 1289796 1081064 IPRT S >>> Is ?? 30:53.24 VBoxHeadless --startvm vm5 >>> >>> after "kill -9 42725", the line changed to >>> >>> 1011 42725 1 0 20 0 1289796 1081064 keglim >>> Ts ?? 30:53.24 VBoxHeadless --startvm vm5 >>> >>> after "kill -9" for another vm, the line changed to something like >>> >>> 1011 42754 1 0 20 0 1289796 1081064 - Ts >>> ?? 30:53.24 VBoxHeadless --startvm vm7 >>> >>> and controlvm command don't work, and these command stuck there >>> themselves. The following are their outputs: >>> >>> 0 89572 79180 0 21 0 44708 1644 select I+ >>> v6 0:00.01 VBoxManage controlvm projects_outside acpipowerbutton >>> 0 89605 89586 0 21 0 44708 2196 select I+ >>> v7 0:00.01 VBoxManage controlvm projects_outside poweroff >>> >>> We now rebooted the host, and left no vm with vnc running. >>> >> >> The problem has become more rampant now. After rebooting and running >> virtualbox-ose-4.1.18, and no vm was started with console, the around 10 >> vms, bridged to each of its own dedicated interface, get no network >> connection a couple times a day. Most times it would recover itself after >> about 10 minutes, sometimes we have to restart host network which >> immediately restore all connections. >> > > Looks like multiple people had similar problem, see the threads in > > http://lists.freebsd.org/pipermail/freebsd-emulation/2011-July/008957.html > http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063197.html > > and > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063172.html > > http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/058708.html > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/thread.html#63221 > > http://lists.freebsd.org/pipermail/freebsd-emulation/2011-July/thread.html#8957 > > In all cases (including mine), the hardware is a beefy Dell, such as Dell > R710, with multiple cores and multiple interfaces. Virtualbox is running > on all machines. Some of them may also have ZFS running (like mine). > > My problem is, after some time, the entire network on the host stops > working, so that one can't ssh to any guest or other machine, not even to > itself. At such point, restarting network on the host will restore > everything. My guests are bridged to its respective interfaces on the host. > > Those other people also reported that they can't scp large file from host > to the guest. (Un)fortunately I also confirmed the same problem. When scp > a 10G file from host to guest, it will get stalled sometimes afterwards. > And at that time, the entire network is broken, as described in the > paragraph above. > > I tried everything they described, including: > > 1. setting net.graph.maxdata and net.graph.maxalloc to 65536 in > /boot/loader.conf > 2. setting kern.ipc.maxsockbut, net.graph.maxdgram, net.graph.recvspaceto > 8388608 in /etc/sysctl.conf > 3. setting kern.maxdsiz in /boot/loader.conf . Although I don't know what > else to set, since somehow the default value is somehow 34G on my 24G > memory server. > > Unfortunately, none of them work, ie, scp from host to guest always stalls > after some variable time (varying from dozens of MBs to 7GB). Scp from > host to other machine appears to have no problem though. > > So appears that something is broken after scp from host to guest for some > time. But I don't know what is broken. Still, this offers a reliable way > to reproduce the problem. If you have any suggestion of checking what is > broken or what change to fix, I'd be happy to comply. This is already in > production so I can't leave the vms not running for more than a few minutes > though. > One more observation is, that it becomes worse may be related to that I installed more vms lately. After shutting down a few vms I do notice this network problem occurred less frequently, albeit still about once a day. Also, do you think if this may not be a virtualbox problem or people in other freebsd subforum may have better expertise as this may turn out to be a network problem? I just want to post on the forum that people would most relate to, so your advice would be appreciated. From owner-freebsd-emulation@FreeBSD.ORG Sat Jul 21 08:28:12 2012 Return-Path: Delivered-To: emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FA9A106564A for ; Sat, 21 Jul 2012 08:28:12 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from portsmonj.FreeBSD.org (portsmonj.freebsd.org [69.147.83.46]) by mx1.freebsd.org (Postfix) with ESMTP id 34AD18FC0A for ; Sat, 21 Jul 2012 08:28:12 +0000 (UTC) Received: from portsmonj.freebsd.org (portsmonj.freebsd.org [69.147.83.46]) by portsmonj.FreeBSD.org (8.14.5/8.14.4) with ESMTP id q6L8SCMs066857 for ; Sat, 21 Jul 2012 08:28:12 GMT (envelope-from linimon@FreeBSD.org) Date: Sat, 21 Jul 2012 08:28:12 GMT Message-Id: <201207210828.q6L8SCMs066857@portsmonj.FreeBSD.org> From: linimon@FreeBSD.org To: emulation@FreeBSD.org Cc: Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jul 2012 08:28:12 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.20120622225352/linux-flashplugin-9.0r289_1.log (_Jun_13_20:34:31_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-flashplugin9 If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. From owner-freebsd-emulation@FreeBSD.ORG Sat Jul 21 08:29:14 2012 Return-Path: Delivered-To: emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1143B106566B for ; Sat, 21 Jul 2012 08:29:14 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from portsmonj.FreeBSD.org (portsmonj.freebsd.org [69.147.83.46]) by mx1.freebsd.org (Postfix) with ESMTP id F15D88FC0A for ; Sat, 21 Jul 2012 08:29:13 +0000 (UTC) Received: from portsmonj.freebsd.org (portsmonj.freebsd.org [69.147.83.46]) by portsmonj.FreeBSD.org (8.14.5/8.14.4) with ESMTP id q6L8TDQv080215 for ; Sat, 21 Jul 2012 08:29:13 GMT (envelope-from linimon@FreeBSD.org) Date: Sat, 21 Jul 2012 08:29:13 GMT Message-Id: <201207210829.q6L8TDQv080215@portsmonj.FreeBSD.org> From: linimon@FreeBSD.org To: emulation@FreeBSD.org Cc: Subject: FreeBSD ports that you maintain which are currently scheduled for deletion X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jul 2012 08:29:14 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description: Accessibility Toolkit, Linux/i386 binary maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=linux-atk portname: archivers/linux-ucl description: RPM of UCL, a lossless data compression library maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=linux-ucl portname: archivers/linux-upx description: RPM of UPX, a high-performance executable packer maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=linux-upx portname: audio/linux-esound description: RPM of esound maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-esound portname: audio/linux-libaudiofile description: RPM of audiofile maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-libaudiofile portname: audio/linux-nas-libs description: Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-nas-libs portname: devel/linux-allegro description: Cross-platform game programming library (linux version) maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-allegro portname: devel/linux-libglade description: RPM of libglade maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-libglade portname: devel/linux-libsigc++20 description: Callback Framework for C++ (linux version) maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description: Cross-platform multi-media development API (linux version) maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-sdl12 portname: emulators/linux_base-fc4 description: Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=linux_base-fc4 portname: graphics/linux-imlib description: RPM of imlib maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-imlib portname: graphics/linux-jpeg description: RPM of the JPEG lib maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-jpeg portname: graphics/linux-libGLU description: OpenGL utility library (Linux version) maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-libGLU portname: graphics/linux-png description: RPM of the PNG lib maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-png portname: graphics/linux-png10 description: RPM of the PNG lib (old 1.0 version) maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-png10 portname: graphics/linux-tiff description: TIFF library, Linux/i386 binary maintainer: emulation@FreeBSD.org status: FORBIDDEN deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/linux-libg2c description: Fortran 77 compatibility runtime maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=linux-libg2c portname: multimedia/linux-libtheora description: Video codec maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=linux-libtheora portname: sysutils/linux-procps description: Linux psproc binaries maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=linux-procps portname: textproc/linux-expat description: Linux/i386 binary port of Expat XML-parsing library maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=linux-expat portname: textproc/linux-libxml description: RPM of libxml maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=linux-libxml portname: www/linux-f10-flashplugin10 description: Adobe Flash Player NPAPI Plugin maintainer: emulation@FreeBSD.org status: FORBIDDEN deprecated because: has vulnerabilities and is EOL expiration date: 2012-03-27 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-fonts/linux-fontconfig description: Linux/i386 binary of Fontconfig maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-fonts&portname=linux-fontconfig portname: x11-toolkits/linux-gtk description: RPM of the Gtk lib maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-gtk portname: x11-toolkits/linux-gtk2 description: GTK+ library, version 2.X, Linux binary maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-gtk2 portname: x11-toolkits/linux-openmotif description: Motif toolkit Linux libraries maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-openmotif portname: x11-toolkits/linux-pango description: Linux pango binary maintainer: emulation@FreeBSD.org status: FORBIDDEN deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango portname: x11/linux-xorg-libs description: Xorg libraries, linux binaries maintainer: emulation@FreeBSD.org deprecated because: expiration date: 2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=linux-xorg-libs If this problem is one that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Thanks for your efforts to help improve FreeBSD. From owner-freebsd-emulation@FreeBSD.ORG Sat Jul 21 08:29:53 2012 Return-Path: Delivered-To: emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B3AB0106568E for ; Sat, 21 Jul 2012 08:29:53 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from portsmonj.FreeBSD.org (portsmonj.freebsd.org [69.147.83.46]) by mx1.freebsd.org (Postfix) with ESMTP id A38048FC0A for ; Sat, 21 Jul 2012 08:29:53 +0000 (UTC) Received: from portsmonj.freebsd.org (portsmonj.freebsd.org [69.147.83.46]) by portsmonj.FreeBSD.org (8.14.5/8.14.4) with ESMTP id q6L8Trkw091617 for ; Sat, 21 Jul 2012 08:29:53 GMT (envelope-from linimon@FreeBSD.org) Date: Sat, 21 Jul 2012 08:29:53 GMT Message-Id: <201207210829.q6L8Trkw091617@portsmonj.FreeBSD.org> From: linimon@FreeBSD.org To: emulation@FreeBSD.org Cc: Subject: FreeBSD ports that you maintain which are currently marked forbidden X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jul 2012 08:29:53 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango If this problem is one that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Thanks for your efforts to help improve FreeBSD.