[Kimchi-devel] Question about KVM domain not available on trusty

[Aline Manera]

On 09/02/2015 18:30, Thierry Fauck ( thierry @ linux.vnet.ibm.com ) wrote:
> On 02/09/15 15:55, Aline Manera wrote:
>>
>> On 06/02/2015 14:54, Thierry Fauck at linux.vnet.ibm.com wrote:
>>> I forgot, on trusty, qemu-kvm doesn't exist as is,
>>>
>>> and when I try to create a template I get errors like:
>>>
>>>     libvirt: QEMU Driver error : unsupported configuration: Domain
>>>     requires KVM, but it is not available. Check that virtualization
>>>     is enabled in the host BIOS, and host configuration is setup to
>>>     load the kvm modules.
>>>
>>>
>>> So 2 issues there
>>> - in trusty get a proper qemu version to avoid  messages
>>>
>>>     error: internal error: process exited while connecting to
>>>     monitor: Warning: Disabling some instructions which are not
>>>     emulated by TCG (0x0, 0x4)
>>>     qemu: hardware error: qemu: could not load LPAR rtas '(null)'
>>>
>>> - in kimchi, detect if kvm not a valid domain type then use qemu
>>
>> When kvm will not be a valid domain? Some dependency on package version?
> yes - on trusty there is no qemu-kvm package by default
> and virsh capabilities show the domain type for arch ppc64 as qemu 
> only - on utopic it shows kvm and qemu.
> The issue is the same for x86_64 arch.
> The question would be - should we use what'is in the release and adapt 
> kimchi for it or should be build what's needed for the product to work ?
> Thanks

Ok - I am OK to switch to qemu when kvm is not present but the default 
must continue to be kvm.
You can use conn.getCapabilities() to get the available options for that 
according to arch.

>>
>>>
>>> Does that sound an issue ? - do you want me to code that ?
>>> Thanks
>>> -- 
>>> Thierry Fauck @ linux.vnet.ibm
>>>
>>>
>>> _______________________________________________
>>> Kimchi-devel mailing list
>>> Kimchi-devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/kimchi-devel
>>
>
>
> -- 
> Thierry Fauck (thierry at linux.vnet.ibm.com)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/kimchi-devel/attachments/20150211/e7603db4/attachment.html>