OS-7819: bhyve upstream sync 2019 June


Issue Type:Improvement
Priority:4 - Normal
Created at:2019-06-04T19:37:41.961Z
Updated at:2019-06-17T19:36:53.248Z


Created by:Former user
Reported by:Former user
Assigned to:Former user


Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2019-06-14T17:50:58.173Z)

Fix Versions

2019-06-20 Urban Fervor (Release Date: 2019-06-20)




Upstream bhyve has begun to take some of our improvements.  It would be good to sync up the small changes which were made as part of that, as well as picking up the vm_maxcpus work that rgrimes did.


Comment by Former user
Created at 2019-06-10T20:30:33.013Z

Verification for this change has consisted mainly of smoke-testing the various guests (Linux, Windows, FreeBSD).
The wad from upstream consisted largely of:
1. Rod's VM_MAXCPU work, which does not change effective behavior yet
2. Changes/fixes we made, which have since gone upstream
3. Improvements to the gdb server (which we don't use)

Comment by Jira Bot
Created at 2019-06-14T17:46:12.271Z

illumos-joyent commit c3cbf49c8d881ba57710e7e8b70aa6275bc5fc44 (branch master, by Patrick Mooney)

OS-7819 bhyve upstream sync 2019 June
Reviewed by: Hans Rosenfeld <hans.rosenfeld@joyent.com>
Reviewed by: Mike Gerdts <mike.gerdts@joyent.com>
Approved by: John Levon <john.levon@joyent.com>