README
1ABOUT
2
3This tool uses two programs, one that lives in dom0 and one that lives in domU
4to verify that no data is lost. dom0 and domU share a handshake with each
5other that they use to exchange a random seed.
6
7Both programs then generate a series of random numbers and then writes and
8reads the numbers via the console. Because each side starts with the same seed
9they know what data the other side is generating and therefore what should be
10expected.
11
12RUNNNING
13
14console-domU should be installed within the guest image. It must be launched
15from the client automatically. I use a custom initrd image and put it in the
16/linuxrc.
17
18console-dom0 and console-domU will communicate with each other and stress the
19console code. You can verify it at various levels by invoking it in different
20ways. procpipe is used to connect the two. I use the following command for
21testing:
22
23./procpipe ./console-dom0 'xm create -c /etc/xen/xmexample1'
24
25xmexample1 has no devices and no root set (this is what triggers /linuxrc).
26
27If it freezes, it probably means that console-domU is expecting more data from
28console-dom0 (which means that some data got dropped). I'd like to add
29timeouts in the future to handle this more gracefully.
30