all these discussions around tftp looked nice and sweet. So I told
myself, instead of using winimage (shareware), why not transferring
files live.
Yet, when you try on a windows host to exchange files with a linux
guest (inside qemu and with -tftp option), all you get is:
Error code 2: Access
On Tue, 7 Jun 2005, Jan Marten Simons wrote:
Well the TFTP-server should get r/w, too, but if I get it right you'd have
to access the data on the guest from the host, which might lead to
situation where users shutdown the guest and then try to get their
(then lost) data from it via TFTP, which
On Mon, 6 Jun 2005, Jim C. Brown wrote:
Like I said, modifying TFTP for R/W would be a good option. It's already there,
the miminalists can't complain about having it removed (e.g. it may one day
be used to support virtual netboots), and one can use ftp clients for the
tftp server (I think).
On Mon, 6 Jun 2005, John R. Hogerhuis wrote:
I can think of some reasons for a non-native file service that is
instead built into QEMU:
vvfat?
e) Scripts to be used across farms of QEMU virtual machines will have
more commonalities even across different OSes. The event and content of
a file
On Tue, 7 Jun 2005, Christian MICHON wrote:
all these discussions around tftp looked nice and sweet. So I told
myself, instead of using winimage (shareware), why not transferring
files live.
Yet, when you try on a windows host to exchange files with a linux
guest (inside qemu and with -tftp
