<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 09/02/2015 18:30, Thierry Fauck (
thierry @ linux.vnet.ibm.com ) wrote:<br>
</div>
<blockquote cite="mid:54D918CA.5000203@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 02/09/15 15:55, Aline Manera
wrote:<br>
</div>
<blockquote cite="mid:54D8CA44.60002@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">On 06/02/2015 14:54, Thierry <a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:Fauck@linux.vnet.ibm.com">Fauck@linux.vnet.ibm.com</a>
wrote:<br>
</div>
<blockquote cite="mid:54D4F1DF.8020906@linux.vnet.ibm.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
I forgot, on trusty, qemu-kvm doesn't exist as is, <br>
<br>
and when I try to create a template I get errors like:<br>
<blockquote>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.<br>
</blockquote>
<br>
So 2 issues there<br>
- in trusty get a proper qemu version to avoid messages <br>
<blockquote>error: internal error: process exited while
connecting to monitor: Warning: Disabling some instructions
which are not emulated by TCG (0x0, 0x4)<br>
qemu: hardware error: qemu: could not load LPAR rtas
'(null)'<br>
</blockquote>
- in kimchi, detect if kvm not a valid domain type then use
qemu <br>
</blockquote>
<br>
When kvm will not be a valid domain? Some dependency on package
version?<br>
</blockquote>
yes - on trusty there is no qemu-kvm package by default<br>
and virsh capabilities show the domain type for arch ppc64 as qemu
only - on utopic it shows kvm and qemu.<br>
The issue is the same for x86_64 arch.<br>
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 ?<br>
Thanks<br>
</blockquote>
<br>
Ok - I am OK to switch to qemu when kvm is not present but the
default must continue to be kvm.<br>
You can use conn.getCapabilities() to get the available options for
that according to arch.<br>
<br>
<blockquote cite="mid:54D918CA.5000203@linux.vnet.ibm.com"
type="cite">
<blockquote cite="mid:54D8CA44.60002@linux.vnet.ibm.com"
type="cite"> <br>
<blockquote cite="mid:54D4F1DF.8020906@linux.vnet.ibm.com"
type="cite"> <br>
Does that sound an issue ? - do you want me to code that ?<br>
Thanks<br>
<pre class="moz-signature" cols="72">--
Thierry Fauck @ linux.vnet.ibm</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Thierry Fauck (<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:thierry@linux.vnet.ibm.com">thierry@linux.vnet.ibm.com</a>)</pre>
</blockquote>
<br>
</body>
</html>