From: Kevin Wolf <kwolf@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
berto@igalia.com, QEMU devel list <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>,
mreitz@redhat.com
Subject: Re: [PATCH 0/2] vvfat: fix two crashes.
Date: Tue, 25 May 2021 18:18:44 +0200 [thread overview]
Message-ID: <YK0jZB86ZGLDTM+J@merkur.fritz.box> (raw)
In-Reply-To: <B4968AF6-F208-48F5-B431-0E84CAE8491C@gmail.com>
Am 24.05.2021 um 18:06 hat Programmingkid geschrieben:
> >>> qemu-system-ppc -usb -device usb-storage,drive=fat16 -drive file=fat:rw:fat-type=16:"<path of a host folder>",id=fat16,format=raw,if=none
> >>>
> On a related topic would you know if it is possible to use fat32
> instead of fat16 for host folder sharing? I did try replacing the text
> fat16 with fat32 but it didn't appear to work.
I think the correct syntax is fat:32:rw:<path>. But one of the first
things it does is:
warn_report("FAT32 has not been tested. You are welcome to do so!");
So probably nobody would be surprised if it broke.
Kevin
next prev parent reply other threads:[~2021-05-25 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 10:12 [PATCH 0/2] vvfat: fix two crashes Vladimir Sementsov-Ogievskiy
2021-05-24 10:12 ` [PATCH 1/2] block/vvfat: child_vvfat_qcow: add .get_parent_aio_context, fix crash Vladimir Sementsov-Ogievskiy
2021-05-24 10:12 ` [PATCH 2/2] block/vvfat: fix vvfat_child_perm crash Vladimir Sementsov-Ogievskiy
2021-05-24 15:41 ` [PATCH 0/2] vvfat: fix two crashes Programmingkid
2021-05-24 15:55 ` Vladimir Sementsov-Ogievskiy
2021-05-24 16:06 ` Programmingkid
2021-05-24 16:56 ` Vladimir Sementsov-Ogievskiy
2021-05-24 17:33 ` Programmingkid
2021-05-25 6:05 ` Vladimir Sementsov-Ogievskiy
2021-05-25 12:10 ` Programmingkid
2021-05-25 16:18 ` Kevin Wolf [this message]
2021-05-26 12:04 ` Programmingkid
2021-05-27 10:22 ` Kevin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YK0jZB86ZGLDTM+J@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=mreitz@redhat.com \
--cc=programmingkidx@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).