2012/5/25 Pádraig Brady <[email protected]> > On 05/25/2012 09:10 AM, Patrick Petit wrote: > > > > > > 2012/5/24 Pádraig Brady <[email protected] <mailto:[email protected]>> > > > > On 05/24/2012 02:49 PM, Patrick Petit wrote: > > > > > > > > > 2012/5/24 Pádraig Brady <[email protected] > > <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>> > > > > > > On 05/24/2012 01:26 PM, Patrick Petit wrote: > > > > Hi Pádraig, > > > > > > > > Thank you for your reply. > > > > > > > > I applied the suggested libvirt_inject_partition = -1 > > > > > > > > It does change things because it's not complaining about > mount error any more but generates further errors down the path in > libvirt.py" > > > > > > > 2012-05-24 14:11:54 TRACE nova.compute.manager [instance: > a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31] File > "/usr/lib64/python2.7/site-packages/libvirt.py", line 540, in > createWithFlags > > > > 2012-05-24 14:11:54 TRACE nova.compute.manager [instance: > a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31] if ret == -1: raise libvirtError > ('virDomainCreateWithFlags() failed', dom=self) > > > > 2012-05-24 14:11:54 TRACE nova.compute.manager [instance: > a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31] libvirtError: internal error Process > exited while reading console log output: char device redirected to > /dev/pts/2 > > > > 2012-05-24 14:11:54 TRACE nova.compute.manager [instance: > a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31] Could not allocate dynamic translator > buffer > > > > > > That's libvirt specific. > > > > > > Do you have "Virtual Machine" support enabled in your BIOS? > > > If not the fallback mode is currently disallowed by SELinux, > > > and you can enable with: setsebool -P virt_use_execmem=on > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=753589#c36 > > > > > > It's quite a non specific error so it could be something else. > > > > > > I am running the all OpenStack in a virtual machine under VBox. > > > nova.conf has libvirt_type = qemu > > > > > > Disabling SELinux solved the problem. > > > Shouldn't that be reported as a bug? > > > > I think the bug referenced above captures the issue sufficiently. > > What I've done is to document the specific SELinux setting above, > > to enable this mode of operation, in the fedora/epel wiki where > > you said you were following the instructions. > > > > > > Pádraig, > > > > Shouldn't the packages installation scripts take care of the SElinux > configuration settings and make that transparent to end-users? > > After all, we might expect that once the various packages are installed > on that distribution OpenStack just works out-of-the-box. > > As far as possible, yes. > > However I'd be wary about auto setting that parameter as the user > could be using the VM for something else and so this security > relaxation needs to be done explicitly at present. > > Also installing to a VM is not a production deployment scenario, > so documenting the setting for testing/dev is OK for now I think. >
Sure. sounds good to me. Thank you for fixing the documentation. Cheers, Patrick > > We'll continue to monitor this issue and perhaps be able to work around it > in future. > > cheers, > Pádraig. > -- *"Give me a place to stand, and I shall move the earth with a lever"*
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
