On Wed, Sep 27, 2017 at 1:14 PM, M R <gr8nextmail(a)gmail.com> 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> wrote:
>
> On Wed, Sep 27, 2017 at 11:32 AM, M R <gr8nextmail(a)gmail.com> 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