top | item 39304106 (no title) parthy | 2 years 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? discuss order hn newest gonzodaruler|2 years 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|2 years ago User error, I had to discard the snapshot state first - just like in normal vbox ;)
gonzodaruler|2 years 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|2 years ago User error, I had to discard the snapshot state first - just like in normal vbox ;)
stevemk14ebr|2 years ago User error, I had to discard the snapshot state first - just like in normal vbox ;)
gonzodaruler|2 years ago
`VBoxManage modifyvm <vm_name> --cpus <number of cpus>`
`VBoxManage modifyvm <vm_name> --memory <amout of memory in MB>`
stevemk14ebr|2 years ago