qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Looking for an easy way to exchange data bidirectional


From: Jim C. Brown
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
User-agent: Mutt/1.4i

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 via email to

[Prev in Thread] Current Thread [Next in Thread]