[Bug 1908832] Re: jack audio dev produces no sound

2021-02-24 Thread José Pekkarinen
Hi, I spend some time debugging this during the morning, I found that there is a check while connecting the ports that always exits the function without connecting the jack ports, simplifying it as in the following diff lets me build and use the audio outputs correctly in the vm: diff --git a/au

[Bug 1908832] Re: jack audio dev produces no sound

2021-02-24 Thread José Pekkarinen
just for completeness, this is how the output of the vm launch looks like after the change: jack: connect out-(null):output 0 -> system:playback_1 jack: connect out-(null):output 1 -> system:playback_2 jack: JACK output configured for 48000Hz (1024 samples) jack: connect system:capture_1 -> in-(nu

[Bug 1908832] Re: jack audio dev produces no sound

2021-02-24 Thread José Pekkarinen
Yes, I agree, the patch itself is a quick fix, indeed, if I look to the graphs in QJackCtl, I would expect to see new bubbles from qemu connected to the system ports, as it happens when I connect Firefox or Falkon through alsa -> jack plugin, as per the output you can see it's using some sort of nu

[PATCH v2] Autoconnect jack ports by default

2021-02-24 Thread José Pekkarinen
This patch provides a default value to connect jack ports when the user don't specify connect-ports. Buglink: https://bugs.launchpad.net/qemu/+bug/1908832 Signed-off-by: José Pekkarinen --- audio/jackaudio.c | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --

[Bug 1908832] [NEW] jack audio dev produces no sound

2020-12-20 Thread José Pekkarinen
Public bug reported: Hi, I'm testing the new jack audiodev backend in my laptop. The host system is gentoo, using the ebuild for qemu 5.1.0-r2, and I'm using jack use flag globally in the system so any ebuild that have support for jack should be build with it. The jack setup reportedly works as I

[Bug 1908832] Re: jack audio dev produces no sound

2020-12-20 Thread José Pekkarinen
I'm afraid it didn't. Jack version is: * media-sound/jack2 Latest version available: 1.9.16 Latest version installed: 1.9.16 Size of files: 952 KiB Homepage: https://jackaudio.org/ Description: Jackdmp jack implemention for multi-processor machine Licens

[Bug 1908832] Re: jack audio dev produces no sound

2020-12-20 Thread José Pekkarinen
I unmasked qemu-5.2.0-r1, well, actually any newer qemu coming from gentoo, and rebuild the software. The situation is still reproducible, which confirms what I tested yesterday with the patch. I also cleaned up the launch script to remove several spice related unneeded since I use the gtk display,

[Qemu-devel] [Bug 1818367] [NEW] Initialization of device cfi.pflash01 failed: Block node is read-only

2019-03-02 Thread José Pekkarinen
Public bug reported: Hi, I have several vms defined in libvirt using ovmf for uefi, since a later update of my server I'm unable to start any of the domains defined. This is an example of the output given: # virsh start os-1 error: Failed to start domain os-1 error: internal error: qemu unexpect

[Qemu-devel] [Bug 1818367] Re: Initialization of device cfi.pflash01 failed: Block node is read-only

2019-04-18 Thread José Pekkarinen
Extract from the libvirt log of todays launch of vms. ** Attachment added: "libvirt.log" https://bugs.launchpad.net/qemu/+bug/1818367/+attachment/5256716/+files/libvirt.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://

[Qemu-devel] [Bug 1818367] Re: Initialization of device cfi.pflash01 failed: Block node is read-only

2019-04-18 Thread José Pekkarinen
The uncommented piece of my /etc/libvirt/qemu.conf. vnc_listen = "192.168.0.61" user = "root" group = "root" dynamic_ownership = 0 nvram = [ "/usr/share/edk2-ovmf/OVMF_CODE.fd:/usr/share/edk2-ovmf/OVMF_VARS.fd", ] For some reason, emails directly from mailing list are not hitting my inbox

[Qemu-devel] [Bug 1818367] Re: Initialization of device cfi.pflash01 failed: Block node is read-only

2019-04-18 Thread José Pekkarinen
seems to be piece of true on Phil's comments, as extracting the command on the log and executing it manually the result is the following: 2019-04-18T19:37:49.685841Z qemu-system-x86_64: -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-6-os-1 /master-key.aes: Unable to read

[Qemu-devel] [Bug 1818367] Re: Initialization of device cfi.pflash01 failed: Block node is read-only

2019-04-19 Thread José Pekkarinen
thanks for the thorough pointers Laszlo, I did and run in different kind of issues, and given that I was just having the vars around I really wonder how it ever worked, perhaps I copied the unified and I forgot, as gentoo thas provide it: # du -h /usr/share/edk2-ovmf/* 1.9M/usr/share/edk2-ovmf

[Qemu-devel] [Bug 1818367] Re: Initialization of device cfi.pflash01 failed: Block node is read-only

2019-04-19 Thread José Pekkarinen
oh well, it turns out to be actually related, it turns out virt-aa-helper is skipping the code file of ovmf: 2019-04-19 10:06:43.576+: 9272: error : AppArmorGenSecurityLabel:469 : internal error: cannot load AppArmor profile 'libvirt-34c41008-ab91-483b-959c-81a7a12ae9be' 2019-04-19 10:09:25.

[Qemu-devel] [Bug 1818367] Re: Initialization of device cfi.pflash01 failed: Block node is read-only

2019-04-20 Thread José Pekkarinen
this is apparmor profile related in the end, rebooting with apparmor disabled allows the domain to boot, so I'll deal with the gentoo community, and this can be closed. Thanks! José. ** Changed in: libvirt Status: New => Invalid -- You received this bug notification because you are a

[Bug 1505759] Re: Usb passthrough of devices plugged to AMD FCH USB OHCI Controller failing on q35.

2020-11-16 Thread José Pekkarinen
I found a different arrangement that made it for me, so that particular case, I don't know if it works for me, or if it still fails the same, and versions has gone so far to check, I'd simply mark this invalid and forget of it. Best regards. José. ** Changed in: qemu Status: Incomplete =>