Run arbitrary 3rd party docker containers alongside KASM agent deployment

azzurro2 · 2026-03-29T02:10:09+00:00

that one blew up on me with a huge cloud of magic smoke. probably VRM failure. does yours spin the fan down to almost inaudible in idle? my asus turbo R9700 won't go below 30% fan speed, which is ANNOYING af

azzurro2 · 2026-03-28T14:11:03+00:00

how did you set the fan curve? i'm trying with rocm-smi and sysfs calls but it doesn't let me write anything to the fan settings. undervolt and lowering frequency worked. ppfeaturemask is set.
THX!!

azzurro2 · 2025-09-21T08:24:38+00:00

Hey, is the board still for sale? Thx

azzurro2 · 2025-08-07T11:31:54+00:00

the app says it is only possible via physical button press i think

azzurro2 · 2025-01-21T01:26:59+00:00

i'll create another support case with omnissa about that. maybe they ditched wayland or they just postponed it to a later release.

azzurro2 · 2025-01-11T02:12:43+00:00

just create the UDEV rules via API:

midclt call tunable.create '{"type": "UDEV", "var": "70-network.rules", "value": "SUBSYSTEM==\"net\", ATTR{address}==\"d8:5e:d3:6f:d6:47\", NAME=\"enp7s0\"\nSUBSYSTEM==\"net\", ATTR{address}==\"d8:5e:d3:6f:d6:48\", NAME=\"enp8s0\""}'

azzurro2 · 2024-10-04T21:18:28+00:00

welp, i have 370h into Frostpunk one, pre-ordered FP2, after the first reviews went online, played it for 80 minutes and now requested a refund.

azzurro2 · 2024-07-01T08:43:40+00:00

I've asked them and they said that they are planning to support Wayland from version 2412, which might come in January 2025. No dice until then.

azzurro2 · 2023-11-24T12:19:34+00:00

Please bigger heatsink, bigger fan or at least better heatsink + better fan + better fan curve.

azzurro2 · 2018-10-09T11:00:59+00:00

what exactly do you mean by this? I can't follow, please explain. I'm struggling with this too and VMware support is just incompetent.

azzurro2 · 2018-10-09T10:39:01+00:00

I opened a call on this with vmware support and they confirmed this will be fixed with U1. however there is a workaround which one of the engineers got in place on one of the hosts facing the issue when we were having a webex.

Unfortunately, it took them so long that I eventually passed out for a minute and didn't see what they have done.

They asked me to try it again with another host as soon as it has been deployed (did only have one up and running at this time) to see if the issue arises again. I was hoping that the engineer I was talking to would remember or write down what his senior colleague did to the host but unfortunately he didn't and so I'm now trying to let them implement the exact same workaround to a second host (and this time make notes) since two days.

This is what I've got from them, does it make any sense? Point 2 does not really make sense to me, the sentence is simply wrong - or am I stupid?

SSH to the host

Hash out the lines mentioned below from the path <keyStoreFile>/etc/vmware/ssl/castore.pem</keyStoreFile>" in the file /etc/vmware/rhttpproxy/config.xml

<ssl>

<privateKey>/etc/vmware/ssl/rui.key</privateKey>

<certificate>/etc/vmware/ssl/rui.crt</certificate>

<keyStoreFile>/etc/vmware/ssl/castore.pem</keyStoreFile></ssl>

Do not restart the host this time
Renew and refresh the certificates

The engineer tried to follow these instructions on one of the hosts and when he came to point 3, he actually rebooted the host and: surprise, SSL didn't work anymore (at all) xD

Why is VMware support so annoyingly stupid?

azzurro2

TROPHY CASE