readme: -monitor is what is killing out ctrl-c

README.adoc

@@ -360,28 +360,24 @@ On one hand, this provides an easy way to quit QEMU.
 +
 On the other, we are unable to easily kill the foreground process, which is specially problematic when it is something like an infinite loop. and not sent to guest processes.
 +
-TODO: understand why and how to change that. See:
-+
---
-** https://unix.stackexchange.com/questions/167165/how-to-pass-ctrl-c-in-qemu
-** https://github.com/cloudius-systems/osv/issues/49
---
-+
 It is also hard to enter the monitor for the same reason:
 +
 --
 * http://stackoverflow.com/questions/14165158/how-to-switch-to-qemu-monitor-console-when-running-with-curses
 * https://superuser.com/questions/488263/how-to-switch-to-the-qemu-control-panel-with-nographics
+* https://superuser.com/questions/1087859/how-to-quit-the-qemu-monitor-when-not-using-a-gui/1211516#1211516
 --
 +
+This behaviour is caused by the `-monitor` option: https://unix.stackexchange.com/questions/167165/how-to-pass-ctrl-c-to-the-guest-when-running-qemu-with-nographic/436321#436321
++
+TODO: find a solution, that allows us to use both `-monitor` and send `Ctrl-C`: https://stackoverflow.com/questions/49716931/how-to-run-qemu-with-nographic-and-monitor-but-still-be-able-to-send-ctrlc-to
++
 Our workaround is:
 +
 ....
 ./qemumonitor
 ....
 +
-I think the problem was reversed in older QEMU versions: https://superuser.com/questions/1087859/how-to-quit-the-qemu-monitor-when-not-using-a-gui/1211516#1211516
-+
 `sendkey sendkey ctrl-c` does not work on the text terminal either.
 +
 This is however fortunate when running QEMU with GDB, as the `Ctrl-C` reaches GDB and breaks.