Edit added dayS later: OP hasn't logged in, which often seems to happen with these one shot 'needful' of:
http://www.catb.org/~esr/faqs/smart-questions.html
An important 'soft skill' when dealing with any problem
Is to: provide enough details, so that your helper could
reproduce the problem.
I am wild-guessing (from a quick web search of: owasp bwa) that you're doing something like:
https://subscription.packtpub.com/bo...ling-owasp-bwa
Since web-searching (and telling what you did to try to find a solution to the problem for which you provided complete and understandable steps to reproduce) is the number one 'soft skill' (for any and every topic, not just technology), the next thing I web-searched is the kernel Panic message you got: i386_start_kernel
Actually, that is likely the
bottom of the stack; you want the
top of the stack, after many very different things may have happened. Take time to look at the various call traces you will find from web searching that function name. Let us know the top and if anything mentions idle.
I found something that mentions adding this kernel boot parameter:
intel_idle.max_cstate=1
(IF you don't know how to use: kernel boot parameters, please Google that.)
I vaguely remember needing to add that (probably 10yo 32-bit XP host) but I don't remember what I learned from web-researching why.
Let us know. Also,
please click Edit on your original post, then click 'Go Advanced'. Change the title from screaming
HELP ME!!!, to something like: Booting OWASP-BWA .vmdk guest on Win10 host gives panic with i386_start_kernel in backtrace
(Actually, change that to something more relevant: towards the top of the stack)
I am guessing you're familiar with running other VMs in virtualbox (I enjoy the trivial
MLL .iso), in which case the problem would be your 'soft skills', which I mentioned above. Best wishes!!! Please do the needful of posting the solution, as a contribution to future web-searchers who encounter this.
"Help Me!!"
