Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 23 Dec 2017 20:59:12 -0500
From:      Derek Schrock <dereks@lifeofadishwasher.com>
To:        freebsd-emulation@freebsd.org
Subject:   Re: VirtualBox VM hangs on shutdown / stopping [SOLVED] - VNC problem
Message-ID:  <20171224015912.GA1835@ircbsd.lifeofadishwasher.com>
In-Reply-To: <20171211132338.GB40043@ircbsd.lifeofadishwasher.com>
References:  <5A2C6895.8030302@quip.cz> <20171210232728.GA37468@ircbsd.lifeofadishwasher.com> <5A2DC749.1090400@quip.cz> <20171211132338.GB40043@ircbsd.lifeofadishwasher.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 11, 2017 at 08:23:38AM EST, Derek Schrock wrote:
> On Sun, Dec 10, 2017 at 06:46:17PM EST, Miroslav Lachman wrote:
> > Derek Schrock wrote on 2017/12/11 00:27:
> > > On Sat, Dec 09, 2017 at 05:49:57PM EST, Miroslav Lachman wrote:
> > >> I did a fresh installation on FreeBSD 10.4-RELEASE-p5 amd64 GENERIC.
> > >>
> > >> Whenever I need to stop the VM it hangs indefinitely. The OS in VM is
> > >> also FreeBSD 10.4-p5 amd64. Virtual machine runs fine, but if is use
> > >> shutdown -r now, shutdown -p now (in VM) or use ACPI PowerOff in
> > >> phpVirtualBox or VBoxManage it always hangs after OS in VM is completely
> > >> down (buffers synced etc.)
> > >>
> > >> Packages used:
> > >>     virtualbox-ose-kmod-5.2.0_1
> > >>     virtualbox-ose-nox11-5.2.0_1
> > >>
> > >> Built with Options        :
> > >>           PYTHON         : off
> > >>           R0LOGGING      : off
> > >>           UDPTUNNEL      : on
> > >>           VDE            : on
> > >>           VNC            : on
> > >>           WEBSERVICE     : on
> > >>
> > >>
> > >>     The process is still running:
> > >>
> > >> # ps auxww | grep FBSD_104_tpl
> > >> vboxusers 1268   0.0  5.3 1062960 891668  -  I    11:30PM   0:32.43
> > >> /usr/local/lib/virtualbox/VBoxHeadless --comment FBSD_104_tpl --startvm
> > >> ba50a283-41fa-48ae-8ff2-87591c50bfed --vrde config
> > >>
> > >> # VBoxManage list vms
> > >> "FBSD_104_tpl" {ba50a283-41fa-48ae-8ff2-87591c50bfed}
> > >>
> > >>      but no running VMs listed by VBoxManage
> > >>
> > >> # VBoxManage list runningvms
> > >>
> > >> # VBoxManage controlvm "FBSD_104_tpl" poweroff
> > >> VBoxManage: error: The virtual machine is being powered down
> > >> VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002),
> > >> component ConsoleWrap, interface IConsole, callee nsISupports
> > >> VBoxManage: error: Context: "PowerDown(progress.asOutParam())" at line
> > >> 578 of file VBoxManageControlVM.cpp
> > >>
> > >> The above is the second try to stop VM after few minutes of waiting on
> > >> "Stopping" in phpVirtualBox.
> > >>
> > >> It must be killed by "kill PID", then I can run the VM again.
> > >> (phpVirtualBox says "Aborted")
> > >>
> > >>
> > >> Can anybody help me to debug and fix this issues?
> > >>
> > >> I never see this problem on different machines with slightly older
> > >> version of VirtualBox. We are using the same setup for years.
> > 
> > > What are the chances that you're VNC'ed to the VM during shutdown?  I've
> > > yet to gather all the parts but there is a bug in libvncserver/vbox that
> > > fails to allow a VM to quit if the VNC session isn't closed before the
> > > the VM is shutdown.
> > 
> > Thank you! You saved me a lot of time.
> > Yes, this is the problem. When VNC is connected, the VM cannot be shut 
> > down. If I disconnect VNC then shutdown works fine.
> > It is really annoying bug but at least I know a workaround now.
> > Thank you.
> > 
> > Do you know if this bug is reported somewhere?
> > 
> > Kind Regards
> > Miroslav Lachman
> > _______________________________________________
> > freebsd-emulation@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> > To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org"
> 
> I haven't reported to Oracle yet and I don't see anything in their bug
> tracker.  Maybe this weekend I'll try to get more information for the
> bug.

Just in case if you want to follow along. It appears that vbox DEBUG is
broken and I think that might give us some more hints on to what's
happening here but for the time being I can't find that much more
information about this issue.

https://www.virtualbox.org/ticket/17396



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171224015912.GA1835>