From owner-freebsd-virtualization@freebsd.org Sat Jan 23 23:16:12 2021 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0F3744E1E0C for ; Sat, 23 Jan 2021 23:16:12 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNX7H0qy2z3M1f for ; Sat, 23 Jan 2021 23:16:10 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.16.1/8.16.1) with ESMTPS id 10NNErsI043403 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Sat, 23 Jan 2021 15:14:53 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.16.1/8.16.1/Submit) id 10NNErvW043399 for freebsd-virtualization@freebsd.org; Sat, 23 Jan 2021 15:14:53 -0800 (PST) (envelope-from warlock) Date: Sat, 23 Jan 2021 15:14:53 -0800 From: John Kennedy To: freebsd-virtualization@freebsd.org Subject: RHEL virtualization Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 4DNX7H0qy2z3M1f X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net X-Spamd-Result: default: False [-1.80 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[107.170.196.116:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[107.170.196.116:from:127.0.2.255]; DMARC_NA(0.00)[phouka.net]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; MAILMAN_DEST(0.00)[freebsd-virtualization]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.34 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: Sat, 23 Jan 2021 23:16:12 -0000 At work, we have RHEL (-ish; some RHEL, some CentOS, some OEL). Mostly v7, some v8. Since I'm doing the Covid work-from-home telecommute, I'm trying to recreate some of my work infrastructure while trying to plan a bit towards the future (migrating a lot of VMs to Azure). What I'd like to recreate is my existing kickstart infrastructure, where I PXE boot the system, feed it anaconda goodness which dovetails into puppet and I can generate a clean system from a template. Works great for VMWare and HyperV, not so much for Azure but if I can generate a snapshot disk image Azure can ingest, I'll be happy on that score. I've been very happy with bhyve for FreeBSD. I messed with VirtualBox for a while (a long time ago), but with my tendency to track stable (think: kernel modules) and keep very current on ports-from-source (frequent package updates, upon which VirtualBox has MANY dependencies) made that a poorer experience than I had with it on Windows. I've been very happy with bhyve since it's basically baked right in. That being said, RHEL on bhyve has been a pain to figure out. The best I've done so far is using sysutils/grub2-bhyve to set up the boot CD, using BHYVE_UEFI.fd as UEFI firmware (sysutils/bhyve-firmware I think) and then getting at the console via net/tigervnc-viewer. Currently I'm fighting grub-bhyve's issue finding the kernel to load (if I'm finding the right problem reports, it doesn't seem to like modern XFS or ext4 partitions). I couldn't get net/ipxe to PXE boot anything, and I din't manage to get very far with sysutils/uefi-edk2-bhyve. And of course some of these are flagged with python2.7 isses. I'm not a fan of grub-bhyve, but that's mostly because you have to specify the full kernel-with-version path (changes every kernel update), but I figure I could make an expect-script that would figure it out if I could find a /boot filesystem type that grub-bhyve could "ls" properly. Ignoring my own setup details right now, what would someone currently bhyving RHEL recommend that I be doing right now? There is so much old information/documentation out there that I'm really second-guessing myself and probably chasing a bunch of dying ports. But someone on here must be happy with what they've got going for them.