qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Looking for an easy way to exchange data bidirectional between host and guest (including some suggestion)
Date: Mon, 6 Jun 2005 10:28:49 -0400	[thread overview]
Message-ID: <20050606142848.GA21394@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0506051236080.11204@filer.marasystems.com>

On Sun, Jun 05, 2005 at 09:17:45PM +0200, Henrik Nordstrom wrote:
> On Fri, 3 Jun 2005, Jan Marten Simons wrote:
> 
> >Ok, I talked about this issue in irc lately, but as this list will have
> >a larger audience I'll post this here as well. So here is the (cleaned) 
> >log:
> >
> >What I want:
> >
> ><jamasi> some feature I'm really missing is: a v(S)FTP sever inside the
> >emulated network offering a local folder of the host for R/W-access.
> 
> Running a FTP server on the host with proper permissions is sufficient for 
> this. There is plenty of FTP servers available for all platforms where 
> qemu runs.
> 

Hmm...what if you don't have root/administrator access? It could still work if
you are determined enough, but thats not the sort of thing you want to force
onto a beginner.

> I don't quite get why everyone insists that qemu should have various 
> network services built-in. There already is too much of that imho (TFTP 
> and some SMB glue). The goal of qemu is to emulate the CPU and required 
> hardware, not to provide full network server services.
> 

I agree. TFTP might be useful if qemu one day supports netbooting, though.

> What would perhaps make sense in this discussion is to generalize the 
> user-net port redirection used for the SMB access allowing it to be used 
> in a more general manner, then perhaps even ripping out the smb (Samba) 
> support glue and replacing it by a wrapper setting things up as suitable 
> using the general slirp pipe support. So instead of having the smb support 
> glue hardcoded within the qemu binary just have it start the suitable 
> daemon wrapper when the port in question is accessed. Apart for allowing 
> it to be used for other services than SMB it would also allow the SMB 
> support to be tailored more closely to your needs.

I agree, thats a very good idea.

Of course, that doesn't apply if you cant use SMB, as was this person's case.
(Does the SMB support in qemu even work on Windows hosts?)

Giving the TFTP write access is probably the way to go (iirc this person would
have used TFTP in lieu of FTP, except that write access was required which made
TFTP a non-option).

> 
> Regards
> Henrik
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2005-06-06 14:42 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-03 13:57 [Qemu-devel] Looking for an easy way to exchange data bidirectional between host and guest (including some suggestion) Jan Marten Simons
2005-06-05 19:17 ` Henrik Nordstrom
2005-06-06 14:28   ` Jim C. Brown [this message]
2005-06-07 21:45     ` Henrik Nordstrom
2005-06-08 18:24       ` Jim C. Brown
2005-06-09 11:56         ` Henrik Nordstrom
2005-06-11 20:58           ` Jim C. Brown
2005-06-11 21:29             ` Christian MICHON
2005-06-13  0:14               ` Henrik Nordstrom
2005-06-13  8:59                 ` Christian MICHON
2005-06-13 11:55                   ` Jernej Simonèiè
2005-06-13 12:52                     ` Christian MICHON
2005-06-14 19:49                       ` John R. Hogerhuis
2005-06-14 20:00                         ` Christian MICHON
2005-06-15 13:40                           ` Henrik Nordstrom
2005-06-14 20:33                       ` Jim C. Brown
2005-06-15 13:43                         ` Henrik Nordstrom
2005-06-13  0:02             ` Henrik Nordstrom
2005-06-13  0:22               ` Paul Brook
2005-06-06 18:11   ` marten
2005-06-06 19:55     ` Jim C. Brown
2005-06-06 23:38       ` Jan Marten Simons
2005-06-07 16:16         ` Johannes Schindelin
2005-06-07 21:52         ` Henrik Nordstrom
2005-06-08 18:27         ` Jim C. Brown
2005-06-07 21:50       ` Henrik Nordstrom
2005-06-06 23:54   ` John R. Hogerhuis
2005-06-07  8:40     ` Christian MICHON
2005-06-07 22:59       ` Henrik Nordstrom
2005-06-08  6:43         ` Christian MICHON
2005-06-08  7:55           ` Henrik Nordstrom
2005-06-08 11:22             ` Christian MICHON
2005-06-08 12:25               ` Henrik Nordstrom
2005-06-08 22:31         ` Jan Marten Simons
2005-06-08 23:50           ` Jim C. Brown
2005-06-21 14:17             ` Jan Marten Simons
2005-06-21 20:02               ` Jim C. Brown
2005-06-21 21:39                 ` Paul Brook
2005-06-21 21:47                   ` Jim C. Brown
2005-06-09 16:33           ` Johannes Schindelin
2005-06-10 13:45             ` Jan Marten Simons
2005-06-07 22:15     ` Henrik Nordstrom
2005-06-08  6:12       ` John R. Hogerhuis
2005-06-08  7:52         ` Henrik Nordstrom
2005-06-08 11:22           ` Johannes Schindelin
2005-06-09 11:48             ` Henrik Nordstrom
2005-06-09 16:26               ` Johannes Schindelin
2005-06-08 18:33     ` Jim C. Brown

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=20050606142848.GA21394@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --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).