On Mon, Feb 04, 2019 at 01:28:02PM +0100, Johannes Berg wrote: > On Sun, 2019-02-03 at 21:56 +0100, Johannes Berg wrote: > > If telnetd is installed, start it inside the VM(s) to be > > able to look into them when something is wrong. Use a user > > network in qemu with a single host forward from ports 4000 > > (and higher for parallel-vm) for this. > > Please drop this for now. It was very useful and helped me debug a bunch > of test setup issues yesterday, but having it by default is annoying > because then you can't run two manual "vm-run.sh" scripts in parallel > without specifying --num, which doesn't make sense... so I guess this > should be opt-in by passing --telnet or something. In addition, it produced this on Ubuntu 16.04: qemu-system-x86_64: -nic: invalid option We also have the comment out bash call in the end of inside.sh. I've used that whenever wanting to do something at the end of a test case. I guess telnetd would be nice for allowing access at any point in time, so it might make sense to enable it with a vm-run.sh option. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
