Public bug reported: Currently not a hard requirement yet, but I believe it could pretty fast become one.
So I wanted to start the MIR discussion at a lower prio to get a security evaluation to know the current status when any hard request comes up. It was just enabled in Debian, but so far qemu drops this dependency due to the component mismatch. [Availability] - Currently in Universe - Upstream is at https://virgil3d.github.io/ [Rationale] - Dependency for qemu's virgl support - Allow users KVM Guest 3d acceleration independent to GPU passthrough [Security] - I could not find any CVEs, but http://seclists.org/oss-sec/2016/q4/711 - Only a lib, no direct callable binaries [Quality assurance] - no open bugs at the moment in Ubuntu [Dependencies] - All further dependencies from there are in main already (as of today) [Standards compliance] - FHS and Debian rules are met [Maintenance] - no delta sync from Debian atm - no owning Team yet (can be decided when other blockers are out of the way) [Background information] - So far virgl considers itself still a "research project" so please as I specified handle this evaluation at a lower prio for now. ** Affects: virglrenderer (Ubuntu) Importance: Low Status: New ** Changed in: virglrenderer (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657409 Title: [MIR] virglrenderer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virglrenderer/+bug/1657409/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
