From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39680) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dzlun-0008VA-35 for qemu-devel@nongnu.org; Wed, 04 Oct 2017 11:48:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dzlui-0002hM-B9 for qemu-devel@nongnu.org; Wed, 04 Oct 2017 11:48:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52490) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dzlui-0002fU-49 for qemu-devel@nongnu.org; Wed, 04 Oct 2017 11:48:48 -0400 References: <1505913885.24609.8.camel@redhat.com> <2b739056-081b-593a-6344-50b60d04872b@redhat.com> <1505917879.24609.11.camel@redhat.com> <394d5515-c9a0-578d-1daf-8af1328f0b4b@redhat.com> <3f8964dc-3fd4-1f0d-c6c6-46afe78a085d@redhat.com> From: Laszlo Ersek Message-ID: <54b31df5-8eff-2312-346e-3fd9a78cab8e@redhat.com> Date: Wed, 4 Oct 2017 17:48:31 +0200 MIME-Version: 1.0 In-Reply-To: <3f8964dc-3fd4-1f0d-c6c6-46afe78a085d@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] kvm_set_phys_mem: assertion failed List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Auger Eric , David Hildenbrand , Gerd Hoffmann , "qemu-devel@nongnu.org" Cc: pbonzini@redhat.com, Joe Clifford 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: >>>> >>>> >>> type="pflash">/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure- >>>> efi.fd >>>> >>> template="/usr/share/edk2.git/ovmf-x64/OVMF_VARS-pure- >>>> efi.fd">/var/lib/libvirt/qemu/nvram/fedora-org-drm-qxl- >>>> base_VARS.fd >>> >>> 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