5 ms·

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

by parthy 3y ago

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?

gonzodaruler 3y ago
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>`
- stevemk14ebr 3y ago
  User error, I had to discard the snapshot state first - just like in normal vbox ;)