[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
I believe this expiration is in error, as the posters did provide
feedback...
** Changed in: qemu-kvm (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
Jake's problem was that pulseaudio was not installed. That could be a bug in
the
installer, but I would actually guess it is just expected with KDE - do they
still use
arts?
Sam's is not a bug, but a shortcoming in vnc. FreeNX and, as he points out,
rdesktop,
do support remote audio. None
Hi Serge,
To be more precise:
* rdesktop from the current workstation to a Windows VM on the current
workstation connects correctly (rdesktop connects correctly) to
PulseAudio on the current workstation. This allows the rdesktop user to
hear the sound being produced by the Windows VM through
FYI I am now running kubuntu 10.10. Just tried a Windows XP VM with KVM
set to emulate an intel integrated audio card. There is still no sound
from the VM to PulseAudio. Rdesktop to the VM loads the RDP driver
correctly in Windows and the sound comes through. Please let me know if
there's a
Quoting Sam Azer (575...@bugs.launchpad.net):
The virtual sound card is in KVM/QEMU, there is some documentation on
the many command line parameters that control it, there are many options
intended to make it possible to use the feature on workstations with
different sound system setups, the
THANK YOU!!
First let me say that the command line options that you listed above
work perfectly. That's already a big step forward.
As you can see from the initial set of error messages provided by Peter
Bienstman, the original problem was a connection refused message.
I don't remember what
Hi Serge,
I'm not the right person for this job. It may be there's something wrong
with the way kvm asks for pulse resources. There might also be a
resource conflict between the virtual network devices and the virtual
sound device. I've put a few hours into it but I'm not knowledgeable
enough to
Hi Jake,
can you tell us the exact command line you were running? I have a basically
stock 10.04 laptop, and the following:
kvm -drive file=lucid.img,if=virtio,index=0,boot=on -m 1G -smp 2
-net nic,model=virtio -net user -soundhw es1370
runs just fine for me. Are you able to run, say,
Serge,
Sorry, I should have provided more info. I'm running the Kubuntu
variant and did a distribution upgrade from Karmic to Lucid, after which
this problem started occurring.
Turns out I was sloppy in my checks, the pulseaudio package was not
installed. I was thrown off by the fact
FYI I also did an online upgrade from karmic to lucid but everything
works perfectly except KVM. Pulseaudio works fine from KDE apps like
amarok as well as Adobe Flash under Firefox and Chrome. I remember I
lost cups-pdf during the upgrade but everything sound-related upgraded
perfectly. The only
I have this same problem:
$ dpkg -s pulseaudio qemu-kvm | grep -E '^(\s*$|Package|Version)'
Package: pulseaudio
Version: 1:0.9.19-0ubuntu4
Package: qemu-kvm
Version: 0.12.3+noroms-0ubuntu9
I get the errors shown in the original report and also some additional
'Internal Error' ones
Could you outline the version of the system and packages used on the
host?
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Low
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
--
no sound: pulseaudio connection refused
https://bugs.launchpad.net/bugs/575919
You
13 matches
Mail list logo
