From owner-freebsd-virtualization@freebsd.org Sun Aug 12 05:20:33 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 381F810648D8 for ; Sun, 12 Aug 2018 05:20:33 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 8F3BE791F2 for ; Sun, 12 Aug 2018 05:20:32 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by clamd daemon 0.100.1 for FreeBSD at relay.sibptus.ru Received: from [212.73.125.240] (HELO admin.sibptus.transneft.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 40075711; Sun, 12 Aug 2018 12:20:30 +0700 Received: from admin.sibptus.transneft.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.transneft.ru (8.15.2/8.15.2) with ESMTP id w7C5KUnH073194; Sun, 12 Aug 2018 12:20:30 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.transneft.ru (8.15.2/8.15.2/Submit) id w7C5KP9b073191; Sun, 12 Aug 2018 12:20:25 +0700 (+07) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.transneft.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Sun, 12 Aug 2018 12:20:25 +0700 From: Victor Sudakov To: "Rodney W. Grimes" Cc: Shawn Webb , freebsd-virtualization@freebsd.org Subject: Re: Curent Centos 7 and bhyve Message-ID: <20180812052025.GB73103@admin.sibptus.transneft.ru> References: <20180811162214.GA67623@admin.sibptus.transneft.ru> <201808111634.w7BGY1J3028598@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201808111634.w7BGY1J3028598@pdx.rh.CN85.dnsmgr.net> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.9.5 (2018-04-13) 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: Sun, 12 Aug 2018 05:20:33 -0000 Rodney W. Grimes wrote: > > Rodney W. Grimes wrote: > > > > > > > > > Are there issues with Current CEntos and bhyve? > > > > > > > > > > > > > > > > Sure there are, please look at > > > > > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230453 > > > > > > > > > > > > > > Booting in UEFI mode works. > > > > > > > > > > > > This means we need an update to /usr/local/share/examples/vm-bhyve/centos7.conf ? > > > > > > It says 'loader="grub"' for the present. > > > > > > > > > > > > Do you have a vm config to boot centos7 in UEFI mode you could share? > > > > > > > > > > I just use /usr/share/examples/bhyve/vmrun.sh. I don't use any > > > > > third-party utility to manage bhyve VMs. vmrun.sh is pretty > > > > > straight-forward. > > > > > > > > Thanks for replying. However, I highly recommend vm-bhyve, maybe you > > > > should give it a try. You will love the ease of VM creation and > > > > provisioning, network management, ZFS integration (VM snapshots and > > > > cloning), console and datastore management etc. > > > > > > 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. What about VM that don't use bhyveload, but some other kind of loader like grub2-bhyve? > > > > > > Its artificial restriction of 16 character VM names is also > > > a fair bit annoying. > > > > Maybe. > > Maybe? No, factually. I migrated a number of ESXi VM's and > had to patch vm-bhyve to not have this restriction, so it is > annoying. Did you send your patches upstream? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859