From owner-freebsd-bugs@FreeBSD.ORG Wed Nov 26 01:36:28 2014 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 16234EDA for ; Wed, 26 Nov 2014 01:36:28 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC1857F3 for ; Wed, 26 Nov 2014 01:36:27 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAQ1aRRS068852 for ; Wed, 26 Nov 2014 01:36:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195395] New: serial console as qvm-kemu guest stops responding freezes on duplex I/O Date: Wed, 26 Nov 2014 01:36:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bkabe@vega.pgw.jp X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2014 01:36:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195395 Bug ID: 195395 Summary: serial console as qvm-kemu guest stops responding freezes on duplex I/O Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: bkabe@vega.pgw.jp Overview: When FreeBSD as a guest under qvm-kemu, and guest setup to use serial console, simultaneous I/O on serial console will lock up the serial console. That is, on console, you could "ls -lR /" and press any key during the scrolling, and console freezes instantly. Ditto for Copy-Pasting a long string on the serial console. Reproduce: Host OS: CentOS 6.5 + kernel-2.6.32-431.el6.x86_64 + qemu-kvm-0.12.1.2-2.415.el6_5.10.x86_64 Guest OS: FreeBSD 10.1 release (amd64) * Boot FreeBSD media on host as Linux qemu-kvm guest. Example: host# virt-install -n fbtest -r 128 --vcpus=1 \ --nodisks \ --cdrom /home/libvirt/images/FreeBSD-10.0-RELEASE-amd64-dvd1.iso \ --network=network=default,model=virtio \ --video=vga --graphics none * Loader prompt will appear on serial; press [Esc] to get OK prompt and type OK set console=comconsole OK boot -s to get single user prompt. * # ls -lR / During scrolling, press any key. Actual Results: Console stops responding. Expected results: At least it should respond for buffer overflow or something. Additional Information: Console freeze will still occur on HDD(-image) installed, multiuser FreeBSD guest with serial console configured as in Hnadbook. When ps-ed from other tty (such as ssh), "ls -lR / >/dev/console" is stuck on "ttyout". 0 632 1 0 20 0 14488 1932 ttyin Ss+ u0 0:00.02 /usr/libexec/getty 3wire.9600 ttyu0 0 595 1 0 52 0 14488 1932 ttyin Is+ v0 0:00.01 /usr/libexec/getty Pc ttyv0 0 621 620 0 21 0 47716 2672 wait Is 0 0:00.06 su 0 624 621 0 20 0 23572 3292 pause S 0 0:00.03 _su (csh) 0 636 624 0 52 0 16852 2932 ttyout S 0 0:00.39 ls -lR / 0 643 624 0 20 0 18736 2100 - R+ 0 0:00.00 ps axlww SIGHUP or SIGKILL-ing process holding /dev/ttyu0 doesn't help. The only way to unlock the console is to reboot. (single user is not enough) -- You are receiving this mail because: You are the assignee for the bug.