On Sat, Aug 19, 2017 at 11:02:58AM -0500, Mario Castelán Castro wrote: > On 2017-08-19 17:02 +1000 Zenaan Harkness <zen...@freedbms.net> wrote: > >Which TUI/GUI do you use? > > I do not know what is TUI.
Text User Interface / command line. > I don't use any GUI. I write Bash scripts > that call QEMU with the required options and I use “qemu-img” from the > command line when needed. Hm. Nice way to go. > >I've been struggling to create a Host-only network. In VirtualBox > >(and VMWare from version 1 or very early) I could basically just > >tick a check box for "Host only network", and name one or more shared > >folders. > > The easiest way to do this in QEMU is to use the “-net > user,restrict=on,hostfwd=...” option. The hostfwd part is optional, but you > will require if you want host–guest network connectivity. > > This way, networking is handled in user space. A more efficient approach > is to use kernel-managed networking. It is my understanding that for this, > one may use the TUN and TAP virtual Linux devices, but I have never done > it. Some years back I was using OpenVPN for a while, so got a little experience with TAP back then. > >I realise I probably have to mount the SAMBA horse again. And for > >libre software, I'm willing to do all this. > > Why do you want to use SAMBA? Install a SSH server in the guest and access > it from the host using scp, sftp or rsync. Rsync is the most efficient. This sounds like a great idea! SAMBA's brittleness in configuration (due to my dunceness) when trying to make it work with XP, W7 or now it would be W10 in the VM, has just never been a comfortable easy thing, for me. Years ago I even ran cygwin sshd from memory - but I'm certain there's cygwin ssh client, so I could use that even from the Windows side. Thank you very much for the reminder :)
