From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124])
 by mx.groups.io with SMTP id smtpd.web12.37383.1623078966941100880
 for <devel@edk2.groups.io>;
 Mon, 07 Jun 2021 08:16:07 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VI5IuK73;
 spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1623078966;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=RwBBt2LKq5JjDW1dSmzBCQbaAmsmuif0bLsblAzourc=;
	b=VI5IuK73lNXGFK9vxiiAuJn6oWRt8cmkKL/4DxQBkhzD6fs/ZQcEc+MmHu9Uht4E7MWrPQ
	juBJ0b60WrpUjkMijF0gCYgVPE+kTYBVsS6A10IikSMU0cqVImMCeiZKB63Qv5A96eDqzq
	uXu1vJKiZfaSalrx/rybo5yXicZFzfM=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-186-cFO2fCMlMuOhOfGi-J2Ggg-1; Mon, 07 Jun 2021 11:16:03 -0400
X-MC-Unique: cFO2fCMlMuOhOfGi-J2Ggg-1
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E765579EC0;
	Mon,  7 Jun 2021 15:16:02 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-114-75.ams2.redhat.com [10.36.114.75])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id D24F05C1C2;
	Mon,  7 Jun 2021 15:16:01 +0000 (UTC)
Subject: Re: [edk2-devel] VirtIO sound device in qemu?
To: devel@edk2.groups.io, mcb30@ipxe.org, harlydavidsen@gmail.com
References: <CAJQtwF2sZewBmJQ-gUgtUiXo7rOrQyth0HV-YGo0GC2Nu9OjwA@mail.gmail.com>
 <c007c66e-9204-f23f-1e98-d257715bb9b8@ipxe.org>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <74f2a141-fe7c-b25c-ab65-aea8989cc885@redhat.com>
Date: Mon, 7 Jun 2021 17:16:00 +0200
MIME-Version: 1.0
In-Reply-To: <c007c66e-9204-f23f-1e98-d257715bb9b8@ipxe.org>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
Authentication-Results: relay.mimecast.com;
	auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 06/07/21 13:40, Michael Brown wrote:
> On 07/06/2021 05:41, Ethin Probst wrote:
>> For my audio output protocol (I wonder if we should abbreviate it as
>> AOP?) I need to get access to VirtIO devices in PCIe configuration
>> space. However, I can't seem to find a way of telling QEMU to use this
>> device for audio output. Is there something I missed, or something
>> that does support this?
> 
> Do you mean that you can't find a way to get QEMU to create a Virtio
> audio device visible to the guest, or that you can't find a way to get
> QEMU to connect this Virtio device to the host-side audio output?

My latest (admittedly, quite old) information has been that QEMU does
not implement a virtio-audio device yet. It's been work in progress.
Best inquire on qemu-devel, CC'ing the audio subsys maintainers.

Thanks
Laszlo