Opened 16 years ago
Closed 12 years ago
#4107 closed defect (worksforme)
Problems with ubuntu vbox and XPCOM C++ binding
Reported by: | xfernandez | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.2.2 |
Keywords: | C++ XPCOM binding | Cc: | |
Guest type: | other | Host type: | Linux |
Description (last modified by )
Hi people
When I try to run the C++ binding XPCOM example appears an error on the Ubuntu host (Tested on lastest and penultimate release). The error is the next one:
Error, could not instantiate VirtualBox object! rc=0x80004005
I have tested with Fedora and CentOS and it works.
It seams that there is a dependency that it isn't on Ubuntu.
Some help about this?
Attachments (1)
Change History (12)
comment:1 by , 16 years ago
by , 16 years ago
comment:3 by , 16 years ago
I did not find any obvious problem in the log. Does a VBoxManage list vms work on the same host?
comment:6 by , 15 years ago
xfernandez, let me ask some basic questions, just to be sure your setup is correct:
- are you able to start VMs?
- which VBox version is that, still 2.2.2?
- which package did you install on that Ubuntu host (exact package name please)
comment:7 by , 15 years ago
Hi
I can start VMs using the basic
2.2.4 (I don't want to update to 3.0.x because I have some development do it based on this API). Has The API specification been updated on this new release?
Distributor ID: Ubuntu Description: Ubuntu 9.04 Release: 9.04 Codename: jaunty
Thank you
comment:8 by , 15 years ago
Yes, but VBox 2.2.4 is fine as well. So you installed the Ubuntu package from our website, I assume the 32-bit version?
comment:9 by , 15 years ago
I use "sudo aptitude install virtualbox-2.2"
Yes I think that is 32-bit :P
Thanks
comment:10 by , 15 years ago
Still no idea what's wrong. You don't work with sudo or something like that, do you? What happens if you start the VBoxSVC daemon in a separate console/xterm and then start the XPCOM example from another console/xterm?
comment:11 by , 12 years ago
Description: | modified (diff) |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
No response, obsolete.
So you are using VirtualBox 2.2.2 for this test, right?
Please execute the testVBoxAPILinux example like this:
Then compress the resulting file ~/log and attach it to this defect.