From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Will Cohen <wwcohen@gmail.com>, Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH 00/11] 9p: Add support for Darwin
Date: Thu, 14 Oct 2021 14:55:55 +0200 [thread overview]
Message-ID: <3493661.FTZtrCqsiM@silver> (raw)
In-Reply-To: <CAB26zV17E_b_-nnLBTeH2QxT=c7vy9zvPak+Tp4TkyECNGUS-Q@mail.gmail.com>
On Donnerstag, 14. Oktober 2021 14:22:19 CEST Will Cohen wrote:
> Correct. It's been tested and functions when applied to QEMU master, with
> host running macOS Big Sur 11.6 (personal machine) using client 9p2000.L
> (taking a cue from the guest mounting instructions on
> https://wiki.qemu.org/Documentation/9psetup).
So it was the Linux kernel's 9p client on guest side with 9p 'local' fs driver
and 9p transport driver was 'virtio-pci'.
I was just wondering if somebody already bothered for macOS being the guest,
because that use case is a bit more challenging, especially with macOS 11 and
higher. But I see that's nothing you were into.
> On Thu, Oct 14, 2021 at 7:57 AM Christian Schoenebeck <
>
> qemu_oss@crudebyte.com> wrote:
> > On Donnerstag, 14. Oktober 2021 12:48:55 CEST Will Cohen wrote:
> > > Many thanks for all the clarifications — it’s my first time using
> > > git-send-email and first time with mailing-list-based devel workflows.
> >
> > Will
> >
> > > adjust accordingly, work through gitlab, and eventually resend via
> > > git-publish as v2.
> >
> > So the intended use case is macOS being host.
> >
> > Has this been tested, and if yes, using which 9p client and which macOS
> > version?
> >
> > Best regards,
> > Christian Schoenebeck
next prev parent reply other threads:[~2021-10-14 12:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 23:03 [PATCH 00/11] 9p: Add support for Darwin Will Cohen
2021-10-13 23:03 ` [PATCH 01/11] 9p: linux: Fix a couple Linux assumptions Will Cohen
2021-10-13 23:03 ` [PATCH 02/11] 9p: Rename 9p-util -> 9p-util-linux Will Cohen
2021-10-13 23:03 ` [PATCH 03/11] 9p: darwin: Handle struct stat(fs) differences Will Cohen
2021-10-13 23:03 ` [PATCH 04/11] 9p: darwin: Handle struct dirent differences Will Cohen
2021-10-13 23:03 ` [PATCH 05/11] 9p: darwin: Ignore O_{NOATIME, DIRECT} Will Cohen
2021-10-13 23:04 ` [PATCH 06/11] 9p: darwin: Compatibility defn for XATTR_SIZE_MAX Will Cohen
2021-10-13 23:04 ` [PATCH 07/11] 9p: darwin: *xattr_nofollow implementations Will Cohen
2021-10-13 23:04 ` [PATCH 08/11] 9p: darwin: Compatibility for f/l*xattr Will Cohen
2021-10-13 23:04 ` [PATCH 09/11] 9p: darwin: Provide a fallback implementation for utimensat Will Cohen
2021-10-13 23:04 ` [PATCH 10/11] 9p: darwin: Implement compatibility for mknodat Will Cohen
2021-10-13 23:04 ` [PATCH 11/11] 9p: darwin: meson: Allow VirtFS on Darwin Will Cohen
2021-10-15 12:10 ` Paolo Bonzini
2021-10-14 7:03 ` [PATCH 00/11] 9p: Add support for Darwin Greg Kurz
2021-10-14 10:48 ` Will Cohen
2021-10-14 11:57 ` Christian Schoenebeck
2021-10-14 12:22 ` Will Cohen
2021-10-14 12:55 ` Christian Schoenebeck [this message]
2021-10-14 13:23 ` Will Cohen
2021-10-20 12:38 ` Christian Schoenebeck
-- strict thread matches above, loose matches on Subject: below --
2021-10-13 21:31 Will Cohen
2021-10-13 21:27 Will Cohen
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=3493661.FTZtrCqsiM@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=wwcohen@gmail.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).