From owner-freebsd-virtualization@freebsd.org Tue Aug 14 08:26:13 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A0BB1070761 for ; Tue, 14 Aug 2018 08:26:13 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-b.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 945C584305 for ; Tue, 14 Aug 2018 08:26:12 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-b.userve.net (Postfix) with ESMTPS id E11F492B; Tue, 14 Aug 2018 09:26:04 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1534235164; bh=1gT5xK7wOEcjMxmM/QaP8e66zXTI6hUnpJTyLMRuT/M=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=Nbk1nkNb7lXWaLIEqDmA0gqm4nQwT9sH4UZDy7fsjBTJot3HzSiKe+B2SHr2JZdZz DgnP4yd2bDUSGjI3wUsUyLe4MQXFyoui6CidrDR6Ltl4e+aSdpu0i/CO0jeofpl6tj wJmbJpBBPWi86fls4V8Kl3bEctRL4Kblq77xGDzk= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 14 Aug 2018 09:26:04 +0100 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Tue, 14 Aug 2018 09:26:03 +0100 From: Matt Churchyard To: "Rodney W. Grimes" CC: "freebsd-virtualization@freebsd.org" Subject: RE: Curent Centos 7 and bhyve Thread-Topic: Curent Centos 7 and bhyve Thread-Index: AQHUMQRwp/VmOgvRrEWW0WbxakcQ6aS5/FiAgACE6YCAAAzbAIAAANiAgAAG4oCAAAHfgIAAFGsAgAADS4CAANYhgIAAockAgAC5ugCAAHVP0IAAe9kAgAEaXQA= Date: Tue, 14 Aug 2018 08:26:02 +0000 Message-ID: References: <1b484d237c4a4f4dabcbd7b0eece7675@SERVER.ad.usd-group.com> <201808131627.w7DGRKKT037840@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201808131627.w7DGRKKT037840@pdx.rh.CN85.dnsmgr.net> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 08:26:13 -0000 > > 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"