Music Assistant 2.0: Your Music, Your Players

[Maltavius]

Thanks, I learned something.

Changing to host instead.

[klogg]

@Maltavius

I learned something.

Thanks from here too.
I kinda did…
But I know just about enough to be dangerous.

Is this literally all I need to do?
Change my Proxmox Processor Type to ‘host’ and then reboot?

@NathanCu

set processor to ‘host’ unless…

It’s just the ‘unless…’ that has thrown me a bit

---

A quick question, if there is a short answer, I don’t expect a full virtualisation seminar…

Is there any reason ‘host’ shouldn’t always be the default?
Unless there is a very specific reason why would you ever want to use something else?

[NathanCu (Nathan Curtis)]

…Unless you’re using Proxmox in a cluster where you intend to bounce the workload around. In that case then you should lock and define the processor capabilities so you don’t send your workload to an incompatible host by accident. For that you must know your workload.

But I also am not a fan of running clusters at home so the chance of that is quite low. It’s the only reason I can image needing it but. If you’re doing that I’d lock the proc selector. The prox scripts are setting it to the least common known good. Safe yes but… *points