From: marten@xtal.rwth-aachen.de
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 20:11:08 +0200 (CEST) [thread overview]
Message-ID: <64655.80.137.250.37.1118081468.squirrel@pc42.xtal.rwth-aachen.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0506051236080.11204@filer.marasystems.com>
> 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.
As Jim Brown said it's not that easy to use a FTP-server on the host, if
you've got no root/admin-access.
Think of this scenario: A DVD with qemu and some disc-image and some
start-up-script for linux and an autostart.exe for win-host which will
fire-up the disk-image really easy. That way you can have a sand-boxed
standard environment which can be used on either windows or linux hosts
without the need to configure those. Now you should preconfigure your
guest to save personal information somewhere. So I'd like to have an
"exchange"-director inside the $home of the current user which should be
avialiable inside the virtual-pc for read/write. I think it would be the
easiest way to offer it via an integrated FTP-server. The advantages are:
- no ide-channel is blocked (unlike vvFat)
- ftp IS a very common protocol (is there SMB for exotic OS?)
- as the server is only virtual, you don't have to care about security-issues
- the server only runs, when it is needed
- implementaion should be easy (get some open-source FTP, strip it down
and change its binding to an interface like it was done with the internal
dhcp)
- the data-transfer resides inside the guest, which would be more
intuitive to the non-technical user when working in the VM.
> btw: The SMB server (Samba) provides read/write access if you insist on
> it. All you in theory need to do is to set up the password file on the
> host.
The Samba-wrapper does not work on Win-on-Win situations
> 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.
This would be desirable, too. But I think that this would be far more
difficult to implement.
Have a nice day,
Jan
next prev parent reply other threads:[~2005-06-06 18:15 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
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 [this message]
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=64655.80.137.250.37.1118081468.squirrel@pc42.xtal.rwth-aachen.de \
--to=marten@xtal.rwth-aachen.de \
--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).