All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Oppermann <1915794@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1915794] Re: could not load PC BIOS 'bios-256k.bin' on latest Windows exe (*-20210203.exe)
Date: Tue, 16 Feb 2021 15:23:32 -0000	[thread overview]
Message-ID: <161348901277.4907.9976105188620705687.malone@gac.canonical.com> (raw)
In-Reply-To: 161346747703.23365.3708625175581048243.malonedeb@chaenomeles.canonical.com

Thanks a lot!

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1915794

Title:
  could not load PC BIOS 'bios-256k.bin' on latest Windows exe
  (*-20210203.exe)

Status in QEMU:
  Confirmed

Bug description:
  I'm using https://scoop.sh/ to install QEMU on a Windows CI job, which
  is run daily. Since today, the job is failing with an `could not load
  PC BIOS 'bios-256k.bin'` error thrown by QEMU.

  The version that causes this error is: https://qemu.weilnetz.de/w64/2021/qemu-w64-setup-20210203.exe#/dl.7z
  The previous version, which worked fine, was: https://qemu.weilnetz.de/w64/2020/qemu-w64-setup-20201124.exe#/dl.7z

  Both CI runs build the exact same code. You can find the full logs at
  https://github.com/rust-
  osdev/x86_64/runs/1908137213?check_suite_focus=true (failing) and
  https://github.com/rust-
  osdev/x86_64/runs/1900698412?check_suite_focus=true (previous).

  (I hope this is the right place to report this issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1915794/+subscriptions


  parent reply	other threads:[~2021-02-16 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16  9:24 [Bug 1915794] [NEW] could not load PC BIOS 'bios-256k.bin' on latest Windows exe (*-20210203.exe) Philipp Oppermann
2021-02-16 11:22 ` [Bug 1915794] " Stefan Weil
2021-02-16 12:00 ` Stefan Weil
2021-02-16 15:23 ` Philipp Oppermann [this message]
2021-05-13 12:02 ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=161348901277.4907.9976105188620705687.malone@gac.canonical.com \
    --to=1915794@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.