Hi, On 2/21/19 3:26 PM, Peter Maydell wrote: > On Thu, 21 Feb 2019 at 14:20, Auger Eric <eric.au...@redhat.com> wrote: >> My qemu cmd line is: >> >> qemu-system-aarch64 -M virt,gic-version=3 -cpu host -smp 2 -m 4G >> -display none --enable-kvm -serial tcp:localhost:4444,server -qmp >> unix:/home/augere/TEST/QEMU/qmp-sock,server,nowait -device >> virtio-blk-pci,bus=pcie.0,scsi=off,drive=drv0,id=virtio-disk0,bootindex=1,werror=stop,rerror=stop >> -drive >> file=aarch64-vm0-rhel-alt-7.6.qcow2,format=qcow2,if=none,cache=writethrough,id=drv0 >> -device virtio-net-pci,bus=pcie.0,netdev=nic0,mac=6a:f5:10:b1:3d:d2 >> -netdev >> tap,id=nic0,script=/home/augere/TEST/SCRIPTS/qemu-ifup,downscript=/home/augere/TEST/SCRIPTS/qemu-ifdown >> -bios >> /home/augere/UPSTREAM/edk2/Build/ArmVirtQemu-AARCH64/DEBUG_GCC5/FV/QEMU_EFI.fd >> -net none -d guest_errors > > Does the bug still occur if you get rid of all the network/disk related > command line options here (hopefully it does, to reduce the size of > the test case) ? Can you provide the QEMU_EFI.fd ? I am using upstream EDK2 (https://github.com/tianocore/edk2) compiled in debug mode
I can reproduce the bug with qemu-system-aarch64 -M virt,gic-version=3 -cpu host -smp 4 -m 4G -display none --enable-kvm -serial stdio \ -device virtio-blk-pci,bus=pcie.0,scsi=off,drive=drv0,id=virtio-disk0,bootindex=1,werror=stop,rerror=stop \ -drive file=/home/augere/VM/IMAGES/aarch64-vm0-rhel-alt-7.6.qcow2,format=qcow2,if=none,cache=writethrough,id=drv0 \ -bios /home/augere/UPSTREAM/edk2/Build/ArmVirtQemu-AARCH64/DEBUG_GCC5/FV/QEMU_EFI.fd \ -net none -d guest_errors also with virtio-blk-device Thanks Eric > > thanks > -- PMM >
