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: Wed, 20 Oct 2021 14:38:35 +0200 [thread overview]
Message-ID: <22395312.jNLmHM9Y7u@silver> (raw)
In-Reply-To: <CAB26zV1W3EDF9_CpQue3TiskP1VYX4SEkmsCiVG3rfh8XHTUDg@mail.gmail.com>
On Donnerstag, 14. Oktober 2021 15:23:25 CEST Will Cohen wrote:
> Correct, sorry for the imprecise language. The use case being contemplated
> is limited to Linux as the guest side, specifically for cross-platform
> tools where the macOS implementation consists of integrating a Linux VM via
> QEMU.
>
> NixOS (updater of the original patch,
> https://github.com/NixOS/nixpkgs/pull/122420) would be able to use this to
> provide macOS support via a VM.
>
> Lima and Podman as containerization alternatives to Docker would like to
> performantly mount volumes between macOS users and their respective VMs.
> Lima currently accomplishes this via sshfs, but would like to move to 9p
> for stability/performance reasons
> (https://github.com/lima-vm/lima/issues/20). Podman has yet to fully settle
> on an implementation at all due to similar outstanding concerns, but the
> furthest along proposed implementation choice has been 9pfs as well
> (https://github.com/containers/podman/pull/11454), pending adoption of such
> functionality in QEMU upstream.
I only had a glimpse on the patches so far. From what I've seen, I don't
expect much of a problem to bring this series through. I will have a closer
look on v2 though. I also have to read the old discussions where I was not
involved yet.
Soft freeze for QEMU 6.2 is close BTW (November 2nd):
https://wiki.qemu.org/Planning/6.2
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2021-10-20 12:39 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
2021-10-14 13:23 ` Will Cohen
2021-10-20 12:38 ` Christian Schoenebeck [this message]
-- 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=22395312.jNLmHM9Y7u@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).