Discussion:
Heeselicht scenarion, cannot launch linux vm
Parfait Tokponnon
2016-07-05 19:42:42 UTC
Permalink
Hello Genode world,
I'm having this issue when trying to launch linux virtual machine in the
Heeselicht scenario. My machine is a Lenovo X230.

unresolvable exception 3, pd 'init -> cli_monitor -> linux -> vbox', thread
'EMT-1', cpu 0, ip=0x1103ca5, no signal handler
unresolvable exception 3, pd 'init -> cli_munresolvable exceptiononitor ->
linux -> vbox', thread 'EMT-2', cpu 0, ip=0x1103ca5, no signal handler
unresolvable exception 3, pd 'init -> cli_monitor -> linux -> vbox', thread
'EMT-3', cpu 0, ip=0x1103ca5, no signal handler
unresolvable exception 3, pd 'init -> cli_monitor -> linux -> vbox', thread
'VMPwrUp', cpu 0, ip=0x1103cdd, no signal handler
unresolvable exception 3, pd 'init -> cli_monitor -> linux -> vbox', thread
'EMT-0', cpu 0, ip=0x1103cdd, no signal handler

The complete output is attached hereby.
Can someone help me figure out what is going on?
--
Parfait T.
Alexander Boettcher
2016-07-06 08:28:08 UTC
Permalink
Hello,
Post by Parfait Tokponnon
unresolvable exception 3, pd 'init -> cli_monitor -> linux -> vbox', thread
'EMT-1', cpu 0, ip=0x1103ca5, no signal handler
some assertion triggered in Virtualbox. The output of Virtualbox is
routed to the terminal_log 'log' server and not to the output of core,
which you posted above that you got via the serial connection.

Simply start the noux subsystem and look into the /shared/log file,
there you will see more verbose messages from Virtualbox and what went
wrong.

Cheers,

Alex.
Parfait Tokponnon
2016-07-06 13:24:27 UTC
Permalink
Thank you Alex,
The log reports no virtualization hardware acceleration available. So I
just had to enable it and it is fine now.
Regards,

2016-07-06 10:28 GMT+02:00 Alexander Boettcher <
Post by Alexander Boettcher
Hello,
Post by Parfait Tokponnon
unresolvable exception 3, pd 'init -> cli_monitor -> linux -> vbox',
thread
Post by Parfait Tokponnon
'EMT-1', cpu 0, ip=0x1103ca5, no signal handler
some assertion triggered in Virtualbox. The output of Virtualbox is
routed to the terminal_log 'log' server and not to the output of core,
which you posted above that you got via the serial connection.
Simply start the noux subsystem and look into the /shared/log file,
there you will see more verbose messages from Virtualbox and what went
wrong.
Cheers,
Alex.
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
genode-main mailing list
https://lists.sourceforge.net/lists/listinfo/genode-main
--
Parfait T.
Loading...