From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 9 11:06:59 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 68069106566C for ; Mon, 9 Jul 2012 11:06:59 +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 395AC8FC16 for ; Mon, 9 Jul 2012 11:06:59 +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 q69B6xPN075271 for ; Mon, 9 Jul 2012 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q69B6wm4075269 for emulation@FreeBSD.org; Mon, 9 Jul 2012 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Jul 2012 11:06:58 GMT Message-Id: <201207091106.q69B6wm4075269@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: emulation@FreeBSD.org Cc: Subject: Current problem reports assigned to emulation@FreeBSD.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 11:06:59 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/169702 emulation [patch] graphics/linux-f10-tiff: fix packing list 1 problem total. From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 9 11:07:08 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 384CC1065672 for ; Mon, 9 Jul 2012 11:07:08 +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 084DC8FC1B for ; Mon, 9 Jul 2012 11:07:08 +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 q69B77MS075390 for ; Mon, 9 Jul 2012 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q69B778U075388 for freebsd-emulation@FreeBSD.org; Mon, 9 Jul 2012 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Jul 2012 11:07:07 GMT Message-Id: <201207091107.q69B778U075388@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, 09 Jul 2012 11:07:08 -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 Jul 9 11:33:24 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 E3DEA106566B; Mon, 9 Jul 2012 11:33:24 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4DEC48FC0A; Mon, 9 Jul 2012 11:33:24 +0000 (UTC) Received: by weyx56 with SMTP id x56so26842wey.13 for ; Mon, 09 Jul 2012 04:33:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:user-agent:cc:mime-version:content-type :content-transfer-encoding:message-id; bh=v9f1VubfGvWnVETv6NK6nfFxLdM+zFhF6v+ZjKdw1UA=; b=DE4u+7umUdxjv0INEJu0Pz94dzNZRXTHJ6aT9uym17BtHn7rVIt7P9Xn5PNPQpWpBh syAsvwVRtaU4auwNsW8gQxJ1iGhgSQ5deTIyyEMVMVhKzW7FhyuDvq6Z6TqN74NsJA5r Hz/YFFqzdT8gEu7Tg4ZYZQnuEcY7Xsy3BpCE4NkFeRYF1Lq3Qjs5QdVQyJmG5vAMxU/N 90TVokXKRbLWXb03ITTKo/eIuHZJXJXOvseeUVYHCCmiwaHYL0rNXSqWx6CX93bccfox kZAX5EnKqsQI125S99lgaZ2YH4R6ush1ebDQYddUz/2GJpaMfvdcz3H+i2bsuaE6iEXv DBIA== Received: by 10.216.238.27 with SMTP id z27mr15404349weq.81.1341833603333; Mon, 09 Jul 2012 04:33:23 -0700 (PDT) Received: from dragon.dg (41-135-0-78.dsl.mweb.co.za. [41.135.0.78]) by mx.google.com with ESMTPS id t8sm22976493wiy.3.2012.07.09.04.33.16 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 Jul 2012 04:33:19 -0700 (PDT) From: David Naylor To: freebsd-ports@freebsd.org Date: Mon, 9 Jul 2012 13:33:10 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-STABLE; KDE/4.8.4; amd64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4645704.TMreJX1oYD"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201207091333.13444.naylor.b.david@gmail.com> Cc: freebsd-emulation@freebsd.org Subject: Wine-fbsd64 updated to 1.5.8 (32bit Wine for 64bit FreeBSD) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 11:33:25 -0000 --nextPart4645704.TMreJX1oYD Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Packages [1] for wine-fbsd64-1.5.8 have been uploaded to mediafire [2]. Th= e=20 packages for FreeBSD 10 use the pkgng* [3] format. =20 There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users= ). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.8,1.tbz) =3D=20 bc57b6b573816d24837c9171e38cdfaf MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.8,1.txz) =3D=20 4c06fd3e68c43c977449ab9f824f69dd MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.8,1.txz) =3D=20 34cce0d89ef9d3db47f7699a3769a6cd [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh * pkgng support for nVidia patching should be working properly and using a= =20 mixed mode between pkgng and pkg also works --nextPart4645704.TMreJX1oYD Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAk/6wXkACgkQUaaFgP9pFrLyMACghNvocGxYl8q7IH3DVT0nx8na cwwAoIBULgfrwE4jBeDCKBTVz601jDUp =qqic -----END PGP SIGNATURE----- --nextPart4645704.TMreJX1oYD-- From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 9 13:11:43 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 3C0A0106564A for ; Mon, 9 Jul 2012 13:11:43 +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 D28258FC08 for ; Mon, 9 Jul 2012 13:11:42 +0000 (UTC) Received: by vcbfy7 with SMTP id fy7so8865894vcb.13 for ; Mon, 09 Jul 2012 06:11:42 -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=HpkAuk7NUGFoT9c804gumZZJkZWTQgThvDfCegmBPZ8=; b=f3XvzI6Z9QiR1CbSGOxI6i8/UGnZIhCdz9K32aVrbt/1QUqkwnmc7U7JXd3SBv3L0Q JEubAMv1onMksOY1pUHH3zi1e/LWezOVOCxzUJBeF75TQGXlt1fhlUiJ+q9Mz/+OJ8KU MzbWWq8RxRNIz8nA624z9XFFm+7GKRnxt39v6j3zS0+g1kdo7S8/3pCRhSL2WBT68zpK INKuxt5E9loynJ2uSlXIJRJqbVQcl/CJ10KuHTHqQdDNfPwKKSKs3u3edCGVBB5Y6tBj zIMlRcqjtPk+qnBNE08mNgtw/d9l2xaE3eBOKXWzxMSuRWo7NE/iSGvdMW0tG4zWD0nk U0hw== MIME-Version: 1.0 Received: by 10.220.142.9 with SMTP id o9mr19019873vcu.51.1341839502099; Mon, 09 Jul 2012 06:11:42 -0700 (PDT) Received: by 10.52.167.136 with HTTP; Mon, 9 Jul 2012 06:11:42 -0700 (PDT) In-Reply-To: <20120612222437.GB14487@in-addr.com> References: <20120612222437.GB14487@in-addr.com> Date: Mon, 9 Jul 2012 09:11:42 -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: 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: Mon, 09 Jul 2012 13:11:43 -0000 On Tue, Jun 12, 2012 at 6:24 PM, Gary Palmer wrote: > On Thu, Jun 07, 2012 at 03:56:22PM -0400, Steve Tuts wrote: > > On Thu, Jun 7, 2012 at 3:54 AM, Steve Tuts wrote: > > > > > > > > > > > On Thu, Jun 7, 2012 at 2:58 AM, Bernhard Fr?hlich >wrote: > > > > > >> On Do., 7. Jun. 2012 01:07:52 CEST, Kevin Oberman < > kob6558@gmail.com> > > >> wrote: > > >> > > >> > On Wed, Jun 6, 2012 at 3:46 PM, Steve Tuts > wrote: > > >> > > On Wed, Jun 6, 2012 at 3:50 AM, Bernhard Froehlich > > >> > > wrote: > > >> > > > > >> > > > On 05.06.2012 20:16, Bernhard Froehlich wrote: > > >> > > > > > >> > > > > On 05.06.2012 19:05, Steve Tuts wrote: > > >> > > > > > > >> > > > > > On Mon, Jun 4, 2012 at 4:11 PM, Rusty Nejdl > > >> > > > > > wrote: > > >> > > > > > > > >> > > > > > On 2012-06-02 12:16, Steve Tuts wrote: > > >> > > > > > > > > >> > > > > > > Hi, we have a Dell poweredge server with a dozen > interfaces. > > >> > > > > > > It hosts > > >> > > > > > > > a > > >> > > > > > > > few guests of web app and email servers with > > >> > > > > > > > VirtualBox-4.0.14. The host > > >> > > > > > > > and all guests are FreeBSD 9.0 64bit. Each guest is > bridged > > >> > > > > > > > to a distinct > > >> > > > > > > > interface. The host and all guests are set to 10.0.0.0 > > >> > > > > > > > network NAT'ed to > > >> > > > > > > > a > > >> > > > > > > > cicso router. > > >> > > > > > > > > > >> > > > > > > > This runs well for a couple months, until we added a new > > >> > > > > > > > guest recently. > > >> > > > > > > > Every few hours, none of the guests can be connected. > We > > >> > > > > > > > can only connect > > >> > > > > > > > to the host from outside the router. We can also go to > the > > >> > > > > > > > console of the > > >> > > > > > > > guests (except the new guest), but from there we can't > ping > > >> > > > > > > > the gateway 10.0.0.1 any more. The new guest just > froze. > > >> > > > > > > > > > >> > > > > > > > Furthermore, on the host we can see a vboxheadless > process > > >> > > > > > > > for each guest, > > >> > > > > > > > including the new guest. But we can not kill it, not > even > > >> > > > > > > > with "kill -9". > > >> > > > > > > > We looked around the web and someone suggested we > should use > > >> > > > > > > > "kill -SIGCONT" first since the "ps" output has the "T" > flag > > >> > > > > > > > for that vboxheadless process for that new guest, but > that > > >> > > > > > > > doesn't help. We also > > >> > > > > > > > tried all the VBoxManager commands to poweroff/reset etc > > >> > > > > > > > that new guest, > > >> > > > > > > > but they all failed complaining that vm is in Aborted > state. > > >> > > > > > > > We also tried > > >> > > > > > > > VBoxManager commands to disconnect the network cable for > > >> > > > > > > > that new guest, > > >> > > > > > > > it > > >> > > > > > > > didn't complain, but there was no effect. > > >> > > > > > > > > > >> > > > > > > > For a couple times, on the host we disabled the > interface > > >> > > > > > > > bridging that new > > >> > > > > > > > guest, then that vboxheadless process for that new guest > > >> > > > > > > > disappeared (we > > >> > > > > > > > attempted to kill it before that). And immediately all > > >> > > > > > > > other vms regained > > >> > > > > > > > connection back to normal. > > >> > > > > > > > > > >> > > > > > > > But there is one time even the above didn't help - the > > >> > > > > > > > vboxheadless process > > >> > > > > > > > for that new guest stubbonly remains, and we had to > reboot > > >> > > > > > > > the host. > > >> > > > > > > > > > >> > > > > > > > This is already a production server, so we can't upgrade > > >> > > > > > > > virtualbox to the > > >> > > > > > > > latest version until we obtain a test server. > > >> > > > > > > > > > >> > > > > > > > Would you advise: > > >> > > > > > > > > > >> > > > > > > > 1. is there any other way to kill that new guest > instead of > > >> > > > > > > > rebooting? 2. what might cause the problem? > > >> > > > > > > > 3. what setting and test I can do to analyze this > problem? > > >> > > > > > > > ______________________________****_________________ > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > I haven't seen any comments on this and don't want you to > > >> > > > > > > think you are being ignored but I haven't seen this but > also, > > >> > > > > > > the 4.0 branch was buggier > > >> > > > > > > for me than the 4.1 releases so yeah, upgrading is > probably > > >> > > > > > > what you are looking at. > > >> > > > > > > > > >> > > > > > > Rusty Nejdl > > >> > > > > > > ______________________________****_________________ > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > sorry, just realize my reply yesterday didn't go to the > list, > > >> > > > > > > so am > > >> > > > > > re-sending with some updates. > > >> > > > > > > > >> > > > > > Yes, we upgraded all ports and fortunately everything went > back > > >> > > > > > and especially all vms has run peacefully for two days now. > So > > >> > > > > > upgrading to the latest virtualbox 4.1.16 solved that > problem. > > >> > > > > > > > >> > > > > > But now we got a new problem with this new version of > > >> virtualbox: > > >> > > > > > whenever > > >> > > > > > we try to vnc to any vm, that vm will go to Aborted state > > >> > > > > > immediately. Actually, merely telnet from within the host > to the > > >> > > > > > vnc port of that vm will immediately Abort that vm. This > > >> > > > > > prevents us from adding new vms. Also, when starting vm > with vnc > > >> > > > > > port, we got this message: > > >> > > > > > > > >> > > > > > rfbListenOnTCP6Port: error in bind IPv6 socket: Address > already > > >> > > > > > in use > > >> > > > > > > > >> > > > > > , which we found someone else provided a patch at > > >> > > > > > > > >> http://permalink.gmane.org/**gmane.os.freebsd.devel.**emulation/10237 > < > > >> http://permalink.gmane.org/gmane.os.freebsd.devel.emulation/10237> > > >> > > > > > > > >> > > > > > So looks like when there are multiple vms on a ipv6 system > (we > > >> > > > > > have 64bit FreeBSD 9.0) will get this problem. > > >> > > > > > > > >> > > > > > > >> > > > > Glad to hear that 4.1.16 helps for the networking problem. > The VNC > > >> > > > > problem is also a known one but the mentioned patch does not > work > > >> > > > > at least for a few people. It seems the bug is somewhere in > > >> > > > > libvncserver so downgrading net/libvncserver to an earlier > version > > >> > > > > (and rebuilding virtualbox) should help until we come up with > a > > >> > > > > proper fix. > > >> > > > > > > >> > > > > > >> > > > You are right about the "Address already in use" problem and the > > >> > > > patch for it so I will commit the fix in a few moments. > > >> > > > > > >> > > > I have also tried to reproduce the VNC crash but I couldn't. > > >> Probably > > >> > > > because > > >> > > > my system is IPv6 enabled. flo@ has seen the same crash and > has no > > >> > > > IPv6 in his kernel which lead him to find this commit in > > >> > > > libvncserver: > > >> > > > > > >> > > > > > >> > > > commit 66282f58000c8863e104666c30cb67**b1d5cbdee3 > > >> > > > Author: Kyle J. McKay > > >> > > > Date: Fri May 18 00:30:11 2012 -0700 > > >> > > > libvncserver/sockets.c: do not segfault when > > >> > > > listenSock/listen6Sock == -1 > > >> > > > > > >> > > > http://libvncserver.git.** > > >> sourceforge.net/git/gitweb.**cgi?p=libvncserver/ > > >> > > > **libvncserver;a=commit;h=**66282f5< > > >> > http://libvncserver.git.sourceforge.net/git/gitweb.cgi?p=libvncserver/libvncserver;a=commit;h=66282f5 > > >> > > > >> > > > > > >> > > > > > >> > > > It looks promising so please test this patch if you can > reproduce > > >> the > > >> > > > crash. > > >> > > > > > >> > > > > > >> > > > -- > > >> > > > Bernhard Froehlich > > >> > > > http://www.bluelife.at/ > > >> > > > > > >> > > > > >> > > Sorry, I tried to try this patch, but couldn't figure out how to > do > > >> > > that. I use ports to compile everything, and can see the file is > at > > >> > > > > >> > /usr/ports/net/libvncserver/work/LibVNCServer-0.9.9/libvncserver/sockets.c > > >> > > . However, if I edit this file and do make clean, this patch is > wiped > > >> > > out before I can do "make" out of it. How to apply this patch in > the > > >> > > ports? > > >> > > > >> > To apply patches to ports: > > >> > # make clean > > >> > # make patch > > >> > > > >> > # make > > >> > # make deinstall > > >> > # make reinstall > > >> > > > >> > Note that the final two steps assume a version of the port is > already > > >> > installed. If not: 'make install' > > >> > I you use portmaster, after applying the patch: 'portmaster -C > > >> > net/libvncserver' -- > > >> > > >> flo has already committed the patch to net/libvncserver so I guess it > > >> fixes the problem. Please update your portstree and verify that it > works > > >> fine. > > >> > > > > > > I confirmed after upgrading all ports and noticing libvncserver > upgraded > > > to 0.99_1 and reboot, then I can vnc to the vms now. Also, starting > vms > > > with vnc doesn't have that error now, instead it issues the following > info, > > > so all problem are solved. > > > > > > 07/06/2012 03:49:14 Listening for VNC connections on TCP port 5903 > > > 07/06/2012 03:49:14 Listening for VNC connections on TCP6 port 5903 > > > > > > Thanks everyone for your great help! > > > > > > > Unfortunately, seems that the original problem of one vm disrupts all vms > > and entire network appears to remain, albeit to less scope. After > running > > on virtualbox-ose-4.1.16_1 and libvncserver-0.9.9_1 for 12 hours, all vms > > lost connection again. Also, phpvirtualbox stopped responding, and > > attempts to restart vboxwebsrv hanged. And trying to kill (-9) the > > vboxwebsrv process won't work. The following was the output of "ps > > aux|grep -i box" at that time: > > > > root 3322 78.7 16.9 4482936 4248180 ?? Is 3:42AM 126:00.53 > > /usr/local/bin/VBoxHeadless --startvm vm1 > > root 3377 0.2 4.3 1286200 1078728 ?? Is 3:42AM 15:39.40 > > /usr/local/bin/VBoxHeadless --startvm vm2 > > root 3388 0.1 4.3 1297592 1084676 ?? Is 3:42AM 15:06.97 > > /usr/local/bin/VBoxHeadless --startvm vm7 -n -m 5907 -o > jtlgjkrfyh9tpgjklfds > > root 2453 0.0 0.0 141684 7156 ?? Ts 3:38AM 4:14.09 > > /usr/local/bin/vboxwebsrv > > root 2478 0.0 0.0 45288 2528 ?? S 3:38AM 1:29.99 > > /usr/local/lib/virtualbox/VBoxXPCOMIPCD > > root 2494 0.0 0.0 121848 5380 ?? S 3:38AM 3:13.96 > > /usr/local/lib/virtualbox/VBoxSVC --auto-shutdown > > root 3333 0.0 4.3 1294712 1079608 ?? Is 3:42AM 19:35.09 > > /usr/local/bin/VBoxHeadless --startvm vm3 > > root 3355 0.0 4.3 1290424 1079332 ?? Is 3:42AM 16:43.05 > > /usr/local/bin/VBoxHeadless --startvm vm5 > > root 3366 0.0 8.5 2351436 2140076 ?? Is 3:42AM 17:32.35 > > /usr/local/bin/VBoxHeadless --startvm vm6 > > root 3598 0.0 4.3 1294520 1078664 ?? Ds 3:50AM 15:01.04 > > /usr/local/bin/VBoxHeadless --startvm vm4 -n -m 5904 -o > > u679y0uojlkdfsgkjtfds > > > > You can see the vboxwebsrv process has the "T" flag there, and the > > vboxheadless process for vm4 has "D" flag there. Both of such processes > I > > can never kill them, not even with "kill -9". So on the host I disabled > > the interface bridged to vm4 and restarted network, and fortunately both > > the vm4 and the vboxwebsrv processed disappeared. And at that point all > > other vms regained network. > > > > There may be one hope that the "troublemaker" may be limited to one of > the > > vms that started with vnc, although there was no vnc connection at that > > time, and the other vm with vnc was fine. And this is just a hopeful > guess. > > > > Also I found no log or error message related to virtualbox in any log > > file. The VBoxSVC.log only had some information when started but never > > since. > > If this is still a problem then > > ps alxww | grep -i box > > may be more helpful as it will show the wait channel of processes stuck > in the kernel. > > Gary > We avoided this problem by running all vms without vnc. But forgot this problem and left one vm on with vnc, together with the other few running vms yesterday, and hit this problem again on virtualbox 4.1.16. Only the old trick of turning off the host interface corresponding to the vm with vnc and then restarting host network got us out of the problem. We then upgraded virtualbox to 4.1.18, turning off all vms, wait until "ps aux|grep -i box" reported nothing, then started all vms. And let no vm with vnc running. Still the problem hit us again. Here is the output of " ps alxww | grep -i box" as you suggested: 1011 42725 1 0 20 0 1289796 1081064 IPRT S Is ?? 30:53.24 VBoxHeadless --startvm vm5 after "kill -9 42725", the line changed to 1011 42725 1 0 20 0 1289796 1081064 keglim Ts ?? 30:53.24 VBoxHeadless --startvm vm5 after "kill -9" for another vm, the line changed to something like 1011 42754 1 0 20 0 1289796 1081064 - Ts ?? 30:53.24 VBoxHeadless --startvm vm7 and controlvm command don't work, and these command stuck there themselves. The following are their outputs: 0 89572 79180 0 21 0 44708 1644 select I+ v6 0:00.01 VBoxManage controlvm projects_outside acpipowerbutton 0 89605 89586 0 21 0 44708 2196 select I+ v7 0:00.01 VBoxManage controlvm projects_outside poweroff We now rebooted the host, and left no vm with vnc running. From owner-freebsd-emulation@FreeBSD.ORG Fri Jul 13 17:47: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 82CCF106566C; Fri, 13 Jul 2012 17:47:24 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id 3BFCD8FC08; Fri, 13 Jul 2012 17:47:24 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id 4A35E1E0071A; Fri, 13 Jul 2012 19:47:23 +0200 (CEST) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.4/8.14.4) with ESMTP id q6DHOwr9022384; Fri, 13 Jul 2012 19:24:58 +0200 (CEST) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.4/8.14.3/Submit) id q6DHOwvD022383; Fri, 13 Jul 2012 19:24:58 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Fri, 13 Jul 2012 19:24:58 +0200 To: freebsd-arm@freebsd.org, freebsd-emulation@freebsd.org Message-ID: <20120713172458.GA21987@triton8.kn-bremen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: cognet@freebsd.org Subject: Progress with qemu arm-bsd-user... X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 17:47:24 -0000 Hi! I know people here would like to be able to run FreeBSD/arm target executables on x86 hosts like Linux users can using qemu linux-user, and this is the first step: I fixed cognet's arm-bsd-user patches, http://www.ci0.org/qemu-bapt.tar.gz to run a static echo executable which he also built: http://www.ci0.org/arm-binaries-2nox.tar.gz so now probably only syscall handling and fixes for threading are still missing, the same as for the other bsd-user targets. Adding handling code for the missing syscalls should be mostly mechanic (the main part of this is in /usr/ports/emulators/qemu-devel/work/qemu-*/bsd-user/syscall.c), and cognet thinks at least for armv6 the threading emulation can be more or less copied from linux-user too... Soo, anyone wants to help? :) The patch against the current emulators/qemu-devel port is here: http://people.freebsd.org/~nox/tmp/qemu-devel-1.1.1-arm-bsd-user-001.patch To run a static arm executable do like: qemu-arm -bsd freebsd -strace -d in_asm,out_asm,cpu arm-binaries/echo foo bar (this can also be invoked from the port's work dir as work/qemu-1.1.1/arm-bsd-user/qemu-arm ) - and -strace prints the sycalls and -d in_asm,out_asm,cpu logs the target- and the translated code as well as the emulated cpu state in /tmp/qemu.log. qemu also has a builtin gdbstub so you can also connect a cross gdb: qemu-arm -bsd freebsd -strace -d in_asm,out_asm,cpu -g 1234 arm-binaries/echo foo bar (gdb) target remote 127.1:1234 As always with patching code in ports if you want to only rebuild the changed parts instead of the whole port from scratch you can patch away below the port's work/ dir and run: rm work/.build_done* make (but don't forget to save your changes before doing make clean. :) Thanx! Juergen From owner-freebsd-emulation@FreeBSD.ORG Fri Jul 13 20:34:18 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 C50FF106566B for ; Fri, 13 Jul 2012 20:34:18 +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 7A4A58FC15 for ; Fri, 13 Jul 2012 20:34:18 +0000 (UTC) Received: by vcbf1 with SMTP id f1so3071166vcb.13 for ; Fri, 13 Jul 2012 13:34:12 -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=3iy9QJi1qOY0jK7J1/QsMX/I252RTjULgf7Q+hM3XZw=; b=qkeGDb754Q7iQKznzd+Q1Ttp0XygZpUm5uLIl4z1FCna2oEO88kGH8mf9S18pHdQL/ SCibtn/SbAasgwOsQqGfM8dkM8MNGHX/NSTk0oTFbSnUYTeziHHMoTUqxYZ51Sb88jNa ZCCM6QZOqHlypjvakGvTPEb71y7Y5a+pkP4fxw7qJtdNWUFEtBJ0Zgnh0ZQFErs3LFlU MjidEDFZsPs95onCfbg992FZDa7HNaIt/UrRA2BFCHsm/cZwmdretENgDRlmd3IwuvMj L78nIeeSvykCLmdE7XqD79a3A1jhRtsEeuP3hl5av3JlJFP1MEfp4iZVHTVp6ew1NKFY v7Gg== MIME-Version: 1.0 Received: by 10.220.106.135 with SMTP id x7mr1259693vco.28.1342211652381; Fri, 13 Jul 2012 13:34:12 -0700 (PDT) Received: by 10.52.115.134 with HTTP; Fri, 13 Jul 2012 13:34:12 -0700 (PDT) Date: Fri, 13 Jul 2012 16:34:12 -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: become worse now - Re: one virtualbox vm disrupts all vms and entire network X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 20:34:18 -0000 On Mon, Jul 9, 2012 at 9:11 AM, Steve Tuts wrote: > > > On Tue, Jun 12, 2012 at 6:24 PM, Gary Palmer wrote: > >> On Thu, Jun 07, 2012 at 03:56:22PM -0400, Steve Tuts wrote: >> > On Thu, Jun 7, 2012 at 3:54 AM, Steve Tuts wrote: >> > >> > > >> > > >> > > On Thu, Jun 7, 2012 at 2:58 AM, Bernhard Fr?hlich > >wrote: >> > > >> > >> On Do., 7. Jun. 2012 01:07:52 CEST, Kevin Oberman < >> kob6558@gmail.com> >> > >> wrote: >> > >> >> > >> > On Wed, Jun 6, 2012 at 3:46 PM, Steve Tuts >> wrote: >> > >> > > On Wed, Jun 6, 2012 at 3:50 AM, Bernhard Froehlich >> > >> > > wrote: >> > >> > > >> > >> > > > On 05.06.2012 20:16, Bernhard Froehlich wrote: >> > >> > > > >> > >> > > > > On 05.06.2012 19:05, Steve Tuts wrote: >> > >> > > > > >> > >> > > > > > On Mon, Jun 4, 2012 at 4:11 PM, Rusty Nejdl >> > >> > > > > > wrote: >> > >> > > > > > >> > >> > > > > > On 2012-06-02 12:16, Steve Tuts wrote: >> > >> > > > > > > >> > >> > > > > > > Hi, we have a Dell poweredge server with a dozen >> interfaces. >> > >> > > > > > > It hosts >> > >> > > > > > > > a >> > >> > > > > > > > few guests of web app and email servers with >> > >> > > > > > > > VirtualBox-4.0.14. The host >> > >> > > > > > > > and all guests are FreeBSD 9.0 64bit. Each guest is >> bridged >> > >> > > > > > > > to a distinct >> > >> > > > > > > > interface. The host and all guests are set to 10.0.0.0 >> > >> > > > > > > > network NAT'ed to >> > >> > > > > > > > a >> > >> > > > > > > > cicso router. >> > >> > > > > > > > >> > >> > > > > > > > This runs well for a couple months, until we added a >> new >> > >> > > > > > > > guest recently. >> > >> > > > > > > > Every few hours, none of the guests can be connected. >> We >> > >> > > > > > > > can only connect >> > >> > > > > > > > to the host from outside the router. We can also go >> to the >> > >> > > > > > > > console of the >> > >> > > > > > > > guests (except the new guest), but from there we can't >> ping >> > >> > > > > > > > the gateway 10.0.0.1 any more. The new guest just >> froze. >> > >> > > > > > > > >> > >> > > > > > > > Furthermore, on the host we can see a vboxheadless >> process >> > >> > > > > > > > for each guest, >> > >> > > > > > > > including the new guest. But we can not kill it, not >> even >> > >> > > > > > > > with "kill -9". >> > >> > > > > > > > We looked around the web and someone suggested we >> should use >> > >> > > > > > > > "kill -SIGCONT" first since the "ps" output has the >> "T" flag >> > >> > > > > > > > for that vboxheadless process for that new guest, but >> that >> > >> > > > > > > > doesn't help. We also >> > >> > > > > > > > tried all the VBoxManager commands to poweroff/reset >> etc >> > >> > > > > > > > that new guest, >> > >> > > > > > > > but they all failed complaining that vm is in Aborted >> state. >> > >> > > > > > > > We also tried >> > >> > > > > > > > VBoxManager commands to disconnect the network cable >> for >> > >> > > > > > > > that new guest, >> > >> > > > > > > > it >> > >> > > > > > > > didn't complain, but there was no effect. >> > >> > > > > > > > >> > >> > > > > > > > For a couple times, on the host we disabled the >> interface >> > >> > > > > > > > bridging that new >> > >> > > > > > > > guest, then that vboxheadless process for that new >> guest >> > >> > > > > > > > disappeared (we >> > >> > > > > > > > attempted to kill it before that). And immediately all >> > >> > > > > > > > other vms regained >> > >> > > > > > > > connection back to normal. >> > >> > > > > > > > >> > >> > > > > > > > But there is one time even the above didn't help - the >> > >> > > > > > > > vboxheadless process >> > >> > > > > > > > for that new guest stubbonly remains, and we had to >> reboot >> > >> > > > > > > > the host. >> > >> > > > > > > > >> > >> > > > > > > > This is already a production server, so we can't >> upgrade >> > >> > > > > > > > virtualbox to the >> > >> > > > > > > > latest version until we obtain a test server. >> > >> > > > > > > > >> > >> > > > > > > > Would you advise: >> > >> > > > > > > > >> > >> > > > > > > > 1. is there any other way to kill that new guest >> instead of >> > >> > > > > > > > rebooting? 2. what might cause the problem? >> > >> > > > > > > > 3. what setting and test I can do to analyze this >> problem? >> > >> > > > > > > > ______________________________****_________________ >> > >> > > > > > > > >> > >> > > > > > > > >> > >> > > > > > > I haven't seen any comments on this and don't want you to >> > >> > > > > > > think you are being ignored but I haven't seen this but >> also, >> > >> > > > > > > the 4.0 branch was buggier >> > >> > > > > > > for me than the 4.1 releases so yeah, upgrading is >> probably >> > >> > > > > > > what you are looking at. >> > >> > > > > > > >> > >> > > > > > > Rusty Nejdl >> > >> > > > > > > ______________________________****_________________ >> > >> > > > > > > >> > >> > > > > > > >> > >> > > > > > > sorry, just realize my reply yesterday didn't go to the >> list, >> > >> > > > > > > so am >> > >> > > > > > re-sending with some updates. >> > >> > > > > > >> > >> > > > > > Yes, we upgraded all ports and fortunately everything went >> back >> > >> > > > > > and especially all vms has run peacefully for two days >> now. So >> > >> > > > > > upgrading to the latest virtualbox 4.1.16 solved that >> problem. >> > >> > > > > > >> > >> > > > > > But now we got a new problem with this new version of >> > >> virtualbox: >> > >> > > > > > whenever >> > >> > > > > > we try to vnc to any vm, that vm will go to Aborted state >> > >> > > > > > immediately. Actually, merely telnet from within the host >> to the >> > >> > > > > > vnc port of that vm will immediately Abort that vm. This >> > >> > > > > > prevents us from adding new vms. Also, when starting vm >> with vnc >> > >> > > > > > port, we got this message: >> > >> > > > > > >> > >> > > > > > rfbListenOnTCP6Port: error in bind IPv6 socket: Address >> already >> > >> > > > > > in use >> > >> > > > > > >> > >> > > > > > , which we found someone else provided a patch at >> > >> > > > > > >> > >> >> http://permalink.gmane.org/**gmane.os.freebsd.devel.**emulation/10237< >> > >> http://permalink.gmane.org/gmane.os.freebsd.devel.emulation/10237> >> > >> > > > > > >> > >> > > > > > So looks like when there are multiple vms on a ipv6 system >> (we >> > >> > > > > > have 64bit FreeBSD 9.0) will get this problem. >> > >> > > > > > >> > >> > > > > >> > >> > > > > Glad to hear that 4.1.16 helps for the networking problem. >> The VNC >> > >> > > > > problem is also a known one but the mentioned patch does not >> work >> > >> > > > > at least for a few people. It seems the bug is somewhere in >> > >> > > > > libvncserver so downgrading net/libvncserver to an earlier >> version >> > >> > > > > (and rebuilding virtualbox) should help until we come up >> with a >> > >> > > > > proper fix. >> > >> > > > > >> > >> > > > >> > >> > > > You are right about the "Address already in use" problem and >> the >> > >> > > > patch for it so I will commit the fix in a few moments. >> > >> > > > >> > >> > > > I have also tried to reproduce the VNC crash but I couldn't. >> > >> Probably >> > >> > > > because >> > >> > > > my system is IPv6 enabled. flo@ has seen the same crash and >> has no >> > >> > > > IPv6 in his kernel which lead him to find this commit in >> > >> > > > libvncserver: >> > >> > > > >> > >> > > > >> > >> > > > commit 66282f58000c8863e104666c30cb67**b1d5cbdee3 >> > >> > > > Author: Kyle J. McKay >> > >> > > > Date: Fri May 18 00:30:11 2012 -0700 >> > >> > > > libvncserver/sockets.c: do not segfault when >> > >> > > > listenSock/listen6Sock == -1 >> > >> > > > >> > >> > > > http://libvncserver.git.** >> > >> sourceforge.net/git/gitweb.**cgi?p=libvncserver/ >> > >> > > > **libvncserver;a=commit;h=**66282f5< >> > >> >> http://libvncserver.git.sourceforge.net/git/gitweb.cgi?p=libvncserver/libvncserver;a=commit;h=66282f5 >> > >> > >> > >> > > > >> > >> > > > >> > >> > > > It looks promising so please test this patch if you can >> reproduce >> > >> the >> > >> > > > crash. >> > >> > > > >> > >> > > > >> > >> > > > -- >> > >> > > > Bernhard Froehlich >> > >> > > > http://www.bluelife.at/ >> > >> > > > >> > >> > > >> > >> > > Sorry, I tried to try this patch, but couldn't figure out how to >> do >> > >> > > that. I use ports to compile everything, and can see the file is >> at >> > >> > > >> > >> >> /usr/ports/net/libvncserver/work/LibVNCServer-0.9.9/libvncserver/sockets.c >> > >> > > . However, if I edit this file and do make clean, this patch is >> wiped >> > >> > > out before I can do "make" out of it. How to apply this patch >> in the >> > >> > > ports? >> > >> > >> > >> > To apply patches to ports: >> > >> > # make clean >> > >> > # make patch >> > >> > >> > >> > # make >> > >> > # make deinstall >> > >> > # make reinstall >> > >> > >> > >> > Note that the final two steps assume a version of the port is >> already >> > >> > installed. If not: 'make install' >> > >> > I you use portmaster, after applying the patch: 'portmaster -C >> > >> > net/libvncserver' -- >> > >> >> > >> flo has already committed the patch to net/libvncserver so I guess it >> > >> fixes the problem. Please update your portstree and verify that it >> works >> > >> fine. >> > >> >> > > >> > > I confirmed after upgrading all ports and noticing libvncserver >> upgraded >> > > to 0.99_1 and reboot, then I can vnc to the vms now. Also, starting >> vms >> > > with vnc doesn't have that error now, instead it issues the following >> info, >> > > so all problem are solved. >> > > >> > > 07/06/2012 03:49:14 Listening for VNC connections on TCP port 5903 >> > > 07/06/2012 03:49:14 Listening for VNC connections on TCP6 port 5903 >> > > >> > > Thanks everyone for your great help! >> > > >> > >> > Unfortunately, seems that the original problem of one vm disrupts all >> vms >> > and entire network appears to remain, albeit to less scope. After >> running >> > on virtualbox-ose-4.1.16_1 and libvncserver-0.9.9_1 for 12 hours, all >> vms >> > lost connection again. Also, phpvirtualbox stopped responding, and >> > attempts to restart vboxwebsrv hanged. And trying to kill (-9) the >> > vboxwebsrv process won't work. The following was the output of "ps >> > aux|grep -i box" at that time: >> > >> > root 3322 78.7 16.9 4482936 4248180 ?? Is 3:42AM 126:00.53 >> > /usr/local/bin/VBoxHeadless --startvm vm1 >> > root 3377 0.2 4.3 1286200 1078728 ?? Is 3:42AM 15:39.40 >> > /usr/local/bin/VBoxHeadless --startvm vm2 >> > root 3388 0.1 4.3 1297592 1084676 ?? Is 3:42AM 15:06.97 >> > /usr/local/bin/VBoxHeadless --startvm vm7 -n -m 5907 -o >> jtlgjkrfyh9tpgjklfds >> > root 2453 0.0 0.0 141684 7156 ?? Ts 3:38AM 4:14.09 >> > /usr/local/bin/vboxwebsrv >> > root 2478 0.0 0.0 45288 2528 ?? S 3:38AM 1:29.99 >> > /usr/local/lib/virtualbox/VBoxXPCOMIPCD >> > root 2494 0.0 0.0 121848 5380 ?? S 3:38AM 3:13.96 >> > /usr/local/lib/virtualbox/VBoxSVC --auto-shutdown >> > root 3333 0.0 4.3 1294712 1079608 ?? Is 3:42AM 19:35.09 >> > /usr/local/bin/VBoxHeadless --startvm vm3 >> > root 3355 0.0 4.3 1290424 1079332 ?? Is 3:42AM 16:43.05 >> > /usr/local/bin/VBoxHeadless --startvm vm5 >> > root 3366 0.0 8.5 2351436 2140076 ?? Is 3:42AM 17:32.35 >> > /usr/local/bin/VBoxHeadless --startvm vm6 >> > root 3598 0.0 4.3 1294520 1078664 ?? Ds 3:50AM 15:01.04 >> > /usr/local/bin/VBoxHeadless --startvm vm4 -n -m 5904 -o >> > u679y0uojlkdfsgkjtfds >> > >> > You can see the vboxwebsrv process has the "T" flag there, and the >> > vboxheadless process for vm4 has "D" flag there. Both of such >> processes I >> > can never kill them, not even with "kill -9". So on the host I disabled >> > the interface bridged to vm4 and restarted network, and fortunately both >> > the vm4 and the vboxwebsrv processed disappeared. And at that point all >> > other vms regained network. >> > >> > There may be one hope that the "troublemaker" may be limited to one of >> the >> > vms that started with vnc, although there was no vnc connection at that >> > time, and the other vm with vnc was fine. And this is just a hopeful >> guess. >> > >> > Also I found no log or error message related to virtualbox in any log >> > file. The VBoxSVC.log only had some information when started but never >> > since. >> >> If this is still a problem then >> >> ps alxww | grep -i box >> >> may be more helpful as it will show the wait channel of processes stuck >> in the kernel. >> >> Gary >> > > We avoided this problem by running all vms without vnc. But forgot this > problem and left one vm on with vnc, together with the other few running > vms yesterday, and hit this problem again on virtualbox 4.1.16. Only the > old trick of turning off the host interface corresponding to the vm with > vnc and then restarting host network got us out of the problem. > > We then upgraded virtualbox to 4.1.18, turning off all vms, wait until "ps > aux|grep -i box" reported nothing, then started all vms. And let no vm > with vnc running. > > Still the problem hit us again. Here is the output of " ps alxww | grep > -i box" as you suggested: > > 1011 42725 1 0 20 0 1289796 1081064 IPRT S > Is ?? 30:53.24 VBoxHeadless --startvm vm5 > > after "kill -9 42725", the line changed to > > 1011 42725 1 0 20 0 1289796 1081064 keglim > Ts ?? 30:53.24 VBoxHeadless --startvm vm5 > > after "kill -9" for another vm, the line changed to something like > > 1011 42754 1 0 20 0 1289796 1081064 - Ts > ?? 30:53.24 VBoxHeadless --startvm vm7 > > and controlvm command don't work, and these command stuck there > themselves. The following are their outputs: > > 0 89572 79180 0 21 0 44708 1644 select I+ > v6 0:00.01 VBoxManage controlvm projects_outside acpipowerbutton > 0 89605 89586 0 21 0 44708 2196 select I+ > v7 0:00.01 VBoxManage controlvm projects_outside poweroff > > We now rebooted the host, and left no vm with vnc running. > The problem has become more rampant now. After rebooting and running virtualbox-ose-4.1.18, and no vm was started with console, the around 10 vms, bridged to each of its own dedicated interface, get no network connection a couple times a day. Most times it would recover itself after about 10 minutes, sometimes we have to restart host network which immediately restore all connections.