perf: use a different subnet in the Docker image

192.168.0.* is often used in home networks, so avoid possible
interference by using a different network.

Signed-off-by: Gert Wollny <gert.wollny@collabora.com>
Reviewed-by: Rohan Garg <rohan.garg@collabora.com>
macos/master
Gert Wollny 4 years ago
parent daa7d9439c
commit 24ed01753d
  1. 4
      perf-testing/Docker/run.sh

@ -206,8 +206,8 @@ crosvm run \
--shared-dir "/apitrace:apitrace-tag:type=fs" \ --shared-dir "/apitrace:apitrace-tag:type=fs" \
--shared-dir "/traces-db:traces-db-tag:type=fs" \ --shared-dir "/traces-db:traces-db-tag:type=fs" \
--shared-dir "/perfetto:perfetto-tag:type=fs" \ --shared-dir "/perfetto:perfetto-tag:type=fs" \
--host_ip 192.168.0.1 --netmask 255.255.255.0 --mac AA:BB:CC:00:00:12 \ --host_ip 192.168.200.1 --netmask 255.255.255.0 --mac AA:BB:CC:00:00:12 \
-p "root=/dev/ram0 rdinit=/init.sh ip=192.168.0.2::192.168.0.1:255.255.255.0:crosvm:eth0 nohz=off clocksource=kvm-clock" \ -p "root=/dev/ram0 rdinit=/init.sh ip=192.168.200.2::192.168.200.1:255.255.255.0:crosvm:eth0 nohz=off clocksource=kvm-clock" \
/vmlinux /vmlinux
rm -f /traces-db/current_trace rm -f /traces-db/current_trace

Loading…
Cancel
Save