|
|
| Line 1: |
Line 1: |
| − | == Introduction ==
| + | #REDIRECT [[Using Scream over IVSHMEM]] |
| − | '''Note: While this setup is possible it is ill-advised, Scream does not benefit from using IVSHMEM in any way, if anything it increases CPU load and latency due to the polling nature of the implementation. Scream operates far better over a vfio-net device which is already a zero-copy data transfer via shared memory. If you however insist on continuing you're on your own if you run into issues.'''
| |
| − | | |
| − | As of a recent windows 10 update (Time of writing: 20th Oct 2019), all programs that utilize audio will hang when the output is set to an ICH6 or ICH9 device. AC97 drivers are quite old, and setup is quite tedious. As a workaround, you can use [https://github.com/duncanthrax/scream Scream]. It's primarily developed by [https://github.com/duncanthrax duncanthrax] and provides an alternate way to send sound to the host. Scream is relatively painless to set up.
| |
| − | | |
| − | Assuming you already finished setting up Looking Glass in your virtual machine, you already have the IVSHMEM drivers installed. You can skip this part in the [https://github.com/duncanthrax/scream#using-ivshmem-between-windows-guest-and-linux-host official guide] for setting up Scream. In this guide, an example for Pulseaudio is provided. But scream supports ALSA as well.
| |
| − | | |
| − | A link to the official tutorial this guide is based on can be found [https://github.com/duncanthrax/scream#using-ivshmem-between-windows-guest-and-linux-host on the official Scream GitHub repository]! Below is a step-by step instruction for modifying your existing Looking Glass machine.
| |
| − | | |
| − | There's some special sauce at the bottom that is not in the official guide, but is highly recommended. See: [[#Linking Looking Glass with Scream for the perfect experience|Linking Looking Glass with Scream for the perfect experience]]
| |
| − | | |
| − | == Steps to install [https://github.com/duncanthrax/scream Scream] ==
| |
| − | At the time of writing, version [https://github.com/duncanthrax/scream/releases/tag/3.4 v3.4] was used.
| |
| − | | |
| − | === Configuring the windows VM ===
| |
| − | * Download the latest Scream release from the [https://github.com/duncanthrax/scream/releases GitHub repository].
| |
| − | ** '''Choose the non-source .zip file'''
| |
| − | * Inside that file, there's a directory called <code>Install</code>. Move it into your Windows 10 virtual machine
| |
| − | * Execute <code>install.bat</code> as administrator
| |
| − | | |
| − | ==== Additional Steps for using Scream via IVSHMEM ====
| |
| − | * Open registry editor and navigate to: <code>HKEY_LOCAL_MACHINE</code>\<code>SYSTEM</code>\<code>CurrentControlSet</code>\<code>Services</code>\<code>Scream</code>\<code>Options</code>
| |
| − | ** If the <code>Options</code> key doesn't exists, create it.
| |
| − | ** Create a <code>DWORD</code> value called <code>UseIVSHMEM</code> and set it to <code>2</code>.
| |
| − | : [[File:Scream_regedit_layout.png]]
| |
| − | :
| |
| − | : [[File:Scream_regedit_dword.png]]
| |
| − | * Alternatively you can set the aforementioned key by executing the following command inside an administrator prompt <code>REG ADD HKLM\SYSTEM\CurrentControlSet\Services\Scream\Options /v UseIVSHMEM /t REG_DWORD /d 2</code>
| |
| − | * Shut down the VM, and use <code>virsh edit <vm-name></code> and insert this snippet in the XML file.
| |
| − | ** '''Please notice that the size must match the number entered in the DWORD value as configured in windows.'''
| |
| − | ** If you get complaints like: "Attempted double use of PCI Address", change the slot number to something else and try again.
| |
| − | <source lang="xml"> <shmem name='scream-ivshmem'>
| |
| − | <model type='ivshmem-plain'/>
| |
| − | <size unit='M'>2</size>
| |
| − | <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/>
| |
| − | </shmem></source>
| |
| − | * Configuring the windows machine is now complete.
| |
| − | | |
| − | === Setting up the Linux host ===
| |
| − | The Linux host will use a 'receiver' to play sound. [https://github.com/duncanthrax/scream#receivers Instructions straight from the guide:]
| |
| − | <blockquote>'''''Linux/Pulseaudio''': Not included in the installer package. Just type ‘make’ to build it. You might need to install build tools and Pulseaudio development packages.''
| |
| − | '''''Linux/ALSA''': Originally contributed by ivan. Not included in the installer package. Just type ‘make’ to build it. You might need to install build tools and ALSA development packages.''
| |
| − | </blockquote>
| |
| − | | |
| − | ==== Additional Steps for using Scream via IVSHMEM ====
| |
| − | * Download the '''source code''' .zip for the same version of [https://github.com/duncanthrax/scream/releases Scream] you downloaded at the beginning.
| |
| − | * Extract the following directory: <code>Scream-X.X</code>/<code>Receivers</code>/<code>pulseaudio-ivshmem</code>
| |
| − | * Open a terminal inside the extracted directory containing a file named: <code>Makefile</code>
| |
| − | ** In the terminal, run: <code>make</code>
| |
| − | ** You might need some dependencies, for those, see the quote above.
| |
| − | * You are left with a file called: <code>scream-ivshmem-pulse</code>. Move it to a location of your choosing. (Your Looking Glass folder is a good choice.)
| |
| − | | |
| − | === Testing functionality ===
| |
| − | * Start the windows VM
| |
| − | * Confirm that Scream is your default audio source now in Windows.
| |
| − | * If using IVSHMEM, check if you have read-access to the <code>/dev/shm/scream-ivshmem</code> file.
| |
| − | * On the Linux Host run your choice of scream. IE: (scream-pulse/scream-alsa/scream-ivshmem/...)
| |
| − | * Play some test tunes in the windows VM. '''Make sure to set the audio output to scream and make sure your Linux host shows scream as an audio application (if using pulse)'''
| |
| − | * You should hear sound at this point. If you don't, something went wrong. (Maybe look at the [https://github.com/duncanthrax/scream#using-ivshmem-between-windows-guest-and-linux-host official guide]?)
| |
| − | | |
| − | === Linking Looking Glass with Scream for the perfect experience ===
| |
| − | We will use some bash magic to make sure Scream only runs for as long as Looking Glass is open. Therefore, we never run Looking Glass directly, but use bash to run it for us.
| |
| − | Create a file with a name of your choosing. This file will be used to start and stop Scream simultaneously with Looking Glass. Read the comments inside the snippet for further instructions and change the VM name and paths accordingly.
| |
| − | | |
| − | <source lang="bash">#!/bin/bash
| |
| − | | |
| − | virsh start Windows_10_VM # Optional line, this will simply start the VM if it isn't running. You can delete this if you wish. Make sure to change the name to your VM name.
| |
| − | /path/to/looking-glass-client >/dev/null 2>&1 & # Starts Looking Glass, and ignores all output (We aren't watching anyways)
| |
| − | # /path/to/scream-pulse & # Starts Scream with pulse
| |
| − | # OR
| |
| − | # /path/to/scream-ivshmem-pulse /dev/shm/scream-ivshmem & # Starts Scream with IVSHMEM
| |
| − | | |
| − | wait -n # We wait for any of these processes to exit. (Like closing the Looking Glass window, in our case)
| |
| − | pkill -P $$ # We kill the remaining processes (In our case, scream)</source>
| |
| − | | |
| − | Make sure the file is executable, and you should be good to go!
| |
