[ https://ovirt-jira.atlassian.net/browse/OST-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Issue Type: Bug (was: By-EMAIL) Project: oVirt system tests (was: oVirt - virtualization made easy) Workflow: Software Simplified Workflow for Project OST (was: Task Management Workflow) Key: OST-106 (was: OVIRT-1943)
Re: he-basic-ansible_suite_master: failed to set MSR 0xd90 to 0×0
Key: OST-106 URL: https://ovirt-jira.atlassian.net/browse/OST-106 Project: oVirt system tests Issue Type: Bug Reporter: eyal edri Assignee: Gal Ben HaimOpening a ticket on it, Gal will look into it, it might take some time to investigate. On Mon, Mar 26, 2018 at 1:24 PM, Yedidyah Bar David <didi@redhat.com> wrote:
Hi all,
Trying to run ovirt-system-tests using mock_runner.sh on my laptop (i7-6820HQ T460p, RHEL 7.4, kernel 3.10.0-693.17.1.el7.x86_64, qemu-kvm-rhev-2.9.0-16.el7_4.13.x86_64).
hosted-engine deploy starts, and fails while running virt-install to create the engine vm (which will be a nested-kvm vm).
qemu log on the nested-kvm host0 says:
2018-03-26T08:02:16.727212Z qemu-kvm: error: failed to set MSR 0xd90 to 0×0 qemu-kvm: /builddir/build/BUILD/qemu-2.9.0/target/i386/kvm.c:1843: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
Searched and found this:
https://bugs.launchpad.net/qemu/+bug/1665389
which seems very similar, although from a year ago and about a fedora 24 kernel+qemu. The conclusion there is:
<quote> Yes, I mean ‘-cpu host’ in the bare metal. There is no workaround; it worked by chance and it triggered other hard to find bugs. </quote>
So, what should I/we do? Is there a workaround? How does this work elsewhere?
Thanks, — Didi _____________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
— Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)