[prev in list] [next in list] [prev in thread] [next in thread] 

List:       libvirt-users
Subject:    Re: [Query] Facing issue in build libvirt6.0 on ubuntu 1804
From:       Ramesh B <rmsh.b4 () gmail ! com>
Date:       2020-04-30 12:48:04
Message-ID: CAJvkk917xdfr4S29oESB-kUCyUx1TZwSXP3vtLjji+s33v=A5g () mail ! gmail ! com
[Download RAW message or body]

Thanks, I'll check it out.

On Thu, Apr 30, 2020, 6:02 PM Michal Privoznik <mprivozn@redhat.com> wrote:

> On 4/30/20 2:26 PM, Ramesh B wrote:
> > Hi Michel,
> >
> > Thanks for quick update.
> >
> >    Weird. I have slightly older version and it works for me. Maybe
> > configure is picking something else, some weird binary/python script?
> >
> > *=>* I have python 3.6 version, is it required latest version e.g Python
> > 3.8 ?
>
> No. I meant that perhaps configure was picking the script from say
> /usr/local/bin, e.g. some local, self installed version which is broken.
>
> >
> >
> >   Ideally, you would construct the domain XML to match the command line
> > and then use 'virsh define' to store the XML in libvirt. From that point
> > on, libvirt will know about the domain and you can use all libvirt APIs
> > to control it.
> >
> > *=>*   could you please share sample xml & commands for reference to try
> > above procedure.
> >             Few Qemu parameters are as follows,
> >            -m 2048 -smp 2 -M q35
> >            -enable-kvm
> >            --cpu host
>
> <domain type='kvm>
>    <name>fedora</name>
>    <memory unit='GiB'>2</memory>
>    <vcpu>2</vcpu>
>    <os>
>      <type arch='x86_64' machine='q35'>hvm</type>
>    </os>
>    <cpu mode='host-passthrough' check='none'>
>      <topology sockets='1' dies='1' cores='2' threads='2'/>
>    </cpu>
>    <devices>
>      <emulator>/usr/bin/qemu-system-x86_64</emulator>
>    </devices>
> </domain>
>
> Michal
>
>

[Attachment #3 (text/html)]

<div dir="auto">Thanks, I&#39;ll check it out.  </div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 30, 2020, 6:02 PM \
Michal Privoznik &lt;<a href="mailto:mprivozn@redhat.com">mprivozn@redhat.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On 4/30/20 2:26 PM, Ramesh B \
wrote:<br> &gt; Hi Michel,<br>
&gt; <br>
&gt; Thanks for quick  update.<br>
&gt; <br>
&gt;      Weird. I have slightly older version and it works for me. Maybe<br>
&gt; configure is picking something else, some weird binary/python script?<br>
&gt; <br>
&gt; *=&gt;* I have python 3.6 version, is it required latest  version e.g Python \
<br> &gt; 3.8 ?<br>
<br>
No. I meant that perhaps configure was picking the script from say <br>
/usr/local/bin, e.g. some local, self installed version which is broken.<br>
<br>
&gt; <br>
&gt; <br>
&gt;     Ideally, you would construct the domain XML to match the command line<br>
&gt; and then use &#39;virsh define&#39; to store the XML in libvirt. From that \
point<br> &gt; on, libvirt will know about the domain and you can use all libvirt \
APIs<br> &gt; to control it.<br>
&gt; <br>
&gt; *=&gt;*     could you please share sample xml &amp; commands for reference to \
try <br> &gt; above procedure.<br>
&gt;                    Few Qemu parameters are as follows,<br>
&gt;                   -m 2048 -smp 2 -M q35<br>
&gt;                   -enable-kvm<br>
&gt;                  --cpu host<br>
<br>
&lt;domain type=&#39;kvm&gt;<br>
     &lt;name&gt;fedora&lt;/name&gt;<br>
     &lt;memory unit=&#39;GiB&#39;&gt;2&lt;/memory&gt;<br>
     &lt;vcpu&gt;2&lt;/vcpu&gt;<br>
     &lt;os&gt;<br>
        &lt;type arch=&#39;x86_64&#39; machine=&#39;q35&#39;&gt;hvm&lt;/type&gt;<br>
     &lt;/os&gt;<br>
     &lt;cpu mode=&#39;host-passthrough&#39; check=&#39;none&#39;&gt;<br>
        &lt;topology sockets=&#39;1&#39; dies=&#39;1&#39; cores=&#39;2&#39; \
threads=&#39;2&#39;/&gt;<br>  &lt;/cpu&gt;<br>
     &lt;devices&gt;<br>
        &lt;emulator&gt;/usr/bin/qemu-system-x86_64&lt;/emulator&gt;<br>
     &lt;/devices&gt;<br>
&lt;/domain&gt;<br>
<br>
Michal<br>
<br>
</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]