Openshift is a RHEL implementation of Kubernetes and container management. and a stack of tools that all work together. For certain workloads, containers are a fantastic way to go. And VMware HAs been Gutted by Broadcom. On Tue, Jul 2, 2024 at 7:42 PM Snyder, Alexander J via PLUG-discuss < plug-discuss@lists.phxlinux.org> wrote: > Hi Greg -- > > Yes, RedHat OpenShift is typically used in conjunction with Kubernetes and > containers, but can also host "classic" VMs, although there is some work > involved ... It's not 1:1. > > My work, APS, is also considering this switch. > > -- > Thanks, > Alexander > > Sent from my Google Pixel 7 Pro > > On Tue, Jul 2, 2024, 14:09 greg zegan via PLUG-discuss < > plug-discuss@lists.phxlinux.org> wrote: > >> speaking of VMs I see they are migrating from VMWare to OpenShift from >> Red Hat at work. >> Anyone know more about this? Is it cost based? >> no one is saying why here. >> >> On Tuesday, July 2, 2024 at 02:05:11 PM MST, Ryan Petris via PLUG-discuss >> wrote: >> >> >> I think the option you're looking for is called "affinity": >> >> >> https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_cpu_resource_limits >> >> With the *affinity* option, you can specify the physical CPU cores that >> are used to run the VM’s vCPUs. Peripheral VM processes, such as those for >> I/O, are not affected by this setting. Note that the *CPU affinity is >> not a security feature*. >> >> >> That said, I'm wondering why you're wanting to do this, specifically what >> you think you're going to gain over just allowing the kernel to schedule >> things the way it normally does. >> >> For instance, it's not going to lock that core specifically for use to >> that VM; other processes can still use that core. You'd literally have to >> set the affinity of every single process on your system to specific cores >> which would be an extreme pain. You still wouldn't have much control over >> which cores receive interrupts and whatnot so even then you still wouldn't >> have complete control. >> >> Just let the scheduler do its thing, otherwise you're likely going to end >> up with weird issues that no one can help with or explain. >> >> On Tue, Jul 2, 2024, at 1:51 PM, Snyder, Alexander J via PLUG-discuss >> wrote: >> >> I have a VM running with QEMU on Debian, v is a TrueNAS. Although they >> give you a GUI to select options, it is my understanding that it's just >> pure QEMU running on the backend. >> >> In this VM, I have vCPUs configured. >> >> -- >> Thanks, >> Alexander >> >> Sent from my Google Pixel 7 Pro >> >> On Tue, Jul 2, 2024, 13:43 Keith Smith via PLUG-discuss < >> plug-discuss@lists.phxlinux.org> wrote: >> >> Hi, >> >> I've started to skim the Ubuntu docs on QEMU. It talks about vCPUs. >> I've run both VirtualBox and Proxmox. Seems both VirtualBox and Proxmox >> only allow for CPU allocation at the CPU level. >> >> I'd really like to be able allocate vCPUs. >> >> Do I understand this correctly? >> >> Thanks!! >> Keith >> >> >> --------------------------------------------------- >> PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> https://lists.phxlinux.org/mailman/listinfo/plug-discuss >> >> --------------------------------------------------- >> PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> https://lists.phxlinux.org/mailman/listinfo/plug-discuss >> >> >> --------------------------------------------------- >> PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> https://lists.phxlinux.org/mailman/listinfo/plug-discuss >> --------------------------------------------------- >> PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> https://lists.phxlinux.org/mailman/listinfo/plug-discuss >> > --------------------------------------------------- > PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > https://lists.phxlinux.org/mailman/listinfo/plug-discuss > -- A mouse trap, placed on top of your alarm clock, will prevent you from rolling over and going back to sleep after you hit the snooze button. Stephen