Re: RHEL virtualization
On Sat, Jan 23, 2021 at 03:14:53PM -0800, John Kennedy wrote: > 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. Let me restate some of this in a different way to maybe get some more thinking. Using the BHYVE_UEFI.fd from uefi-edk2-bhyve, I can boot my OEL8 (RHEL8 clone). That currently worries me because it has the big python-2.7 warning on it (as does uefi-edk2-bhyve-csm). On physical boxes, I've been able to grab a PXEBOOT ISO when the firmware lacks PXE booting, but I haven't got that to work yet for these. Those python worries are basically what is driving me to look elsewhere (like fighting with grub-bhyve and away from the only UEFI booting that I know about). I personally like PXE-booting a new system (and possibly making a gold image from that, depending on what I'm doing) because it basically answers that little auditor-voice in the back of my head that, in the event of some possible security problem, how do I know that my backups haven't been compromised. In all of those gigabytes, after all of the toxic recursive mindless non-logic, how do you *know*? My happy answer to myself is: "here is a configuration file that I can review, all the binaries are on the vendor's site or re-downloaded, here are the puppet customization rules, blam! done! 10 minutes later I have a clean system." In any case, that is why I'm chasing PXE booting, although I'd be interested in the way other people solve that problem. That really doesn't work that way in Azure, thus the gold images approach I'll probably have to take with them in the future. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: RHEL virtualization
On Sat, Jan 23, 2021 at 3:16 PM John Kennedy wrote: ... > 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. Hi I ran into a similar situation (RHELL VM's in bhyve) and created a version of grub-bhyve that knows how to find the grub.cfg and/or syslinux.conf files in a VM's disk image. Because of this, you don't have to maintain a copy of the grub configuration just for grub-bhyve. I implemented this on the latest version of grub which includes XFS and other goodies. The fine print: - The syntax is slightly different. To load an image use grub-bhyve --disk=/path/to/vm/disk.img --vm=vm_name note that the root, device-map, and directory options are no longer necessary - The project is at the "it works for me" stage and hasn't received much usage aside from myself. That said, feedback is welcome. - It builds on FreeBSD 12.x but 13.x has an issue Code is here: https://gitlab.com/ctuffli/grub To build: $ env PYTHON=python3.7 ./bootstrap $ env MAKE=gmake ./configure --with-platform=bhyve $ gmake The resulting binary, `grub-bhyve`, will be in the `grub-core/` directory. If you have success or troubles with it, please let me know. --chuck ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: RHEL virtualization
Hello, I can't talk about RHEL but by using vm-bhyve and customized configuration (based on https://github.com/churchers/vm-bhyve/blob/master/sample-templates/centos7.conf), I have managed to successfully install Ubuntu 20.04 in bhyve last week. In general, both booting and installation were smooth and installed system is completely usable. Maybe you would like to try RHEL with centos7.conf? Regards, Nazim Can. On 24/01/2021 02:14, John Kennedy wrote: > 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. > > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: RHEL virtualization
Hello, I can't talk about RHEL but by using vm-bhyve and customized configuration (based on https://github.com/churchers/vm-bhyve/blob/master/sample-templates/centos7.conf), I have managed to successfully install Ubuntu 20.04 in bhyve last week. In general, both booting and installation were smooth and installed system is completely usable. Maybe I would like to try RHEL with centos7.conf? Regards, Nazim Can. On 24/01/2021 02:14, John Kennedy wrote: > 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. > > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
RHEL virtualization
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. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
