With KVM as Hypervisor Selected, BIOS Capability Not Checked

[Stephan Fabel]

FUEL collects syslog messages by default and during bootstrap/deployment. If the BIOS does not support KVM virtualization, the kernel will syslog[ERR]:

    kernel: kvm: disabled by bios

This is obviously prohibitive to deployment of the cloud. FUEL should point this out to the operator rather drastically, instead of relying on him/her to scan the logs for this error.

[Vladimir Kuklin (vkuklin)]

Stephan, thank you for posting this bug. Actually, you are still able to deploy controllers/ceph/cinder nodes without KVM virtualization. Unfortunately, we have reached 5.1 release code freeze stage and this bug severity is not so high as hardware virtualization support is included into requirements for your cloud deployment. We will ensure that this is pointed rigorously in the documentation and we will work on the fix for upcoming release.

[Irina Povolotskaya (ipovolotskaya)]

Should this be added into Release notes?
It there any workaround?

[Stephan Fabel (sfabel)]

Irina, good idea. Definitively add a note to release notes at least. While
not being prohibitive to deploying nodes, it *is* invasive enough IMHO that
it warrants mentioning.

On Fri, Sep 19, 2014 at 4:04 AM, Irina <email address hidden> wrote:

> Should this be added into Release notes?
> It there any workaround?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1370670
>
> Title:
> With KVM as Hypervisor Selected, BIOS Capability Not Checked
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/fuel/+bug/1370670/+subscriptions
>

--
Be true to your work, your word and your friend. - H.D. Thoreau
Never tell a lie when you can bullshit your way through. - E. Ambler, *Dirty
Story*

[Mike Scherbakov (mihgen)]

This bug largely intersects with https://blueprints.launchpad.net/fuel/+spec/auto-virt-type. Actually, I believe we should rather implement auto-detection, with possible correction of virt type by user. See blueprint for more details.
It has to be prioritized in the Roadmap, as I believe it affects partners too (to make heterogenous envs with both VMWare & KVM, for example).

[Stephan Fabel (sfabel)]

Please don't mark this bug as invalid without giving explanation. Thanks

[Dmitry Pyzhov (dpyzhov)]

Sorry. As Mike wrote, it is not a bug, it is a feature request. And it will be delivered with https://blueprints.launchpad.net/fuel/+spec/auto-virt-type blueprint.