Stuart Henderson wrote:
> On 2023-07-25, Kevin wrote:
> > Regarding the Zenbleed vulnerability itself, none of our AMD hosts are
> > known to be vulnerable at this time as they are all running Milan and
> > later CPUs.
>
> rather than going with "none are known to be vulnerable" they should
>
Kevin wrote:
> Would this be worth putting a ticket into Vultr to get them to make
> appropriate
> updates on their side?
You are the customer.
On 2023-07-25, Kevin wrote:
> Regarding the Zenbleed vulnerability itself, none of our AMD hosts are
> known to be vulnerable at this time as they are all running Milan and
> later CPUs.
rather than going with "none are known to be vulnerable" they should
probably run the PoC program themselves
>
> > Just applied the fix to the first affected AMD machine and all is well
> > again.
> >
> > Would this be worth putting a ticket into Vultr to get them to make
> > appropriate updates on their side?
>
> Yes (but I see you already did)
>
Here's the reply I got from Vultr about this:
Thank
On Tue, Jul 25, 2023 at 10:42:25AM -0700, Kevin wrote:
> On Tue, Jul 25, 2023 at 7:42 AM Theo de Raadt wrote:
>
> > It seems some of the smaller hypervisor companies didn't get the memo,
> > and they are blocking the msr write to to set the chicken bit.
> >
> > They block it by raising an
I made a ticket with Vultr I believe they already know about it!
I just fucking love you guys.
Thank you.
Just applied the fix to the first affected AMD machine and all is well
again.
Would this be worth putting a ticket into Vultr to get them to make
appropriate updates on their side?
On Tue, Jul 25, 2023 at 7:42 AM Theo de Raadt wrote:
> It seems some of the smaller hypervisor companies didn't get the memo,
> and they are blocking the msr write to to set the chicken bit.
>
> They block it by raising an exception.
> They should IGNORE that bit if they allow setting it.
>
> I
Everything is working after the newest patch! Thank you all!
On 7/25/23 11:18 AM, Jag Talon wrote:
I ran into the same issue with the "2048.00 MB AMD High Performance, 2
vCPU" on my end. Fortunately I had a snapshot and I was able to roll
back.
Here's my dmesg output if that's helpful:
On Mon, Jul 24, 2023 at 11:37:12PM -0700, Kevin wrote:
> After applying today's zenbleed patches and running fw_update and
> installboot -v sd0, ALL of our AMD servers running 7.3 at Vultr that
> were--as part of the patch process--rebooted are now dead in the water and
> won't boot.
>
I
I ran into the same issue with the "2048.00 MB AMD High Performance, 2
vCPU" on my end. Fortunately I had a snapshot and I was able to roll back.
Here's my dmesg output if that's helpful:
OpenBSD 7.3 (GENERIC.MP) #1125: Sat Mar 25 10:36:29 MDT 2023
Snapshots got that diff about 8 hours earlier.
> For what it’s worth, my Vultr VPS machine is running snapshots and updated
> without issue.
>
> Hope this helps as a clue!
>
> On Tue, Jul 25, 2023 at 10:45 AM Theo de Raadt wrote:
>
> > It seems some of the smaller hypervisor companies didn't
For what it’s worth, my Vultr VPS machine is running snapshots and updated
without issue.
Hope this helps as a clue!
On Tue, Jul 25, 2023 at 10:45 AM Theo de Raadt wrote:
> It seems some of the smaller hypervisor companies didn't get the memo,
> and they are blocking the msr write to to set
It seems some of the smaller hypervisor companies didn't get the memo,
and they are blocking the msr write to to set the chicken bit.
They block it by raising an exception.
They should IGNORE that bit if they allow setting it.
I also have a strong suspicion some of them do not have the firmware
13 matches
Mail list logo
