From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 9418565CD2 for ; Mon, 4 Jan 2021 16:55:59 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8B8DF1F2A3 for ; Mon, 4 Jan 2021 16:55:59 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id DCB771F297 for ; Mon, 4 Jan 2021 16:55:57 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id A202444143; Mon, 4 Jan 2021 16:55:57 +0100 (CET) To: Proxmox VE development discussion , Gilles Pietri References: <309fe8ad-2589-5699-be3d-4f5a1ac0cbea@gilouweb.com> From: Aaron Lauterer Message-ID: <90c45c7c-c131-c761-dafd-6f18cf4ec69f@proxmox.com> Date: Mon, 4 Jan 2021 16:55:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <309fe8ad-2589-5699-be3d-4f5a1ac0cbea@gilouweb.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.021 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] Audio support, dummy/none X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jan 2021 15:55:59 -0000 Hi Gilou! On 1/3/21 1:55 AM, Gilles Pietri wrote: > Hi! > > Happy new year to everyone, especially the devs working on Proxmox, it's > still awesome in 2021 ;) > > I'm interested in replicating a qemu audio setup that uses the dummy > driver (called "none") on Proxmox, but the enum $audio_fmt > (PVE/QemuServer.pm) for drivers only contains spice as a choice, which > is all nice, but a bit restrictive! May I ask what your use case is? The reason why we currently only support the spice audio backend is that for other possible use cases, other (better / simpler) options exist. Windows RDP supports audio by itself and if you need to play audio on the actual sound card it is simple to pass it through as PCI device to the VM. > > Since this is used only (?) to generate the audio conf (through > conf_has_audio), which generate the audio devices through audio_devs, > which in turn generates both the -device param and the -audiodev > backend,id=xxx, it seems there wouldn't be any side effect if we fed > "none" instead of spice, as the id param is valid and works the same here. > > I haven't tried patching that, but it might be that this would boil down to: > > diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm > index bca5669..54278e5 100644 > --- a/PVE/QemuServer.pm > +++ b/PVE/QemuServer.pm > @@ -211,7 +211,7 @@ my $audio_fmt = { > }, > driver => { > type => 'string', > - enum => ['spice'], > + enum => ['spice', 'none'], > default => 'spice', > optional => 1, > description => "Driver backend for the audio device." > > And maybe, if we want to go further, we may want a bit of documentation > also, maybe on the wiki… Is the current documentation in the admin guide [0] enough or do you mean more documentation on how to setup more advanced audio setups, such as with PA or ALSA? > Also, though it's not my usecase atm, it might > be interesting to add others backends as well, like alsa or pa. It was > mentionned here: > https://forum.proxmox.com/threads/audiodev-driver-pa-support.62317/#post-285020 > > However that will require second level options for the audio backends, > which are not supported as it's coded. > > Cheers, > > Gilou All the best! Aaron [0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_audio_device