On Fri, Feb 12, 2016 at 06:12:46PM +0100, Markus Armbruster wrote: > "Daniel P. Berrange" <[email protected]> writes: > > > On Fri, Feb 12, 2016 at 05:49:38PM +0100, Markus Armbruster wrote: > >> "Daniel P. Berrange" <[email protected]> writes: > >> > >> > On Thu, Jan 21, 2016 at 07:16:25AM +0100, Hervé Poussineau wrote: > >> >> Hi, > >> >> > >> >> This patch (commit d0d7708ba29cbcc343364a46bff981e0ff88366f) regresses > >> >> the following command line: > >> >> qemu-system-i386 -nodefaults -chardev vc,id=mon0 -mon chardev=mon0 > >> >> > >> >> Before: > >> >> [nothing is print on console] > >> >> > >> >> After: > >> >> QEMU 2.5.50 monitor - type 'help' for more information > >> >> (qemu) > >> >> > >> >> In both cases, a working vc is created in the GTK+ UI. > >> >> > >> >> Reverting the commit (and fixing the trivial conflict) makes things > >> >> work again. > >> > > >> > Thanks for the heads-up, I'll investigate and submit a fix > >> > >> For the record, it also breaks ivshmem-test when the slow tests are > >> included. I'd be willing to test your fix; got a pointer for me? > > > > https://lists.gnu.org/archive/html/qemu-devel/2016-02/msg02738.html > > No luck. Please try the following reproducer: > > $ make tests/ivshmem-test > $ QTEST_QEMU_BINARY='x86_64-softmmu/qemu-system-x86_64' > QTEST_QEMU_IMG=qemu-img MALLOC_PERTURB_=${MALLOC_PERTURB_:-$((RANDOM % 255 + > 1))} gtester -k --verbose -m slow tests/ivshmem-test
Yes, I can reproduce that. Will put it on my todo list for next week. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
