Bug#973571: ovmf: does not work with qemu-system-i386 5.1

2020-11-03 Thread Ryutaroh Matsumoto
I also verified that 32-bit version of OVMF_CODE_4M.ms.fd works. I did cp /home/ryutaroh/OVMF_VARS_4M.ms.fd /tmp qemu-system-i386 -m 1024 -smp 1 -nographic -net nic,model=virtio -net user,hostfwd=tcp:127.0.0.1:10022-:22 \ -object rng-random,filename=/dev/urandom,id=rng0 \ -device

Bug#973571: ovmf: does not work with qemu-system-i386 5.1

2020-11-03 Thread dann frazier
On Tue, Nov 3, 2020 at 12:45 PM Christian Kastner wrote: > > Control: severity -1 wishlist > > On 11/2/20 8:44 PM, Ryutaroh Matsumoto wrote: > > Control: reassign -1 src:edk2> Control: forcemerge -1 842683 > > > > I am hoping the above control commands merge 973571 and 842683 > > (I don't know

Bug#973571: ovmf: does not work with qemu-system-i386 5.1

2020-11-03 Thread Christian Kastner
Control: severity -1 wishlist On 11/2/20 8:44 PM, Ryutaroh Matsumoto wrote: > Control: reassign -1 src:edk2> Control: forcemerge -1 842683 > > I am hoping the above control commands merge 973571 and 842683 > (I don't know how to merge multiple BTS bugs...). They did merge, but the bug number

Bug#973571: ovmf: does not work with qemu-system-i386 5.1

2020-11-02 Thread Ryutaroh Matsumoto
Control: reassign -1 src:edk2 Control: forcemerge -1 842683 >> I wonder if there is a good reason NOT building IA32 OVMF... >> I have no idea about that... > > I would guess that the maintainers might have face similar problems to > #842683 and that these problems have been fixed upstream in the

Bug#973571: ovmf: does not work with qemu-system-i386 5.1

2020-11-02 Thread Christian Kastner
On 11/2/20 2:31 PM, Ryutaroh Matsumoto wrote: >> Looking at #842683, others have attempted to build the 32-bit versions >> and encountered build failures. However, that information is now 2 years >> old -- perhaps upstream has changed in the meantime such that a build is >> now possible. > > It

Bug#973571: ovmf: does not work with qemu-system-i386 5.1

2020-11-02 Thread Ryutaroh Matsumoto
Hi Christian, thanks again for paying attention! >The question is: if upstream states that i386 is supported, what can we >do to enable this functionality in this particular package? Building IA32-capable OVMF is REALLY EASY in 2020. $ mkdir ovmf-ia32 $ cd ovmf-ia32 $ git clone

Bug#973571: ovmf: does not work with qemu-system-i386 5.1

2020-11-01 Thread Christian Kastner
Hi Ryutaroh, On 11/2/20 1:22 AM, Ryutaroh Matsumoto wrote: > Package: ovmf > Version: 2020.08-1 > Severity: important > X-Debbugs-Cc: c...@debian.org > Control: block 973522 by -1 > > Dear Maintainer, > > ovmf works fine with qemu-system-x86_64 with KVM, > but it does not work with

Bug#973571: ovmf: does not work with qemu-system-i386 5.1

2020-11-01 Thread Ryutaroh Matsumoto
Control: retitle -1 ovmf: does not boot i386 autopkg QEMU testbed autopkg QEMU i386 UEFI testbed cannot booted even by qemu-system-x86_64 as below as well as qemu-system-i386, though the situation improves a bit as qemu-system-x86_64 prints some booting message. Title is changed accordingly. #

Bug#973571: ovmf: does not work with qemu-system-i386 5.1

2020-11-01 Thread Ryutaroh Matsumoto
Package: ovmf Version: 2020.08-1 Severity: important X-Debbugs-Cc: c...@debian.org Control: block 973522 by -1 Dear Maintainer, ovmf works fine with qemu-system-x86_64 with KVM, but it does not work with qemu-system-i386 with or without KVM. The upstream README