Kyvos was updated

@white

Quote:
Yes. The VirtioGPU graphics commands are piped through the host OS' drivers, so you can use any graphics card that's supported by the host system.


Quote:
The virtio GPU specification doesn't include an audio block. There is a virtio audio specification, but that's a totally different drier.

I haven't written any audio drivers. We were going to use Geennaam's HD audio driver, but discovered that the RadeonHD/RX driver would have to be rewritten to use AMD's new (very big) display module. HDMI audio support is incomplete in the original framebuffer driver code, and so doesn't work.

Hans

@Hans

I'm starting to understand the Virtio GPU driver better.

Excellent.

As for the audio, I'll fix it sooner or later.


It would be difficult to create a Virtio audio driver to use with Qemu for AmigaOS.
I mean in terms of development time ?

possibly:
-ac97 -es1370

@white
You probably misunderstood what I wrote. I didn't say that you should reply to Zoltan and his comment. I just said that it would be better to move that discussion to another thread, for the clarity of discussions, since the whole topic you are talking about is not related with Kyvos at all.

Quote:

I am so sorry I disappointed you and I didn't give you the answer you expected. As you can understand, for me giving you any answer requires me to put a lot of energy work on something that I do not use, on an operating system (windows) I do not use, on a topic that I do not see the point of. To do that and investigate it for you and find a solution for you, I need to stop doing the other things I am already work on, especially on bringing new software for OS4 and new features to Kyvos. If that's what you ask, I am afraid it won't happen. The projects I will work on are only me to choose.

Also, in case you haven't realised yet, the virtio-gpu driver is under beta testing, and all the beta testers have signed an NDA which does not allow us to comment anything about the driver, its performance and the way it works.

So, if you need to discuss how you can load in Qemu apps from other systems, please open a new thread. If you make it work, and provide that information, I can consider providing that solution to everyone through my application Kyvos.

No one told you not to discuss it, and no one told you that your comments will be deleted. Please stop attacking me like that.

@white
"The problem is the audio doesn't work."

S/PDIF doesn't work, but line out works.

S/PDIF works under Linux but not with QEMU and AmigaOS 4.1.

Tested with onboard sound on a Z170X Gaming7 with Creative Soundcore 3D


@walkero
Could you add/enable GPU passthrough to the Linux version?

@white
Quote:
Maybe move this discussion to some other thread too. QEMU can't use VMWare network and neither NPCAP. This is some hack UAE supports but QEMU does not. Linux version of NPCAP does exist as you can read on the NPCAP homepage which says it's a Windows version of a Linux library but it's not needed to make virtual network cards for QEMU as that is using TAP which is built in the Linux kernel. There is also a version of TAP for Windows (maybe newer Windows versions can do it and for older it was part of some VPN package) which QEMU can use. Unless you write a new network backend in QEMU you won't be able to use what UAE uses as QEMU does not support that but it can do the same with TAP just in another way.

@Falke_34
Quote:
Adding the -device vfio-pci option to QEMU command line is easy but it won't work unless you did all the previous setup that Kyvos won't do for you. (See my page on this at the URL in my signature below on what needs to be setup.) Without that it won't work. Maybe Kyvos should have an "add custom QEMU options" input if it does not have that yet where you could add these options that you need.

@Falke_34
Quote:

As much as I know, having a GPU passthrough configured is quite complicated because the user needs to understand the way that the graphics card is connected to the host system. This I believe is for advanced Qemu users. When someone wants to do that, usually do not need a tool like Kyvos, and possibly, they need to set up a system that boots straight into the OS4.

If I add an option like that I should make all the configuration to be available through Kyvos, with all the needed options. This is not in my target yet.

But, Kyvos doesn't restrict you to add anything you need. Using the VM config file it is possible to add any argument needed. That's why I provided it as a plain text file, than saving it to a more closed type. This is open to everyone to add more arguments, or change others as they need. I have some information about it in the manual.

@balaton
Quote:

This is something that I have in my to-do list. But this can already be done since the first release of Kyvos, and described in the manual as well. The config files can be changed any way the users would like.

@walkero
Quote:
Those who choose a GUI to generate the command script/config file probably don't want to edit it without a GUI. So an input field within the GUI to enter additional options or an edit window to allow editing (and breaking) the config file from within the GUI might help encourage users to do that, otherwise they probably will just keep complaining to add everything to the GUI.

@balaton
Yeap, you are right. That's why I have it in my to-do list. Although, I have not implemented it yet because, it is not high on my priority, and secondly, there needs to be a way to understand if the user tries to override one of the arguments that is already there. So, as you can imagine, is not just a matter of taking whatever the user puts into a text field and use them with the Qemu command.

In my opinion, the person who is aware of what kind of extra arguments to use without breaking anything else, should be advanced enough to understand how to add them in the config files, which is already available.

@Walkero
Sorry,I'm a bit dumb, but I registered to your site then I did a donation to get Kyvos, but I don't find where to download it

@ilbarbax

it should be in your settings - try https://ko-fi.com/manage/supportreceived?src=sidemenu and change the drop down menu to 'shop orders' (there are a few depending on how it was paid/not paid).

You should then be able to click on a 'View Details' button for the order, and then 'View Content' to see the download links for the files.

Ok thanks it worked, even if, I'm quite sure, before, this view content button was not present.

@walkero

And adding a "manual override options commandline" textbox and just adding/pasting to the "internal" command line options you build with gui.