All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave <dave@0bits.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: absolute firmware path made relocatable in qemu 5.2.0
Date: Wed, 13 Jan 2021 11:51:00 +0400	[thread overview]
Message-ID: <e132f0dd-e9ee-5519-e539-ceb760b7c6a6@0bits.com> (raw)
In-Reply-To: <536bbda3-ebcb-e098-2625-5de4db08422e@redhat.com>

This is my qemu binary compiled with --prefix=/nonexistent


bash-5.1# ./qemu-system-x86_64 -L help
/usr/share/qemu
/usr/share/qemu-firmware
/usr/src/sources/qemu-5.2.0/build/pc-bios

bash-5.1# ./qemu-system-x86_64 --help|grep helper
 
[,br=bridge][,helper=helper][,sndbuf=nbytes][,vnet_hdr=on|off][,vhost=on|off]
                 use network helper 'helper' 
(default=/nonexistent/libexec/qemu-bridge-helper) to
-netdev bridge,id=str[,br=bridge][,helper=helper]
                 using the program 'helper 
(default=/nonexistent/libexec/qemu-bridge-helper)

See that it will call /nonexistent/libexec/qemu-bridge-helper by default.

Dave

On 12/01/2021 23:53, Paolo Bonzini wrote:
> On 12/01/21 18:04, Dave wrote:
>> Thanks Paola,
>>
>> We are still in testing and that's the only thing we've uncovered so 
>> far with the new 5.2.0. I will post if the ops guys find anything else.
> 
> Hmm, that's weird though.  The path to the default bridge helper is 
> relocated:
> 
> net/tap.c:        helper = default_helper = 
> get_relocated_path(DEFAULT_BRIDGE_HELPER);
> 
> Paolo
> 


  reply	other threads:[~2021-01-13  7:52 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
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 [this message]
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=e132f0dd-e9ee-5519-e539-ceb760b7c6a6@0bits.com \
    --to=dave@0bits.com \
    --cc=pbonzini@redhat.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.