That's odd about the core count. I only get that behavior if my host system only has 1 CPU to begin with (tested in qemu/KVM with nesting). Could you comment on your host system parameters a bit?
Re:VirtualBox KVM Public Release
by gonzodaruler on Thursday February 08, 2024 @12:31PM
(#39304844)
This is definitively not expected. You could also try setting the CPU/Mem configuration via VBoxManage. Maybe you get a good error message then.
`VBoxManage modifyvm <vm_name> --cpus <number of cpus>`
`VBoxManage modifyvm <vm_name> --memory <amout of memory in MB>`
Re:VirtualBox KVM Public Release
by stevemk14ebr on Thursday February 08, 2024 @01:55PM
(#39305967)
User error, I had to discard the snapshot state first - just like in normal vbox ;)
I built and tried this, it worked great, so excellent work there. I found the processor CPU core counts being grayed out unpleasant, it's not clear to me how I am supposed to adjust my core and ram values now, maybe document this?