qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Anthony Lannuzel <anthony.lannuzel@hynesim.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] bidirectional data exchange between guest and host without network
Date: Wed, 8 Jul 2009 09:31:00 -0400	[thread overview]
Message-ID: <20090708133059.GQ15751@csclub.uwaterloo.ca> (raw)
In-Reply-To: <42816.89.3.148.243.1247047400.squirrel@webmail.aql.fr>

On Wed, Jul 08, 2009 at 12:03:20PM +0200, Anthony Lannuzel wrote:
> Yes, the thing is, I can not use the network, as it is used for another
> purpose, so I think I have to content myself with the basic linux
> filesystems.
> 
> I tried using a fat partition with the "sync" mount option, to avoid
> caching on both sides (still using virtio on /dev/sda8 on the host and
> /dev/vda on the guest).

sync only affects write caching, it does nothing for read caching,
which is where your real problem is.

> The host now reads data written by the guest but the guest does not see
> the host data.
> 
> Is there anything related to virtio that prevents this from working, as I
> think the mount option provides me with a filesystem that fulfils the
> conditions you just told me ?

Just the fact any sane OS does read caching is what makes it not work.
Filesystems are NOT going to do this for you.  You can not share
filesystems like that unless explicitly designed for it.

I remember many years ago in highschool we had a small set of machines
that had a shared scsi drive between 5 machines (all daisy chained).
You would shutdown all the machines, then start up the master machine,
make the drive read/write, add new software and updates, then shutdown,
switch the drive to read only, and boot all the systems.  They could
then all use the software on the drive, but anything you wanted to save
had to be done to floppy disks on the individual machines.  Writing a
shared drive was simply not an option.

-- 
Len Sorensen

  reply	other threads:[~2009-07-08 13:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  8:45 [Qemu-devel] bidirectional data exchange between guest and host without network Anthony Lannuzel
2009-07-07  9:02 ` Jamie Lokier
2009-07-07 13:11   ` Anthony Lannuzel
2009-07-07 14:12     ` Lennart Sorensen
2009-07-07 14:39       ` Jamie Lokier
2009-07-08 10:03         ` Anthony Lannuzel
2009-07-08 13:31           ` Lennart Sorensen [this message]
2009-07-11  0:01             ` Jamie Lokier
2009-07-08 13:34           ` Paul Brook
2009-07-08 13:57           ` Jamie Lokier
2009-07-09  7:51             ` Anthony Lannuzel
2009-07-11  0:04               ` Jamie Lokier
2009-07-12  9:02                 ` Richard W.M. Jones
2009-07-13 22:38                   ` Jamie Lokier
2009-07-14  5:54                     ` Richard W.M. Jones
2009-07-16  7:46     ` Amit Shah

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=20090708133059.GQ15751@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=anthony.lannuzel@hynesim.org \
    --cc=qemu-devel@nongnu.org \
    /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).