https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242666
Aleksandr Fedorov <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aleksandr.fedorov@itglobal. | |com --- Comment #1 from Aleksandr Fedorov <[email protected]> --- As I understand it, you are using sysutils/vm-bhyve port. Then, this may not 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? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "[email protected]"
