This seems to be the case when xen is running as dom0. Or at least that seems to be happening. When its running a "regular" linux kernel, the procinfo has the vmx flag, otherwise when xen is running as dom0 it doesn't (maybe xen stops that from being seen?) I think there is a previous error that is causing this, not this message being the error.
On 8/17/11 5:15 AM, "Chmouel Boudjnah" <launch...@chmouel.com> wrote: On Aug 16, 2011, at 5:06 PM, Joshua Harlow wrote: 2011-08-16 16:58:35,459 ERROR nova.compute.manager [-] Instance '4' failed to spawn. Is virtualization enabled in the BIOS? Details: POST operation failed: xend_post: error from xen daemon: (xend.err "(22, 'Invalid wouldn't be that the problem ? Chmouel.
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
