<div dir="auto"><div>Hi Greg --</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">My work, APS, is also considering this switch.</div><div><br></div><div data-smartmail="gmail_signature">--<br>Thanks,<br>Alexander<br><br>Sent from my Google Pixel 7 Pro</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 2, 2024, 14:09 greg zegan via PLUG-discuss <<a href="mailto:plug-discuss@lists.phxlinux.org">plug-discuss@lists.phxlinux.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Helvetica Neue,Helvetica,Arial,sans-serif;font-size:13px"><div></div>
<div dir="ltr">speaking of VMs I see they are migrating from VMWare to OpenShift from Red Hat at work.</div><div dir="ltr">Anyone know more about this? Is it cost based?</div><div dir="ltr">no one is saying why here.</div><div><br></div>
</div><div id="m_-2718937967792454185yahoo_quoted_0621863811">
<div style="font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;color:#26282a">
<div>
On Tuesday, July 2, 2024 at 02:05:11 PM MST, Ryan Petris via PLUG-discuss <<a href="mailto:plug-discuss@lists.phxlinux.org" target="_blank" rel="noreferrer">plug-discuss@lists.phxlinux.org</a>> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="m_-2718937967792454185yiv1180701151"><div><div>I think the option you're looking for is called "affinity":<br clear="none"></div><div><br clear="none"></div><div><a rel="nofollow noopener noreferrer noreferrer" shape="rect" href="https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_cpu_resource_limits" target="_blank">https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_cpu_resource_limits</a><br clear="none"></div><div><br clear="none"></div><blockquote type="cite"><div>With the <b>affinity</b> 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 <b>CPU affinity is not a security
feature</b>.<br clear="none"></div></blockquote><div><br clear="none"></div><div>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.<br clear="none"></div><div><br clear="none"></div><div>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.<br clear="none"></div><div><br clear="none"></div><div>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.<br clear="none"></div><div><br clear="none"></div><div id="m_-2718937967792454185yiv1180701151yqt45668"><div>On Tue, Jul 2, 2024, at 1:51 PM, Snyder, Alexander J via PLUG-discuss wrote:<br clear="none"></div><blockquote id="m_-2718937967792454185yiv1180701151qt" type="cite"><div><div>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. <br clear="none"></div><div><br clear="none"></div><div>In this VM, I have vCPUs configured.<br clear="none"></div><div><br clear="none"></div><div><div>--<br clear="none"></div><div>Thanks,<br clear="none"></div><div>Alexander<br clear="none"></div><div><br clear="none"></div><div>Sent from my Google Pixel 7 Pro<br clear="none"></div></div></div><div><br clear="none"></div><div><div dir="ltr">On Tue, Jul 2, 2024, 13:43 Keith Smith via PLUG-discuss <<a rel="nofollow noopener noreferrer noreferrer" shape="rect" href="mailto:plug-discuss@lists.phxlinux.org" target="_blank">plug-discuss@lists.phxlinux.org</a>> wrote:<br clear="none"></div><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div>Hi,<br clear="none"></div><div> <br clear="none"></div><div> I've started to skim the Ubuntu docs on QEMU. It talks about vCPUs. <br clear="none"></div><div> I've run both VirtualBox and Proxmox. Seems both VirtualBox and Proxmox <br clear="none"></div><div> only allow for CPU allocation at the CPU level.<br clear="none"></div><div> <br clear="none"></div><div> I'd really like to be able allocate vCPUs.<br clear="none"></div><div> <br clear="none"></div><div> Do I understand this correctly?<br clear="none"></div><div> <br clear="none"></div><div> Thanks!!<br clear="none"></div><div> Keith<br clear="none"></div><div> <br clear="none"></div><div> <br clear="none"></div><div> ---------------------------------------------------<br clear="none"></div><div> PLUG-discuss mailing list: <a rel="nofollow noopener noreferrer noreferrer" shape="rect" href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br clear="none"></div><div> To subscribe, unsubscribe, or to change your mail settings:<br clear="none"></div><div> <a rel="nofollow noopener noreferrer noreferrer" shape="rect" href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br clear="none"></div></blockquote></div><div>---------------------------------------------------<br clear="none"></div><div>PLUG-discuss mailing list: <a rel="nofollow noopener noreferrer noreferrer" shape="rect" href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br clear="none"></div><div>To subscribe, unsubscribe, or to change your mail settings:<br clear="none"></div><div><a rel="nofollow noopener noreferrer noreferrer" shape="rect" href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br clear="none"></div><div><br clear="none"></div></blockquote></div><div><br clear="none"></div></div></div><div id="m_-2718937967792454185yqt74041">---------------------------------------------------<br clear="none">PLUG-discuss mailing list: <a shape="rect" href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank" rel="noreferrer">PLUG-discuss@lists.phxlinux.org</a><br clear="none">To subscribe, unsubscribe, or to change your mail settings:<br clear="none"><a shape="rect" href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank" rel="noreferrer">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br clear="none"></div></div>
</div>
</div></div>---------------------------------------------------<br>
PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank" rel="noreferrer">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" rel="noreferrer noreferrer" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
</blockquote></div>