Anthony Liguori <anth...@codemonkey.ws> writes: > On 05/19/2010 02:00 PM, Chris Wright wrote: >> When libvirt launches a guest it first chowns the relevenat >> /sys/bus/pci/.../config file for an assigned device then drops privileges. >> >> This causes an issue for device assignment because despite being file >> owner, the sysfs config space file checks for CAP_SYS_ADMIN before >> allowing access to device dependent config space. >> >> This adds a new qdev configfd property which allows libvirt to open the >> sysfs config space file and give qemu an already opened file descriptor. >> Along with a change pending for the 2.6.35 kernel, this allows the >> capability check to compare against privileges from when the file was >> opened. >> >> Signed-off-by: Chris Wright<chr...@redhat.com> >> > > An fd as a qdev property seems like a bad idea to me. I'm not sure I > have a better suggestion though.
Shot from the hip without much thought: could we use monitor command getfd? That associates the fd with a name. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
