> Can you retry this with one of the 1.0 release candidates > or current head-of-git, please? OK, I'll try with 1.0-rc3, but before that just a quick query - I use the Fedora source rpm as a basis and do "rpmbuild -bp qemu.spec" to prepare the source. This, according to the said .spec file, applies the following patches (by Fedora, not me):
Patch01: 0001-char-Split-out-tcp-socket-close-code-in-a-separate-f.patch Patch02: 0002-char-Add-a-QemuChrHandlers-struct-to-initialise-char.patch Patch03: 0003-iohandlers-Add-enable-disable_write_fd_handler-funct.patch Patch04: 0004-char-Add-framework-for-a-write-unblocked-callback.patch Patch05: 0005-char-Update-send_all-to-handle-nonblocking-chardev-w.patch Patch06: 0006-char-Equip-the-unix-tcp-backend-to-handle-nonblockin.patch Patch07: 0007-char-Throttle-when-host-connection-is-down.patch Patch08: 0008-virtio-console-Enable-port-throttling-when-chardev-i.patch Patch09: 0009-spice-qemu-char.c-add-throttling.patch Patch10: 0010-spice-qemu-char.c-remove-intermediate-buffer.patch Patch11: 0011-usb-redir-Add-flow-control-support.patch Patch12: 0012-spice-add-worker-wrapper-functions.patch Patch13: 0013-spice-add-qemu_spice_display_init_common.patch Patch14: 0014-spice-qxl-move-worker-wrappers.patch Patch15: 0015-qxl-fix-surface-tracking-locking.patch Patch16: 0016-qxl-add-io_port_to_string.patch Patch17: 0017-qxl-error-handling-fixes-and-cleanups.patch Patch18: 0018-qxl-make-qxl_guest_bug-take-variable-arguments.patch Patch19: 0019-qxl-only-disallow-specific-io-s-in-vga-mode.patch Patch20: 0020-qxl-async-io-support-using-new-spice-api.patch Patch21: 0021-qxl-add-QXL_IO_FLUSH_-SURFACES-RELEASE-for-guest-S3-.patch Patch22: 0022-qxl-bump-pci-rev.patch Patch23: 0023-virtio-serial-bus-replay-guest_open-on-migration.patch Patch24: 0024-qemu-char-make-qemu_chr_event-public.patch Patch25: 0025-spice-qemu-char-Generate-chardev-open-close-events.patch Patch26: 0026-usb-redir-Call-qemu_chr_guest_open-close.patch Patch27: 0027-usb-redir-Device-disconnect-re-connect-robustness-fi.patch Patch28: 0028-usb-redir-Don-t-try-to-write-to-the-chardev-after-a-.patch I am almost certain that the majority of these will fail with the new source, so I'll try to build without those. Is that OK? > (when I do a static build it doesn't try to link against ssl3.) Interesting. I'll do a "vanilla" build (with no patches applied) and see how it goes, unless you have something else in mind?
