Is it possible to run asl3 on Hyperv VM as a “Hub” only without having to map a sound card from host machine. If so, is it working well? I’m wanting to setup a test environment with 1VM acting as the “server” with 2 remote nodes communicating through it.
As long as your talking about a full virtualized Debian 12 instance in HyperV and not the integrated WSL/WSL2 stack, you shouldn’t have any issues.
Good Deal. Next on the todo list! I’m not sure if i need to introduce another variable in my learning process but i have a nice data center 2016 server doing nothing and tons of bandwidth and thought it could be more useful putting it to work. If all works out i could easily provide private node servers for anyone that may want to use for testing. One static public ip address for each VM.
Prior to ASL3, I did some testing with VM’s and ended up with stuttering issues using Hyper-V. The VM was allocated multiple cores and I believe I tested with up to 16 GB of RAM and still had the issue. I moved it to another server that was on VmWare and no stuttering. In the end, I ended up moving it to a micro PC with Linux installed to bare metal to host the 5 nodes.
Hopefully Hyper-V does better with ASL3. I can also tell you both Server 2019 and 2022 do better with real-time apps in Hyper-V than 2016 does, so if updating the underlying server OS is an option, you might have more luck there as well.
Ok. good to know and thanks much for that info. I misstated my server, and it is 2022 data center not 2016 thankfully. When i get the chance to implement i can update.
Having 2022 is much much better than 2016. HyperV wasn’t all that great until recently.
1 Like
Absolutely, I have Hyper-V 2019 running on a Dell R630 and am having no issues related to virtualization; it works just fine.
1 Like
Just a quick update. Wish I started on this sooner as it’s a real nice setup! I have 3 VM instances running each on their own public ip and a few test nodes here and there and it hasn’t skipped a beat. Good stuff! Thanks for the info.