The contents of events.txt:
-vfio_region_read
vfio_region_write
I'm not sure if the events.txt is needed for JCS Qemu, but they don't
hurt. :)
Does it always hang? I did notice this version of qemu would often hang
during OS startup (less than 50% of the time though). Glad to know it
wasn't just me. :)
On 6/25/21 12:53 PM, <email address hidden> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #302 from Vincent Morel (<email address hidden>) ---
> Yes!
> I'll force the driver install. Thanks for your support. I have to go now
> but sure I will try all of this. On a side note, the Qemu I compile from
> the Git do not seems to start, just stuck.
> The one from the Ubuntu repo starts with no problem.
>
> Le ven. 25 juin 2021 à 15:37, <email address hidden> a
> écrit :
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>>
>> --- Comment #300 from TT (<email address hidden>) ---
>> (In reply to Vincent Morel from comment #299)
>>> I tried to follow the information about installing Qemu
>>> (
>> https://github.com/ryanprescott/realtek-verb-tools/wiki/How-to-sniff-verbs-
>>> from-a-Windows-sound-driver), but ran into problem and I'm not able to
>>> install the driver in windows (I have an error while starting qemu abut
>> my
>>> soundcard address
>>> -> qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no
>> available
>>> reset mechanism.
>>> ).
>>> So sadly I'm not able to get the hda_verb output here... :( Would love to
>>> help but for today I'm done. Maybe will have time sunday to try something
>>> else.
>>> Is there a program I can run into a windows partition to sniff the hda?
>> I'm
>>> almost sure I saw something but I cannot remember where...
>> Are you referring to RtHDDump_V236 binary?
>> Check Comment #236.
>>
>> --
>> You may reply to this email to add a comment.
>>
>> You are receiving this mail because:
>> You are on the CC list for the bug.
What were your ./configure arguments?
Here were mine: /opt/qemu/ jcs --enable-kvm trace-backends= log --target- list=x86_ 64-softmmu
./configure --prefix=
--enable-
Then I would run it with this script:
#!/bin/bash
_qemu=/ opt/qemu/ jcs/bin/ qemu-system- x86_64
sudo $_qemu -enable-kvm -hda win10.qcow2 -m 8G -smp 4 -vga std \ host=00: 1f.3,multifunct ion=on, x-no-mmap= true \ /path/to/ events. txt
-device vfio-pci,
-trace events=
The contents of events.txt:
-vfio_region_read
vfio_region_write
I'm not sure if the events.txt is needed for JCS Qemu, but they don't
hurt. :)
Does it always hang? I did notice this version of qemu would often hang
during OS startup (less than 50% of the time though). Glad to know it
wasn't just me. :)
On 6/25/21 12:53 PM, <email address hidden> wrote: /bugzilla. kernel. org/show_ bug.cgi? id=208555 /bugzilla. kernel. org/show_ bug.cgi? id=208555 /github. com/ryanprescot t/realtek- verb-tools/ wiki/How- to-sniff- verbs- Windows- sound-driver) , but ran into problem and I'm not able to
> https:/
>
> --- Comment #302 from Vincent Morel (<email address hidden>) ---
> Yes!
> I'll force the driver install. Thanks for your support. I have to go now
> but sure I will try all of this. On a side note, the Qemu I compile from
> the Git do not seems to start, just stuck.
> The one from the Ubuntu repo starts with no problem.
>
> Le ven. 25 juin 2021 à 15:37, <email address hidden> a
> écrit :
>
>> https:/
>>
>> --- Comment #300 from TT (<email address hidden>) ---
>> (In reply to Vincent Morel from comment #299)
>>> I tried to follow the information about installing Qemu
>>> (
>> https:/
>>> from-a-
>>> install the driver in windows (I have an error while starting qemu abut
>> my
>>> soundcard address
>>> -> qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no
>> available
>>> reset mechanism.
>>> ).
>>> So sadly I'm not able to get the hda_verb output here... :( Would love to
>>> help but for today I'm done. Maybe will have time sunday to try something
>>> else.
>>> Is there a program I can run into a windows partition to sniff the hda?
>> I'm
>>> almost sure I saw something but I cannot remember where...
>> Are you referring to RtHDDump_V236 binary?
>> Check Comment #236.
>>
>> --
>> You may reply to this email to add a comment.
>>
>> You are receiving this mail because:
>> You are on the CC list for the bug.