Date: Tue, 14 Aug 2018 08:26:02 +0000 From: Matt Churchyard <matt.churchyard@userve.net> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: RE: Curent Centos 7 and bhyve Message-ID: <fbb3718ebc3148eaa332b1bee429e71e@SERVER.ad.usd-group.com> In-Reply-To: <201808131627.w7DGRKKT037840@pdx.rh.CN85.dnsmgr.net> References: <1b484d237c4a4f4dabcbd7b0eece7675@SERVER.ad.usd-group.com> <201808131627.w7DGRKKT037840@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Rodney W. Grimes wrote: >=20 > [dd] >=20 > > > > > >=20 > > > > > > Though it has a lot of features, it also has some short=20 > > > > > > comings, like you can not spec a vm to be wired in memory,=20 > > > > > > which IMHO is the only way to insure consistent VM performance. > > > > >=20 > > > > > Well, we have "bhyve_options" configuration option in the vm=20 > > > > > config, why not put "-S" there, is that what you mean by=20 > > > > > wiring the vm in memory? > > > >=20 > > > > I believe that fails as that only adds the -S to bhyve, and you=20 > > > > must specify it both on bhyveload and bhyve for it to work. > > >=20 > > > I think it is totally doable becase vm-bhyve is nothing but a suit=20 > > > of scripts. A PR with a feature request would be appropriate. > >=20 > > I made several attempts to contact the author at the email address=20 > > provided at the git hub while making other bhyve changes to try and=20 > > 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.) >=20 > > You can add yourself to > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230580 > > maybe something useful comes out of it. >=20 > 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 wi= ll add this to the next release. >=20 > The name limit has been increased to 32 since v1.2 >This is better, but still an artificial limit, the implementation of bhyve= allows this string to be any valid filename, the scripts should be designe= d to allow for that as the valid limit. As far as I'm aware bhyve is currently limited to 32 characters, although t= his obviously may change. We use the name in various situations (interface = descriptions, console names, etc) so it's beneficial to make sure it's not = excessively long, or contains characters that could cause problems when use= d in other places. if(name =3D=3D NULL || strlen(name) >=3D VM_MAX_NAMELEN) return (EINVAL); #define VM_MAX_NAMELEN 32 >I modified the script so that the vm name is the last column, and removed = the length check all togeather, this allows for the string to be what ever = length and not mess with column widths. >root@x230a:# vm list >DATASTORE LOADER CPU MEMORY VNC AUTOSTAR= T STATE NAME >default bhyveload 1 128M - No = Stopped fb-bld-10-amd64 >default bhyveload 4 2048M - No = Stopped fb-bld-11-amd64 >default bhyveload 4 1024M - No = Stopped fb-bld-11-i386 >default bhyveload 1 128M - No = Stopped fb-bld-11.0-p1-amd64 >default bhyveload 1 128M - No = Stopped fb-bld-11.0-p1-i386 >default bhyveload 4 512M - No = Stopped fb-bld-11.1-amd64 >default bhyveload 4 512M - No = Stopped fb-bld-11.1-i386 >> I didn't realize the changes for cpu topology had actually made it=20 >> into head, although I don't believe it's actually in a release yet? >Yes, they are in head, the MFC has been delayed for other reasons. >It is in the 12.0-ALPHA1 snapshot, and many before that. =20 >> I will plan to support configuration and display of these before 12=20 >> release. >Thanks. I think mostly just extract the NCPU's from the topology string. = The code actually works now, but due to fixed column width assumptions the= output looks bad. I've added some additional cpu_ settings to control the new cpu fields. "vm= list" just shows the original cpu setting so this remains unmodified. "vm = info" shows full settings. >=20 > Matt >=20 > > -- > > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > > AS43859 > > _______________________________________________ > > freebsd-virtualization@freebsd.org mailing list=20 > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fr= eebsd.org" >=20 >=20 --=20 Rod Grimes rgrimes@freebsd.= org _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/m= ailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs= d.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fbb3718ebc3148eaa332b1bee429e71e>