Re: [ovirt-users] Qemu prevents vm from starting up properly
Hello! I have maybe found a way to do this. I found this older email archive where similar problem was described: https://www.mail-archive.com/users@ovirt.org/msg40422.html With this -cpu arguments show up corretcly in log. But the it still won't fix nvidia problem 43, which is annoying "bug" implemented by nvidia. I have several gtx graphic cards collecting dust and would like to use them, but fail to do so... best regards Mikko On Thu, Sep 28, 2017 at 8:46 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Wed, Sep 27, 2017 at 8:32 PM, M R <gr8nextmail@gmail.com> wrote:
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.
You should first come up with something that works when you try it manually, then try adapting that to the hook's syntax.
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>
I guess you refer above to libvirt xml. This isn't strictly related to qemu, although in practice most usage of libvirt is with qemu.
How do I write this in custom properties for qemu_cmdline?
If you have a working libvirt vm, with the options you need, simply check how it translated your xml to qemu's command line. You can see this either in its logs, or using ps.
Best,
best regards
Mikko
On 27 Sep 2017 3:27 pm, "Yedidyah Bar David" <didi@redhat.com> wrote:
On Wed, Sep 27, 2017 at 1:14 PM, M R <gr8nextmail@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@redhat.com> wrote:
On Wed, Sep 27, 2017 at 11:32 AM, M R <gr8nextmail@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
-- Didi
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Ei viruksia. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
participants (1)
-
M R