On Tue, Apr 16, 2019 at 12:45:04PM -0400, Bandan Das wrote: > Daniel P. Berrangé <berra...@redhat.com> writes: > > > On Tue, Apr 16, 2019 at 12:10:16PM -0400, Bandan Das wrote: > >> Daniel P. Berrangé <berra...@redhat.com> writes: > >> ... > >> >> > The store is read only by default. Are you trying something like: > >> >> > -device usb-mtp,rootdir=/code/mtpshare,readonly=false ? > >> >> > >> >> Ah ha, I didn't realize I had to enable write support explicitly. Will > >> >> retry with that. > >> > > >> > Even after setting readonly=false, I still can't get "mtp-sendfile" > >> > to succeed in a guest. > >> > > >> I posted a patch for a bug introduced by a recent commit that made smaller > >> file sizes return back with a incomplete file transfer. > >> > >> https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg02552.html > > > > Yes, I applied that and didn't see any difference in behaviour > > > > Just noticed the error message you posted: > > Error sending file. > Error 2: PTP Layer error 02ff: send_file_object_info(): Could not send > object info. > Error 2: Error 02ff: PTP I/O Error > ERROR: Could not close session! > > I can't find usb-mtp sending a "I/O error" on an error condition > for the objectinfo phase. It might be libmtp or even the command itself > failing for some reason. For incomplete transfer, I just checked, it's > spitting out the error message correctly as INCOMPLETE_FILE_TRANSFER. > > With libmtp version 1.13 on a FC24 guest, here's the output: > > $ mtp-sendfile test.txt test.img > libmtp version: 1.1.13 > > Device 0 (VID=46f4 and PID=0004) is UNKNOWN in libmtp v1.1.13. > Please report this VID/PID and the device model to the libmtp development team > ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, > trying again after resetting USB interface > LIBMTP libusb: Attempt to reset device > Sending test.txt to test.img > type: txt, 44 > Sending file... > Progress: 322 of 322 (100%) > New file ID: 7 > > What guest is this ? I can try to reproduce.
This was Fedora 26, so technically it is end of life, but then so is your F24 guest :-) Should really check with a modern guest like Fedora 29 or rawhide. 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 :|
