Hello! I have followed instructions in https://www.ovirt.org/develop/developer-guide/vdsm/hook/qemucmdline/ After adding any command for qemu cmdline, vm will try to start, but will immediately shutdown. Is this a bug?

or is the information in the link insufficient? If it would be possible to confirm this and if there's a way to fix, I would really like to have step by step guide of how to get this working.

Hello! I did check logs from hosts, but didnt notice anything that would help me. I can copy paste logs later. I was not trying to get qemu crash vm. I'm trying to add new functionalities with qemu. I wasnt sure if my syntax was correct, so I copy pasted the example command for spice from that website. And it still behaves similarly. My conclusion is that qemu cmdline is setup wrong or it's not working at all. But I dont know how to check that.

On 27 Sep 2017 12:32, "Yedidyah Bar David" <didi(a)redhat.com&gt; wrote: > > On Wed, Sep 27, 2017 at 11:32 AM, M R <gr8nextmail(a)gmail.com&gt; wrote: > > Hello! > > > > I have followed instructions in > > https://www.ovirt.org/develop/developer-guide/vdsm/hook/qemucmdline/ > > > > After adding any command for qemu cmdline, vm will try to start, but > > will > > immediately shutdown. > > > > Is this a bug? > > If you intended, with the params you passed, to make qemu fail, for > whatever > reason (debugging qemu?), then it's not a bug :-) Otherwise, it is, but we > can't know where. > > > or is the information in the link insufficient? > > If it would be possible to confirm this and if there's a way to fix, I > > would > > really like to have step by step guide of how to get this working. > > Did you check relevant logs? vdsm/libvirt? > > Best, > -- > Didi

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?

best regards Mikko On 27 Sep 2017 3:27 pm, "Yedidyah Bar David" <didi(a)redhat.com&gt; wrote: > > On Wed, Sep 27, 2017 at 1:14 PM, M R <gr8nextmail(a)gmail.com&gt; wrote: > > Hello! > > > > I did check logs from hosts, but didnt notice anything that would help > > me. I > > can copy paste logs later. > > > > I was not trying to get qemu crash vm. > > I'm trying to add new functionalities with qemu. > > > > I wasnt sure if my syntax was correct, so I copy pasted the example > > command > > for spice from that website. And it still behaves similarly. > > > > My conclusion is that qemu cmdline is setup wrong or it's not working at > > all. But I dont know how to check that. > > Please check/share /var/log/libvirt/qemu/* and /var/log/vdsm/* . Thanks. > > > > > On 27 Sep 2017 12:32, "Yedidyah Bar David" <didi(a)redhat.com&gt; wrote: > >> > >> On Wed, Sep 27, 2017 at 11:32 AM, M R <gr8nextmail(a)gmail.com&gt; wrote: > >> > Hello! > >> > > >> > I have followed instructions in > >> > https://www.ovirt.org/develop/developer-guide/vdsm/hook/qemucmdline/ > >> > > >> > After adding any command for qemu cmdline, vm will try to start, but > >> > will > >> > immediately shutdown. > >> > > >> > Is this a bug? > >> > >> If you intended, with the params you passed, to make qemu fail, for > >> whatever > >> reason (debugging qemu?), then it's not a bug :-) Otherwise, it is, but > >> we > >> can't know where. > >> > >> > or is the information in the link insufficient? > >> > If it would be possible to confirm this and if there's a way to fix, > >> > I > >> > would > >> > really like to have step by step guide of how to get this working. > >> > >> Did you check relevant logs? vdsm/libvirt? > >> > >> Best, > >> -- > >> Didi > > > > -- > Didi