From: Auger Eric <eric.auger@redhat.com>
To: David Hildenbrand <david@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: pbonzini@redhat.com
Subject: Re: [Qemu-devel] kvm_set_phys_mem: assertion failed
Date: Thu, 21 Sep 2017 16:28:21 +0200 [thread overview]
Message-ID: <3f8964dc-3fd4-1f0d-c6c6-46afe78a085d@redhat.com> (raw)
In-Reply-To: <394d5515-c9a0-578d-1daf-8af1328f0b4b@redhat.com>
Hi David,
On 20/09/2017 16:34, David Hildenbrand wrote:
> On 20.09.2017 16:31, Gerd Hoffmann wrote:
>> Hi,
>>
>>> Dropping from os section:
>>>
>>> <loader readonly="yes"
>>> type="pflash">/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-
>>> efi.fd</loader>
>>> <nvram
>>> template="/usr/share/edk2.git/ovmf-x64/OVMF_VARS-pure-
>>> efi.fd">/var/lib/libvirt/qemu/nvram/fedora-org-drm-qxl-
>>> base_VARS.fd</nvram>
>>
>> Bad idea I guess.
>>
>>> 1) Does the assert trigger right at startup? Or how is it triggered?
>>
>> Yes, right at startup, before OVMF is done initializing.
>> So probably something in OVMF triggers it.
>
> I'll try to include ovmf to reproduce it.
>
>>
>>> 2) Does your setup work when dopping the assertion?
>>
>> Can try tomorrow.
I encounter the problem on ARM too. My setup works when dropping the
assertion.
Thanks
Eric
>
> I think that assertion might not be stable, because properties (romd
> mode) might not be stable and can change. So if it works without the
> assert, dropping it is the right thing to do.
>
>>
>> cheers,
>> Gerd
>>
>
>
next prev parent reply other threads:[~2017-09-21 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 13:24 [Qemu-devel] kvm_set_phys_mem: assertion failed Gerd Hoffmann
2017-09-20 13:54 ` David Hildenbrand
2017-09-20 14:25 ` David Hildenbrand
2017-09-20 14:31 ` Gerd Hoffmann
2017-09-20 14:34 ` David Hildenbrand
2017-09-21 14:28 ` Auger Eric [this message]
2017-10-04 15:48 ` Laszlo Ersek
2017-10-16 11:23 ` David Hildenbrand
2017-10-16 11:52 ` Joe Clifford
2017-10-16 11:54 ` Joe Clifford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f8964dc-3fd4-1f0d-c6c6-46afe78a085d@redhat.com \
--to=eric.auger@redhat.com \
--cc=david@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).