proxmox
PART 2! – Proxmox on Intel’s Hybrid Big Little – IT WORKS!
PART 2! – Proxmox on Intel’s Hybrid Big Little – IT WORKS!
#PART #Proxmox #Intels #Hybrid #Big #WORKS
“Craft Computing”
Thanks to NordPass for sponsoring today’s video. Take control of your passwords! Visit to take advantage of their best offers, risk free for 30-days!
Grab yourself a Pint Glass or Coffee Tumbler at
Proxmox and Intel’s Hybrid “big/LITTLE”…
source
To see the full content, share this page by clicking one of the buttons below |
Thanks to NordPass for sponsoring today's video. Take control of your passwords! Visit https://nordpass.com/Craft to take advantage of their best offers, risk free for 30-days!
Gotta love when validating results, and you discover a whole new world 🌎!
Results presentation and description is a bit hard to follow. I never touched 12gen+ Intel CPUs in my experiments and probably missing some details on the way they function. But watched this video couple of times and still find the way "tables and graphs" are layed out is not helping but making it more confusing.
So glad to see this update!
Pulling the trigger on a MS 01 after seeing this 🎉
Will I need to do this kind of patching on the i5 1235U with the ZimaCube Pro coming if I want to run Proxmox?
Interesting stuff. Won't be able to test it myself though as I only have a Epyc 7543 and a Xeon E-2314. Neither have E cores, and the Xeon doesn't even have SMT :p
This is really interesting. What this also says is that the N100/N300 process have a real place in the marketplace for multi-threaded systems.
Nice work, great content. Would be even better if you considered power usage statistics when performing these kinds of discovery test. For most, that seems to be one of the biggest concerns with home lab equipment.
Now to see how it works in TrueNAS Scale!
I wonder what Joyent Illumos would do. The thread/core thing was "solved" by Sun Microsystems and Solaris about 20 years ago in their Niagara architecture. Illumos is the current Free-ish version of Solaris and I'm sure some of that scheduling mojo was carried over. Unix and later Linux always had the ability to manually pin tasks and processes to CPUs/CPU sets. I'm wondering if. you could run a full Cinebench session pinned to the P-cores and then pinned to the E-cores (alone) and see the results.
Also, you gotta try a proper Belgian Witbier or even a Geuze.
screw intel, wanna the same but in arm
Hi Jeff, awesome content as always! Did you try i7-13620H 1x VM, pinned 4T from P cores with HT disabled? I'm curious af
It's wonderful to see a YouTuber that actually has the stones to admit fault. Great job man.
Glad you took another look into this 😊 I wish you would take another look at the 3070m GPU that got BIOS bricked (if you were unable to unbrick it, you could always send the GPU to another YouTube content creator for the unbrick video – then use the Frankendriver on the fixed GPU)
microcode: updated early: 0x41d -> 0x430, date = 2023-06-07
I've had a lot of issues with the 12000 series CPUs, but after applied the microcode, you linked to, it started working as it should 😀 Usually I am sticking with AMD 5000 series CPUs….
I’d love a video on a cpu core / threads and a crash course of what it all means..
I'm running Intel NUC with 1340p since november without any issues. Usually there is 5 VMs on at all times and I did not notice any stability issues. Even go iGPU passtrough for jellyfin HW acceleration working in a VM
I went trough few of tteck proxmox helper scripts after install which includes microcode update, that was most likely what saved me from issues
Thanks a bunch for following up on this. This kind of actual hands-on testing and reporting of functionality – and especially your follow-up, when you got the microcode updated and stable and redid all the benchmarks, and your new findings – is incredibly valuable, harder to come by presented in such a comprehensive manner, and happens to line up with stuff I'm tinkering with right now, so, cheers!
Personally on my Alder lake system i only give a VM either Performance cores (threads included) or E cores NEVER both! aka i generally keep the E cores for the base Linux OS and give Widnows Games VM the P cores
Now i Just have to Google if the PCI passthrough works on those Chinese mobo. Thanks
Why open a can of worms if you can open a can of cider?
Such a shame about the engineering samples, ive been storking them in AliExpress for months now looking to replace one of my servers running a E5-2690 for a while. And it looks like im going to have to hold off for now 😔.
Lets hope in another gen or two they will fix the stability issues. They always do and i can wait!
Wow, great update, and so soon after the first part! Big kudos @DotBowder for pinpointing this to the microcode. I did not really think about that, because we generally update our BIOS on our retail boards and have the microcode installed (Not only for stability, but also for security reasons). BTW, we already have a section in our reference documentation about the microcode if you want to link to that ( Section 3.3 Firmware Updates) It is also on our wiki. Thanks for the good work!
Where is link to part 1?
If the ca of worms this video opens leads to similar great results – keep 'em coming!
Do the non mobile chips with hybrid architecture require the microcode applied?
Been wondering if It would be worth it to use my spare, 12900K for my main proxmox server. These videos definitely help with making that decision. Was also toying with the idea of possibly turning this 13900KS daily into a proxmox desktop that still runs windows daily on it but can also run other vm's and containers while being able to shut down windows. Have only seen one other person do this on YouTube, and probably isn't a choice many would want to make for their daily. But I need room to start building more than just the networking portion of my home lab. Buying old Xeon E5v4's and trying to get my MSI GS66 to work with proxmox ve without throwing errors, seems so far like it's not going to work.
I am surprise because I’m Running a 13900k for Two Years now on proxmox With 16 vms running. ECore allways enabeld and i had never Problems with crashes Without applaying some microcode.
Huh! The Linux kernel is smarter than us in allocating CPUs. Go figure.
I don’t remember if you said how well Hyper-V supports the hybrid CPUs.
Welcome to bleeding edge. I’m glad you were able to find the needed help and succeed in your attempts.
That thing looks like a small form factor way to get monkeys to mars! lol.
I built a 12900k system for low latency audio processing in windows and found that disabling hyperthreading improved performance considerably in that work load. Not really the same thing obviously but thought it was interesting.
The interesting part to cover in part 3 is how these boards perform in idle mode. I mean power consumption, falling into c6+ states, etc. Everyone measures performance, but my home server is idling most of time, and though I need to squeeze every GHz out of it sometimes , 80% of time its just idle and costs me $$$
And many thanks for such niche videos, it's insaly hard to find how virtualization works on these Chinese mobos
It's cool to see you revisit this.
To help with further testing, you can use run 'taskset –cpu-list –all-tasks –pid <AFFINITY> "$(< /run/qemu-server/<VMID>.pid)"' to on-the-fly restrict a running VM to a specific set of cores.
Example:
taskset –cpu-list –all-tasks –pid 0-3 "$(< /run/qemu-server/101.pid)"
–all-tasks, Lock both the root pid AND all of it's children to the specified cores
–cpu-list, Let's us specify the cpus that the process will be pinned to (above value: 0-3)
–pid, The root pid id is appended to the arguments (above value: "$(< /run/qemu-server/101.pid)")
You can also use taskset to start a command and pin that command to a specific set of cores.
# Create 4 threads to stress our cpu
stress -c 4
# Create 4 threads to stress cores 1, 7, 8 and 9.
taskset –cpu-list –all-tasks 1,7-9 stress -c 4
The –pid argument is what let's us target a process that is already running.
All of the proxmox VM's root pids are stored in their /run/qemu-server/<VMID>.pid file.
Consider starting your VM, begin your benchmark, then start htop and watch it's threads bounce around. Then, run the taskset command from the proxmox shell to restrict your VM to a set of cores. Then slide it around to another set of cores.
The source for this is a Proxmox Forums Thread # 67805 called "CPU pinning?". It's what led to the affinity feature being created. The 2nd page of comments has a fun exploration into using this taskset with numa memory.
Also, I think you incorrectly attributed the instructions in the video comment to me. I believe you got the instructions from someone else.
SOC2 type 2 is NOT a validation of security or how secure an org is. It's simply a certification that states that an auditor attested that you've implemented policies and procedures and adhere to those policies and procedures. "do you scan for vulnerabilities" yes, then pass. It doesn't test that you remediate all vulnerabilities or even the highest. If an org says we "remediate or run vulnerabilities through our risk process and either accept and insure them and move on" then SOC2type2 will ALSO pass them.
Better than bare metal. Linux ftw. Love the video. Great content as usual. Thanks Jeff!
Wait, Proxmox isn’t applying microcode updates by default? Or is the version you got from GitHub just newer?
This jogged my memory on virtualization and right-sizing VMs compared to bare metal, and why a mid-way loaded host (with noisy neighbor VMs) is faster with a diverse workload. It's because the scheduler should be able to extract more performance during the delay intervals of other threads when they don't overlap too much. Oversubscription can still net performance to an extent when many guests are nearly idle.
Wow. What a change!
Can't wait for part three
Hyper_V also works.
I wonder if Intel's "big" Xeons like the Xeon platinum 8558 are "true big little" as intel's Ark page says "high priority cores" and "low priority cores"…is that the same as P and E? my gut feeling says no as Vmware DOES support these Cpus. Just food for thought