All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Dave <dave@0bits.com>, qemu-devel@nongnu.org
Subject: Re: absolute firmware path made relocatable in qemu 5.2.0
Date: Tue, 12 Jan 2021 15:48:13 +0100	[thread overview]
Message-ID: <c9b36f34-8783-9c11-ffb9-afd25fdf9ac0@redhat.com> (raw)
In-Reply-To: <abd662c1-9a4a-9c77-6533-875ab1924695@0bits.com>

On 12/01/21 15:05, Dave wrote:
> Is seem that absolute firmwarepath compilation option is converted  to 
> relocatable in 5.2.0 qemu.
> 
> # QEMU configure log Tue 12 Jan 14:46:41 GST 2021
> # Configured with: '../configure' '--prefix=/usr' 
> '--sysconfdir=/etc/qemu' '--disable-bochs'  
> '*--firmwarepath=/usr/share/qemu:/usr/share/qemu-firmware*'
> #

Yes, all paths within the prefix are relocated.  The workaround is 
simply to configure the intended prefix with configure:

./configure --prefix=/root/qemu ...

or if you don't know the prefix:

./configure --prefix=/nonexistent ...

Because /usr/share/qemu and /usr/share/qemu-firmware are outside /usr, 
they will be treated as absolute just like /etc/qemu.

Thanks,

Paolo

> And trying to run the executable
> 
>     bash-5.1# ./qemu-system-x86_64
>     qemu: could not load PC BIOS 'bios-256k.bin'
> 
> If i print out the resultant binary paths
> 
>     bash-5.1# ./qemu-system-x86_64 -L help
>     /root/qemu/../share/qemu
>     /root/qemu/../share/qemu-firmware
> 
> So there is no way to have a absolute path for firmware /bios and all 
> qemu's that we test need to be at the right directory nesting to find 
> firmware, bios etc or else they all need their own duplicate firmware 
> files. Firmware path needs to honor the absolute paths i believe.
> 



  reply	other threads:[~2021-01-12 14:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 14:05 absolute firmware path made relocatable in qemu 5.2.0 Dave
2021-01-12 14:48 ` Paolo Bonzini [this message]
2021-01-12 16:46   ` Dave
2021-01-12 16:53     ` Paolo Bonzini
2021-01-12 17:04       ` Dave
2021-01-12 19:53         ` Paolo Bonzini
2021-01-13  7:51           ` Dave
2021-01-13  8:29             ` Paolo Bonzini

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=c9b36f34-8783-9c11-ffb9-afd25fdf9ac0@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dave@0bits.com \
    --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.