Xen project Mailing List

Re: [Xen-devel] vsnd issue

On 11/25/19 3:31 PM, Oleksandr Grytsov wrote:

On Mon, Nov 25, 2019 at 2:25 PM Peng Fan <peng.fan@xxxxxxx> wrote:

Cc: sstabellini@xxxxxxxxxx; julien@xxxxxxx; xen-devel@xxxxxxxxxxxxx
Subject: Re: [Xen-devel] vsnd issue

On 11/25/19 12:40 PM, Artem Mygaiev wrote:

Hello Peng Fan

Please contact Oleksandr Andrushchenko (added to this thread) on this
issue.

   -- Artem

On Mon, 2019-11-25 at 10:24 +0000, Julien Grall wrote:

On 25/11/2019 10:19, Peng Fan wrote:

Hi All,

Hi,

I am trying vsnd from xen-troops with xen 4.13 and Linux 5.4, but
domu reports:

xen-troops is not part of Xen Project. Please contact the owner of
the repo for any help here.

I have CCed Artem who should be able to point to the author of vsnd.

Best regards,

aplay compl.mp3

Hm, could you please try the same with wav and not mp3 and get back with
the logs?

Same issue.
aplay hu01_48k.wav
ALSA lib 
../../../alsa-lib-1.1.9/src/pcm/pcm_direct.c:1156:(snd1_pcm_direct_initialize_slave)
 slave plugin does not support mmap interleaved or mmap noninterleaved access
ALSA lib ../../../alsa-lib-1.1.9/src/pcm/pcm_dmix.c:1120:(snd_pcm_dmix_open) 
unable to initialize slave
aplay: main:828: audio open error: Invalid argument

Is there any limitation with current vsnd? Is there any plan to upstream 
libxenbe and snd_be
to xen?

Thanks,
Peng.

ALSA lib ../../../alsa-lib-
1.1.9/src/pcm/pcm_direct.c:1156:(snd1_pcm_direct_initialize_slave)
slave plugin does not support mmap interleaved or mmap
noninterleaved access

ALSA frontend does not support mmap because of [1], so this is expected

ALSA lib ../../../alsa-lib-
1.1.9/src/pcm/pcm_dmix.c:1120:(snd_pcm_dmix_open) unable to
initialize slave
aplay: main:828: audio open error: Invalid argument

When executing aplay in domu, dom0 side log:
root@imx8qmmek:~# 13.11.19 08:24:57.484 | XenEvtchn       | DBG

Event received, port: 10
13.11.19 08:24:57.491 | StreamRing      | DBG - Request received,
id: alsa<hw:2;0>, cmd:9
13.11.19 08:24:57.500 | CommandHandler  | DBG - Handle command
[QUERY_HW_PARAM]
13.11.19 08:24:57.508 | AlsaPcm         | DBG - Query pcm device
hw:2,0 for HW parameters
13.11.19 08:24:57.516 | CommandHandler  | DBG - Return status: [0]
13.11.19 08:24:57.523 | XenEvtchn       | DBG - Notify event
channel, port: 10
13.11.19 08:24:57.531 | XenEvtchn       | DBG - Event received,
port: 10
13.11.19 08:24:57.538 | StreamRing      | DBG - Request received,
id: alsa<hw:2;0>, cmd:9
13.11.19 08:24:57.546 | CommandHandler  | DBG - Handle command
[QUERY_HW_PARAM]
13.11.19 08:24:57.554 | AlsaPcm         | DBG - Query pcm device
hw:2,0 for HW parameters
13.11.19 08:24:57.563 | CommandHandler  | DBG - Return status: [0]
13.11.19 08:24:57.570 | XenEvtchn       | DBG - Notify event
channel, port: 10
13.11.19 08:24:57.577 | XenEvtchn       | DBG - Event received,
port: 10
13.11.19 08:24:57.584 | StreamRing      | DBG - Request received,
id: alsa<hw:2;0>, cmd:9
13.11.19 08:24:57.593 | CommandHandler  | DBG - Handle command
[QUERY_HW_PARAM]
13.11.19 08:24:57.601 | AlsaPcm         | DBG - Query pcm device
hw:2,0 for HW parameters
13.11.19 08:24:57.610 | CommandHandler  | DBG - Return status: [0]
13.11.19 08:24:57.616 | XenEvtchn       | DBG - Notify event
channel, port: 10
13.11.19 08:24:57.624 | XenEvtchn       | DBG - Event received,
port: 10
13.11.19 08:24:57.631 | StreamRing      | DBG - Request received,
id: alsa<hw:2;0>, cmd:9
13.11.19 08:24:57.640 | CommandHandler  | DBG - Handle command
[QUERY_HW_PARAM]
13.11.19 08:24:57.647 | AlsaPcm         | DBG - Query pcm device
hw:2,0 for HW parameters
13.11.19 08:24:57.656 | CommandHandler  | DBG - Return status: [0]
13.11.19 08:24:57.663 | XenEvtchn       | DBG - Notify event
channel, port: 10
13.11.19 08:24:57.671 | XenEvtchn       | DBG - Event received,
port: 10
13.11.19 08:24:57.678 | StreamRing      | DBG - Request received,
id: alsa<hw:2;0>, cmd:9
13.11.19 08:24:57.686 | CommandHandler  | DBG - Handle command
[QUERY_HW_PARAM]
13.11.19 08:24:57.694 | AlsaPcm         | DBG - Query pcm device
hw:2,0 for HW parameters
13.11.19 08:24:57.703 | CommandHandler  | DBG - Return status: [0]
13.11.19 08:24:57.709 | XenEvtchn       | DBG - Notify event
channel, port: 10


My xl.cfg:
       vsnd = [
           ['CARD, short-name=Main,

sample-formats=s16_le;s8;u32_be',

               'PCM, name=Main',
                   'STREAM, unique-id=alsa<hw:2;0>, type=p',
                   'STREAM, unique-id=alsa<hw:2;1>, type=c,

channels-

max=2'
           ],
       ]

Config seems to be ok

The audio device on my board:
aplay -l
**** List of PLAYBACK Hardware Devices **** card 0: imxaudmix
[imx-audmix], device 0: HiFi-AUDMIX-FE (*) []
     Subdevices: 1/1
     Subdevice #0: subdevice #0
card 0: imxaudmix [imx-audmix], device 1: HiFi-AUDMIX-FE (*) []
     Subdevices: 1/1
     Subdevice #0: subdevice #0
card 1: cs42888audio [cs42888-audio], device 0: HiFi cs42888-0 [HiFi
cs42888-0]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
card 1: cs42888audio [cs42888-audio], device 1: HiFi-ASRC-FE (*) []
     Subdevices: 1/1
     Subdevice #0: subdevice #0
card 2: wm8960audio [wm8960-audio], device 0: HiFi wm8960-hifi-0 []
     Subdevices: 0/1
     Subdevice #0: subdevice #0

Is there something wrong in my configuration?

Thanks,
Peng.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx

https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fur

ldefense.com%2Fv3%2F__https%3A%2F%2Flists.xenproject.org%2Fmailman
%2
Flistinfo%2Fxen-devel__%3B!K6dmGCEab4ueJg!iTeJON61Y2nUcGMQr_y7-27
bR_
QlOG8gXqvRMaU8yy8nJuDhzWizylvl_6stD-ILOQ%24&amp;data=02%7C01%7
Cpeng.
fan%40nxp.com%7Ca70282eacf484b0c054408d77196071d%7C686ea1d3bc2
b4c6fa
92cd99c5c301635%7C0%7C0%7C637102761486569821&amp;sdata=eFoYN
WSSYod6l

7oBisDswR93cknmIpMaAcF70HqGKns%3D&amp;reserved=0

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist

s.xenproject.org%2Fmailman%2Flistinfo%2Fxen-devel&amp;data=02%7C01%
7Cp
eng.fan%40nxp.com%7Ca70282eacf484b0c054408d77196071d%7C686ea1d
3bc2b4c6
fa92cd99c5c301635%7C0%7C0%7C637102761486579808&amp;sdata=pfrVX
H1YFBOtX

ECbv40KKwTwd7EFygcOWrhjHDjViu4%3D&amp;reserved=0

[1]
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Felixir.b
ootlin.com%2Flinux%2Fv5.4-rc8%2Fsource%2Fsound%2Fxen%2Fxen_snd_fro
nt_alsa.c%23L685&amp;data=02%7C01%7Cpeng.fan%40nxp.com%7Ca7028
2eacf484b0c054408d77196071d%7C686ea1d3bc2b4c6fa92cd99c5c301635%
7C0%7C0%7C637102761486579808&amp;sdata=pEvilGNZSTvoY4YGg9%2BU
vDg7RHDzF26V2B4Bexkkaj0%3D&amp;reserved=0

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

Hi Peng,

When you use ALSA as sound backend on Dom0, HW parameters introduced
in xl.cfg must match ones that real HW has, e.g. format, rate, num channels,
buffer size.

1. You could check your real HW by playing the file on Dom0:

  aplay -D hw:2,0 sound.wav --dump-hw-params

See supported formats, channels, rate and buffer in bytes.
Then update xl.cfg accordingly.

Also make sure that aplay works as expected on your Dom0.

2. I don't see any errors in the sndbe log, could you provide log with place
     where the error occurs.

3. You can use pulseaudio as sound backend on Dom0. Pulseaudio doesn't
require exact matching of real HW params.

Please also see [1] which may be of some help as well [1] https://github.com/xen-troops/snd_be/issues/34 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.