From owner-freebsd-emulation@FreeBSD.ORG Sat Jun 2 17:16:42 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 DC95A106577B for ; Sat, 2 Jun 2012 17:16:42 +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 90B448FC15 for ; Sat, 2 Jun 2012 17:16:42 +0000 (UTC) Received: by vcbfy7 with SMTP id fy7so2269738vcb.13 for ; Sat, 02 Jun 2012 10:16:42 -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=UwL9SQHoGwvKyRYrskFCggnoumzfXc82+O/OfIEh2co=; b=X0wyeRT3XWPoJhMIiVPD/6gdKpg/jWU16p1kx/uNam1Ebo8uOnqvcI95qpm0zVy5Gh fClCGJLwqdiC8d13/6DJBc9zsB4RQz/5+QbLkPExv+Sct+fDwWAzjwSPfiX9t6UiPxGr 9ZLSxhembJWUmQZ48tDxVzxdOJNYPoipyv+zI4eQVQC1FwbdSA+BkYR1CI8j+OLn8LVF VFp4HdA2fG7T4XNdgwd+vbV0E5/hLHD9C9hAqRjWnRcAbrOUH31Pnx46EJUxy+SE4tSs SGzzrjN7uDWmSkBlC8P9ppDNASlA6BJD3fUeqjDz+sJhulM7DyQ4v685GzxKWm3zBwiI 4hHg== MIME-Version: 1.0 Received: by 10.52.33.37 with SMTP id o5mr6115804vdi.86.1338657401847; Sat, 02 Jun 2012 10:16:41 -0700 (PDT) Received: by 10.52.30.73 with HTTP; Sat, 2 Jun 2012 10:16:41 -0700 (PDT) Date: Sat, 2 Jun 2012 13:16:41 -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: 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: Sat, 02 Jun 2012 17:16:43 -0000 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?