[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] kvm_set_phys_mem: assertion failed
From: |
Laszlo Ersek |
Subject: |
Re: [Qemu-devel] kvm_set_phys_mem: assertion failed |
Date: |
Wed, 4 Oct 2017 17:48:31 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 |
Hi,
On 09/21/17 16:28, Auger Eric wrote:
> 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.
There seems to be a new issue report on LaunchPad about the same
(f357f564be0b) commit, stating that the removal of the assertion does
not help:
https://bugs.launchpad.net/qemu/+bug/1721221
(Just trying to connect the dots here; I have no comments on the commit
otherwise. CC'ing Joe who has filed the LP report.)
Thanks
Laszlo
- Re: [Qemu-devel] kvm_set_phys_mem: assertion failed,
Laszlo Ersek <=