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.
cheers,
Pádraig.
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
