[Openstack-operators] [vmware][nova] "could not find capabilities for domaintype=kvm"

José Manuel Hernández josemhb at gmail.com
Tue Mar 8 07:47:24 UTC 2016


Hi all,

The steps are valid for vsphere webclient.

@Adam, you can upgrade virtual harware in the vsphere client (web cliet is
recomended) , with the virtual machine power off, right clic and "Upgrade
virtual hardware".

Regards,
Jose Manuel Hernandez

2016-03-08 8:32 GMT+01:00 Geo Varghese <gvarghese at aqorn.com>:

> Hi Jose,
>
> Thnaks for the detailed steps.
>
> Can you please tell us, is these steps for vsphere client or vshpere
> webclient?
>
> On Mon, Mar 7, 2016 at 6:46 PM, José Manuel Hernández <josemhb at gmail.com>
> wrote:
>
>> Hi all,
>>
>> For running KVM on ESX you need to make some changes:
>>
>>
>>    1. Edit the virtual machine Hardware (harware virtual 9  or higher)
>>    2. Select "Linux" as the guestOS Family and "Other Linux (64-bit)" as
>>    the guestOS Version.
>>    3. During the customize hardware wizard, expand the "CPU" section and
>>    select "Hardware Virtualization" box to enable VHV.
>>    4. Check and enable "Hardware vitualization: Expose hardware assited
>>    virtualization to the guest OS"
>>    5. Complete the wizard
>>
>>
>> I hope this may help you
>>
>> José M. Hernández
>> www.josemhernandez.com
>>
>>
>>
>>
>> 2016-03-07 11:22 GMT+01:00 Daniel P. Berrange <berrange at redhat.com>:
>>
>>> On Fri, Mar 04, 2016 at 11:15:23AM -0800, Adam Lawson wrote:
>>> > Hey all,
>>> >
>>> > We're testing OpenStack Liberty on an ESX host and it installs fine.
>>> When
>>> > attempting to create a VM, receiving an error:
>>> >
>>> > *libvirtError: invalid argument : could not find capabilities for
>>> > domaintype=kvm*
>>> >
>>> > VMware environment is ESX 5.5:
>>> > *Capabilities*
>>> >
>>> > nestedHVSupported = true
>>> >
>>> > Intel VT-X = Supported
>>> >
>>> >
>>> > Is there any obvious ways to solve this or clarify whether this is a
>>> > physical or ESX configuration issue?
>>>
>>> Try running 'virt-host-validate' as root in the guest, and it should tell
>>> you whether the guest running the kvm compute node is configured suitably
>>> for runing KVM and point out any obvious problem it finds.
>>>
>>> Regards,
>>> Daniel
>>> --
>>> |: http://berrange.com      -o-
>>> http://www.flickr.com/photos/dberrange/ :|
>>> |: http://libvirt.org              -o-
>>> http://virt-manager.org :|
>>> |: http://autobuild.org       -o-
>>> http://search.cpan.org/~danberr/ :|
>>> |: http://entangle-photo.org       -o-
>>> http://live.gnome.org/gtk-vnc :|
>>>
>>> _______________________________________________
>>> OpenStack-operators mailing list
>>> OpenStack-operators at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>
>>
>>
>> --
>>
>>
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
>
> --
> --
> Regards,
> Geo Varghese
>



-- 

José M. Hernández
www.josemhernandez.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160308/d0887b29/attachment.html>


More information about the OpenStack-operators mailing list