Granted. I'm sure that's true, but yes, I am using VVFAT for two reasons: (1) it is direct, read/write, host-to-guest file access, and (2) it is the easiest method to transfer files between host and guest.
When I first encountered the need to transfer files I had on my host to my VM, I looked for direct methods because it seemed more strait forward. VVFAT worked for small files, which is all I had to move for a long time. Also, I didn't test writes to the VVFAT because I didn't do that much, until recently. After using this feature for a while, I found it to be extremely convenient and useful. Secondly, I found VVFAT much easier to use than the network-based transfer methods. I didn't want to use QEMU's CIFS/SMB/Samba option because it does not allow the use of an alternate Samba configuration file. I didn't want to have to configure /etc/smb.conf just run my VM in user space. (At least, I couldn't figure out how to do it, otherwise.) Similar inconveniences occur using FTP and SSH (which I'm using now, but wouldn't want to at work). Generally speaking, I'm not really using VVFAT as a disk image. I'm using it as a file transfer method. Using an actual disk image would require mounting the disk image in on the host, either via root access, FUSE, or using filesystem editing tools, which are inconvenient. I have created ISO9660 images to import files, which works, but requires creating a new image every time I need to import more files and doesn't support writes, of course. (I don't know how UDF would work on a disk image file. Would that work?) I suppose the next thing I should try is an NTFS-3g filesystem which I could mount with FUSE in my Linux host and natively in my Windows VM. That's still less convenient than VVFAT, however, since I would have to mount/umount the image on the host to get access and the VM would still have to be off. I would still prefer VVFAT to all of these options. I really appreciate your help. Thank you for taking my report seriously. If VVFAT is buggy and cannot be fixed easily, I defer to the judgment of others and ask only that this limitation be well documented in the primary references. But, I'm convinced that a direct, host-to- guest file access scheme is valuable. If there is another solution, I apologize for my ignorance and I would appreciate being pointed in the right direction. -- Corruption of File Data/Filename w/ Virtual FAT (VFAT) https://bugs.launchpad.net/bugs/356808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
