From owner-freebsd-emulation@freebsd.org Sun Dec 10 23:46:28 2017 Return-Path: Delivered-To: freebsd-emulation@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D06CEA1778 for ; Sun, 10 Dec 2017 23:46:28 +0000 (UTC) (envelope-from SRS0=P2Qr=DG=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6075468BB6 for ; Sun, 10 Dec 2017 23:46:27 +0000 (UTC) (envelope-from SRS0=P2Qr=DG=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 6A8B528454 for ; Mon, 11 Dec 2017 00:46:19 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 688AD28412 for ; Mon, 11 Dec 2017 00:46:18 +0100 (CET) Subject: Re: VirtualBox VM hangs on shutdown / stopping [SOLVED] - VNC problem To: freebsd-emulation@freebsd.org References: <5A2C6895.8030302@quip.cz> <20171210232728.GA37468@ircbsd.lifeofadishwasher.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5A2DC749.1090400@quip.cz> Date: Mon, 11 Dec 2017 00:46:17 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <20171210232728.GA37468@ircbsd.lifeofadishwasher.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 10 Dec 2017 23:46:28 -0000 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