New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qvm-run fails with audio devices attached / audio broken #3042

Open
taonik opened this Issue Aug 23, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@taonik

taonik commented Aug 23, 2017

Qubes OS version (e.g., R3.2):

Qubes R4.0 rc1

Affected TemplateVMs:

dom0 + fedora-25 / debian-8


Expected behavior:

Designed AppVM should start normally and it does it with no audio devices attached.

Actual behavior:

  1. Audio devices pre-attached
[user@dom0 ~]$ qvm-pci
BACKEND:DEVID  DESCRIPTION
...
dom0:00_03.0       Audio Device: Intel Corporation Haswell-ULT HD Audio Controller
                                           audiovideo
dom0:00_1b.0       Audio Device: Intel Corporation 8 Series HD Audio Controller
                                           audiovideo
...
[user@dom0 ~]$ qvm-run audiovideo
audiovideo: Start failed: internal error: libxenlight failed to create new domain 'audiovideo'
  1. Attach the audio devices after the VM is started
[user@dom0 ~]$ qvm-pci
BACKEND:DEVID  DESCRIPTION
...
dom0:00_03.0       Audio Device: Intel Corporation Haswell-ULT HD Audio Controller
dom0:00_1b.0       Audio Device: Intel Corporation 8 Series HD Audio Controller
...

[user@dom0 ~]$ qvm-run audiovideo
[user@dom0 ~]$ qvm-pci attach audiovideo dom0:00_03.0
Got empty response from qubesd
[user@dom0 ~]$ qvm-pci attach audiovideo dom0:00_1b.0
Got empty response from qubesd

Steps to reproduce the behavior:

  1. Attach the audio devices from Qubes Menu -> (audiovideo) -> (audiovideo) VM Settings -> Devices and then start the AppVM.
  2. Start the AppVM and then try to attach the audio devices.

General notes:

My laptop is almost new and with Qubes R3.2 the sound worked fine and I had never encountered problems like these ones.
Now I can't use audio at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment