Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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>`



User error, I had to discard the snapshot state first - just like in normal vbox ;)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: