From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lwv2f-0000wF-Iy for qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:16:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lwv2a-0000uc-Kb for Qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:16:25 -0400 Received: from [199.232.76.173] (port=50328 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lwv2a-0000uZ-BU for Qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:16:20 -0400 Received: from gecko.sbs.de ([194.138.37.40]:19221) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Lwv2Z-0006Cp-69 for Qemu-devel@nongnu.org; Thu, 23 Apr 2009 05:16:20 -0400 Message-ID: <49F031C2.5000204@siemens.com> Date: Thu, 23 Apr 2009 11:15:46 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: Question about KVM and PC speaker References: <49EF69BC.90300@gmx.de> <49F01C8D.1010203@web.de> <20090423083252.GB5277@const.bordeaux.inria.fr> In-Reply-To: <20090423083252.GB5277@const.bordeaux.inria.fr> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Samuel Thibault Cc: Simon Bienlein , Qemu-devel@nongnu.org Samuel Thibault wrote: > Jan Kiszka, le Thu 23 Apr 2009 09:45:17 +0200, a =E9crit : >> Simon Bienlein wrote: >>> I hear the beep if I am in the bash of the wirtsystem and press the >>> backspace key on the start of the line. The PC speaker works therefor= e. >>> >>> How can I configure KVM so that the PC speaker also works in the VM? >>> Supports the BIOS PC Speaker beeps? >> Nope, not yet. Neither QEMU nor KVM (with its in-kernel handling of th= e >> involved timer chip) translates the guest's speaker settings into >> anything audible. But that should be feasible. >=20 > Err, have you read the first paragraph? The speaker does work. Misunderstanding: "Wirt" means host in English. So it works on his host system, but not inside the guest. And that's consistent with QEMU code: there is no handling of port 0x61 in user space, only dummy code in the KVM kernel part, and no one bother about the counter value of PIT channel 2 (which defines the beeper frequency). >=20 >>> The environment variable QEMU_AUDIO_DRV=3Dalsa is set and I run KVM w= ith >>> the option -soundhw all. >> You may succeed with this approach when redirecting the guest's consol= e >> beep to the sound card of your virtual machine. >=20 > The problem is not the guest's console beep: as mentioned above, that > one does work. The one that doesn't is the syslinux beep of the debian > installer CD, which is supposed to be implemented in the bios. Doing beep via the BIOS is surely another to-do, and a useful hint in this context. But unless you add a paravirt firmware beep channel or BIOS support for sound cards or, and that' probably the best approach, PC speaker emulation, how should the beep be emitted? Jan --=20 Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux