On Tue, May 16, 2023 at 05:06:24PM +0200, Markus Armbruster wrote: > Daniel P. Berrangé <berra...@redhat.com> writes: > > > On Tue, May 16, 2023 at 04:04:39PM +0200, Markus Armbruster wrote: > >> Daniel P. Berrangé <berra...@redhat.com> writes: > >> > >> > On Tue, May 16, 2023 at 12:23:28PM +0200, Markus Armbruster wrote: > >> >> Daniel P. Berrangé <berra...@redhat.com> writes: > >> >> > >> >> > On Tue, May 16, 2023 at 10:47:52AM +0200, Markus Armbruster wrote: > >> >> > >> >> [...] > >> >> > >> >> >> So, this is basically a way to retrieve an eBPF program by some > >> >> >> well-known name. > >> >> >> > >> >> >> Ignorant question: how are these programs desposited? > >> >> > > >> >> > The eBPF code blob is linked into QEMU at build time. THis API lets > >> >> > libvirt fetch it from QEMU, in base64 format. When libvirt later > >> >> > creates NICs, it can attach the eBPF code blob to the TAP device > >> >> > (which > >> >> > requires elevated privilleges that QEMU lacks). NB, libvirt would > >> >> > fetch > >> >> > the eBPF code from QEMU when probing capabilities, as once a VM is > >> >> > running it is untrusted. > >> >> > >> >> Okay, I can see how that helps. I trust the blob is in a read-only > >> >> segment. Ideally, libvirt fetches it before the guest runs. > >> > > >> > Whether the blob is in a read-only segment or not isn't important, > >> > because it transits writable memory in the QMP command marshalling. > >> > >> True. We could bypass marshalling. Unclean hack. Or we could sign the > >> bits cryptograhically. Key management headaches. Not worth it, because > >> fetching it before QEMU becomes untrusted is easier. > >> > >> However, I now wonder why we fetch it from QEMU. Why not ship it with > >> QEMU? > > > > Fetching it from QEMU gives us a strong guarantee that the eBPF > > code actually matches the QEMU binary we're talking to, which is > > useful if you're dealing with RPMs which can be upgraded behind > > your back, or have multiple parallel installs of QEMU. > > Yes, but what makes this one different from all the other things that > need to match?
Many of the external resources QEMU uses don't need to be a precise match to a QEMU version, it is sufficient for them to be of "version X or newer". eBPF programs need to be a precise match, because the QEMU code has assumptions about the eBPF code it uses, such as the configuration maps present. There is another example where a perfect match is needed - loadable .so modules. eg if you're running QEMU and trigger dlopen of a QEMU module, the loaded module needs to come from the perfect matching build. Most distros don't solve that, but there was something added a while back that let QEMU load modules from a specific location. The idea was that the RPM/Deb package manager can upgrade the modules, but the modules from the previously installed QEMU would be kept in somewhere temporary like /var/run/...., so that pre-existing running QEMU could still load the exact matched .sos. While that hack kinda works it has too many moving parts for my liking, leaving failure scenarios open. IMHO, being able to directly fetch the resource directly from QEMU is a better strategy for eBPF programs, as it eliminates more of the failure scenarios with very little effort. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
