Major Intel CPU vulnerability
-
-
Wonderful.
Now the NSA doesn't even need to access "your system" they just need to be on the same server to get access to whatever they want.
-
This year has really shown that Intel has no idea what they are doing. Time to get to AMD and ARM procs and stay there.
-
@scottalanmiller said in Major Intel CPU vulnerability:
This year has really shown that Intel has no idea what they are doing. Time to get to AMD and ARM procs and stay there.
Windows licensing isn't favorable to AMD
-
@irj said in Major Intel CPU vulnerability:
@scottalanmiller said in Major Intel CPU vulnerability:
This year has really shown that Intel has no idea what they are doing. Time to get to AMD and ARM procs and stay there.
Windows licensing isn't favorable to AMD
All the more reason to drop Windows, too.
-
Writing this from my Linux on AMD desktop
-
@irj said in Major Intel CPU vulnerability:
@scottalanmiller said in Major Intel CPU vulnerability:
This year has really shown that Intel has no idea what they are doing. Time to get to AMD and ARM procs and stay there.
Windows licensing isn't favorable to AMD
That's fine, if you can afford windows, just buy Datacenter everything. Problem solved.
-
Ludicrous that the fixes are still under NDA, with comments in the fix redacted.
-
"Forcefully Unmap Complete Kernel With Interrupt Trampolines, aka FUCKWIT" is the issue
-
@dustinb3403 said in Major Intel CPU vulnerability:
@irj said in Major Intel CPU vulnerability:
@scottalanmiller said in Major Intel CPU vulnerability:
This year has really shown that Intel has no idea what they are doing. Time to get to AMD and ARM procs and stay there.
Windows licensing isn't favorable to AMD
That's fine, if you can afford windows, just buy Datacenter everything. Problem solved.
No it doesn't solve a thing. The problem applies to DC exactly the same as any other version.
-
@momurda said in Major Intel CPU vulnerability:
Ludicrous that the fixes are still under NDA, with comments in the fix redacted.
yeah, how is that possible? Is the US gov't hiding this?
-
@irj said in Major Intel CPU vulnerability:
@scottalanmiller said in Major Intel CPU vulnerability:
This year has really shown that Intel has no idea what they are doing. Time to get to AMD and ARM procs and stay there.
Windows licensing isn't favorable to AMD
Intel procs just doubled in price compared to AMD, Windows might be a lot better on AMD today than before.
-
@scottalanmiller it was a response about how everyone is vulnerable to this issue. Microsoft licensing is simplified once you go "Datacenter".
You just need stupidly deep pockets.
-
@dustinb3403 said in Major Intel CPU vulnerability:
@scottalanmiller it was a response about how everyone is vulnerable to this issue. Microsoft licensing is simplified once you go "Datacenter".
You just need stupidly deep pockets.
It's not simplified, though, it's just cheaper past 13VMs. At 12 VMs, Standard is still better. DC still has all the core counting complexity of other versions. DC is just as simple as Standard.
-
Does AMD have a sixteen core server proc released yet? If so, Windows on AMD just became the go to solution.
-
@irj said in Major Intel CPU vulnerability:
@scottalanmiller said in Major Intel CPU vulnerability:
This year has really shown that Intel has no idea what they are doing. Time to get to AMD and ARM procs and stay there.
Windows licensing isn't favorable to AMD
Actually, it's PERFECT for AMD now. It's more favourable for AMD than for Intel by a long shot (as of today.) AMD Epyc 16 core single proc is now nearly double the performance of the Intel counterpart (or half the cost, however you want to look at it) with the same Windows licensing.
-
A base Windows license core count is sixteen. So dual proc EPYC 7251 or single proc 7281, 7301, 7351, or 7351P procs incur no Windows licensing penalties.
-
This might be the worst vulnerability we've seen to date...
You can plan for patching and maintenance. You cannot plan for unexpectedly losing resources. Can you imagine how many cloud providers this is going to affect. They share so many services across so many servers, I doubt they could afford to take a 30% resource hit. It could take down their whole environment.
-
@irj That is why the Linux Kernel dev team was passionately referring to this issue as FUCKWIT aka Forcefully Unmap Complete Kernel With Interrupt Trampolines.
-
@scottalanmiller said in Major Intel CPU vulnerability:
This year has really shown that Intel has no idea what they are doing. Time to get to AMD and ARM procs and stay there.
ARM's impacted.
