Curent Centos 7 and bhyve

Matt Churchyard matt.churchyard at
Mon Aug 13 08:15:11 UTC 2018

> Rodney W. Grimes wrote:


> > > > > 
> > > > > Though it has a lot of features, it also has some short 
> > > > > comings, like you can not spec a vm to be wired in memory, 
> > > > > which IMHO is the only way to insure consistent VM performance.
> > > > 
> > > > Well, we have "bhyve_options" configuration option in the vm 
> > > > config, why not put "-S" there, is that what you mean by wiring 
> > > > the vm in memory?
> > > 
> > > I believe that fails as that only adds the -S to bhyve, and you 
> > > must specify it both on bhyveload and bhyve for it to work.
> > 
> > I think it is totally doable becase vm-bhyve is nothing but a suit 
> > of scripts. A PR with a feature request would be appropriate.
> I made several attempts to contact the author at the email address 
> provided at the git hub while making other bhyve changes to try and 
> coordinate with him.  I got no response after 3 attempts,
> so have stopped trying to contact them.   (This was while I was
> adding the -c cpu topology modifications.)

> You can add yourself to
> maybe something useful comes out of it.

I've already commented on the bug, although I'll reply here as well.
If "-S" is found in bhyve_options it does currently affect both commands. I have decided that a specific wired_memory option is useful though and will add this to the next release.

The name limit has been increased to 32 since v1.2

I didn't realize the changes for cpu topology had actually made it into head, although I don't believe it's actually in a release yet? I will plan to support configuration and display of these before 12 release.


> --
> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> AS43859
> _______________________________________________
> freebsd-virtualization at mailing list
> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe at"

More information about the freebsd-virtualization mailing list