It would be useful to be able to set more than 512GB of ram from the GUI, along with the ability to use more than 30 virtual CPU's. We can get around this by increasing the core count, but I would prefer to keep things the same across the board.
If I increase the socket count I can run more but not more than 30 with a single socket. I have to wonder why you guys create your own limitations, I am guessing there must be some type of reasoning to not follow suite with what KVM can do. The larger issue is setting the ram above 512GB.
Just out of curiosity, may I inquire about your use case? Because that high a number of cores makes me believe that you're dealing with some sort of HPC system, which generally should not be virtualized.
Additionally the most cores on a single actual (i.e. not xeon phi) x86_64 (i.e. not SPARC) cpu I can see would be 16core opterons and using more qemu cores than you have physically available is very bad for performance.
Just out of curiosity, may I inquire about your use case? Because that high a number of cores makes me believe that you're dealing with some sort of HPC system, which generally should not be virtualized.
Additionally the most cores on a single actual (i.e. not xeon phi) x86_64 (i.e. not SPARC) cpu I can see would be 16core opterons and using more qemu cores than you have physically available is very bad for performance.
It was for simplicity sake during setup on the bench. They are dual socket E5-2690 v2's, with hyper threading that is 20 cores, so that means I can give a single VM 30+ vcpu's. We have an interesting use case, but it is working out quite well for us.