From: Programmingkid <programmingkidx@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Alberto Garcia <berto@igalia.com>,
QEMU devel list <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH 0/2] vvfat: fix two crashes.
Date: Wed, 26 May 2021 08:04:48 -0400 [thread overview]
Message-ID: <066C0E39-302E-4D12-A9D8-C7C1D0C5D91D@gmail.com> (raw)
In-Reply-To: <YK0jZB86ZGLDTM+J@merkur.fritz.box>
> On May 25, 2021, at 12:18 PM, Kevin Wolf <kwolf@redhat.com> wrote:
>
> 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
>
Thank you very much for this information.
next prev parent reply other threads:[~2021-05-26 12:05 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
2021-05-26 12:04 ` Programmingkid [this message]
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=066C0E39-302E-4D12-A9D8-C7C1D0C5D91D@gmail.com \
--to=programmingkidx@gmail.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.