[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re:Re:Re:Re: Fwd: qemu no sound
From: |
Helge Konetzka |
Subject: |
Re:Re:Re:Re: Fwd: qemu no sound |
Date: |
Mon, 19 Dec 2022 21:59:35 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 |
Hello Andreas,
I noticed that many questions in the qemu-discus maling list are not
answered here? Doesn't anyone use qemu on Windows and doesn't know the
command how to start qemu-system-x86_64.exe with sound support? Where
are the developers of Qemu? it would be very nice if you would give
support for your project.
I already wrote an answer on qemu-devel list
(https://lists.gnu.org/archive/html/qemu-devel/2022-12/msg02445.html).
Here it is:
I'm focussing on your sound problem, so I did not test with kali image.
This command works for me on Windows 10 22H2 using a
Msys2/Mingw64-Bash-Shell with Qemu 7.1.94:
qemu-system-x86_64 \
-M q35 \
-accel whpx,kernel-irqchip=off \
-m 1536 \
-audiodev id=audio0,driver=dsound \
-device ich9-intel-hda -device hda-duplex,audiodev=audio0 \
-cdrom openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso
"-audiodev id=audio0,driver=dsound" defines, how the host provides the
sound
"-device ich9-intel-hda -device hda-duplex,audiodev=audio0" refers to
the sound provider and creates sound devices for the guest.
Maybe the whole command can be a starting point, too.
I did not use "-vga qxl" here, because this implies spice usage which
adds more complexity because the spice client needs to communicate with
qemu.
"-M q35" defines a more current computer than leaving it out
Regards,
Helge.