New Question
0

virtualbox driver - error starting nova-compute

asked 2015-05-10 23:30:26 +0300

igraham gravatar image

First off, thank you for the virtualBox driver for OpenStack and the very detailed page at http://www.cloudbase.it/virtualbox-op...

I have followed the installation and all goes pretty well until I get to "Install nova & requirements".

When I try to start nova with: nova-compute --config-file nova_compute.conf

I get ERROR nova.virt.driver [-] Compute driver option required, but not specified

I also did try to start neutron, even with that nova issue. At first the $PATH and $LOGDIR gave some problems but I changed $PATH to be ./etc/policy.json and $LOGDIR to be /opt/stack/logs. When I try to start neutron with: neutron-vbox-agent --config-file neutron_agent.conf

I get a traceback and I see CRITICAL neutron [req-c5c2c181-7067-4e4f-8366-978e1140d46f None] OSError: [Errno 2] No such file or directory

I thought that might be a path to VirtualBox so I did add: vboxmanage_cmd=C:\Program Files\Oracle\VirtualBox\VBoxManage.exe

to the neutronagent.conf, as it is in the novacompute.conf, but that did not help.

I would appreciate any help as it will be really great to be able to run devstack like this in VirtualBox, and learn to much more, just with my laptop.

Regards,

Ian

Notes: I include the following info in case it is helpful to anyone else. Before I could successfully run ./stack.sh I did have to add the bridge to openvswitch with:

sudo ovs-vsctl add-br br-eth1 sudo ovs-vsctl add-port br-eth1 eth1

and also I also added python security with: pip install requests[security]

My VM OS is Ubuntu 14.04 with Python 2.7.6

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
1

answered 2015-05-12 23:45:15 +0300

Hello,

If you are using Ubuntu 14.04 the VBoxManage path cannot be C:\Program Files\Oracle\VirtualBox\VBoxManage.exe because that path is for a Windows host.

If the VBoxManage executable is in a location available in $PATH environment variable you can remove the vboxmanage_cmd from your config file or you can use the default value (vboxmanage_cmd=VBoxMange).

If VBoxManage is not available, then the value of vboxmanage_cmd should be the path to the executable.

Please check if the VirtualBox hypervisor is properly installed on your virtual machine.

If you have any questions or problems please let me know.

Thnaks,

Alex

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

Stats

Asked: 2015-05-10 23:30:26 +0300

Seen: 325 times

Last updated: May 12 '15