From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A8175C28CC3 for ; Fri, 31 May 2019 16:10:17 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 743D626B9A for ; Fri, 31 May 2019 16:10:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 743D626B9A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=mail.jerryxiao.cc Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([127.0.0.1]:45859 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hWk6i-0005Ww-Dc for qemu-devel@archiver.kernel.org; Fri, 31 May 2019 12:10:16 -0400 Received: from eggs.gnu.org ([209.51.188.92]:35049) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hWk4p-0004CN-FV for qemu-devel@nongnu.org; Fri, 31 May 2019 12:08:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hWjsx-0008MU-O9 for qemu-devel@nongnu.org; Fri, 31 May 2019 11:56:05 -0400 Received: from indium.canonical.com ([91.189.90.7]:53176) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hWjsx-0008KB-HL for qemu-devel@nongnu.org; Fri, 31 May 2019 11:56:03 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1hWjst-0005yD-Ho for ; Fri, 31 May 2019 15:55:59 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 8739B2E80E7 for ; Fri, 31 May 2019 15:55:57 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 31 May 2019 15:40:35 -0000 From: Jerry To: qemu-devel@nongnu.org X-Launchpad-Notification-Type: bug X-Launchpad-Bug: product=qemu; status=New; importance=Undecided; assignee=None; X-Launchpad-Bug-Tags: aarch64 uefi X-Launchpad-Bug-Information-Type: Public X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Bug-Commenters: jerryxiao lersek X-Launchpad-Bug-Reporter: Jerry (jerryxiao) X-Launchpad-Bug-Modifier: Jerry (jerryxiao) References: <155923186868.25498.16417785082829115907.malonedeb@gac.canonical.com> Message-Id: <155931723594.7669.5080130826154722782.malone@wampee.canonical.com> X-Launchpad-Message-Rationale: Subscriber (QEMU) @qemu-devel-ml X-Launchpad-Message-For: qemu-devel-ml Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="18968"; Instance="launchpad-lazr.conf" X-Launchpad-Hash: f868c2e40dd70f9fc222b79706c4c21ace5e24e8 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 91.189.90.7 Subject: [Qemu-devel] [Bug 1831115] Re: qemu 4.0.0 on aarch64: uefi firmware oversize X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Bug 1831115 <1831115@bugs.launchpad.net> Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" I'm quite sure that debian has done the padding procedure https://salsa.debian.org/qemu-team/edk2/blob/debian/debian/rules#L82 ** Changed in: qemu Status: Invalid =3D> New -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1831115 Title: qemu 4.0.0 on aarch64: uefi firmware oversize Status in QEMU: New Bug description: I'd like to enable uefi in my virtual machine, however qemu is always sho= wing the same error: qemu-system-aarch64: Initialization of device cfi.pf= lash01 failed: device requires 67108864 bytes, block backend provides 78643= 2 bytes = It's clearly impossible to fit a uefi firmware into 786432 bytes. = Environment: qemu-system-aarch64 with kvm on an amlogic s905d aarch64 dev board, running archlinuxarm, qemu in the repository is compiled with https://download.qemu.org/qemu-4.0.0.tar.xz (My AAVMF_CODE.fd and AAVMF_VARS.fd are extracted from debian package qemu-efi-aarch64 0~20181115.85588389-3) Below is my libvirt log. 2019-05-30 15:07:44.216+0000: starting up libvirt version: 5.3.0, qemu ve= rsion: 4.0.0, kernel: 4.19.46-1-ARCH, hostname: jerry-n1.localdomain LC_ALL=3DC \ PATH=3D/usr/local/sbin:/usr/local/bin:/usr/bin \ HOME=3D/var/lib/libvirt/qemu/domain-2-debiantesting \ XDG_DATA_HOME=3D/var/lib/libvirt/qemu/domain-2-debiantesting/.local/share= \ XDG_CACHE_HOME=3D/var/lib/libvirt/qemu/domain-2-debiantesting/.cache \ XDG_CONFIG_HOME=3D/var/lib/libvirt/qemu/domain-2-debiantesting/.config \ QEMU_AUDIO_DRV=3Dnone \ /usr/bin/qemu-system-aarch64 \ -name guest=3Ddebiantesting,debug-threads=3Don \ -S \ -object secret,id=3DmasterKey0,format=3Draw,file=3D/var/lib/libvirt/qemu/= domain-2-debiantesting/master-key.aes \ -machine virt-4.0,accel=3Dkvm,usb=3Doff,dump-guest-core=3Doff,gic-version= =3D2 \ -cpu host \ -drive file=3D/opt/ovmf/aarch64/AAVMF_CODE.fd,if=3Dpflash,format=3Draw,un= it=3D0,readonly=3Don \ -drive file=3D/var/lib/libvirt/qemu/nvram/debiantesting_VARS.fd,if=3Dpfla= sh,format=3Draw,unit=3D1 \ -m 1024 \ -overcommit mem-lock=3Doff \ -smp 4,sockets=3D4,cores=3D1,threads=3D1 \ -uuid 508d100a-b4e5-4199-9ff9-ac6d40fe2896 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=3Dcharmonitor,fd=3D25,server,nowait \ -mon chardev=3Dcharmonitor,id=3Dmonitor,mode=3Dcontrol \ -rtc base=3Dutc \ -no-reboot \ -boot strict=3Don \ -device pcie-root-port,port=3D0x8,chassis=3D1,id=3Dpci.1,bus=3Dpcie.0,mul= tifunction=3Don,addr=3D0x1 \ -device pcie-root-port,port=3D0x9,chassis=3D2,id=3Dpci.2,bus=3Dpcie.0,add= r=3D0x1.0x1 \ -device pcie-root-port,port=3D0xa,chassis=3D3,id=3Dpci.3,bus=3Dpcie.0,add= r=3D0x1.0x2 \ -device pcie-root-port,port=3D0xb,chassis=3D4,id=3Dpci.4,bus=3Dpcie.0,add= r=3D0x1.0x3 \ -device pcie-root-port,port=3D0xc,chassis=3D5,id=3Dpci.5,bus=3Dpcie.0,add= r=3D0x1.0x4 \ -device pcie-root-port,port=3D0xd,chassis=3D6,id=3Dpci.6,bus=3Dpcie.0,add= r=3D0x1.0x5 \ -device qemu-xhci,p2=3D15,p3=3D15,id=3Dusb,bus=3Dpci.2,addr=3D0x0 \ -device virtio-scsi-pci,id=3Dscsi0,bus=3Dpci.3,addr=3D0x0 \ -device virtio-serial-pci,id=3Dvirtio-serial0,bus=3Dpci.4,addr=3D0x0 \ -drive file=3D/mnt/hddp1/jerry/libvirt/aarch64-images/debiantesting.qcow2= ,format=3Dqcow2,if=3Dnone,id=3Ddrive-scsi0-0-0-0 \ -device scsi-hd,bus=3Dscsi0.0,channel=3D0,scsi-id=3D0,lun=3D0,device_id= =3Ddrive-scsi0-0-0-0,drive=3Ddrive-scsi0-0-0-0,id=3Dscsi0-0-0-0,bootindex= =3D2 \ -drive file=3D/mnt/hddp1/jerry/libvirt/aarch64-iso/debian-testing-arm64-n= etinst.iso,format=3Draw,if=3Dnone,id=3Ddrive-scsi0-0-0-1,readonly=3Don \ -device scsi-cd,bus=3Dscsi0.0,channel=3D0,scsi-id=3D0,lun=3D1,device_id= =3Ddrive-scsi0-0-0-1,drive=3Ddrive-scsi0-0-0-1,id=3Dscsi0-0-0-1,bootindex= =3D1 \ -netdev tap,fd=3D27,id=3Dhostnet0 \ -device virtio-net-pci,netdev=3Dhostnet0,id=3Dnet0,mac=3D52:54:00:d5:28:6= d,bus=3Dpci.1,addr=3D0x0 \ -chardev pty,id=3Dcharserial0 \ -serial chardev:charserial0 \ -chardev socket,id=3Dcharchannel0,fd=3D28,server,nowait \ -device virtserialport,bus=3Dvirtio-serial0.0,nr=3D1,chardev=3Dcharchanne= l0,id=3Dchannel0,name=3Dorg.qemu.guest_agent.0 \ -object rng-random,id=3Dobjrng0,filename=3D/dev/urandom \ -device virtio-rng-pci,rng=3Dobjrng0,id=3Drng0,bus=3Dpci.5,addr=3D0x0 \ -sandbox on,obsolete=3Ddeny,elevateprivileges=3Ddeny,spawn=3Ddeny,resourc= econtrol=3Ddeny \ -msg timestamp=3Don 2019-05-30 15:07:44.216+0000: Domain id=3D2 is tainted: host-cpu char device redirected to /dev/pts/2 (label charserial0) 2019-05-30T15:07:46.701125Z qemu-system-aarch64: Initialization of device= cfi.pflash01 failed: device requires 67108864 bytes, block backend provide= s 786432 bytes 2019-05-30 15:07:46.779+0000: shutting down, reason=3Dfailed (END) # /etc/libvirt/qemu.conf = nvram =3D [ "/opt/ovmf/aarch64/AAVMF_CODE.fd:/opt/ovmf/aarch64/AAVMF_VARS.fd" ] To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1831115/+subscriptions