Date: Mon, 04 Jun 2012 15:11:17 -0500 From: Rusty Nejdl <rnejdl@ringofsaturn.com> To: <freebsd-emulation@freebsd.org> Subject: Re: one virtualbox vm disrupts all vms and entire network Message-ID: <assp.050217e07a.6a54445e6fa4183cff3692d9deed5635@ringofsaturn.com> In-Reply-To: <CAEXKtDreCQ0O4NAi5opGm_KnR4As=dDvc-zP5Z0z5g84GQQuyg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
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 Nejdlhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?assp.050217e07a.6a54445e6fa4183cff3692d9deed5635>