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