#AVX Warning from whisper

1 messages ยท Page 1 of 1 (latest)

terse wedge
#

getting this warning in the logs now when i restart whisper. I verified avx is enabled in the bios. I never got this before and i've tried everything to reset it.

#

my assumption is it has something to do with the vm. i didn't change any settings

viscid bobcat
terse wedge
#

Still vmware atm. Intel i9 11th gen

viscid bobcat
#

on proxmox it would look like this

#

that way the VM can use the HOST cpu instruction set directly

terse wedge
#

Not at home but ill check. Dont remember seeing host though in the options

viscid bobcat
#

can ensure all the virtualization settings are enabled on the host system too.

treat it as a sign to ditch vmware and join us in the glory of proxmox ๐Ÿ™‚

terse wedge
#

Yes. I wanna get a mini pc and install proxmox on it and put ha on it.
One other thing to note. I had tried my hand at docker desktop and had to enable wsl for terminal. I though it had been one of those things at first because for whatever reason it caused an error in the vm saved state so i had to delete that state.

#

But after deleting docker and disabling linux for windows none of that fixed it

#

I just fucking hate windows

viscid bobcat
#

that could be it, you can only have 1 hypervisor. so when you installed WSL you probably disabled the vmware hypervisor so its switching to using a purely software based virtual system instead of a real hypervisor...
if that makes any sense?

#

a mini pc with proxmox is definetly the way to go though

terse wedge
#

Yes it does

viscid bobcat
#

if you enabled WSL i know virtualbox vomits and tells you off. VMware might just silently do its own thing

terse wedge
#

Wonder if it isnt best to do a fresh install of vm for the time being

viscid bobcat
#

fresh vmware install may help it reconfigure itself back to normal setup

terse wedge
#

It just seems to me after disabling wsl it should have returned to normal

viscid bobcat
#

the VM itself is probably fine, its just getting loaded without a proper hypervisor

terse wedge
#

I fucking hate windows

viscid bobcat
#

lol, yeah any way of running HA or Docker on windows is bad.

#

stuff is kinda fine for testing/getting your feat wet etc...
but a production setup needs to be on linux

terse wedge
#

Ok so gonna push the button on a mini pc for ha. However unsure what i need really. I want to run proxmox with ha in a vm and thinking of putting plex on it to with kometa. Ill run whisper on the desktop

viscid bobcat
#

for media centre stuff i recomend looking at jellyfin, its great

terse wedge
#

Has the Beelink EQ14 gotten better support?

viscid bobcat
#

its fine as long as you update the kernel. proxmox is based on debian stable so by default i think it still uses 6.1 but theres others in the repo

terse wedge
#

The other model seems unavailable

viscid bobcat
#

can check various suppliers, guess it depends where your located though

terse wedge
#

I wouldnt need a secondary m2 slot tbh. I found the s12 on another site

#

But performance wise is there really a difference between the 2?

viscid bobcat
#

not really

#

theres some videos with more details but realistically n100/n150 are basically the same its just the n150 costs more

terse wedge
#

Hmm ordered. Reading another thing where some say its best to run ha directly on one of these without virtual to make use of the whole machine. Plus make it easier for usb detection

viscid bobcat
#

you can definetly run haos directly if you want but realistically the system is overkill for just haos, so running proxmox means you can run other stuff alongside it

#

usb passthrough is easy enough in proxmox

#

you can passthrough either a "device" or a "port" in the ui

#

having proxmox means its easier to reinstall any guest OS too should you need to

#

but whatever works for you

terse wedge
#

Even with piper? I get whisper would be slow on it.

viscid bobcat
#

i run piper on my mini pc without issue, i offload whisper to another system

#

piper doesnt require too much power

#

tbh with the "tiny" model whisper runs "okay" on an n100. experience with accuracy may vary though

terse wedge
#

I tried every size tbh. Every single one below medium sucked

viscid bobcat
#

yeah i had a simalar experience. i use larrge-v3-turbo and its pretty good most of the time

terse wedge
#

After i get ha on the mini, im going to try my hand again on the desktop with whisper. When i tried through docker desktop the container kept stopping and restarting Maybe it was due to having ha on the other vm at the same time. My question though is, should i scrap windows all together on the desktop. I was trying the linux container for whisper that most suggest.

#

It was a crash course figuring out docker tbh.

viscid bobcat
#

if you can scrap windows then go for it, i use windows on my desktop. primarily because i also use it for gaming and i am not gunna bother dual booting.

however most of my servers are linux including the one I run whisper on.
I know some people have gotten whisper containers working with windows but i havent ever tried.

terse wedge
#

whats the best way to go about it? i do have some things like icue that need to run, drivepool. wonder if i should load proxmox directly and do a vm of windows?

viscid bobcat
#

if your wanting to be using applications on this machine directly then proxmox is not the answer

terse wedge
#

i'm at a lose. getting same avx warning after completely uninstalling and reinstalling virtual box

#

these settings should be correct

viscid bobcat
#

check the bios for the intel virtualization tech and vt-d and stuff is switched on

#

maybe windows just fucked up hypervisors once it used its own for a bit

terse wedge
#

when i checked bios before for avx it was set to auto, then switched to on but ill check again

viscid bobcat
#

its probably just windows fucking you over tbh

#

you could play by its rules and try hyper-v ๐Ÿ˜›

terse wedge
#

should i switch to hyper-v in the vm to?

viscid bobcat
#

you could give it a go

#

given it started when you were messing around with windows virtualisation stuff i am pretty sure its that messing with stuff

terse wedge
#

if all else, a windows restore lol

#

[21:09:24] WARNING: Your CPU does not support Advanced Vector Extensions (AVX). Whisper will run slower than normal. [2025-04-24 21:09:32.350] [ctranslate2] [thread 55] [warning] The compute type inferred from the saved model is float16, but the target device or backend do not support efficient float16 computation. The model weights have been automatically converted to use the float32 compute type instead. INFO:__main__:Ready [21:09:33] INFO: Successfully send discovery information to Home Assistant. s6-rc: info: service discovery successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started

#

same thing for whisper

viscid bobcat
#

thats so odd

terse wedge
#

not sure if this helps but found it from the logs of virtualbox

#

yea im at a lose lol

#

for whatever reason the vm isnt allowing it to ha

viscid bobcat
#

yeah i am at a loss also, i think its just windows acting up though

terse wedge
#

might have found a solution

#

apparently turning hyper v off in features doesnt actually turn it off

terse wedge
#

that did it

#

all that to take ha off windows this weekend..

#

lol

#

yea i dunno about wsl

#

Might be fine for whisper but thats about it

#

Fks too much shit up and windows always has to be vague