CPU temp monitoring is way off for me. Graph shows a constant 31-32C on all cores (even under load), while
Code:
sysctl -a | grep temp
shows temps about 15-20C higher than that. CPU is an FX-8120 (which I know has terrible temp reporting anyway), but people should know that they cannot rely on the current state of the temp graph in the UI. I'm really happy this was added but it's not yet usable as is.
Another issue I'm having is trying to install a Win 10 VM always gets stuck at "installing updates" during the setup screen, I left it there for a few hrs with no changes. If I try to quit and boot back up it drops me into the shell, I try to exit and find the boot file manually but it's not where it should be so the install never completed. This is better than 11.0-U4 which never made it past the splash screen before install though. Ubuntu VM still runs fine, only Windows has this issue. (*See Edit)
Thanks for adding VNC resolution settings, that was huge for me.
I have to say I'm not a huge fan of the new UI. It seems like it has less info than it used to (especially in reporting, I have to hover the mouse to get values rather than just seeing them below the graph) and wastes more space to give you the same info. It also takes longer to navigate using the new "minimalist" look. I usually am all for minimalist but not if it makes it harder to navigate and get info.
Thanks for your hard work guys. I hope the remaining bugs can get ironed out soon.
*Edit: I was able to install Windows after all. The issue was that the default setting in loader for number of CPUs per socket was 1. Since Win10 Pro can't do more than 2 sockets it was failing when I allocated more than 2 virtual cores to the VM. I installed it with only 1 virtual core and it ran fine. When I tried to give it more virt cores after install it only was able to see two of them. I then changed the setting in the loader.conf to 8 CPU cores per socket (which is what my CPU has) and Windows was able to recognize all the allocated virtual cores.