Here’s the trick in /etc/pulse/default.pa: But with just one sound card the default is the shortest option. One can (presumably) set the ID to something else (instead of the default), say 7, and then set inside.
But it suffices to replace the element with this: Now this^^^ won’t work by default, presumably, because sound goes to nowhere. So ultimately my solution was to create a “default” ICH9 audio card in virt-manager, which translates into something like this: However, this^^^ low-level configuration does *not* resemble the audio devices configured by default by virt-manager, which is quite confusing, because it doesn’t appear in the left configuration bar in virt-manager etc. 😉įor the record, your solution worked fine for me. This^^^ was not necessarily for “4.1 and below” it actually worked until 5.2.x and the legacy support for these environment variables got ultimately dropped in 6.0. So, my very first configuration used to be: I’ve found a oneliner modification to the XML generated by default by virt-manager (at least for my FreeBSD VM and ArchLinux host) that gets pulseaudio working.
Your pulseaudio method appears to be rather complex. The 1000 in /run/user/1000/pulse/native represents your user-id. If you have no sound at all, run pax11publish and check if a server with name /run/user/1000/pulse/native is available.
Make sure no further audio devices are added by virt-manager – remove all audio devices from the virtual hardware details bar (left side in VM info view). Replace your-username with your username. home/ your-username/.config/pulse/cookie k, Sudo nano /etc/apparmor.d/abstractions/libvirt-qemu Open the apparmor libvirt abstractions file via The part can hold further options, simply append the sound options if others were already present. Represents your user-id, 1000 is the default (one user) Id. The 1000 in server=unix:/run/user/1000/pulse/native In case is missing, find the line which ends with Make sure the very first line of the file does read: Ĭheck at the bottom of your config if a line exists. (-) Lots of users complain about bad sound quality Pulse Audio with QEMU 4.2 (and above) (+) Less sound delay than the spice server version Open VM spice server window while VM is running Option 2 – use Pulse Audio Basically it is double clicking on the running VM in the virt-manager list. In order to hear sound, I have to open the VM while it is running (I hope the sentence make sense 🙂 ). Add spice server via virt-manager GUIĪdding the spice server adds actually several devices to the VM config, one for example is a display. This one is pretty straight forward, open the info page of the VM on virt-manager and add a spice server. (-) a little more delay than direct pulse audio version (-) Needs VM window open in order to work (+) Very good for first setup of the VM OS.
MACSPICE PULSE WINDOWS 10
Set the frequency of your windows sound to 44100 Hz Set sample rate for default audio device in windows 10 Option 1 – use Spice Server Setting default sample rate in LinuxĪnd find/add/uncomment the lines and set these values: default-sample-rate = 44100 alternate-sample-rate = 48000Īfterwards restart the pulse audio service via In order to fix this make sure the host and the guest use the same default playback sample rate. In any case – harmonize sample rates of host and guest systemĪ common issue with sound passthrough between guest and host is lagging or chopped up sound playback. The Host runs an Asus Xonar DGX 5.1 PCIE sound card. I will compare spice server, pulse audio and a hardware solution.
MACSPICE PULSE HOW TO
In this post, I compare several options of how to get the sound output from an KVM virtual machine guest, back into the host. Virtual machine audio setup – or how to get pulse audio working
0 kommentar(er)
