Date: Mon, 13 Aug 2018 08:32:40 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Victor Sudakov <vas@mpeks.tomsk.su> Cc: Shawn Webb <shawn.webb@hardenedbsd.org>, freebsd-virtualization@freebsd.org Subject: Re: Curent Centos 7 and bhyve Message-ID: <201808131532.w7DFWeK0037668@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <20180813020412.GA83165@admin.sibptus.transneft.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> Rodney W. Grimes wrote: > > [dd] > > > > > > > > > > > > > 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 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230580 > maybe something useful comes out of it. I added virtualization@ to the PR, though it looks as if wired_memory= has already been added as an option, which is what I did locally. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201808131532.w7DFWeK0037668>