From owner-freebsd-emulation@FreeBSD.ORG Mon Jun 4 11:07:35 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 167E01065752 for ; Mon, 4 Jun 2012 11:07:35 +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 D86978FC18 for ; Mon, 4 Jun 2012 11:07:34 +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 q54B7Y35017390 for ; Mon, 4 Jun 2012 11:07:34 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q54B7YDV017388 for freebsd-emulation@FreeBSD.org; Mon, 4 Jun 2012 11:07:34 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Jun 2012 11:07:34 GMT Message-Id: <201206041107.q54B7YDV017388@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, 04 Jun 2012 11:07:35 -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/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 30 problems total. From owner-freebsd-emulation@FreeBSD.ORG Mon Jun 4 20:11:20 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 2EAD91065679 for ; Mon, 4 Jun 2012 20:11:20 +0000 (UTC) (envelope-from rnejdl@ringofsaturn.com) Received: from tethys.ringofsaturn.com (tethys.ringofsaturn.com [71.252.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id D2FD68FC1D for ; Mon, 4 Jun 2012 20:11:19 +0000 (UTC) Received: from ASSP.nospam (localhost [127.0.0.1]) (authenticated bits=0) by tethys.ringofsaturn.com (8.14.5/8.14.5) with ESMTP id q54KBIJM095376 for ; Mon, 4 Jun 2012 15:11:18 -0500 (CDT) (envelope-from rnejdl@ringofsaturn.com) Received: from anyhost.local ([127.0.0.1] helo=anyhost.local) by ASSP.nospam with ESMTP (ASSP 1.9); 4 Jun 2012 15:11:17 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 04 Jun 2012 15:11:17 -0500 From: Rusty Nejdl To: Mail-Reply-To: In-Reply-To: References: Message-ID: X-Sender: rnejdl@ringofsaturn.com User-Agent: Roundcube Webmail/0.9-git Subject: Re: one virtualbox vm disrupts all vms and entire network X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rnejdl@ringofsaturn.com List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 20:11:20 -0000 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 From owner-freebsd-emulation@FreeBSD.ORG Mon Jun 4 21:19:30 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 DB9FE106566B for ; Mon, 4 Jun 2012 21:19:30 +0000 (UTC) (envelope-from kris@pcbsd.org) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) by mx1.freebsd.org (Postfix) with ESMTP id 45C408FC08 for ; Mon, 4 Jun 2012 21:19:30 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.iXsystems.com (Postfix) with ESMTP id D36D71674 for ; Mon, 4 Jun 2012 14:19:29 -0700 (PDT) Received: from mail.iXsystems.com ([127.0.0.1]) by localhost (mail.ixsystems.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 18948-05 for ; Mon, 4 Jun 2012 14:19:29 -0700 (PDT) Received: from [192.168.0.126] (75-130-56-30.static.kgpt.tn.charter.com [75.130.56.30]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id 3ED241672 for ; Mon, 4 Jun 2012 14:19:29 -0700 (PDT) Message-ID: <4FCD2657.4030106@pcbsd.org> Date: Mon, 04 Jun 2012 17:19:19 -0400 From: Kris Moore User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120506 Thunderbird/12.0.1 MIME-Version: 1.0 To: freebsd-emulation@freebsd.org X-Enigmail-Version: 1.5pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: virtualbox-ose-additions broken? 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, 04 Jun 2012 21:19:30 -0000 Before I file a PR, is anybody else experiencing this with the latest VB on 9-STABLE? ------------------------- kBuild: Linking VBoxClient kBuild: Pass - Other Stuff kBuild: Pass - Staging /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: In function `VBoxClient::GetClipboardService()': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: undefined reference to `operator new(unsigned long)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: In function `~Service': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: undefined reference to `operator delete(void*)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: In function `~ClipboardService': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: undefined reference to `operator delete(void*)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: In function `VBoxClient::GetSeamlessService()': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: undefined reference to `operator new(unsigned long)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: In function `~VBoxGuestThreadFunction': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/thread.h:33: undefined reference to `operator delete(void*)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: In function `~VBoxGuestSeamlessObserver': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-glue.h:26: undefined reference to `operator delete(void*)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: In function `VBoxGuestWinCleanup(VBoxGuestWinInfo*, void*)': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:81: undefined reference to `operator delete(void*)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: In function `~VBoxGuestSeamlessGuestThread': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:46: undefined reference to `operator delete(void*)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: In function `~VBoxGuestSeamlessGuestObserver': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:111: undefined reference to `operator delete(void*)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o:/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:79 : more undefined references to `operator delete(void*)' follow /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o: In function `VBoxGuestWindowList::addWindow(unsigned long, bool, int, int, int, int, int, XRectangle*)': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: undefined reference to `operator new(unsigned long)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: undefined reference to `operator new(unsigned long)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: In function `VBoxClient::GetDisplayService()': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:243: undefined reference to `operator new(unsigned long)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: In function `~DisplayService': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:218: undefined reference to `operator delete(void*)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: In function `VBoxClient::GetHostVersionService()': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:211: undefined reference to `operator new(unsigned long)' /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: In function `~HostVersionService': /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:35: undefined reference to `operator delete(void*)' kmk: *** [/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient] Error 1 The failing command: @cc -m64 -o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd6 4/release/obj/VBoxClient/main.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o /usr/ports/emulators/virtualbox-ose-addit ions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboa rd.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/s eamless-host.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ob j/VBoxClient/thread.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ obj/VBoxClient/hostversion.o -L/usr/X11R6/lib32 -L/usr/X11R6/lib -L/usr/lib -L/usr/X11R6/lib -L/usr/local/lib -liconv /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/ RuntimeGuestR3.a /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/rel ease/lib/additions/RuntimeGuestR3.a -lX11 -lXrandr -lXt -lsupc++ -lgcc_eh -lXext -lXmu -lpthread -liconv *** Error code 2 Stop in /usr/ports/emulators/virtualbox-ose-additions. -- Kris Moore PC-BSD Software iXsystems From owner-freebsd-emulation@FreeBSD.ORG Mon Jun 4 22:22:13 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 E517810656D8 for ; Mon, 4 Jun 2012 22:22:13 +0000 (UTC) (envelope-from rnejdl@ringofsaturn.com) Received: from tethys.ringofsaturn.com (tethys.ringofsaturn.com [71.252.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id 958538FC15 for ; Mon, 4 Jun 2012 22:22:11 +0000 (UTC) Received: from ASSP.nospam (localhost [127.0.0.1]) (authenticated bits=0) by tethys.ringofsaturn.com (8.14.5/8.14.5) with ESMTP id q54MMACB029968 for ; Mon, 4 Jun 2012 17:22:11 -0500 (CDT) (envelope-from rnejdl@ringofsaturn.com) Received: from anyhost.local ([127.0.0.1] helo=anyhost.local) by ASSP.nospam with ESMTP (ASSP 1.9); 4 Jun 2012 17:22:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 04 Jun 2012 17:22:09 -0500 From: Rusty Nejdl To: Mail-Reply-To: In-Reply-To: <4FCD2657.4030106@pcbsd.org> References: <4FCD2657.4030106@pcbsd.org> Message-ID: X-Sender: rnejdl@ringofsaturn.com User-Agent: Roundcube Webmail/0.9-git Subject: Re: virtualbox-ose-additions broken? X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rnejdl@ringofsaturn.com List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 22:22:14 -0000 Kris, Yes, I get the same error when building. Rusty Nejdl On 2012-06-04 16:19, Kris Moore wrote: > Before I file a PR, is anybody else experiencing this with the latest > VB > on 9-STABLE? > > ------------------------- > > kBuild: Linking VBoxClient > kBuild: Pass - Other Stuff > kBuild: Pass - Staging > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: > In function `VBoxClient::GetClipboardService()': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: > undefined reference to `operator new(unsigned long)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: > In function `~Service': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: > undefined reference to `operator delete(void*)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: > In function `~ClipboardService': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: > undefined reference to `operator delete(void*)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `VBoxClient::GetSeamlessService()': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: > undefined reference to `operator new(unsigned long)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `~VBoxGuestThreadFunction': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/thread.h:33: > undefined reference to `operator delete(void*)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `~VBoxGuestSeamlessObserver': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-glue.h:26: > undefined reference to `operator delete(void*)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `VBoxGuestWinCleanup(VBoxGuestWinInfo*, void*)': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:81: > undefined reference to `operator delete(void*)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `~VBoxGuestSeamlessGuestThread': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:46: > undefined reference to `operator delete(void*)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `~VBoxGuestSeamlessGuestObserver': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:111: > undefined reference to `operator delete(void*)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o:/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:79 > : more undefined references to `operator delete(void*)' follow > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o: > In function `VBoxGuestWindowList::addWindow(unsigned long, bool, int, > int, int, int, int, XRectangle*)': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: > undefined reference to `operator new(unsigned long)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: > undefined reference to `operator new(unsigned long)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: > In function `VBoxClient::GetDisplayService()': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:243: > undefined reference to `operator new(unsigned long)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: > In function `~DisplayService': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:218: > undefined reference to `operator delete(void*)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: > In function `VBoxClient::GetHostVersionService()': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:211: > undefined reference to `operator new(unsigned long)' > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: > In function `~HostVersionService': > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:35: > undefined reference to `operator delete(void*)' > kmk: *** > > [/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient] > Error 1 > The failing command: > @cc -m64 -o > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd6 > 4/release/obj/VBoxClient/main.o > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o > /usr/ports/emulators/virtualbox-ose-addit > > ions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboa > rd.o > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/s > eamless-host.o > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ob > j/VBoxClient/thread.o > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ > obj/VBoxClient/hostversion.o -L/usr/X11R6/lib32 -L/usr/X11R6/lib > -L/usr/lib -L/usr/X11R6/lib -L/usr/local/lib -liconv > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/ > RuntimeGuestR3.a > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a > > > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/rel > ease/lib/additions/RuntimeGuestR3.a -lX11 -lXrandr -lXt > -lsupc++ -lgcc_eh -lXext -lXmu -lpthread -liconv > *** Error code 2 > > Stop in /usr/ports/emulators/virtualbox-ose-additions. From owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 02:21:06 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 C5ADA106564A for ; Tue, 5 Jun 2012 02:21:06 +0000 (UTC) (envelope-from madis555@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 548108FC08 for ; Tue, 5 Jun 2012 02:21:06 +0000 (UTC) Received: by wibhj8 with SMTP id hj8so2802021wib.13 for ; Mon, 04 Jun 2012 19:21:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:reply-to:to:cc:subject:message-id:date; bh=mNKaiHVuQp5bCjh9HAApTFeIQ3ahZeJwPWAu2h++ezA=; b=BGrl7I+Z8ighGQz+4KE38bbrJnjSyGvS9Kw76xOsKvgUkfl0K0oUNDKVCC2PdoVFd3 i0BQc7ZRg9QqJjkmz481bUbSALr6ygg3sGctEfEL98RSDl8HQbGPYi2LF99TgwleJudp w+jY2Jvd4NKLAYYQXRe3tJeNtr7155rXs6PynDykWdE1MscabrhJm5bTu/e/QLJRDWB3 mWQqirNdmGzDqA5Olc94IKUsxPq3pLLDhfzN4FfukXoYn/h/U1DihlN67jkg1mQg86Co AtXM0FLK0p6EMg7wZlRYTODeAuJGp2rM3NJCArfX6Kn4V/fVA7VIMRVu/khaxwSIGroW eo9A== Received: by 10.216.228.224 with SMTP id f74mr12583050weq.217.1338862864153; Mon, 04 Jun 2012 19:21:04 -0700 (PDT) Received: from ketas-laptop.mydomain (195.20.191.90.dyn.estpak.ee. [90.191.20.195]) by mx.google.com with ESMTPS id fo7sm23965676wib.9.2012.06.04.19.21.03 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jun 2012 19:21:03 -0700 (PDT) Sender: Sulev-Madis Silber Received: by ketas-laptop.mydomain (Postfix, from userid 1001) id 1851A11F823; Tue, 5 Jun 2012 05:21:02 +0300 (EEST) From: "Sulev-Madis 'ketas' Silber" To: emulation@FreeBSD.org Message-Id: <20120605022102.1851A11F823@ketas-laptop.mydomain> Date: Tue, 5 Jun 2012 05:10:41 +0300 (EEST) Cc: Sulev-Madis 'ketas' Silber Subject: FreeBSD Ports conflicts checker X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sulev-Madis 'ketas' Silber List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 02:21:06 -0000 HTML version of this report is here: http://ketas.si.pri.ee/ports-conflicts/emulation@FreeBSD.org For port audio/linux-f10-alsa-lib suggesting new CONFLICTS alsa-lib-[0-9]* because of overlapping files lib/libasound.so.2 (also used by audio/alsa-lib) For port audio/linux-f10-libaudiofile suggesting new CONFLICTS linux-libaudiofile-[0-9]* because of overlapping files usr/bin/sfconvert (also used by ) ... skipped 22 other ones For port audio/linux-f10-nas-libs suggesting new CONFLICTS linux-nas-libs-[0-9]* because of overlapping files usr/lib/libaudio.so.2 (also used by audio/linux-nas-libs) ... skipped 1 other ones For port audio/linux-f10-pulseaudio-libs suggesting new CONFLICTS pulseaudio-[0-9]* because of overlapping files etc/pulse/client.conf-dist (also used by audio/pulseaudio) For port audio/linux-nas-libs suggesting new CONFLICTS linux-f10-nas-libs-[0-9]* because of overlapping files usr/lib/libaudio.so.2 (also used by audio/linux-f10-nas-libs) ... skipped 1 other ones For port devel/linux-f10-dbus-libs suggesting new CONFLICTS dbus-[0-9]* because of overlapping files lib/libdbus-1.so.3 (also used by devel/dbus) For port devel/linux-f10-libsigc++20 suggesting new CONFLICTS because of overlapping files For port devel/linux-f10-nspr suggesting new CONFLICTS nspr-[0-9]* because of overlapping files lib/libnspr4.so (also used by devel/nspr) ... skipped 2 other ones For port devel/linux-f10-sdl12 suggesting new CONFLICTS linux-sdl-[0-9]* because of overlapping files usr/lib/libSDL-1.2.so.0 (also used by devel/linux-sdl12) For port devel/linux-sdl12 suggesting new CONFLICTS linux-f10-sdl-[0-9]* because of overlapping files usr/lib/libSDL-1.2.so.0 (also used by devel/linux-f10-sdl12) For port emulators/linux_base-c6 suggesting new CONFLICTS bash-[0-9]* bash-static-[0-9]* bsd-grep-[0-9]* bsd-sort-[0-9]* bzip2-[0-9]* db43-[0-9]* db47-[0-9]* e2fsprogs-[0-9]* freegrep-[0-9]* glib-[0-9]* gnat-aux-[0-9]* gnugrep-[0-9]* krb5-[0-9]* ncurses-[0-9]* ncurses-devel-[0-9]* popt-[0-9]* readline-[0-9]* readlink-[0-9]* tex-[0-9]* zlib-[0-9]* because of overlapping files bin/bash (also used by emulators/linux_base-f10 emulators/linux_base-fc4 emulators/linux_base-gentoo-stage3 shells/bash shells/bash-static) ... skipped 45 other ones For port emulators/linux_base-f10 suggesting new CONFLICTS bash-[0-9]* bash-static-[0-9]* bsd-grep-[0-9]* bsd-sort-[0-9]* bzip2-[0-9]* db47-[0-9]* e2fsprogs-[0-9]* e2fsprogs-libblkid-[0-9]* e2fsprogs-libss-[0-9]* e2fsprogs-libuuid-[0-9]* freegrep-[0-9]* glib-[0-9]* gnat-aux-[0-9]* gnugrep-[0-9]* linux_base-fc-[0-9]* ncurses-[0-9]* ncurses-devel-[0-9]* popt-[0-9]* zlib-[0-9]* because of overlapping files bin/basename (also used by emulators/linux_base-fc4) ... skipped 1409 other ones For port emulators/linux_base-fc4 suggesting new CONFLICTS bash-[0-9]* bash-static-[0-9]* bsd-grep-[0-9]* bsd-sort-[0-9]* db42-[0-9]* db42-nocrypto-[0-9]* db43-[0-9]* e2fsprogs-[0-9]* e2fsprogs-libblkid-[0-9]* e2fsprogs-libss-[0-9]* e2fsprogs-libuuid-[0-9]* freegrep-[0-9]* gnat-aux-[0-9]* gnugrep-[0-9]* linux_base-f10-[0-9]* because of overlapping files bin/basename (also used by emulators/linux_base-f10) ... skipped 1395 other ones For port ftp/linux-f10-curl suggesting new CONFLICTS linux_base-gentoo-stage3-[0-9]* because of overlapping files usr/bin/curl (also used by emulators/linux_base-gentoo-stage3) ... skipped 1 other ones For port graphics/linux-dri74 suggesting new CONFLICTS nvidia-driver-[0-9]* because of overlapping files usr/lib/libGL.so.1 (also used by graphics/linux-f10-dri x11/nvidia-driver x11/nvidia-driver-173 x11/nvidia-driver-71 x11/nvidia-driver-96) For port graphics/linux-f10-dri suggesting new CONFLICTS linux-f10-libGLU-[0-9]* nvidia-driver-[0-9]* because of overlapping files usr/lib/libGL.so.1 (also used by graphics/linux-dri74 x11/nvidia-driver x11/nvidia-driver-173 x11/nvidia-driver-71 x11/nvidia-driver-96) ... skipped 2 other ones For port graphics/linux-f10-libGLU suggesting new CONFLICTS linux-f10-dri-[0-9]* because of overlapping files usr/lib/libGLU.so.1 (also used by graphics/linux-f10-dri) ... skipped 1 other ones For port graphics/linux-f10-png10 suggesting new CONFLICTS linux-png-[0-9]* because of overlapping files usr/lib/libpng.so.2 (also used by ) For port graphics/linux_dri suggesting new CONFLICTS linux_base-gentoo-stage3-[0-9]* because of overlapping files usr/lib/libexpat.so.1 (also used by emulators/linux_base-gentoo-stage3) For port security/linux-f10-libgpg-error suggesting new CONFLICTS libgpg-error-[0-9]* because of overlapping files lib/libgpg-error.so.0 (also used by security/libgpg-error) For port security/linux-f10-openssl suggesting new CONFLICTS linux_base-gentoo-stage3-[0-9]* because of overlapping files usr/bin/openssl (also used by emulators/linux_base-gentoo-stage3 security/linux-openssl) For port sysutils/linux-procps suggesting new CONFLICTS linux_base-gentoo-stage3-[0-9]* because of overlapping files bin/ps (also used by emulators/linux_base-gentoo-stage3) ... skipped 15 other ones For port textproc/linux-expat suggesting new CONFLICTS linux_base-gentoo-stage3-[0-9]* because of overlapping files usr/bin/xmlwf (also used by emulators/linux_base-gentoo-stage3 textproc/linux-f10-expat) For port textproc/linux-f10-expat suggesting new CONFLICTS linux_base-gentoo-stage3-[0-9]* because of overlapping files usr/bin/xmlwf (also used by emulators/linux_base-gentoo-stage3 textproc/linux-expat) For port textproc/linux-f10-libxml2 suggesting new CONFLICTS linux_base-gentoo-stage3-[0-9]* because of overlapping files usr/bin/xmlcatalog (also used by emulators/linux_base-gentoo-stage3 textproc/linux-libxml2) ... skipped 2 other ones For port textproc/linux-f10-scim-gtk suggesting new CONFLICTS linux-scim-gtk-fc4-[0-9]* because of overlapping files usr/lib/gtk-2.0/immodules/im-scim.so (also used by ) For port textproc/linux-f10-scim-libs suggesting new CONFLICTS linux-scim-libs-fc4-[0-9]* because of overlapping files usr/lib/libscim-1.0.so.8 (also used by ) ... skipped 5 other ones For port www/linux-f10-flashplugin10 suggesting new CONFLICTS linux-f10-flashplugin-11.2r202.235 because of overlapping files bin/flash-player-properties (also used by www/linux-f10-flashplugin11) ... skipped 8 other ones For port www/linux-f10-flashplugin11 suggesting new CONFLICTS linux-f10-flashplugin-10.3r183.11 because of overlapping files bin/flash-player-properties (also used by www/linux-f10-flashplugin10) ... skipped 8 other ones For port www/linux-flashplugin9 suggesting new CONFLICTS linux-f10-flashplugin-11.2r202.235 because of overlapping files usr/lib/libflashsupport.so (also used by www/linux-f10-flashplugin10 www/linux-f10-flashplugin11) For port x11-fonts/linux-fontconfig suggesting new CONFLICTS fontconfig-[0-9]* because of overlapping files etc/fonts/fonts.dtd (also used by x11-fonts/fontconfig) For port x11-toolkits/linux-f10-gtk2 suggesting new CONFLICTS gtk-[0-9]* because of overlapping files etc/gtk-2.0/im-multipress.conf (also used by x11-toolkits/gtk20) For port x11-toolkits/linux-f10-pango suggesting new CONFLICTS pango-[0-9]* because of overlapping files etc/pango/pangox.aliases (also used by x11-toolkits/linux-pango x11-toolkits/pango) For port x11-toolkits/linux-pango suggesting new CONFLICTS pango-[0-9]* because of overlapping files etc/pango/pangox.aliases (also used by x11-toolkits/linux-f10-pango x11-toolkits/pango) -- ------------------------------------------------------------ NOTE: Full file list may be incomplete This message was sent using new experimental Ports tree CONFLICTS cross-checker tool made by Sulev-Madis "ketas" Silber Reports are currently sent manually. They are sent in good will, without any meaning to SPAM anyone. Source: http://ketas.si.pri.ee/ports-check-conflicts3.sh Example output: http://ketas.si.pri.ee/ports-check-conflicts-output3.txt Ask me for latest version if you want to try it by yourself, current version isn't yet available for downloading. Tue Jun 5 05:21:02 EEST 2012 ------------------------------------------------------------ From owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 04:33:37 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 AAE0D106566C for ; Tue, 5 Jun 2012 04:33:37 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6FE298FC19 for ; Tue, 5 Jun 2012 04:33:37 +0000 (UTC) Received: by obcni5 with SMTP id ni5so10646495obc.13 for ; Mon, 04 Jun 2012 21:33:36 -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:content-transfer-encoding; bh=TUW4ay6vg5nhz8ahgJJDjV2vhqw3cUdFXEPcuWFJS6M=; b=pWOe5w3noZQiAFMyiZmw3rgz40LcVXsezeO8C3kU+8p/nqNdaHaqmc2MU/8w402aD5 vRcqePi4MHku5Z80Nlb3DYYLctWXnvy4b/Ftp6Ii1e+/CkOH7EQTkk4RLzoFSsCmpYbu 2zA1D6mSAxY2X28+0c585Ko6sb61ECPdGhYJnvg2tWy2B1xaY7wQMHwebvhH4S8x3BQK vhhTOD012AbCccSJ3MTPkwDqOCoB/CJg96ldydeB+YSen4iqXQEsDlkuaAqKxFFU1/Y1 Fmw678Rq7rD9CuIqlQNv3kN1TjBqFQ2vZmT60SLVT0Q2IOQvlTpvAK7EHf3lm0ON2vYP 6CqA== MIME-Version: 1.0 Received: by 10.60.24.7 with SMTP id q7mr14273116oef.50.1338870816864; Mon, 04 Jun 2012 21:33:36 -0700 (PDT) Received: by 10.60.66.230 with HTTP; Mon, 4 Jun 2012 21:33:36 -0700 (PDT) In-Reply-To: References: Date: Mon, 4 Jun 2012 23:33:36 -0500 Message-ID: From: Brandon Gooch To: freebsd-emulation@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [SOLVED] Re: VirtualBox 4.1.16 on 10-CURRENT: /usr/X11R6/lib/libGL.so: undefined reference 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: Tue, 05 Jun 2012 04:33:37 -0000 On Sun, May 27, 2012 at 10:03 PM, Brandon Gooch wrote: > I'm having issues compiling VirtualBox 4.1.16; here is the relevant > snip from the configure.log file: > > $ cat /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/configur= e.log > [SNIP] > ***** Checking Mesa / GLU ***** > compiling the following source file: > #include > #include > #include > #include > extern "C" int main(void) > { > =A0Display *dpy; > =A0int major, minor; > > =A0dpy =3D XOpenDisplay(NULL); > =A0if (dpy) > =A0{ > =A0 =A0Bool glx_version =3D glXQueryVersion(dpy, &major, &minor); > =A0 =A0XCloseDisplay(dpy); > =A0 =A0if (glx_version) > =A0 =A0{ > =A0 =A0 =A0printf("found version %u.%u, OK.\n", major, minor); > =A0 =A0 =A0return 0; > =A0 =A0} > =A0} > =A0printf("found (inactive), OK.\n"); > =A0return 0; > } > using the following command line: > c++ =A0-g -O -Wall -o > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/.tmp_out > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/.tmp_src.cc > "-L/usr/X11R6/lib -L/usr/X11R6/lib64 -L/usr/local/lib -lXext -lX11 > -lGL -I/usr/local/include" > /usr/X11R6/lib/libGL.so: undefined reference to `_nv017tls' > /usr/X11R6/lib/libGL.so: undefined reference to `_nv014tls' > > I running: > > FreeBSD m6500.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r236044: Sat > May 26 03:04:16 CDT 2012 > root@m6500.local:/usr/obj/usr/src/sys/DELL_M6500 =A0amd64 > > xorg-7.5.2 > xorg-server-1.7.7_5,1 > nvidia-driver-295.49 The error I was experiencing was my own fault -- I had previously performed an install of a version of the NVIDIA driver outside of ports which placed files in /usr/X11R6/lib -- the error message should have been obvious to me, but for whatever reason I overlooked it. Simply moving /usr/X11R6/lib out of the way resolved the issue; sorry for the noise! -Brandon From owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 05:37:11 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 1EBB01065675 for ; Tue, 5 Jun 2012 05:37:11 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id B943D8FC0A for ; Tue, 5 Jun 2012 05:37:10 +0000 (UTC) Received: from [10.33.44.148] (89.144.192.140) by groupware.itac.at (Axigen) with (CAMELLIA256-SHA encrypted) ESMTPSA id 38D09A; Tue, 5 Jun 2012 07:37:12 +0200 From: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= To: Kris Moore , freebsd-emulation@freebsd.org X-Mailer: Modest 3.90.7 References: <4FCD2657.4030106@pcbsd.org> In-Reply-To: <4FCD2657.4030106@pcbsd.org> Content-Type: text/plain; charset=utf-8 Content-ID: <1338874646.15905.1.camel@Nokia-N900-42-11> Date: Tue, 05 Jun 2012 07:37:27 +0200 Message-Id: <1338874647.15905.2.camel@Nokia-N900-42-11> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0204.4FCD9B05.016A,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: Subject: Re: virtualbox-ose-additions broken? X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 05:37:11 -0000 Shit. I have only seen that compile errors on head yet but was unable to find out what caused it. It seems it was MFCd now. Any hints are very appreciated. Creating a PR is probably worthless as I am usually the only one that looks at them. emulation@ covers a wider audience of people that care about vbox and are able to debug and fix bugs. Thanks for the report and getting my attention! On Mo.,  4. Jun. 2012 23:19:19 CEST, Kris Moore wrote: > Before I file a PR, is anybody else experiencing this with the latest VB > on 9-STABLE? > > ------------------------- > > kBuild: Linking VBoxClient > kBuild: Pass - Other Stuff > kBuild: Pass - Staging > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: > In function `VBoxClient::GetClipboardService()': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: > undefined reference to `operator new(unsigned long)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: > In function `~Service': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: > undefined reference to `operator delete(void*)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: > In function `~ClipboardService': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: > undefined reference to `operator delete(void*)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `VBoxClient::GetSeamlessService()': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: > undefined reference to `operator new(unsigned long)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `~VBoxGuestThreadFunction': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/thread.h:33: > undefined reference to `operator delete(void*)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `~VBoxGuestSeamlessObserver': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-glue.h:26: > undefined reference to `operator delete(void*)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `VBoxGuestWinCleanup(VBoxGuestWinInfo*, void*)': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:81: > undefined reference to `operator delete(void*)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `~VBoxGuestSeamlessGuestThread': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:46: > undefined reference to `operator delete(void*)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > In function `~VBoxGuestSeamlessGuestObserver': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:111: > undefined reference to `operator delete(void*)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o:/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:79 > : more undefined references to `operator delete(void*)' follow > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o: > In function `VBoxGuestWindowList::addWindow(unsigned long, bool, int, > int, int, int, int, XRectangle*)': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: > undefined reference to `operator new(unsigned long)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: > undefined reference to `operator new(unsigned long)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: > In function `VBoxClient::GetDisplayService()': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:243: > undefined reference to `operator new(unsigned long)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: > In function `~DisplayService': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:218: > undefined reference to `operator delete(void*)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: > In function `VBoxClient::GetHostVersionService()': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:211: > undefined reference to `operator new(unsigned long)' > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: > In function `~HostVersionService': > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:35: > undefined reference to `operator delete(void*)' > kmk: *** > [/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient] > Error 1 > The failing command: > @cc                                  -m64    -o > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd6 > 4/release/obj/VBoxClient/main.o > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o > /usr/ports/emulators/virtualbox-ose-addit > ions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboa > rd.o > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/s > eamless-host.o > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ob > j/VBoxClient/thread.o > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ > obj/VBoxClient/hostversion.o    -L/usr/X11R6/lib32  -L/usr/X11R6/lib > -L/usr/lib  -L/usr/X11R6/lib  -L/usr/local/lib    -liconv  > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/ > RuntimeGuestR3.a  > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a >  > /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/rel > ease/lib/additions/RuntimeGuestR3.a    -lX11    -lXrandr    -lXt    -lsupc++ >    -lgcc_eh    -lXext    -lXmu    -lpthread    -liconv *** Error code 2 > > Stop in /usr/ports/emulators/virtualbox-ose-additions. > > > -- > Kris Moore > PC-BSD Software > iXsystems > > _______________________________________________ > 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 owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 05:39:04 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 08431106564A for ; Tue, 5 Jun 2012 05:39:04 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id B6F0F8FC12 for ; Tue, 5 Jun 2012 05:39:03 +0000 (UTC) Received: by obcni5 with SMTP id ni5so10735575obc.13 for ; Mon, 04 Jun 2012 22:39:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=rnmOZBLdFZ5gLsakL28kJM9p2npi5KNA1svrgWJc+lk=; b=ABZEDsx5dEU0pF6cTgxrX4W40Fk+j9iTpZElYUpa2Iqf17i5kjWlESKinhgoTU0wKL KGeqnL2QPtvyn/pL3U0sAFgfSX9fYrf7Tqv5XS5sEBv/qLA5XRe4DP6Q3TWXGAxtAVvG C6mPdxHfwJtnJL9Ki1+0iIuPFip966pNXOtMw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=rnmOZBLdFZ5gLsakL28kJM9p2npi5KNA1svrgWJc+lk=; b=pTZL32GmpFAY7PC1INcTmDIfbOqrv5fr+RvC7Pm7MF8yQUYf8v/jW3iNfTWJb2QbJ2 WB4c3tXFCKt8m/3SHafODAf4jYpwY0J00gdDIKXe8gC8mMczkLPfUcg9naBBN2W3W7q8 uuMHjTKEi79WifpECyD9Ox1IaosXxN20JVCvn9749Dnjk4fXolqWvmLNDytuYdPXZCQw nH+4hcrUY+YcIJawQFJUHG2OF8OxRHDj2JqIKXhn34qelSx8Q14GpBMECLvzFhyYxrDh ttvH4qUuieNluz9NJOKX/RNMW/Qyb4ACrLkQ8L0pCcqDvfCekNeoeGAIoCL72v+DpF6X yYGw== Received: by 10.60.1.165 with SMTP id 5mr9204202oen.36.1338874743139; Mon, 04 Jun 2012 22:39:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.204.69 with HTTP; Mon, 4 Jun 2012 22:38:32 -0700 (PDT) In-Reply-To: <1338874647.15905.2.camel@Nokia-N900-42-11> References: <4FCD2657.4030106@pcbsd.org> <1338874647.15905.2.camel@Nokia-N900-42-11> From: Eitan Adler Date: Tue, 5 Jun 2012 01:38:32 -0400 Message-ID: To: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQnoBTdHje02XN4qwWbfaLAT+siJ/yOjz39J8dgrR5B8046wEXDCQHTIXKeZi1dxrcyV4C++ Cc: freebsd-emulation@freebsd.org, Kris Moore Subject: Re: virtualbox-ose-additions broken? 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: Tue, 05 Jun 2012 05:39:04 -0000 On 5 June 2012 01:37, Bernhard Fr=C3=B6hlich wrote: > Shit. I have only seen that compile errors on head yet but was unable to = find out what caused it. It seems it was MFCd now. Any hints are very appre= ciated. > > Creating a PR is probably worthless as I am usually the only one that loo= ks at them. emulation@ covers a wider audience of people that care about vb= ox and are able to debug and fix bugs. Thanks for the report and getting my= attention! Can you please submit a PR anyways? It is good to have some kind of 'official' record of what needs to be fixed. --=20 Eitan Adler From owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 05:45: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 169381065673 for ; Tue, 5 Jun 2012 05:45:44 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 8BB9A8FC0A for ; Tue, 5 Jun 2012 05:45:43 +0000 (UTC) Received: from [10.33.44.148] (89.144.192.140) by groupware.itac.at (Axigen) with (CAMELLIA256-SHA encrypted) ESMTPSA id 37FAB1; Tue, 5 Jun 2012 07:45:44 +0200 From: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= To: Eitan Adler X-Mailer: Modest 3.90.7 References: <4FCD2657.4030106@pcbsd.org> <1338874647.15905.2.camel@Nokia-N900-42-11> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-ID: <1338875158.15905.4.camel@Nokia-N900-42-11> Date: Tue, 05 Jun 2012 07:45:59 +0200 Message-Id: <1338875159.15905.5.camel@Nokia-N900-42-11> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0204.4FCD9D06.0110,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: freebsd-emulation@freebsd.org, Kris Moore Subject: Re: virtualbox-ose-additions broken? X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 05:45:44 -0000 vbox never had a lot of PRs but we maintain a wiki page with almost all vbox problems that users reported (mailinglists, private mail, irc, ...). http://wiki.freebsd.org/Virtualbox/ToDo I will add the currently missing reports once I am on a device with a proper kwertz keyboard. On Di.,  5. Jun. 2012 07:38:32 CEST, Eitan Adler wrote: > On 5 June 2012 01:37, Bernhard Fröhlich wrote: > > Shit. I have only seen that compile errors on head yet but was unable > > to find out what caused it. It seems it was MFCd now. Any hints are > > very appreciated. > > > > Creating a PR is probably worthless as I am usually the only one that > > looks at them. emulation@ covers a wider audience of people that care > > about vbox and are able to debug and fix bugs. Thanks for the report > > and getting my attention! > > Can you please submit a PR anyways? It is good to have some kind of > 'official' record of what needs to be fixed. > > > -- > Eitan Adler From owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 07:08:05 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 B35EF106566C for ; Tue, 5 Jun 2012 07:08:05 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward12.mail.yandex.net (forward12.mail.yandex.net [IPv6:2a02:6b8:0:801::2]) by mx1.freebsd.org (Postfix) with ESMTP id 363908FC0A for ; Tue, 5 Jun 2012 07:08:05 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward12.mail.yandex.net (Yandex) with ESMTP id D71A8C21962; Tue, 5 Jun 2012 11:08:03 +0400 (MSK) Received: from smtp11.mail.yandex.net (localhost [127.0.0.1]) by smtp11.mail.yandex.net (Yandex) with ESMTP id B44FC7E033A; Tue, 5 Jun 2012 11:08:03 +0400 (MSK) Received: from 87.249.28.58.tel.ru (87.249.28.58.tel.ru [87.249.28.58]) by smtp11.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 836W0Cqs-836KfESn; Tue, 5 Jun 2012 11:08:03 +0400 X-Yandex-Rcpt-Suid: madis555@hot.ee X-Yandex-Rcpt-Suid: emulation@FreeBSD.org Message-ID: <4FCDB053.7040900@passap.ru> Date: Tue, 05 Jun 2012 11:08:03 +0400 From: Boris Samorodov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:12.0) Gecko/20120428 Thunderbird/12.0 MIME-Version: 1.0 To: Sulev-Madis 'ketas' Silber References: <20120605022102.1851A11F823@ketas-laptop.mydomain> In-Reply-To: <20120605022102.1851A11F823@ketas-laptop.mydomain> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: emulation@FreeBSD.org Subject: Re: FreeBSD Ports conflicts checker 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: Tue, 05 Jun 2012 07:08:05 -0000 05.06.2012 06:10, Sulev-Madis 'ketas' Silber написал: > For port audio/linux-f10-alsa-lib suggesting new CONFLICTS alsa-lib-[0-9]* because of overlapping files lib/libasound.so.2 (also used by audio/alsa-lib) Seems to be a false positive. PREFIX for linux-f10-alsa-lib and alsa-lib should be different (/compat/linux/ and /usr/local/). -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 07:13:35 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 9F19B106564A for ; Tue, 5 Jun 2012 07:13:35 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C971B8FC14 for ; Tue, 5 Jun 2012 07:13:34 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA16533; Tue, 05 Jun 2012 10:13:27 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1SbnxH-0004AW-6t; Tue, 05 Jun 2012 10:13:27 +0300 Message-ID: <4FCDB195.5010009@FreeBSD.org> Date: Tue, 05 Jun 2012 10:13:25 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120503 Thunderbird/12.0.1 MIME-Version: 1.0 To: =?UTF-8?B?QmVybmhhcmQgRnLDtmhsaWNo?= References: <4FCD2657.4030106@pcbsd.org> <1338874647.15905.2.camel@Nokia-N900-42-11> In-Reply-To: <1338874647.15905.2.camel@Nokia-N900-42-11> X-Enigmail-Version: 1.5pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-emulation@FreeBSD.org, Kris Moore Subject: Re: virtualbox-ose-additions broken? 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: Tue, 05 Jun 2012 07:13:35 -0000 on 05/06/2012 08:37 Bernhard Fröhlich said the following: > Shit. I have only seen that compile errors on head yet but was unable to find out what caused it. It seems it was MFCd now. Any hints are very appreciated. It looks like a C compiler (cc) is used to link C++ code. I think that adding -lstdc++ may fix the problem, but a better solution would be to use c++ instead of cc. > Creating a PR is probably worthless as I am usually the only one that looks at them. emulation@ covers a wider audience of people that care about vbox and are able to debug and fix bugs. Thanks for the report and getting my attention! > > > On Mo., 4. Jun. 2012 23:19:19 CEST, Kris Moore wrote: > >> Before I file a PR, is anybody else experiencing this with the latest VB >> on 9-STABLE? >> >> ------------------------- >> >> kBuild: Linking VBoxClient >> kBuild: Pass - Other Stuff >> kBuild: Pass - Staging >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `VBoxClient::GetClipboardService()': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `~Service': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `~ClipboardService': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `VBoxClient::GetSeamlessService()': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `~VBoxGuestThreadFunction': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/thread.h:33: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `~VBoxGuestSeamlessObserver': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-glue.h:26: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `VBoxGuestWinCleanup(VBoxGuestWinInfo*, void*)': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:81: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `~VBoxGuestSeamlessGuestThread': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:46: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `~VBoxGuestSeamlessGuestObserver': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:111: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o:/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:79 >> : more undefined references to `operator delete(void*)' follow >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o: >> In function `VBoxGuestWindowList::addWindow(unsigned long, bool, int, >> int, int, int, int, XRectangle*)': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: >> In function `VBoxClient::GetDisplayService()': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:243: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: >> In function `~DisplayService': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:218: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: >> In function `VBoxClient::GetHostVersionService()': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:211: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: >> In function `~HostVersionService': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:35: >> undefined reference to `operator delete(void*)' >> kmk: *** >> [/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient] >> Error 1 >> The failing command: >> @cc -m64 -o ^^^^^^^^ >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd6 >> 4/release/obj/VBoxClient/main.o >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o >> /usr/ports/emulators/virtualbox-ose-addit >> ions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboa >> rd.o >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/s >> eamless-host.o >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ob >> j/VBoxClient/thread.o >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ >> obj/VBoxClient/hostversion.o -L/usr/X11R6/lib32 -L/usr/X11R6/lib >> -L/usr/lib -L/usr/X11R6/lib -L/usr/local/lib -liconv >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/ >> RuntimeGuestR3.a >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/rel >> ease/lib/additions/RuntimeGuestR3.a -lX11 -lXrandr -lXt -lsupc++ >> -lgcc_eh -lXext -lXmu -lpthread -liconv *** Error code 2 >> >> Stop in /usr/ports/emulators/virtualbox-ose-additions. -- Andriy Gapon From owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 08:46:33 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 B27481065675 for ; Tue, 5 Jun 2012 08:46:33 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 4209B8FC19 for ; Tue, 5 Jun 2012 08:46:33 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 2A7E53; Tue, 5 Jun 2012 10:46:34 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 05 Jun 2012 10:46:31 +0200 From: Bernhard Froehlich To: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= In-Reply-To: <1338875159.15905.5.camel@Nokia-N900-42-11> References: <4FCD2657.4030106@pcbsd.org> <1338874647.15905.2.camel@Nokia-N900-42-11> <1338875159.15905.5.camel@Nokia-N900-42-11> Message-ID: <8dfc1830ed81dbb6538d647368127b2b@bluelife.at> X-Sender: decke@bluelife.at User-Agent: Roundcube Webmail/0.7.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B020A.4FCDC767.033F,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: freebsd-emulation@freebsd.org, Moore , Kris Subject: Re: virtualbox-ose-additions broken? 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: Tue, 05 Jun 2012 08:46:33 -0000 The below link is wrong but here it is: http://wiki.freebsd.org/VirtualBox/ToDo I will add the open problems in a few minutes. -- Bernhard Fröhlich http://www.bluelife.at/ On 05.06.2012 07:45, Bernhard Fröhlich wrote: > vbox never had a lot of PRs but we maintain a wiki page with almost > all vbox problems that users reported (mailinglists, private mail, > irc, ...). > > http://wiki.freebsd.org/Virtualbox/ToDo > > I will add the currently missing reports once I am on a device with a > proper kwertz keyboard. > > > On Di.,  5. Jun. 2012 07:38:32 CEST, Eitan Adler > wrote: > >> On 5 June 2012 01:37, Bernhard Fröhlich wrote: >> > Shit. I have only seen that compile errors on head yet but was >> unable >> > to find out what caused it. It seems it was MFCd now. Any hints >> are >> > very appreciated. >> > >> > Creating a PR is probably worthless as I am usually the only one >> that >> > looks at them. emulation@ covers a wider audience of people that >> care >> > about vbox and are able to debug and fix bugs. Thanks for the >> report >> > and getting my attention! >> >> Can you please submit a PR anyways? It is good to have some kind of >> 'official' record of what needs to be fixed. >> >> >> -- >> Eitan Adler > > _______________________________________________ > 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 owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 08:52:08 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 276E41065744 for ; Tue, 5 Jun 2012 08:52:08 +0000 (UTC) (envelope-from david.morgan@gmail.com) Received: from metztli.tomaw.net (metztli.tomaw.net [82.165.134.85]) by mx1.freebsd.org (Postfix) with ESMTP id C54CE8FC1E for ; Tue, 5 Jun 2012 08:52:07 +0000 (UTC) Received: by metztli.tomaw.net (Postfix, from userid 1004) id 2EF1B10160BD; Tue, 5 Jun 2012 09:44:34 +0100 (BST) Date: Tue, 5 Jun 2012 09:44:34 +0100 From: David Morgan To: freebsd-emulation@FreeBSD.org Message-ID: <20120605084433.GD909@tomaw.net> References: <4FCD2657.4030106@pcbsd.org> <1338874647.15905.2.camel@Nokia-N900-42-11> <4FCDB195.5010009@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4FCDB195.5010009@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: Re: virtualbox-ose-additions broken? 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: Tue, 05 Jun 2012 08:52:08 -0000 On 10:13 Tue 05 Jun , Andriy Gapon wrote: > on 05/06/2012 08:37 Bernhard Fröhlich said the following: > > Shit. I have only seen that compile errors on head yet but was unable to find out what caused it. It seems it was MFCd now. Any hints are very appreciated. > > It looks like a C compiler (cc) is used to link C++ code. > I think that adding -lstdc++ may fix the problem, but a better solution would be > to use c++ instead of cc. > That's correct - re-running the failing command with gcc gives the same error, with g++ it succeeds. If I recall correctly adding -lstdc++ doesn't fix it. A change was made to Version.map for libsupc++ recently, which apparently made this compile correctly on i386, but didn't solve the problem for me on amd64. > > Creating a PR is probably worthless as I am usually the only one that looks at them. emulation@ covers a wider audience of people that care about vbox and are able to debug and fix bugs. Thanks for the report and getting my attention! > > > > > > On Mo., 4. Jun. 2012 23:19:19 CEST, Kris Moore wrote: > > > >> Before I file a PR, is anybody else experiencing this with the latest VB > >> on 9-STABLE? > >> > >> ------------------------- > >> > >> kBuild: Linking VBoxClient > >> kBuild: Pass - Other Stuff > >> kBuild: Pass - Staging > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: > >> In function `VBoxClient::GetClipboardService()': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: > >> undefined reference to `operator new(unsigned long)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: > >> In function `~Service': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: > >> undefined reference to `operator delete(void*)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: > >> In function `~ClipboardService': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: > >> undefined reference to `operator delete(void*)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > >> In function `VBoxClient::GetSeamlessService()': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: > >> undefined reference to `operator new(unsigned long)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > >> In function `~VBoxGuestThreadFunction': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/thread.h:33: > >> undefined reference to `operator delete(void*)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > >> In function `~VBoxGuestSeamlessObserver': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-glue.h:26: > >> undefined reference to `operator delete(void*)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > >> In function `VBoxGuestWinCleanup(VBoxGuestWinInfo*, void*)': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:81: > >> undefined reference to `operator delete(void*)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > >> In function `~VBoxGuestSeamlessGuestThread': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:46: > >> undefined reference to `operator delete(void*)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: > >> In function `~VBoxGuestSeamlessGuestObserver': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:111: > >> undefined reference to `operator delete(void*)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o:/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:79 > >> : more undefined references to `operator delete(void*)' follow > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o: > >> In function `VBoxGuestWindowList::addWindow(unsigned long, bool, int, > >> int, int, int, int, XRectangle*)': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: > >> undefined reference to `operator new(unsigned long)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: > >> undefined reference to `operator new(unsigned long)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: > >> In function `VBoxClient::GetDisplayService()': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:243: > >> undefined reference to `operator new(unsigned long)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: > >> In function `~DisplayService': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:218: > >> undefined reference to `operator delete(void*)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: > >> In function `VBoxClient::GetHostVersionService()': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:211: > >> undefined reference to `operator new(unsigned long)' > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: > >> In function `~HostVersionService': > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:35: > >> undefined reference to `operator delete(void*)' > >> kmk: *** > >> [/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient] > >> Error 1 > >> The failing command: > >> @cc -m64 -o > ^^^^^^^^ > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd6 > >> 4/release/obj/VBoxClient/main.o > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o > >> /usr/ports/emulators/virtualbox-ose-addit > >> ions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboa > >> rd.o > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/s > >> eamless-host.o > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ob > >> j/VBoxClient/thread.o > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ > >> obj/VBoxClient/hostversion.o -L/usr/X11R6/lib32 -L/usr/X11R6/lib > >> -L/usr/lib -L/usr/X11R6/lib -L/usr/local/lib -liconv > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/ > >> RuntimeGuestR3.a > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a > >> > >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/rel > >> ease/lib/additions/RuntimeGuestR3.a -lX11 -lXrandr -lXt -lsupc++ > >> -lgcc_eh -lXext -lXmu -lpthread -liconv *** Error code 2 > >> > >> Stop in /usr/ports/emulators/virtualbox-ose-additions. > > -- > Andriy Gapon > _______________________________________________ > 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 owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 10:06:32 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 73E80106564A for ; Tue, 5 Jun 2012 10:06:32 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id EFDC98FC1A for ; Tue, 5 Jun 2012 10:06:31 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 156DCA; Tue, 5 Jun 2012 12:06:33 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 05 Jun 2012 12:06:29 +0200 From: Bernhard Froehlich To: David Morgan In-Reply-To: <20120605084433.GD909@tomaw.net> References: <4FCD2657.4030106@pcbsd.org> "<1338874647.15905.2.camel@Nokia-N900-42-11>" <4FCDB195.5010009@FreeBSD.org> <20120605084433.GD909@tomaw.net> Message-ID: X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.7.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0205.4FCDDA26.009F,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: freebsd-emulation@freebsd.org Subject: Re: virtualbox-ose-additions broken? 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: Tue, 05 Jun 2012 10:06:32 -0000 That was a good hint! It seems the newly added libsupc++ causes that problems because until very recently the new operator symbols were not included. They have been added on current as of r236177 http://svnweb.freebsd.org/base?view=revision&revision=236177 On 9-STABLE the situation is that libstdc++/libsupc++ was already MFCd but that fix from head for thew new operator wasn't yet. So it currently fails on 9-STABLE. According to David that fix for the new operator also seems to have no affect on amd64 so the symbols probably have a different name there. I've already talked to DES about that and we need some nm output of latest libsupc++ on HEAD / amd64 to find the symbol names and add them to the map. So who can provide the nm output? -- Bernhard Froehlich http://www.bluelife.at/ On 05.06.2012 10:44, David Morgan wrote: > On 10:13 Tue 05 Jun , Andriy Gapon wrote: >> on 05/06/2012 08:37 Bernhard Fröhlich said the following: >> > Shit. I have only seen that compile errors on head yet but was >> unable to find out what caused it. It seems it was MFCd now. Any hints >> are very appreciated. >> >> It looks like a C compiler (cc) is used to link C++ code. >> I think that adding -lstdc++ may fix the problem, but a better >> solution would be >> to use c++ instead of cc. >> > > That's correct - re-running the failing command with gcc gives the > same > error, with g++ it succeeds. If I recall correctly adding -lstdc++ > doesn't fix it. > > A change was made to Version.map for libsupc++ recently, which > apparently made this compile correctly on i386, but didn't solve the > problem for me on amd64. > > >> > Creating a PR is probably worthless as I am usually the only one >> that looks at them. emulation@ covers a wider audience of people that >> care about vbox and are able to debug and fix bugs. Thanks for the >> report and getting my attention! >> > >> > >> > On Mo., 4. Jun. 2012 23:19:19 CEST, Kris Moore >> wrote: >> > >> >> Before I file a PR, is anybody else experiencing this with the >> latest VB >> >> on 9-STABLE? >> >> >> >> ------------------------- >> >> >> >> kBuild: Linking VBoxClient >> >> kBuild: Pass - Other Stuff >> >> kBuild: Pass - Staging >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> >> In function `VBoxClient::GetClipboardService()': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: >> >> undefined reference to `operator new(unsigned long)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> >> In function `~Service': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: >> >> undefined reference to `operator delete(void*)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> >> In function `~ClipboardService': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: >> >> undefined reference to `operator delete(void*)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> >> In function `VBoxClient::GetSeamlessService()': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: >> >> undefined reference to `operator new(unsigned long)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> >> In function `~VBoxGuestThreadFunction': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/thread.h:33: >> >> undefined reference to `operator delete(void*)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> >> In function `~VBoxGuestSeamlessObserver': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-glue.h:26: >> >> undefined reference to `operator delete(void*)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> >> In function `VBoxGuestWinCleanup(VBoxGuestWinInfo*, void*)': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:81: >> >> undefined reference to `operator delete(void*)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> >> In function `~VBoxGuestSeamlessGuestThread': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:46: >> >> undefined reference to `operator delete(void*)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> >> In function `~VBoxGuestSeamlessGuestObserver': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:111: >> >> undefined reference to `operator delete(void*)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o:/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:79 >> >> : more undefined references to `operator delete(void*)' follow >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o: >> >> In function `VBoxGuestWindowList::addWindow(unsigned long, bool, >> int, >> >> int, int, int, int, XRectangle*)': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: >> >> undefined reference to `operator new(unsigned long)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: >> >> undefined reference to `operator new(unsigned long)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: >> >> In function `VBoxClient::GetDisplayService()': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:243: >> >> undefined reference to `operator new(unsigned long)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: >> >> In function `~DisplayService': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:218: >> >> undefined reference to `operator delete(void*)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: >> >> In function `VBoxClient::GetHostVersionService()': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:211: >> >> undefined reference to `operator new(unsigned long)' >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: >> >> In function `~HostVersionService': >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:35: >> >> undefined reference to `operator delete(void*)' >> >> kmk: *** >> >> >> [/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient] >> >> Error 1 >> >> The failing command: >> >> @cc -m64 -o >> ^^^^^^^^ >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd6 >> >> 4/release/obj/VBoxClient/main.o >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o >> >> /usr/ports/emulators/virtualbox-ose-addit >> >> >> ions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboa >> >> rd.o >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/s >> >> eamless-host.o >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ob >> >> j/VBoxClient/thread.o >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ >> >> obj/VBoxClient/hostversion.o -L/usr/X11R6/lib32 >> -L/usr/X11R6/lib >> >> -L/usr/lib -L/usr/X11R6/lib -L/usr/local/lib -liconv >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/ >> >> RuntimeGuestR3.a >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a >> >> >> >> >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/rel >> >> ease/lib/additions/RuntimeGuestR3.a -lX11 -lXrandr >> -lXt -lsupc++ >> >> -lgcc_eh -lXext -lXmu -lpthread -liconv *** >> Error code 2 >> >> >> >> Stop in /usr/ports/emulators/virtualbox-ose-additions. >> >> -- >> Andriy Gapon >> _______________________________________________ >> 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" > _______________________________________________ > 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 owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 10:56: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 4626B106566C for ; Tue, 5 Jun 2012 10:56:24 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id C37878FC19 for ; Tue, 5 Jun 2012 10:56:23 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 3DD4A9; Tue, 5 Jun 2012 12:56:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 05 Jun 2012 12:56:22 +0200 From: Bernhard Froehlich To: David Morgan In-Reply-To: References: <4FCD2657.4030106@pcbsd.org> "<1338874647.15905.2.camel@Nokia-N900-42-11>" <4FCDB195.5010009@FreeBSD.org> <20120605084433.GD909@tomaw.net> Message-ID: X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.7.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0206.4FCDE5D6.02A3,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: freebsd-emulation@freebsd.org Subject: Re: virtualbox-ose-additions broken? 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: Tue, 05 Jun 2012 10:56:24 -0000 We have such an output from 10-current/amd64 now. http://pastebin.com/cVd8ryxG It seems that those 5 symbols are missing for amd64: 00000000000090d0 t _Znam 00000000000090b0 t _ZnamRKSt9nothrow_t 0000000000009220 t _Znwm 00000000000093f0 t _ZnwmPv 0000000000009110 t _ZnwmRKSt9nothrow_t Add them to Version.map like in r236177 and recompile libsupc++ or world and try again rebuilding vbox additions: http://svnweb.freebsd.org/base/head/gnu/lib/libsupc%2B%2B/Version.map?r1=236177&r2=236176&pathrev=236177 -- Bernhard Froehlich http://www.bluelife.at/ On 05.06.2012 12:06, Bernhard Froehlich wrote: > That was a good hint! It seems the newly added libsupc++ causes > that problems because until very recently the new operator symbols > were not included. They have been added on current as of r236177 > > http://svnweb.freebsd.org/base?view=revision&revision=236177 > > On 9-STABLE the situation is that libstdc++/libsupc++ was already > MFCd but that fix from head for thew new operator wasn't yet. So > it currently fails on 9-STABLE. According to David that fix for > the new operator also seems to have no affect on amd64 so the > symbols probably have a different name there. > > I've already talked to DES about that and we need some nm output > of latest libsupc++ on HEAD / amd64 to find the symbol names > and add them to the map. So who can provide the nm output? > > > -- > Bernhard Froehlich > http://www.bluelife.at/ > > > On 05.06.2012 10:44, David Morgan wrote: >> On 10:13 Tue 05 Jun , Andriy Gapon wrote: >>> on 05/06/2012 08:37 Bernhard Fröhlich said the following: >>> > Shit. I have only seen that compile errors on head yet but was >>> unable to find out what caused it. It seems it was MFCd now. Any >>> hints are very appreciated. >>> >>> It looks like a C compiler (cc) is used to link C++ code. >>> I think that adding -lstdc++ may fix the problem, but a better >>> solution would be >>> to use c++ instead of cc. >>> >> >> That's correct - re-running the failing command with gcc gives the >> same >> error, with g++ it succeeds. If I recall correctly adding -lstdc++ >> doesn't fix it. >> >> A change was made to Version.map for libsupc++ recently, which >> apparently made this compile correctly on i386, but didn't solve the >> problem for me on amd64. >> >> >>> > Creating a PR is probably worthless as I am usually the only one >>> that looks at them. emulation@ covers a wider audience of people that >>> care about vbox and are able to debug and fix bugs. Thanks for the >>> report and getting my attention! >>> > >>> > >>> > On Mo., 4. Jun. 2012 23:19:19 CEST, Kris Moore >>> wrote: >>> > >>> >> Before I file a PR, is anybody else experiencing this with the >>> latest VB >>> >> on 9-STABLE? >>> >> >>> >> ------------------------- >>> >> >>> >> kBuild: Linking VBoxClient >>> >> kBuild: Pass - Other Stuff >>> >> kBuild: Pass - Staging >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >>> >> In function `VBoxClient::GetClipboardService()': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: >>> >> undefined reference to `operator new(unsigned long)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >>> >> In function `~Service': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: >>> >> undefined reference to `operator delete(void*)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >>> >> In function `~ClipboardService': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: >>> >> undefined reference to `operator delete(void*)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>> >> In function `VBoxClient::GetSeamlessService()': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: >>> >> undefined reference to `operator new(unsigned long)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>> >> In function `~VBoxGuestThreadFunction': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/thread.h:33: >>> >> undefined reference to `operator delete(void*)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>> >> In function `~VBoxGuestSeamlessObserver': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-glue.h:26: >>> >> undefined reference to `operator delete(void*)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>> >> In function `VBoxGuestWinCleanup(VBoxGuestWinInfo*, void*)': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:81: >>> >> undefined reference to `operator delete(void*)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>> >> In function `~VBoxGuestSeamlessGuestThread': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:46: >>> >> undefined reference to `operator delete(void*)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>> >> In function `~VBoxGuestSeamlessGuestObserver': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:111: >>> >> undefined reference to `operator delete(void*)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o:/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:79 >>> >> : more undefined references to `operator delete(void*)' follow >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o: >>> >> In function `VBoxGuestWindowList::addWindow(unsigned long, bool, >>> int, >>> >> int, int, int, int, XRectangle*)': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: >>> >> undefined reference to `operator new(unsigned long)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: >>> >> undefined reference to `operator new(unsigned long)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: >>> >> In function `VBoxClient::GetDisplayService()': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:243: >>> >> undefined reference to `operator new(unsigned long)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: >>> >> In function `~DisplayService': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:218: >>> >> undefined reference to `operator delete(void*)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: >>> >> In function `VBoxClient::GetHostVersionService()': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:211: >>> >> undefined reference to `operator new(unsigned long)' >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: >>> >> In function `~HostVersionService': >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:35: >>> >> undefined reference to `operator delete(void*)' >>> >> kmk: *** >>> >> >>> [/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient] >>> >> Error 1 >>> >> The failing command: >>> >> @cc -m64 -o >>> ^^^^^^^^ >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd6 >>> >> 4/release/obj/VBoxClient/main.o >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o >>> >> /usr/ports/emulators/virtualbox-ose-addit >>> >> >>> ions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboa >>> >> rd.o >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/s >>> >> eamless-host.o >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ob >>> >> j/VBoxClient/thread.o >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ >>> >> obj/VBoxClient/hostversion.o -L/usr/X11R6/lib32 >>> -L/usr/X11R6/lib >>> >> -L/usr/lib -L/usr/X11R6/lib -L/usr/local/lib -liconv >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/ >>> >> RuntimeGuestR3.a >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a >>> >> >>> >> >>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/rel >>> >> ease/lib/additions/RuntimeGuestR3.a -lX11 -lXrandr >>> -lXt -lsupc++ >>> >> -lgcc_eh -lXext -lXmu -lpthread -liconv *** >>> Error code 2 >>> >> >>> >> Stop in /usr/ports/emulators/virtualbox-ose-additions. >>> >>> -- >>> Andriy Gapon >>> _______________________________________________ >>> 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" >> _______________________________________________ >> 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" > _______________________________________________ > 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 owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 13:14:44 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 384721065672 for ; Tue, 5 Jun 2012 13:14:44 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id B511E8FC0A for ; Tue, 5 Jun 2012 13:14:43 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 032D4E; Tue, 5 Jun 2012 15:14:38 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 05 Jun 2012 15:14:35 +0200 From: Bernhard Froehlich To: David Morgan In-Reply-To: References: <4FCD2657.4030106@pcbsd.org> "<1338874647.15905.2.camel@Nokia-N900-42-11>" <4FCDB195.5010009@FreeBSD.org> <20120605084433.GD909@tomaw.net> Message-ID: <0b99207bd9e96c80b84555e883130440@bluelife.at> X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.7.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0207.4FCE063B.02E1,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: freebsd-emulation@freebsd.org Subject: Re: virtualbox-ose-additions broken? 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: Tue, 05 Jun 2012 13:14:44 -0000 The bug was just fixed by des in HEAD in r236614 [1]. I've created a patch for 9-STABLE that includes r236177 and r236614 which should fix the virtualbox-ose-additions compile error. http://home.bluelife.at/patches/libsupcpp-fix-new-operator-9-STABLE.diff Feedback would be welcome. [1] http://svnweb.freebsd.org/base?view=revision&revision=236614 -- Bernhard Froehlich http://www.bluelife.at/ On 05.06.2012 12:56, Bernhard Froehlich wrote: > We have such an output from 10-current/amd64 now. > > http://pastebin.com/cVd8ryxG > > It seems that those 5 symbols are missing for amd64: > > 00000000000090d0 t _Znam > 00000000000090b0 t _ZnamRKSt9nothrow_t > 0000000000009220 t _Znwm > 00000000000093f0 t _ZnwmPv > 0000000000009110 t _ZnwmRKSt9nothrow_t > > Add them to Version.map like in r236177 and recompile > libsupc++ or world and try again rebuilding vbox > additions: > > > http://svnweb.freebsd.org/base/head/gnu/lib/libsupc%2B%2B/Version.map?r1=236177&r2=236176&pathrev=236177 > > -- > Bernhard Froehlich > http://www.bluelife.at/ > > > > On 05.06.2012 12:06, Bernhard Froehlich wrote: >> That was a good hint! It seems the newly added libsupc++ causes >> that problems because until very recently the new operator symbols >> were not included. They have been added on current as of r236177 >> >> http://svnweb.freebsd.org/base?view=revision&revision=236177 >> >> On 9-STABLE the situation is that libstdc++/libsupc++ was already >> MFCd but that fix from head for thew new operator wasn't yet. So >> it currently fails on 9-STABLE. According to David that fix for >> the new operator also seems to have no affect on amd64 so the >> symbols probably have a different name there. >> >> I've already talked to DES about that and we need some nm output >> of latest libsupc++ on HEAD / amd64 to find the symbol names >> and add them to the map. So who can provide the nm output? >> >> >> -- >> Bernhard Froehlich >> http://www.bluelife.at/ >> >> >> On 05.06.2012 10:44, David Morgan wrote: >>> On 10:13 Tue 05 Jun , Andriy Gapon wrote: >>>> on 05/06/2012 08:37 Bernhard Fröhlich said the following: >>>> > Shit. I have only seen that compile errors on head yet but was >>>> unable to find out what caused it. It seems it was MFCd now. Any >>>> hints are very appreciated. >>>> >>>> It looks like a C compiler (cc) is used to link C++ code. >>>> I think that adding -lstdc++ may fix the problem, but a better >>>> solution would be >>>> to use c++ instead of cc. >>>> >>> >>> That's correct - re-running the failing command with gcc gives the >>> same >>> error, with g++ it succeeds. If I recall correctly adding -lstdc++ >>> doesn't fix it. >>> >>> A change was made to Version.map for libsupc++ recently, which >>> apparently made this compile correctly on i386, but didn't solve >>> the >>> problem for me on amd64. >>> >>> >>>> > Creating a PR is probably worthless as I am usually the only one >>>> that looks at them. emulation@ covers a wider audience of people >>>> that care about vbox and are able to debug and fix bugs. Thanks for >>>> the report and getting my attention! >>>> > >>>> > >>>> > On Mo., 4. Jun. 2012 23:19:19 CEST, Kris Moore >>>> wrote: >>>> > >>>> >> Before I file a PR, is anybody else experiencing this with the >>>> latest VB >>>> >> on 9-STABLE? >>>> >> >>>> >> ------------------------- >>>> >> >>>> >> kBuild: Linking VBoxClient >>>> >> kBuild: Pass - Other Stuff >>>> >> kBuild: Pass - Staging >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >>>> >> In function `VBoxClient::GetClipboardService()': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: >>>> >> undefined reference to `operator new(unsigned long)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >>>> >> In function `~Service': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: >>>> >> undefined reference to `operator delete(void*)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >>>> >> In function `~ClipboardService': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: >>>> >> undefined reference to `operator delete(void*)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>>> >> In function `VBoxClient::GetSeamlessService()': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: >>>> >> undefined reference to `operator new(unsigned long)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>>> >> In function `~VBoxGuestThreadFunction': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/thread.h:33: >>>> >> undefined reference to `operator delete(void*)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>>> >> In function `~VBoxGuestSeamlessObserver': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-glue.h:26: >>>> >> undefined reference to `operator delete(void*)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>>> >> In function `VBoxGuestWinCleanup(VBoxGuestWinInfo*, void*)': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:81: >>>> >> undefined reference to `operator delete(void*)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>>> >> In function `~VBoxGuestSeamlessGuestThread': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:46: >>>> >> undefined reference to `operator delete(void*)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >>>> >> In function `~VBoxGuestSeamlessGuestObserver': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:111: >>>> >> undefined reference to `operator delete(void*)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o:/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.h:79 >>>> >> : more undefined references to `operator delete(void*)' follow >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o: >>>> >> In function `VBoxGuestWindowList::addWindow(unsigned long, >>>> bool, int, >>>> >> int, int, int, int, XRectangle*)': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: >>>> >> undefined reference to `operator new(unsigned long)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:135: >>>> >> undefined reference to `operator new(unsigned long)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: >>>> >> In function `VBoxClient::GetDisplayService()': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:243: >>>> >> undefined reference to `operator new(unsigned long)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o: >>>> >> In function `~DisplayService': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/display.cpp:218: >>>> >> undefined reference to `operator delete(void*)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: >>>> >> In function `VBoxClient::GetHostVersionService()': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:211: >>>> >> undefined reference to `operator new(unsigned long)' >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o: >>>> >> In function `~HostVersionService': >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/hostversion.cpp:35: >>>> >> undefined reference to `operator delete(void*)' >>>> >> kmk: *** >>>> >> >>>> [/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient] >>>> >> Error 1 >>>> >> The failing command: >>>> >> @cc -m64 -o >>>> ^^^^^^^^ >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd6 >>>> >> 4/release/obj/VBoxClient/main.o >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o >>>> >> /usr/ports/emulators/virtualbox-ose-addit >>>> >> >>>> ions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboa >>>> >> rd.o >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/s >>>> >> eamless-host.o >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ob >>>> >> j/VBoxClient/thread.o >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/ >>>> >> obj/VBoxClient/hostversion.o -L/usr/X11R6/lib32 >>>> -L/usr/X11R6/lib >>>> >> -L/usr/lib -L/usr/X11R6/lib -L/usr/local/lib -liconv >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/ >>>> >> RuntimeGuestR3.a >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a >>>> >> >>>> >> >>>> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/rel >>>> >> ease/lib/additions/RuntimeGuestR3.a -lX11 -lXrandr >>>> -lXt -lsupc++ >>>> >> -lgcc_eh -lXext -lXmu -lpthread -liconv >>>> *** Error code 2 >>>> >> >>>> >> Stop in /usr/ports/emulators/virtualbox-ose-additions. >>>> >>>> -- >>>> Andriy Gapon >>>> _______________________________________________ >>>> 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" >>> _______________________________________________ >>> 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" >> _______________________________________________ >> 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" > _______________________________________________ > 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 owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 17:05:05 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 430571065686 for ; Tue, 5 Jun 2012 17:05:05 +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 E02528FC18 for ; Tue, 5 Jun 2012 17:05:04 +0000 (UTC) Received: by vbmv11 with SMTP id v11so4004763vbm.13 for ; Tue, 05 Jun 2012 10:05:04 -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=tQBgXDI1Cl1TXAFHtbnQtLeMr1aJQ1g0JwlfWN/wugI=; b=or8Jp+l3eDY9I5VKmIsbkvkRuAGz6Z2zJKCaCO87ItIU8Zq4qlQL52NDOYjX63jq70 uXR650YD+16CD8EaNIA/e/AUS8SxtdOTpdA3YveQJW/YFlfCrN5npqkWHGsT0OmGgwlA TfOKX5J/biZmsvk/jW12UwZJP7s0mXnjXZzODFuj1Qh30DTwoAe1QNZQTGfMMkNhCzV9 jZ98w6NbzeJZir/EIzh0p7LnVFn93g4u6ZtpRSqaqgC96RsoahHDsyW73JXjhuT8WoBo iafeUQIOpw1hGs0clmQgMyKB/mOnbjk1GOCtRuG2c9LINd8EYwLPGgSNSeybwLMZLdno xY0A== MIME-Version: 1.0 Received: by 10.220.230.135 with SMTP id jm7mr17537574vcb.23.1338915904144; Tue, 05 Jun 2012 10:05:04 -0700 (PDT) Received: by 10.52.30.73 with HTTP; Tue, 5 Jun 2012 10:05:04 -0700 (PDT) In-Reply-To: References: Date: Tue, 5 Jun 2012 13:05:04 -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: 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: Tue, 05 Jun 2012 17:05:05 -0000 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 So looks like when there are multiple vms on a ipv6 system (we have 64bit FreeBSD 9.0) will get this problem. From owner-freebsd-emulation@FreeBSD.ORG Tue Jun 5 18:16:48 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 63581106566B for ; Tue, 5 Jun 2012 18:16:48 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 1226D8FC16 for ; Tue, 5 Jun 2012 18:16:48 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 15E20A; Tue, 5 Jun 2012 20:16:50 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 05 Jun 2012 20:16:46 +0200 From: Bernhard Froehlich To: Steve Tuts In-Reply-To: References: Message-ID: X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.7.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0202.4FCE4D0F.0001,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: freebsd-emulation@freebsd.org Subject: 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: Tue, 05 Jun 2012 18:16:48 -0000 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 > > 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. -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-emulation@FreeBSD.ORG Wed Jun 6 07:50:36 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 B36E5106566C for ; Wed, 6 Jun 2012 07:50:36 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 622D38FC12 for ; Wed, 6 Jun 2012 07:50:36 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 23948D; Wed, 6 Jun 2012 09:50:38 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 06 Jun 2012 09:50:35 +0200 From: Bernhard Froehlich To: Steve Tuts In-Reply-To: References: Message-ID: X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.7.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0207.4FCF0BCB.0151,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: freebsd-emulation@freebsd.org Subject: 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: Wed, 06 Jun 2012 07:50:36 -0000 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 >> >> 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 66282f58000c8863e104666c30cb67b1d5cbdee3 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 It looks promising so please test this patch if you can reproduce the crash. -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-emulation@FreeBSD.ORG Wed Jun 6 17:00:25 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 9CBB3106566C for ; Wed, 6 Jun 2012 17:00:25 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 879028FC17 for ; Wed, 6 Jun 2012 17:00:25 +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 q56H0Phg069886 for ; Wed, 6 Jun 2012 17:00:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q56H0P8C069883; Wed, 6 Jun 2012 17:00:25 GMT (envelope-from gnats) Date: Wed, 6 Jun 2012 17:00:25 GMT Message-Id: <201206061700.q56H0P8C069883@freefall.freebsd.org> To: freebsd-emulation@FreeBSD.org From: Chris Rees Cc: Subject: Re: ports/148097: [patch] X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Chris Rees List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 17:00:25 -0000 The following reply was made to PR ports/148097; it has been noted by GNATS. From: Chris Rees To: bug-followup@freebsd.org Cc: Subject: Re: ports/148097: [patch] Date: Wed, 6 Jun 2012 17:49:57 +0100 This IRC transcript from Freenode/##FreeBSD might be relevant. frag4: no, I am root under normal system frag4: The behaviour of the script is different when startet during boot. Don't forget to add linuxtest_enable="YES" to /etc/rc.conf fleximus: I'm unable to reproduce your problem. yes but you need to call like /compat/linux/bin/bash first er somethin? fleximus: please do procstat -f $$ in very same shell you run /bin/sh /usr/local/etc/rc.d/startscript frag4: It's the default /bin/csh for root from command line. The systems reboots at the moment, give you the other result in a second frag4: During boot it is /bin/sh. Anyway, if I call /bin/sh /usr/local/etc/rc.d/startscript it works fine frag4: The latter will also display /bin/sh. fleximus: well, I'm running 9.0 here and cannot reproduce this. Eithery way, I'm going home now, some good luck with debugging. :) fleximus: s/some/so/ frag4: This is also 9.0, but I must leave soon, too ;-( frag4: Thank you for your ideas oh, that might be the solution, I will test now: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/159646 and this one: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/148097 PR148097 is the workaround for me! Now I can go home. bye bye frag4: =) From owner-freebsd-emulation@FreeBSD.ORG Wed Jun 6 22:46:09 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 A41F41065672 for ; Wed, 6 Jun 2012 22:46:09 +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 52E678FC0C for ; Wed, 6 Jun 2012 22:46:09 +0000 (UTC) Received: by vbmv11 with SMTP id v11so5087207vbm.13 for ; Wed, 06 Jun 2012 15:46:07 -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=OjoOwnJRq2yy9W8Tq1p4NEqztNnGb2zi60mBHXEie9k=; b=h1AERWc2J7t6+reE5KmxWhPGhX6a64tMghYa0LOWcm4ozN5rxoW2snSQewN4YUtLSh XWpYKfTvKmfwoeeXIGZpc/oipaJxrSHy2VkvR05DIlYSZFWsoqIPZ1mnq8mrSpDP4gFj bm2xOUwOqrE3WPkSSuFmGIGKM7PScdyx6E7T0YFFVXzOH13hH7fMzutpFt29rSVKMyPK sSO1keD0m3rBCj7WaYQJwaADqReTOc3uN595Q2yVe2VJPK4u24t2eNXozyEjiFmqIH1F QmAKfV6U3OJi+JVeasx2C54Fzxs5yMwROrLU6HXybOer1BQKy+5Gi8SQrhaIMeFnx84d iwcA== MIME-Version: 1.0 Received: by 10.220.115.12 with SMTP id g12mr22501032vcq.44.1339022767125; Wed, 06 Jun 2012 15:46:07 -0700 (PDT) Received: by 10.52.30.73 with HTTP; Wed, 6 Jun 2012 15:46:07 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 Jun 2012 18:46:07 -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: 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: Wed, 06 Jun 2012 22:46:09 -0000 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 >>> >>> 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 > > > 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? From owner-freebsd-emulation@FreeBSD.ORG Wed Jun 6 23:08:00 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 036E3106566B for ; Wed, 6 Jun 2012 23:08:00 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 841E28FC12 for ; Wed, 6 Jun 2012 23:07:59 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so4548403wib.13 for ; Wed, 06 Jun 2012 16:07:53 -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 :cc:content-type:content-transfer-encoding; bh=MEUNzuFgJcizQDFG1+BbGfz6O7zEwF0ATFfJ6XR0SxA=; b=xHWD26dJ3SoggtqZFENOda6cD+Gtiss3FaBlAEC+Qip4zfv0M3p0bi2K1Qjv1uhu3Q tzAh/nfQAT3C2rob0H9zNVzfNwGHcBjXWH5z7PWFNaeCR+ZQgQINFjosLj5FhOVpaMuh yWqm3mMkjFfKo8ZvhqMlc5Ms42eoXYgL3SXHblXNrxCiYgH+qGGhryJWJyMNEHy4uKuK 2jdCQPmoWaCyjKkV554V/6GTllIY39hYE32VgeUtxrNc8vV0ufN2JN/sWS3jvb/HL6TY x9pShp6InrdbjxQuithoik1O5a2PCX3sUCCGkaNU4VMaCvCXT00TAWqZ2BXsIkegnqLN 7y6A== MIME-Version: 1.0 Received: by 10.216.194.93 with SMTP id l71mr2480279wen.169.1339024073143; Wed, 06 Jun 2012 16:07:53 -0700 (PDT) Received: by 10.223.155.4 with HTTP; Wed, 6 Jun 2012 16:07:52 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 Jun 2012 16:07:52 -0700 Message-ID: From: Kevin Oberman To: Steve Tuts Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-emulation@freebsd.org Subject: 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: Wed, 06 Jun 2012 23:08:00 -0000 On Wed, Jun 6, 2012 at 3:46 PM, Steve Tuts wrote: > On Wed, Jun 6, 2012 at 3:50 AM, Bernhard Froehlich wro= te: > >> 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: >>>> >>>> =A0On 2012-06-02 12:16, Steve Tuts wrote: >>>>> >>>>> =A0Hi, we have a Dell poweredge server with a dozen interfaces. =A0It= hosts >>>>>> a >>>>>> few guests of web app and email servers with VirtualBox-4.0.14. =A0T= he >>>>>> host >>>>>> and all guests are FreeBSD 9.0 64bit. =A0Each guest is bridged to a >>>>>> distinct >>>>>> interface. =A0The host and all guests are set to 10.0.0.0 network NA= T'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. =A0We can only >>>>>> connect >>>>>> to the host from outside the router. =A0We can also go to the consol= e of >>>>>> the >>>>>> guests (except the new guest), but from there we can't ping the gate= way >>>>>> 10.0.0.1 any more. =A0The new guest just froze. >>>>>> >>>>>> Furthermore, on the host we can see a vboxheadless process for each >>>>>> guest, >>>>>> including the new guest. =A0But we can not kill it, not even with "k= ill >>>>>> -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. =A0W= e >>>>>> also >>>>>> tried all the VBoxManager commands to poweroff/reset etc that new >>>>>> guest, >>>>>> but they all failed complaining that vm is in Aborted state. =A0We a= lso >>>>>> 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 t= hat >>>>>> new >>>>>> guest, then that vboxheadless process for that new guest disappeared >>>>>> (we >>>>>> attempted to kill it before that). =A0And 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 rebootin= g? >>>>>> 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 a= re >>>>> 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 >>>>> ______________________________****_________________ >>>>> >>>>> >>>>> =A0sorry, just realize my reply yesterday didn't go to the list, so a= m >>>> 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. =A0So upgradin= g 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 v= m >>>> will immediately Abort that vm. =A0This prevents us from adding new vm= s. >>>> 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 64= bit >>>> FreeBSD 9.0) will get this problem. >>>> >>> >>> Glad to hear that 4.1.16 helps for the networking problem. The VNC prob= lem >>> 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 downgradin= g >>> net/libvncserver to an earlier version (and rebuilding virtualbox) shou= ld >>> help until we come up with a proper fix. >>> >> >> You are right about the "Address already in use" problem and the patch f= or >> 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: =A0 Fri May 18 00:30:11 2012 -0700 >> =A0 =A0 libvncserver/sockets.c: do not segfault when listenSock/listen6S= ock =3D=3D >> -1 >> >> http://libvncserver.git.**sourceforge.net/git/gitweb.**cgi?p=3Dlibvncser= ver/ >> **libvncserver;a=3Dcommit;h=3D**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 > . =A0However, if I edit this file and do make clean, this patch is wiped = out > before I can do "make" out of it. =A0How 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/libvncse= rver' --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-emulation@FreeBSD.ORG Thu Jun 7 06:58:09 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 D354B1065677 for ; Thu, 7 Jun 2012 06:58:08 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 3F15A8FC15 for ; Thu, 7 Jun 2012 06:58:08 +0000 (UTC) Received: from [10.34.35.99] (89.144.192.75) by groupware.itac.at (Axigen) with (CAMELLIA256-SHA encrypted) ESMTPSA id 2C7039; Thu, 7 Jun 2012 08:58:03 +0200 From: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= To: Kevin Oberman , Steve Tuts X-Mailer: Modest 3.90.7 References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-ID: <1339052297.16686.1.camel@Nokia-N900-42-11> Date: Thu, 07 Jun 2012 08:58:17 +0200 Message-Id: <1339052297.16686.2.camel@Nokia-N900-42-11> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B020A.4FD050F8.003B,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: freebsd-emulation@freebsd.org Subject: Re: one virtualbox vm disrupts all vms and entire network X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2012 06:58:10 -0000 On Do.,  7. Jun. 2012 01:07:52 CEST, Kevin Oberman 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 > > > > > > > > > > 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 > > > > > > > > > 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. From owner-freebsd-emulation@FreeBSD.ORG Thu Jun 7 07:05:50 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 A923A106566B for ; Thu, 7 Jun 2012 07:05:50 +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 5210E8FC08 for ; Thu, 7 Jun 2012 07:05:50 +0000 (UTC) Received: by vcbfy7 with SMTP id fy7so169073vcb.13 for ; Thu, 07 Jun 2012 00:05:49 -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 :cc:content-type; bh=/strLcD6I6gLpxeYmK6RIJ+CE6tu2+y/Bdw9EYSr3nM=; b=ARrOgPDtstM7zZbHgIeWV9wudY13byOb+aziO0RpwTdCb5XbIMB/s7EcfqCHZtil+T 8eihCHKi5nsSU9k7jMVwdBjA+Tfqe1Eq4dqyWzsbN/mWKXzT15Ou0Pt7bxMNxWc6nfW9 lh5eJfhJcOEFByOMloGEinU6f1zOBOVSVaT7rJSeC7Da4AnHJ88Q0cN3n/5uoXmlLxgW AFq/7nRUEGYUje4IxxMY/DnihG+y3YBT+Qr+uoCWBjflrq0TEzmoDLg9UR5aBM1GuZfV eQmzZL2ISCq2RZ70BhdQVhF5Jo86XZDz+djCmlXNIpBRLjRsJnECE7SuU2ipNoRef82P v6LA== MIME-Version: 1.0 Received: by 10.52.29.69 with SMTP id i5mr838621vdh.84.1339052748937; Thu, 07 Jun 2012 00:05:48 -0700 (PDT) Received: by 10.52.30.73 with HTTP; Thu, 7 Jun 2012 00:05:48 -0700 (PDT) In-Reply-To: References: Date: Thu, 7 Jun 2012 03:05:48 -0400 Message-ID: From: Steve Tuts To: Kevin Oberman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-emulation@freebsd.org Subject: 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: Thu, 07 Jun 2012 07:05:50 -0000 On Wed, Jun 6, 2012 at 7:07 PM, Kevin Oberman 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 > > >>>> > >>>> 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' > -- > R. Kevin Oberman, Network Engineer > E-mail: kob6558@gmail.com > Thanks. Last night I realized we are using make :-) so I just did: cd /usr/ports/net/libvncserver/work/LibVNCServer-0.9.9 make cd /usr/ports/net/libvncserver pkg_delete virtualbox-ose-4.1.16_1 make reinstall cd /usr/ports/emulation/virtualbox-ose make reinstall Note I have quite a bunch of servers running. When I just kill one of the vm and then start it with vnc, I still get that message: rfbListenOnTCP6Port: error in bind IPv6 socket: Address already in use HOWEVER, now telnetting to that vm's vnc port woNOT kill it, and furthermore I can VNC to it now! I suspect that rfbListenOnTCP6Port error will disappear if I reboot the machine or kill all vms. Is this a valid test? From owner-freebsd-emulation@FreeBSD.ORG Thu Jun 7 07:54:52 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 4590D106566B for ; Thu, 7 Jun 2012 07:54:52 +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 E7A738FC08 for ; Thu, 7 Jun 2012 07:54:51 +0000 (UTC) Received: by vcbfy7 with SMTP id fy7so188849vcb.13 for ; Thu, 07 Jun 2012 00:54:51 -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=Emd2/Xj4ucLTg1+L/SnEHGIl7tzsLeePNI8KRoQxd98=; b=n/wccF+n7NIhLPpFORYRIBfazfeABNJ8AR50I7O4c8KTRXXDTaoxDGRRW+ZfRTi/WY IbzE7HZLXMVNG3I5bMucj4siCj9htGzSeLxDh6/kP1UNesou4yNGO0KTmWG38v5E+pZj ejKR+BniBH2ZvbG9cPhKXFCrkRWwrK2PlxTcXezTsA8mJM1xjjJ8LWM0bd15BRJ74mDh WJfTE9gt3vchYQqgCRdYESZKd9hyN5qAY50ndnO75YGo0WsQeh9aQbJ4UBPl2N8DAVrm Od7ow4OYPuwShI7aScZZCCuBZOnSce4zJYhvTFUnIK2AymN0oqx78J6m5RTkrD2IsZb3 teWw== MIME-Version: 1.0 Received: by 10.52.29.69 with SMTP id i5mr922517vdh.84.1339055691155; Thu, 07 Jun 2012 00:54:51 -0700 (PDT) Received: by 10.52.30.73 with HTTP; Thu, 7 Jun 2012 00:54:51 -0700 (PDT) In-Reply-To: <1339052297.16686.2.camel@Nokia-N900-42-11> References: <1339052297.16686.2.camel@Nokia-N900-42-11> Date: Thu, 7 Jun 2012 03:54:51 -0400 Message-ID: From: Steve Tuts To: freebsd-emulation@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 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: Thu, 07 Jun 2012 07:54:52 -0000 On Thu, Jun 7, 2012 at 2:58 AM, Bernhard Fr=F6hlich wro= te: > On Do., 7. Jun. 2012 01:07:52 CEST, Kevin Oberman > 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 bridge= d > > > > > > > > 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 us= e > > > > > > > > "kill -SIGCONT" first since the "ps" output has the "T" fla= g > > > > > > > > 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 virtualbo= x: > > > > > > whenever > > > > > > we try to vnc to any vm, that vm will go to Aborted state > > > > > > immediately. Actually, merely telnet from within the host to th= e > > > > > > vnc port of that vm will immediately Abort that vm. This > > > > > > prevents us from adding new vms. Also, when starting vm with vn= c > > > > > > 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 VN= C > > > > > 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 versio= n > > > > > (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. Probab= ly > > > > 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 =3D=3D -1 > > > > > > > > http://libvncserver.git.** > sourceforge.net/git/gitweb.**cgi?p=3Dlibvncserver/ > > > > **libvncserver;a=3Dcommit;h=3D**66282f5< > http://libvncserver.git.sourceforge.net/git/gitweb.cgi?p=3Dlibvncserver/l= ibvncserver;a=3Dcommit;h=3D66282f5 > > > > > > > > > > > > > > It looks promising so please test this patch if you can reproduce t= he > > > > 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 wipe= d > > > 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! From owner-freebsd-emulation@FreeBSD.ORG Thu Jun 7 08:29:13 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 BE2A21065742 for ; Thu, 7 Jun 2012 08:29:13 +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 AAC4D8FC16 for ; Thu, 7 Jun 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 q578TDtx063557 for ; Thu, 7 Jun 2012 08:29:13 GMT (envelope-from linimon@FreeBSD.org) Date: Thu, 7 Jun 2012 08:29:13 GMT Message-Id: <201206070829.q578TDtx063557@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: Thu, 07 Jun 2012 08:29:13 -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 Thu Jun 7 08:29:45 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 A014F1065678 for ; Thu, 7 Jun 2012 08:29:45 +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 8F1FD8FC23 for ; Thu, 7 Jun 2012 08:29:45 +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 q578TjZR067856 for ; Thu, 7 Jun 2012 08:29:45 GMT (envelope-from linimon@FreeBSD.org) Date: Thu, 7 Jun 2012 08:29:45 GMT Message-Id: <201206070829.q578TjZR067856@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: Thu, 07 Jun 2012 08:29:45 -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. From owner-freebsd-emulation@FreeBSD.ORG Thu Jun 7 19:56:23 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 A2E821065670 for ; Thu, 7 Jun 2012 19:56:23 +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 55DF88FC16 for ; Thu, 7 Jun 2012 19:56:23 +0000 (UTC) Received: by vcbfy7 with SMTP id fy7so640682vcb.13 for ; Thu, 07 Jun 2012 12:56:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=YmW/TJEiXLOqjhb0TBBg/hZfM4OWifql3O+kvrNxsIc=; b=H8dW5GCSh3fR8tsveWbyullxdZLUyg9af9si03JOaqrrZZukY22timjX+r+GmSYhPf SeqLefrdW7ZoxJkgtvcbPn/HUI83BbjZmjwdpR9Y4sR7cukV4YeNPu7vD+nSGvNX7PzA skoQXNFPK00XI2VAjq5xhc5dgaykyzLBaDEvqAtmlAlqiO3YAdfPwZCsA7CRyGouX4cW S0dCuF9Ye7wYNfgpZAH0ElYfNS+5mxwpdpVLp8GVoUSYlbGhZWe764ZUsrwxGLeE/6mb Ex6bjJ6fDYXQGeefxi8RblleYeQOKJbnFRabYiAA+2ro+lFhKHt5fP/iz5j972o8aTHj g6Dg== MIME-Version: 1.0 Received: by 10.52.174.52 with SMTP id bp20mr2767312vdc.29.1339098982686; Thu, 07 Jun 2012 12:56:22 -0700 (PDT) Received: by 10.52.30.73 with HTTP; Thu, 7 Jun 2012 12:56:22 -0700 (PDT) Date: Thu, 7 Jun 2012 15:56:22 -0400 Message-ID: From: Steve Tuts To: freebsd-emulation@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Still unresolved - 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: Thu, 07 Jun 2012 19:56:23 -0000 On Thu, Jun 7, 2012 at 3:54 AM, Steve Tuts wrote: > > > On Thu, Jun 7, 2012 at 2:58 AM, Bernhard Fr=F6hlich wr= ote: > >> On Do., 7. Jun. 2012 01:07:52 CEST, Kevin Oberman >> 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 bridg= ed >> > > > > > > > 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 th= e >> > > > > > > > console of the >> > > > > > > > guests (except the new guest), but from there we can't pin= g >> > > > > > > > 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 u= se >> > > > > > > > "kill -SIGCONT" first since the "ps" output has the "T" fl= ag >> > > > > > > > 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 stat= e. >> > > > > > > > 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 o= f >> > > > > > > > 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 lis= t, >> > > > > > > so am >> > > > > > re-sending with some updates. >> > > > > > >> > > > > > Yes, we upgraded all ports and fortunately everything went bac= k >> > > > > > and especially all vms has run peacefully for two days now. S= o >> > > > > > 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 t= he >> > > > > > vnc port of that vm will immediately Abort that vm. This >> > > > > > prevents us from adding new vms. Also, when starting vm with v= nc >> > > > > > port, we got this message: >> > > > > > >> > > > > > rfbListenOnTCP6Port: error in bind IPv6 socket: Address alread= y >> > > > > > 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 V= NC >> > > > > problem is also a known one but the mentioned patch does not wor= k >> > > > > at least for a few people. It seems the bug is somewhere in >> > > > > libvncserver so downgrading net/libvncserver to an earlier versi= on >> > > > > (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 =3D=3D -1 >> > > > >> > > > http://libvncserver.git.** >> sourceforge.net/git/gitweb.**cgi?p=3Dlibvncserver/ >> > > > **libvncserver;a=3Dcommit;h=3D**66282f5< >> http://libvncserver.git.sourceforge.net/git/gitweb.cgi?p=3Dlibvncserver/= libvncserver;a=3Dcommit;h=3D66282f5 >> > >> > > > >> > > > >> > > > 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 wip= ed >> > > out before I can do "make" out of it. How to apply this patch in th= e >> > > 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 inf= o, > 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 jtlgjkrfyh9tpgjklfd= s 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. From owner-freebsd-emulation@FreeBSD.ORG Thu Jun 7 20:15:14 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 A27CF106567A for ; Thu, 7 Jun 2012 20:15:12 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 927328FC08 for ; Thu, 7 Jun 2012 20:15:12 +0000 (UTC) Received: from outgoing.leidinger.net (p4FC4380C.dip.t-dialin.net [79.196.56.12]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id DAD1884473A; Thu, 7 Jun 2012 22:14:54 +0200 (CEST) Received: from unknown (IO.Leidinger.net [192.168.1.12]) by outgoing.leidinger.net (Postfix) with ESMTPS id 336C82B99; Thu, 7 Jun 2012 22:14:52 +0200 (CEST) Date: Thu, 7 Jun 2012 22:14:49 +0200 From: Alexander Leidinger To: freebsd-emulation@freebsd.org Message-ID: <20120607221449.00007473@unknown> In-Reply-To: <20120605022102.1851A11F823@ketas-laptop.mydomain> References: <20120605022102.1851A11F823@ketas-laptop.mydomain> X-Mailer: Claws Mail 3.7.10cvs42 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: DAD1884473A.A1766 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-0.745, required 6, autolearn=disabled, ALL_TRUSTED -1.00, AWL 0.27, T_RP_MATCHES_RCVD -0.01) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1339704897.2773@yCL8Zm7HLpD3HznIjDC2pQ X-EBL-Spam-Status: No Cc: Sulev-Madis 'ketas' Silber Subject: Re: FreeBSD Ports conflicts checker 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, 07 Jun 2012 20:15:14 -0000 On Tue, 5 Jun 2012 05:10:41 +0300 (EEST) "Sulev-Madis 'ketas' Silber" wrote: > HTML version of this report is here: > http://ketas.si.pri.ee/ports-conflicts/emulation@FreeBSD.org > > For port audio/linux-f10-alsa-lib suggesting new CONFLICTS > alsa-lib-[0-9]* because of overlapping files lib/libasound.so.2 (also > used by audio/alsa-lib) I take this as an example, it's not the only one: This is a false positive. You need to check the PREFIX of each port, and only if the prefix is the same (maybe via a call to realpath) you can say that you have a conflict. This is a linux infrastructure port and it installs into /compat/linux, not to /usr/local. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-emulation@FreeBSD.ORG Sat Jun 9 10:01:37 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 CAC141065674; Sat, 9 Jun 2012 10:01:37 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 7998B8FC1D; Sat, 9 Jun 2012 10:01:37 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 3A8F8E; Sat, 9 Jun 2012 12:01:41 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 09 Jun 2012 12:01:36 +0200 From: Bernhard Froehlich To: , Message-ID: <9061ccbe3ec04242959d28e274402812@bluelife.at> X-Sender: decke@FreeBSD.org User-Agent: Roundcube Webmail/0.7.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B020D.4FD31F00.019D,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: Subject: VirtualBox on FreeBSD is looking for you! 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: Sat, 09 Jun 2012 10:01:38 -0000 Hi VirtualBox users! We are again at the point where I am kindly asking if someone is interested to help with the VirtualBox on FreeBSD work. We started with an active team of around 3 people but since about one year I ended up being a lonely ranger. Maintaining such a beast/high profile port by a single person is not possible for a longer period so we should really try to form a team to improve the situation. Additionally I started working on redports.org which requires more and more time so I cannot dedicate all my work to virtualbox. The situation of the port right now is not bad but I always end up fire fighting and only concentrate on serious problems due to the limited time I have. So it happens that people send bugreports and patches for virtualbox and don't get a response for weeks if at all. A lot of bugs that we have since day one are still present and the list of items that we should seriously do is getting longer. Many things of them are userland and porting stuff but there are also a lot of things to do in the kernel modules. Andriy Gapon has rewritten the r0 memory allocation stuff which significantly improved the situation in that area but the networking kernel modules are still in a bad shape. There are various known bugs (performance problems, instabilities, ...) in that area so it would be great if someone with networking expertise could have a look at the code. The USB stuff needs some love too. It is there but only works for a few special combinations of Device and Guest OS. Since VirtualBox 4.1 there is experimental support for PCI Passthrough so if we want that we need some Kernel API for the Intel/AMD IOMMU. I think the IOMMU code has already been written for BeHyVe so we need someone who puts all the stuff together and wants to find out how to integrate that in the kernel and vbox. The vbox developers offered their help on that but they need a Kernel API before we can start talking about it. So what is it that the virtualbox team needs to do? - regulary test latest SVN sources to find new problems early (build, runtime testing, create build fixes) - maintain all 8 ports (changes in CURRENT or other port updates keep breaking virtualbox around once per month) - update ports to new bugfix releases - review patches from the community and send them upstream then nag vbox developers to get them committed - help users to diagnose problems (help debugging, get stacktraces, collect information, give hints) - further porting efforts (coordinate and probably do it yourself) - optionsng adaptions - FreeBSD installer for the vbox additions to be able to build a VBoxAdditions.iso with FreeBSD support - implement vboxsf support (Shared Folders) - PCI Passthrough support - USB support (needs fixing) - Networking support (needs fixing) It is unrealistic that one single person can do a majority of these things so we seriously need a few people from different areas to improve the situation. Be it kernel developers, ports people or just power users that can help testing and diagnosing bugs. If you have an interest in VirtualBox on FreeBSD and a few spare cycles please get in contact with us (me?) to coordinate the further steps. I will do my best to help answering questions and help you with your first steps in vbox land. Don't worry if you think you are not experienced enough for the task. We all started that way and you get the chance to learn a lot - it just needs some time to get used to it. I have also created a dedicated VirtualBox on FreeBSD channel on freenode: #freebsd-vbox so you're welcome to join us! -- Bernhard Froehlich http://www.bluelife.at/