Definitive command line args to get networking 'working' with docker container.

[hanetzer]

Ello. Using the docker container. As such, there's a fair amount of moving parts involved. I want to do a recording of an application which requires 'real' network access (it authenticates against a remote server), and as such I've been trying to get the e1000 device to work (because I may be interested in using the network plugin in the future), and so far I've had no joy. Specifically, I'm using a windows 7 x32 guest.

If this could be added to the docs it'd be a great help.

[AndrewFasano]

I'm no expert in this, but it seems like nobody on our dev team really understand qemu networking so I'll try to help anyway. By default, I believe qemu/panda allow outbound network. If you're restoring from a snapshot you'll generally need to renew your DHCP lease since it will be stale. If you're using docker you probably need to mess with the docker network settings, probably by running the container with --net=host.

Does running with that flag and a fresh DHCP make things work for you?

The upstream qemu networking docs are my goto for debugging general networking issues with PANDA (since PANDA's networking is basically just what was shipped with as qemu 2.9).

[hanetzer]

with docker run --net=host --rm -it -p 5900:5900 -v pwd:/dir pandare/pandadev and run.sh:

#!/bin/bash
panda-system-i386 -m 4G -os windows-32-7sp0 \
	-spice port=5900,disable-ticketing=on\
	-serial mon:stdio \
	-netdev user,id=mynet -device e1000,netdev=mynet "$@"

executed as run.sh win7.qcow2 I get 10.0.2.15/24 as my ip address in the vm, but it has the yellow exclamation and I can't reach say, google.com, in internet explorer.