On Tue, Jun 21, 2016 at 05:12:02PM +0200, Andrew Jones wrote: > On Tue, Jun 21, 2016 at 03:55:46PM +0100, Peter Maydell wrote: > > On 21 June 2016 at 15:45, Andrew Jones <drjo...@redhat.com> wrote: > > > On Wed, Jun 15, 2016 at 04:53:35PM +0800, Shannon Zhao wrote: > > >> I have another test with a freebsd guest. When I specify gic-version=3 > > >> at the QEMU command line, the guest can't start. But with gic-version=2 > > >> it's fine. And if I use gic-version=3 with kvm, the guest boots well too. > > >> > > >> It hangs with below log: > > >> [Bds]=============Begin Load Options Dumping ...============= > > >> Driver Options: > > >> SysPrep Options: > > >> Boot Options: > > >> Boot0000: UiApp 0x0109 > > >> Boot0001: EFI Internal Shell 0x0001 > > >> Boot0002: UEFI Misc Device 0x0001 > > >> Boot0003: UEFI Misc Device 2 0x0001 > > >> Boot0004: UEFI Misc Device 3 0x0001 > > >> Boot0005: UEFI PXEv4 (MAC:525400123456) 0x0001 > > >> PlatformRecovery Options: > > >> PlatformRecovery0000: Default PlatformRecovery 0x0001 > > >> [Bds]=============End Load Options Dumping============= > > >> [Bds]BdsWait ...Zzzzzzzzzzzz... > > >> [Bds]BdsWait(3)..Zzzz... > > > > > > I can reproduce this exact output with the latest version of AAVMF, > > > built on commit 988715a. > > > > I thought we'd decided this was a FreeBSD bug? Or does UEFI itself > > use interrupts here and not set them up properly? > > Looks like AAVMF. I'm using RHEL for AArch64 kernel, which does > work with tcg,gic-version=3 -kernel boots, kvm,gic-version=3 boots, > and bare-metal gicv3 boots. >
Laszlo asked me to reply again, this time with Ard on CC, and with some more details. Issue: AAVMF boot under gicv3 emulation, e.g. -machine virt,accel=tcg,gic-version=3 fails with the above message. gicv3 emulation is not yet in master, but can be built from git://git.linaro.org/people/pmaydell/qemu-arm.git staging Shannon reported successful boots of UEFI, but I don't know what build he used. The AAVMF I'm using is based on upstream commit 988715a3a7. Thanks, drew
