Date: Tue, 17 Dec 2019 04:44:10 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 242666] Stopped VM cant restart again Message-ID: <bug-242666-27103-sR93rp84pc@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-242666-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-242666-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242666 Aleksandr Fedorov <aleksandr.fedorov@itglobal.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aleksandr.fedorov@itglobal. | |com --- Comment #1 from Aleksandr Fedorov <aleksandr.fedorov@itglobal.com> --- As I understand it, you are using sysutils/vm-bhyve port. Then, this may no= t be a bhyve problem. If the bhyve process unexpectedly terminates with an error or is killed via kill -9, the device file remains in /dev/vmm/<vmname>. And the attempt to restart the virtual machine will fail until you run the bhyvectl --destroy = --vm <vmname> command. But, I don't know how well sysutils/vm-bhyve handles such situations. Can you show us the output of the bhyvectl --get-exit-reason --vm test-pc command to determine the exit reason for the VM? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242666-27103-sR93rp84pc>