Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2018-03-13T11:56:07.407Z)
2018-03-15 Nibelheim (Release Date: 2018-03-15)
vmm_do_vm_destroy_lockedfunction we're going to return
EBUSYif a compromised zone attacks another one.
zone_enterinto a given zone, then issues the
VMM_DESTROY_VMioctl against a specific vmm name (
SYSbhyve-21) on my test setup. I then target that test program into a different bhyve branded zone. I used DTrace to confirm that before the fix we're going into
vmmdev_do_vm_destroy(SYSbhyve-21), but after the fix we get
vmmdev_do_vm_destroy. I also verified that normal zone halt and reboot work as expected, both from the CLI and from within the VM.
illumos-joyent commit b13e485c93c36fd37d5470756bc0f7d7bd44d018 (branch master, by Jerry Jelinek) OS-6682 bhyve zones can destroy any VM Reviewed by: Patrick Mooney <firstname.lastname@example.org> Reviewed by: Mike Gerdts <email@example.com> Approved by: Patrick Mooney <firstname.lastname@example.org>