I installed kvm and nova computer in same machine, but <span id="result_box" class="short_text" lang="en"><span class="hps">occurred a </span></span>error:<br><br>2011-10-26 18:47:05,936 ERROR nova.exception [-] Uncaught exception<br>
(nova.exception): TRACE: Traceback (most recent call last):<br>(nova.exception): TRACE: File "/usr/lib/python2.7/dist-packages/nova/exception .py", line 98, in wrapped<br>
(nova.exception): TRACE: return f(*args, **kw)<br>(nova.exception): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/libv irt/connection.py", line 673, in spawn<br>
(nova.exception): TRACE: self.firewall_driver.setup_basic_filtering(instance , network_info)<br>(nova.exception): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/libv irt/firewall.py", line 525, in setup_basic_filtering<br>
(nova.exception): TRACE: self.refresh_provider_fw_rules()<br>(nova.exception): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/libv irt/firewall.py", line 737, in refresh_provider_fw_rules<br>
(nova.exception): TRACE: self._do_refresh_provider_fw_rules()<br>(nova.exception): TRACE: File "/usr/lib/python2.7/dist-packages/nova/utils.py" , line 687, in inner<br>
(nova.exception): TRACE: with lock:<br>(nova.exception): TRACE: File "/usr/lib/pymodules/python2.7/lockfile.py", line 223, in __enter__<br>
(nova.exception): TRACE: self.acquire()<br>(nova.exception): TRACE: File "/usr/lib/pymodules/python2.7/lockfile.py", line 239, in acquire<br>
(nova.exception): TRACE: raise LockFailed("failed to create %s" % self.uniqu e_name)<br>(nova.exception): TRACE: LockFailed: failed to create /usr/lib/python2.7/dist-pa ckages/OPSTACK-CTR-02.Dummy-9-23053<br>
(nova.exception): TRACE:<br>2011-10-26 18:47:05,937 ERROR nova.compute.manager [-] Instance '10' failed to s pawn. Is virtualization enabled in the BIOS? Details: failed to create /usr/lib/ python2.7/dist-packages/OPSTACK-CTR-02.Dummy-9-23053<br>
(nova.compute.manager): TRACE: Traceback (most recent call last):<br>(nova.compute.manager): TRACE: File "/usr/lib/python2.7/dist-packages/nova/com pute/manager.py", line 424, in _run_instance<br>
(nova.compute.manager): TRACE: network_info, block_device_info)<br>(nova.compute.manager): TRACE: File "/usr/lib/python2.7/dist-packages/nova/exc eption.py", line 129, in wrapped<br>
(nova.compute.manager): TRACE: raise Error(str(e))<br>(nova.compute.manager): TRACE: Error: failed to create /usr/lib/python2.7/dist-p ackages/OPSTACK-CTR-02.Dummy-9-23053<br>
(nova.compute.manager): TRACE:<br><br><br><div class="gmail_quote">2011/10/26 Sharif Islam <span dir="ltr"><<a href="mailto:islamsh@indiana.edu">islamsh@indiana.edu</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div>On 10/26/2011 03:30 PM, Roberto Dalas Z. Benavides wrote:<br>
> I have a server with all the novaservices it and on another server I<br>
<div class="im">> have installed kvm.<br>
> As the new will know what he kvm server will create the machine in?<br>
<br>
<br>
</div>Ok. the server you have kvm, you will need to install nova-compute and<br>
in nova.conf file add --libvirt_type=kvm along with the other options.<br>
This way nova services will know which server to use.<br>
<div class="im"><br>
<br>
> For example: I use the vmware vmwareapi User data information and<br>
> password. But in kvm?<br>
<br>
</div>I think this will depend how you create your images. You can add a local<br>
user in the image or as I mentioned before use a ssh key which will be<br>
injected by nova as it boots up.<br>
<br>
- --sharif<br>
<div class="im">-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
<br>
</div>iQEcBAEBAgAGBQJOqGLsAAoJEACffes9SivFZMQIALchlwetKfSF5NIT4P2EzK2d<br>
Gp7MTDLm77ATJ2XC2bhdZiHR64wdyC6ehjmHoyl5JBHcQWP6cECFuS93Yc1D8cc1<br>
kmTKSNXtKxvn0eKxCPyARohIaJO2rXMHGEhZTr5amOx31uuebbAVpU+ONJkaw6zP<br>
nlNvNwqfxAefHicD3jMYY+PSrQWSRDy6oxWHh5ctNDtVF0b7o3jjY7D+RzhO2gNi<br>
dUuBHqsQQTiqmp5bRFQ0uh+nvPFTFEqazzpbS4uMRWRTXi2PVjWZLoBMZU9+Tl7g<br>
aRbpmBOdebhsaqsvYI2vKqzR5kXRdrulRpZUGUxHIEZW6XfItvBHnVEegxyLH8g=<br>
=aJjg<br>
<div><div></div><div class="h5">-----END PGP SIGNATURE-----<br>
_______________________________________________<br>
Openstack-operators mailing list<br>
<a href="mailto:Openstack-operators@lists.openstack.org">Openstack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</div></div></blockquote></div><br>