[JIRA] Issue Comment Edited: (JENKINS-6721) Provide Link to VirtualBox Cloud Setup Documentation

20 views
Skip to first unread message

manan_01@hotmail.com (JIRA)

unread,
Mar 23, 2011, 12:33:59 PM3/23/11
to jenkinsc...@googlegroups.com

[ http://issues.jenkins-ci.org/browse/JENKINS-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147041#comment-147041 ]

mrobinet edited comment on JENKINS-6721 at 3/23/11 4:33 PM:
------------------------------------------------------------

It is worth mentioning that vboxwebsrv is not something bundled with VirtualBox, but rather a separate install:
http://code.google.com/p/vboxweb/wiki/install

I too was lost on this for quite a while until I searched for "vboxwebsrv" and found the project on Google Code.

It does not appear to work with VirtualBox OSE (3.2) either. I was able to get vboxwebsrv working with VirtualBox 4.04 on Ubuntu x64 fairly simply. I get the "Unsupported Content-Type" error message when testing the connection from Jenkins however.

was (Author: mrobinet):
It is worth mentioning that vboxwebsrv is not something bundled with VirtualBox, but rather a separate install:
http://code.google.com/p/vboxweb/wiki/install

I too was lost on this for quite a while until I searched for "vboxwebsrv" and found the project on Google Code.

It does not appear to work with VirtualBox OSE (3.2) either. I was able to get it working with VirtualBox 4.04 on Ubuntu x64 fairly simply though.

> Provide Link to VirtualBox Cloud Setup Documentation
> ----------------------------------------------------
>
> Key: JENKINS-6721
> URL: http://issues.jenkins-ci.org/browse/JENKINS-6721
> Project: Jenkins
> Issue Type: Improvement
> Components: virtualbox
> Reporter: ajag
> Assignee: godin
> Priority: Minor
>
> Hi,
> I have been using both VBox and Hudson quite a while. I came accross the Hudson VirtualBox Plugin. My understanding is that I can use this e.g. to create/clone/start/stop build slaves. So I'd assume that I set up a VDI that could be used as template and manage instances via the plugin. Looking at the plugin configuration section in the hudson config, I'm required to provide a URL to my VirtualBox. In the VirtualBox UI I can't find any options to remote enable my VirtualBox installation neither did I find anything in the documentation. Can you point me to some info and perhaps a link to it what the prerequisites regarding the VirtualBox installation are?
> Thanks and Best Regards,
> ajag

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


manan_01@hotmail.com (JIRA)

unread,
Mar 23, 2011, 1:18:59 PM3/23/11
to jenkinsc...@googlegroups.com

[ http://issues.jenkins-ci.org/browse/JENKINS-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147041#comment-147041 ]

mrobinet edited comment on JENKINS-6721 at 3/23/11 5:17 PM:
------------------------------------------------------------

-It is worth mentioning that vboxwebsrv is not something bundled with VirtualBox, but rather a separate install:-
http://code.google.com/p/vboxweb/wiki/install

-I too was lost on this for quite a while until I searched for "vboxwebsrv" and found the project on Google Code.-

-It does not appear to work with VirtualBox OSE (3.2) either. I was able to get vboxwebsrv working with VirtualBox 4.04 on Ubuntu x64 fairly simply. I get the "Unsupported Content-Type" error message when testing the connection from Jenkins however.-

was (Author: mrobinet):
-It is worth mentioning that vboxwebsrv is not something bundled with VirtualBox, but rather a separate install:
http://code.google.com/p/vboxweb/wiki/install

I too was lost on this for quite a while until I searched for "vboxwebsrv" and found the project on Google Code.

It does not appear to work with VirtualBox OSE (3.2) either. I was able to get vboxwebsrv working with VirtualBox 4.04 on Ubuntu x64 fairly simply. I get the "Unsupported Content-Type" error message when testing the connection from Jenkins however.-

manan_01@hotmail.com (JIRA)

unread,
Mar 23, 2011, 1:19:01 PM3/23/11
to jenkinsc...@googlegroups.com

[ http://issues.jenkins-ci.org/browse/JENKINS-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147041#comment-147041 ]

mrobinet edited comment on JENKINS-6721 at 3/23/11 5:17 PM:
------------------------------------------------------------

-It is worth mentioning that vboxwebsrv is not something bundled with VirtualBox, but rather a separate install:

http://code.google.com/p/vboxweb/wiki/install

I too was lost on this for quite a while until I searched for "vboxwebsrv" and found the project on Google Code.

It does not appear to work with VirtualBox OSE (3.2) either. I was able to get vboxwebsrv working with VirtualBox 4.04 on Ubuntu x64 fairly simply. I get the "Unsupported Content-Type" error message when testing the connection from Jenkins however.-

was (Author: mrobinet):


It is worth mentioning that vboxwebsrv is not something bundled with VirtualBox, but rather a separate install:
http://code.google.com/p/vboxweb/wiki/install

I too was lost on this for quite a while until I searched for "vboxwebsrv" and found the project on Google Code.

It does not appear to work with VirtualBox OSE (3.2) either. I was able to get vboxwebsrv working with VirtualBox 4.04 on Ubuntu x64 fairly simply. I get the "Unsupported Content-Type" error message when testing the connection from Jenkins however.

manan_01@hotmail.com (JIRA)

unread,
Mar 23, 2011, 1:41:00 PM3/23/11
to jenkinsc...@googlegroups.com

[ http://issues.jenkins-ci.org/browse/JENKINS-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147096#comment-147096 ]

mrobinet edited comment on JENKINS-6721 at 3/23/11 5:39 PM:
------------------------------------------------------------

I finally got the test connection working by using http://localhost:18083/. It would not accept my machine name rather than localhost for some reason.

Now I'm stuck at this error when launching the slave:
{noformat}
[VirtualBox] Powering up VirtualBoxMachine{host=VirtualBoxHost{url='http://localhost:18083/', username=''},name='JENKINS_SLAVE'}...
FATAL: org.virtualbox_3_1.RuntimeFaultMsg: VirtualBox error: Argument aNameOrId is empty or NULL (0x80070057)
javax.xml.ws.WebServiceException: org.virtualbox_3_1.RuntimeFaultMsg: VirtualBox error: Argument aNameOrId is empty or NULL (0x80070057)
at com.sun.xml.ws.commons.virtualbox_3_1.IVirtualBox.findMachine(IVirtualBox.java:336)
at hudson.plugins.virtualbox.VirtualBoxUtils.startVm(VirtualBoxUtils.java:57)
at hudson.plugins.virtualbox.VirtualBoxComputerLauncher.launch(VirtualBoxComputerLauncher.java:48)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:197)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.virtualbox_3_1.RuntimeFaultMsg: VirtualBox error: Argument aNameOrId is empty or NULL (0x80070057)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
at $Proxy47.iVirtualBoxFindMachine(Unknown Source)
at com.sun.xml.ws.commons.virtualbox_3_1.IVirtualBox.findMachine(IVirtualBox.java:331)
{noformat}

It seems like a lot of people have reported this problem. I'm guessing rolling back to an older version of VirtualBox would fix it?

was (Author: mrobinet):
I finally got the test connection working by using http://localhost:18083/. It would not accept my machine name rather than localhost for some reason.

Now I'm stuck at this error when launching the slave:
[VirtualBox] Powering up VirtualBoxMachine{host=VirtualBoxHost{url='http://localhost:18083/', username=''},name='JENKINS_SLAVE'}...
FATAL: org.virtualbox_3_1.RuntimeFaultMsg: VirtualBox error: Argument aNameOrId is empty or NULL (0x80070057)
javax.xml.ws.WebServiceException: org.virtualbox_3_1.RuntimeFaultMsg: VirtualBox error: Argument aNameOrId is empty or NULL (0x80070057)
at com.sun.xml.ws.commons.virtualbox_3_1.IVirtualBox.findMachine(IVirtualBox.java:336)
at hudson.plugins.virtualbox.VirtualBoxUtils.startVm(VirtualBoxUtils.java:57)
at hudson.plugins.virtualbox.VirtualBoxComputerLauncher.launch(VirtualBoxComputerLauncher.java:48)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:197)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.virtualbox_3_1.RuntimeFaultMsg: VirtualBox error: Argument aNameOrId is empty or NULL (0x80070057)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
at $Proxy47.iVirtualBoxFindMachine(Unknown Source)
at com.sun.xml.ws.commons.virtualbox_3_1.IVirtualBox.findMachine(IVirtualBox.java:331)

It seems like a lot of people have reported this problem. I'm guessing rolling back to an older version of VirtualBox would fix it?

Reply all
Reply to author
Forward
0 new messages