On Mi, 2014-04-23 at 16:09 +0200, Laszlo Ersek wrote: > On 04/23/14 10:31, Gerd Hoffmann wrote: > > Implementation of a USB Media Transfer Device device for easy > > filesharing. Read-only. No access control inside qemu, it will > > happily export any file it is able to open to the guest, i.e. > > standard unix access rights for the qemu process apply. > > > > Signed-off-by: Gerd Hoffmann <kra...@redhat.com> > > --- > > default-configs/usb.mak | 1 + > > hw/usb/Makefile.objs | 4 + > > hw/usb/dev-mtp.c | 1103 > > +++++++++++++++++++++++++++++++++++++++++++++++ > > trace-events | 21 + > > 4 files changed, 1129 insertions(+) > > create mode 100644 hw/usb/dev-mtp.c > > Not a review or a note of any significance, just a question: how does it > appear in the guest (Windows and Linux)? Mountable block device > containing vfat, exposed by some guest driver?
Like a modern android phone (4.x, which doesn't export the sdcard as usb-storage any more), except that it is read-only (i.e. host -> guest xfer only). Guest integration usually is at file manager level. Windows has a shell extension for MTP, so it shows up in the explorer, you can browse like any other folder, you can copy stuff, and if you double-click a file it will work just fine too (as far I know windows does a temporary copy to a real file system to handle this transparently for applications). Linux filemanagers like gnome nautilus work simliar. cheers, Gerd
