io.kamax.hboxd.hypervisor.Hypervisor missing element version

[Matias Ribichich]

Hi there, I'm trying to use the hyperbox, but when I try to connect to the hypervisor the window dialog comes empty.

I'm using:

windows 7 x64

hyperbox 0.13

java: jre-8u101-windows-x64

virtualbox: VirtualBox-5.1.0-108711-Win and also tried VirtualBox-5.1.2-108956-Win

Thanks!

The logs says this:

+==============================================================+

 Log start on 31/07/2016 @ 20:00:04           +

+==============================================================+

Hyperbox 0.0.13 - Java 1.8.0_101 Java HotSpot(TM) 64-Bit Server VM 25.101-b13 - Windows 7 6.1 amd64

2016.07.31-20:00:04.030 |      Info | Hyperbox Init Sequence started

2016.07.31-20:00:07.979 |      Info | Server ID: af244c84-0dc6-49a5-a406-b8ad4196abd3

2016.07.31-20:00:07.979 |      Info | Server Name: WIN-2TCHN0BRKF1

2016.07.31-20:00:08.900 |      Info | Refreshing modules...

2016.07.31-20:00:08.900 |      Info | Searching in C:\Program Files\Hyperbox\Server\modules for modules...

2016.07.31-20:00:08.900 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-4_2-ws.xml

2016.07.31-20:00:08.931 |      Info | Module ID vbox-4_2-ws (Virtualbox 4.2 WebService Connector) was successfully registered

2016.07.31-20:00:09.134 |      Info | Module ID vbox-4_2-ws (Virtualbox 4.2 WebService Connector) was autoloaded

2016.07.31-20:00:09.134 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-4_2-xpcom.xml

2016.07.31-20:00:09.149 |      Info | Module ID vbox-4_2-xpcom (VirtualBox 4.2 XPCOM Connector) was successfully registered

2016.07.31-20:00:09.648 |      Info | Module ID vbox-4_2-xpcom (VirtualBox 4.2 XPCOM Connector) was autoloaded

2016.07.31-20:00:09.648 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-4_3-ws.xml

2016.07.31-20:00:09.664 |      Info | Module ID vbox-4_3-ws (Virtualbox 4.3 WebServices Connector) was successfully registered

2016.07.31-20:00:09.992 |      Info | Module ID vbox-4_3-ws (Virtualbox 4.3 WebServices Connector) was autoloaded

2016.07.31-20:00:09.992 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-4_3-xpcom.xml

2016.07.31-20:00:09.992 |      Info | Module ID vbox-4_3-xpcom (VirtualBox 4.3 XPCOM Connector) was successfully registered

2016.07.31-20:00:10.054 |      Info | Module ID vbox-4_3-xpcom (VirtualBox 4.3 XPCOM Connector) was autoloaded

2016.07.31-20:00:10.054 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-5_0-ws.xml

2016.07.31-20:00:10.070 |      Info | Module ID vbox-5_0-ws (Virtualbox 5.0 WebService Connector) was successfully registered

2016.07.31-20:00:10.163 |      Info | Module ID vbox-5_0-ws (Virtualbox 5.0 WebService Connector) was autoloaded

2016.07.31-20:00:10.163 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-5_0-xpcom.xml

2016.07.31-20:00:10.179 |      Info | Module ID vbox-5_0-xpcom (Virtualbox 5.0 XPCOM Connector) was successfully registered

2016.07.31-20:00:10.226 |      Info | Module ID vbox-5_0-xpcom (Virtualbox 5.0 XPCOM Connector) was autoloaded

2016.07.31-20:00:10.226 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-5_1-ws.xml

2016.07.31-20:00:10.226 |      Info | Module ID vbox-5_1-ws (Virtualbox 5.1 WebService Connector) was successfully registered

2016.07.31-20:00:10.350 |      Info | Module ID vbox-5_1-ws (Virtualbox 5.1 WebService Connector) was autoloaded

2016.07.31-20:00:10.350 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-5_1-xpcom.xml

2016.07.31-20:00:10.366 |      Info | Module ID vbox-5_1-xpcom (Virtualbox 5.1 XPCOM Connector) was successfully registered

2016.07.31-20:00:10.397 |      Info | Module ID vbox-5_1-xpcom (Virtualbox 5.1 XPCOM Connector) was autoloaded

2016.07.31-20:00:10.397 |      Info | Finished refreshing modules.

2016.07.31-20:00:10.397 |      Info | No Hypervisor configuration found, skipping

2016.07.31-20:00:10.397 |      Info | Starting Front-ends

2016.07.31-20:00:10.538 |      Info | Kryonet connector is listening on port 45612

2016.07.31-20:00:10.538 |      Info | KryonetServerFront has started

2016.07.31-20:00:10.538 |      Info | Done starting Front-ends

2016.07.31-20:00:10.538 |      Info | -------> Hyperbox is running <-------

2016.07.31-20:00:24.734 |      Info | Conn #1 192.168.1.66 connected.

2016.07.31-20:00:27.636 | Exception | SessWT - Session #1470006024734 - Connection #1 | TaskManager

java.lang.annotation.IncompleteAnnotationException: io.kamax.hboxd.hypervisor.Hypervisor missing element version

at sun.reflect.annotation.AnnotationInvocationHandler.invoke(Unknown Source)

at com.sun.proxy.$Proxy3.version(Unknown Source)

at io.kamax.hboxd.comm.io.factory.HypervisorIoFactory.getOut(HypervisorIoFactory.java:60)

at io.kamax.hboxd.core.action.hypervisor.HypervisorList.run(HypervisorList.java:63)

at io.kamax.hboxd.task.TaskManager$TaskWorker.execute(TaskManager.java:158)

at io.kamax.hboxd.task.TaskManager.process(TaskManager.java:110)

at io.kamax.hboxd.session.AbstractSession.run(AbstractSession.java:153)

at java.lang.Thread.run(Unknown Source)

[Maxime Dor]

Has been answered here: https://github.com/hyperbox/hyperbox/issues/8