Markus Partheymueller

Just to clarify: Our instructions including disabling hardening are mainly because that's how we know it's possible to run the freshly built binaries. We are not recommending to ignore warnings...

Just to let everyone know, we have now included more information in the readme. Feel free to have a look and let us know if that clarifies things!

Thanks for your interest! Our current development model makes it a bit complicated to just accept PRs on GitHub, but if you don't mind, a colleague will reach out to...

I just built the standard VirtualBox from source and I am getting the same issue. I am not really an expert in packaging VirtualBox for various distributions, but I've seen...

I'll close this since it's more of a packaging problem and not about this particular backend implementation. If you feel like there is more we should discuss here, feel free...

From what I understand on the website, that should be possible. However, we currently don't focus on binary packaging so we could only assist when something doesn't work.

We are currently in the process of validating AMD. We have not seen any issues yet, so it should be perfectly fine to give it a try. It's just not...

While it is currently not officially supported or very well tested, you can try to use the PCI pass-through functionality we added for SR-IOV. If you adapt the [instructions](https://github.com/cyberus-technology/virtualbox-kvm/blob/dev/README.intel-sriov-graphics.md) to...

Actually, no patch disappeared. But the link name is currently tied to the release version of VirtualBox and at the time of the update (#330796), the new KVM backend version...

Yes, you are correct that the patch set is currently created against VirtualBox 7.0. We did not look into 7.1 yet.