+
+$ ./host_on_off_processes ${srcdir:=.}/../../../examples/platforms/small_platform.xml 5 --log=no_loc
+> [Tremblay:test_launcher:(1) 0.000000] [msg_test/INFO] Test 5 (turn off dest during a communication : Create a Process/task to make a communication between Tremblay and Jupiter and turn off Jupiter during the communication
+> [Jupiter:commRX:(2) 10.000000] [msg_test/INFO] Start RX
+> [Tremblay:commTX:(3) 10.000000] [msg_test/INFO] Start TX
+> [Tremblay:test_launcher:(1) 10.000000] [msg_test/INFO] number of processes: 3
+> [Tremblay:test_launcher:(1) 20.000000] [msg_test/INFO] Turn Jupiter off
+> [Tremblay:test_launcher:(1) 20.000000] [msg_test/INFO] Test 5 seems ok (number of Process: 2, it should be 2)
+> [Tremblay:test_launcher:(1) 20.000000] [msg_test/INFO] Test done. See you!
+> [Tremblay:commTX:(3) 40.000000] [msg_test/INFO] TX done
+> [40.000000] [msg_test/INFO] Simulation time 40
+
+$ ./host_on_off_processes ${srcdir:=.}/../../../examples/platforms/small_platform.xml 6 --log=no_loc
+> [Tremblay:test_launcher:(1) 0.000000] [msg_test/INFO] Test 6: Turn on Jupiter, assign a VM on Jupiter, launch a process inside the VM, and turn off the node
+> [vm0:process_daemon:(2) 0.000000] [msg_test/INFO] Start daemon on vm0 (76296000.000000)
+> [vm0:process_daemon:(2) 0.000000] [msg_test/INFO] Execute daemon
+> [Jupiter:process_daemonJUPI:(3) 0.000000] [msg_test/INFO] Start daemon on Jupiter (76296000.000000)
+> [Jupiter:process_daemonJUPI:(3) 0.000000] [msg_test/INFO] Execute daemon
+> [Jupiter:process_daemonJUPI:(3) 1.000001] [msg_test/INFO] Execute daemon
+> [Jupiter:process_daemonJUPI:(3) 2.000002] [msg_test/INFO] Execute daemon
+> [Jupiter:process_daemonJUPI:(3) 3.000004] [msg_test/INFO] Execute daemon
+> [Jupiter:process_daemonJUPI:(3) 4.000005] [msg_test/INFO] Execute daemon
+> [Jupiter:process_daemonJUPI:(3) 5.000006] [msg_test/INFO] Execute daemon
+> [Jupiter:process_daemonJUPI:(3) 6.000007] [msg_test/INFO] Execute daemon
+> [Jupiter:process_daemonJUPI:(3) 7.000008] [msg_test/INFO] Execute daemon
+> [Jupiter:process_daemonJUPI:(3) 8.000009] [msg_test/INFO] Execute daemon
+> [Jupiter:process_daemonJUPI:(3) 9.000011] [msg_test/INFO] Execute daemon
+> [Tremblay:test_launcher:(1) 10.000000] [msg_test/INFO] Turn Jupiter off
+> [Tremblay:test_launcher:(1) 10.000000] [msg_test/INFO] Shutdown vm0
+> [Tremblay:test_launcher:(1) 10.000000] [msg_test/INFO] Destroy vm0
+> [10.000000] [surf_vm/WARNING] Dirty page tracking: 1 pending task(s) on a destroyed VM (first one is (name hidden)).
+> If you don't understand why your task was not properly removed, please report that bug.
+> This is a known bug if you turned the host off during the VM execution.
+> Please remind us of that problem at some point: our code base is not ready to fix this harmless issue in 2016, sorry.
+> [Tremblay:test_launcher:(1) 10.000000] [msg_test/INFO] Test 6 is also weird: when the node Jupiter is turned off once again, the VM and its daemon are not killed. However, the issue regarding the shutdown of hosted VMs can be seen a feature not a bug ;)
+> [Tremblay:test_launcher:(1) 10.000000] [msg_test/INFO] Test done. See you!
+> [10.000000] [msg_test/INFO] Simulation time 10
+> [10.000000] [surf_maxmin/WARNING] Probable bug: a simgrid::surf::CpuCas01Action variable (#13) not removed before the LMM system destruction.
+> [10.000000] [surf_maxmin/WARNING] Probable bug: a simgrid::surf::CpuCas01Action variable (#2) not removed before the LMM system destruction.
+
+p The previous test suffers of bug https://github.com/simgrid/simgrid/issues/120
+p but the code is still not clean enough to really solve it.