<div dir="auto"><div><pre style="word-wrap:break-word;white-space:pre-wrap">Hello!
Thank you very much! I had misunderstood how it was suppose to be written in qemu_cmdline. There was a typo in syntax and error log revealed it. It is working IF I use ["-spice", "tls-ciphers=DES-CBC3-SHA"].
So I believe that installation is correctly done.
Though, my problem still exists.
This is what I have been trying to use for qemu_cmdline:
["-cpu", "kvm=off, hv_vendor_id=sometext"]
It does not work and most likely is incorrectly written.
I understood that qemu commands are often exported into xml files and the command I'm trying to write is the following:
<features>
<hyperv>
<vendor_id state='on' value='customvalue'/>
</hyperv>
<kvm>
<hidden state='on'/>
</kvm>
</features>
How do I write this in custom properties for qemu_cmdline?</pre><pre style="word-wrap:break-word;white-space:pre-wrap"><br></pre><pre style="word-wrap:break-word;white-space:pre-wrap">best regards </pre><pre style="word-wrap:break-word;white-space:pre-wrap">Mikko</pre><br><div class="gmail_extra"><br><div class="gmail_quote">On 27 Sep 2017 3:27 pm, "Yedidyah Bar David" <<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Sep 27, 2017 at 1:14 PM, M R <<a href="mailto:gr8nextmail@gmail.com" target="_blank">gr8nextmail@gmail.com</a>> wrote:<br>
> Hello!<br>
><br>
> I did check logs from hosts, but didnt notice anything that would help me. I<br>
> can copy paste logs later.<br>
><br>
> I was not trying to get qemu crash vm.<br>
> I'm trying to add new functionalities with qemu.<br>
><br>
> I wasnt sure if my syntax was correct, so I copy pasted the example command<br>
> for spice from that website. And it still behaves similarly.<br>
><br>
> My conclusion is that qemu cmdline is setup wrong or it's not working at<br>
> all. But I dont know how to check that.<br>
<br>
Please check/share /var/log/libvirt/qemu/* and /var/log/vdsm/* . Thanks.<br>
<br>
><br>
> On 27 Sep 2017 12:32, "Yedidyah Bar David" <<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>> wrote:<br>
>><br>
>> On Wed, Sep 27, 2017 at 11:32 AM, M R <<a href="mailto:gr8nextmail@gmail.com" target="_blank">gr8nextmail@gmail.com</a>> wrote:<br>
>> > Hello!<br>
>> ><br>
>> > I have followed instructions in<br>
>> > <a href="https://www.ovirt.org/develop/developer-guide/vdsm/hook/qemucmdline/" rel="noreferrer" target="_blank">https://www.ovirt.org/develop/<wbr>developer-guide/vdsm/hook/qemu<wbr>cmdline/</a><br>
>> ><br>
>> > After adding any command for qemu cmdline, vm will try to start, but<br>
>> > will<br>
>> > immediately shutdown.<br>
>> ><br>
>> > Is this a bug?<br>
>><br>
>> If you intended, with the params you passed, to make qemu fail, for<br>
>> whatever<br>
>> reason (debugging qemu?), then it's not a bug :-) Otherwise, it is, but we<br>
>> can't know where.<br>
>><br>
>> > or is the information in the link insufficient?<br>
>> > If it would be possible to confirm this and if there's a way to fix, I<br>
>> > would<br>
>> > really like to have step by step guide of how to get this working.<br>
>><br>
>> Did you check relevant logs? vdsm/libvirt?<br>
>><br>
>> Best,<br>
>> --<br>
>> Didi<br>
<br>
<br>
<br>
--<br>
Didi<br>
</blockquote></div></div>
</div></div>