qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cole Robinson <crobinso@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: hw-display-qxl.so: undefined symbol: qemu_qxl_io_log_semaphore
Date: Mon, 17 Aug 2020 14:06:36 -0400	[thread overview]
Message-ID: <01e27737-bd35-4a9e-ada8-fa0f0b690926@redhat.com> (raw)
In-Reply-To: <20200817053909.yivisow25afbrulf@sirius.home.kraxel.org>

On 8/17/20 1:39 AM, Gerd Hoffmann wrote:
>   Hi,
> 
>> FWIW I'm still hitting issues with qemu-5.1.0 GA but maybe it's
>> unrelated to that specific fix. Issues reproduce on fedora 33+, not
>> fedora 32.
> 
>> +Failed to open module:
>> /builddir/build/BUILD/qemu-5.1.0-rc3/build-dynamic/x86_64-softmmu/../hw-display-qxl.so:
>> undefined symbol: qemu_qxl_client_monitors_config_crc_semaphore
> 
>> /builddir/build/BUILD/qemu-5.1.0/build-dynamic/s390x-softmmu/../hw-usb-smartcard.so:
>> undefined symbol: ccid_card_send_apdu_to_guest
> 
>> So maybe there's a more general problem. FWIW Fedora 33 started using
>> LTO by default, but it was disabled for the qemu package.
> 
> Hmm, the first looks like a problem.  I'm wondering why it happens on
> f33 only, not f32.  LTO could explain that (optimizing away symbols used
> by modules but not main qemu), but with that already turned off I have
> no clue offhand.
> 

I stripped down the reproducer. Dropping --enable-trace-backend=dtrace
makes things work AFAICT. This is on f33

dnf builddep -y qemu  # to get all the fedora package build deps
cd qemu.git
git checkout v5.1.0
./configure --target-list=x86_64-softmmu --disable-werror
--enable-modules --enable-trace-backend=dtrace
make
./x86_64-softmmu/qemu-system-x86_64 -vga qxl

# ./x86_64-softmmu/qemu-system-x86_64 -vga qxl
Failed to open module: /root/qemu.git/x86_64-softmmu/../ui-gtk.so:
undefined symbol: qemu_xkeymap_keymap_semaphore
Failed to open module: /root/qemu.git/x86_64-softmmu/../ui-sdl.so:
undefined symbol: qemu_sdl2_process_key_semaphore
Failed to open module:
/root/qemu.git/x86_64-softmmu/../hw-display-qxl.so: undefined symbol:
qemu_qxl_render_blit_semaphore
qemu-system-x86_64: QXL VGA not available

So nothing specific to qxl, seems all modules are busted.
I tried downgrading gcc to f32 versions, no difference. Same after
downgrading binutils. Downgrading glibc downgrades the whole distro so I
didn't attempt it

Output of this looks similar on f33 and f32:

nm {hw-display-qxl.so,x86_64-softmmu/qemu-system-x86_64} | grep
qemu_qxl_spice_destroy_surfaces_complete_semaphore

Any suggestions?

Thanks,
Cole



  reply	other threads:[~2020-08-17 18:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 21:10 hw-display-qxl.so: undefined symbol: qemu_qxl_io_log_semaphore Cole Robinson
2020-07-29 12:50 ` Stefan Hajnoczi
2020-08-12 15:46   ` Cole Robinson
2020-08-17  5:39     ` Gerd Hoffmann
2020-08-17 18:06       ` Cole Robinson [this message]
2020-08-18  7:22         ` Gerd Hoffmann
2020-08-18 12:15     ` Daniel P. Berrangé
2020-08-18 12:33       ` Daniel P. Berrangé
2020-08-20  8:29       ` Gerd Hoffmann
2020-08-20  8:46         ` Daniel P. Berrangé

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=01e27737-bd35-4a9e-ada8-fa0f0b690926@redhat.com \
    --to=crobinso@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).