https://bugzilla.kernel.org/show_bug.cgi?id=219190 Bug ID: 219190 Summary: Kernel USB device namespacing Product: Virtualization Version: unspecified Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: kvm Assignee: virtualization_kvm@xxxxxxxxxxxxxxxxxxxx Reporter: weiss_julian@xxxxxxxxxx Regression: No When trying to bring a Rpi Compute Module 4 into flashable state. One has to connect the CM4 via USB to e.g. another Linux PC and exeecute rpiboot. Rpiboot will probe for the correct USB device, writes something to it, makes the device reconnect the USB connection and writes to the device again. When executing the rpiboot tool from within a podman container, which is started in privileged mode, rpiboot will successful probe the device and execute the first write. However, after resetting the device, strace shows rpiboot is about to open an USB device, which does not exist inside the container. When checking the hosts filesystem, the USB device exists at that specific location. How is it possible that my container knows the correct location of the outsides USB device, but is unable to find the filename of the USB device inside the container? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
