From: "Ludovic Courtès" <ludo@gnu.org>
To: 43062@debbugs.gnu.org, elaexuotee@wilsonb.com
Subject: bug#43062: --expose in vm does not reflect file modifications in guest
Date: Fri, 28 Aug 2020 16:11:26 +0200 [thread overview]
Message-ID: <87wo1ioo6p.fsf@gnu.org> (raw)
In-Reply-To: <3150ZD6Q06IY5.2LQMQ0E8MMOHQ@wilsonb.com> (elaexuotee's message of "Thu, 27 Aug 2020 11:04:47 +0900")
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
Hi,
elaexuotee--- via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:
> When using --expose to mirror a path between host and guest, the guest mirror
> fails to reflect file modifications from the host. However, file creation and
> deletion are correctly propogated.
>
> To pick up file modifications in the guest, it is sufficient to remount
> mirroring 9p filesystem.
>
> Is this behaviour expected?
I believe this comes from the “cache=loose” 9p mount option added in
commit e0d96774dd48c29ccc4c90fea1f8f71850ab0879.
Does the patch below help?
Chris, what do you think? How would this affect the performance issues
that led to e0d96774dd48c29ccc4c90fea1f8f71850ab0879?
Thanks,
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 529 bytes --]
diff --git a/gnu/system/vm.scm b/gnu/system/vm.scm
index 861f2a427a..80a8618729 100644
--- a/gnu/system/vm.scm
+++ b/gnu/system/vm.scm
@@ -699,7 +699,8 @@ of the GNU system as described by OS."
(device (file-system->mount-tag source))
(type "9p")
(flags (if writable? '() '(read-only)))
- (options "trans=virtio,cache=loose")
+ (options (string-append "trans=virtio"
+ (if writable? "" ",cache=loose")))
(check? #f)
(create-mount-point? #t)))))
next prev parent reply other threads:[~2020-08-28 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 2:04 bug#43062: --expose in vm does not reflect file modifications in guest elaexuotee--- via Bug reports for GNU Guix
2020-08-28 14:11 ` Ludovic Courtès [this message]
2020-08-29 6:38 ` elaexuotee--- via Bug reports for GNU Guix
2020-08-30 18:23 ` Christopher Baines
2020-08-31 13:52 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wo1ioo6p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43062@debbugs.gnu.org \
--cc=elaexuotee@wilsonb.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).