1ca0a66ea9
The guest VM can now be provided with a framebuffer and keyboard input. Mouse positioning of the guest is a problem. Because the PS2 model applies some calculations to the movement values, it can happen that overflows mess with the cursor. Therefore the handling was changed and only movements of 1 and -1 are sent. Since absolute positioning is not possible with PS2, we have to live with this limitation until USB HID is implemented. For the framebuffer size in Vancouver the configuration value in the machine XML node is used. It is possible to map the corresponding memory area directly to the guest, regardless if it is from nitpicker, liquid_framebuffer or vesa_drv. The guest is provided with two modes (text mode 3 and graphics mode 0x114 (0x314 in Linux). Pressing LWIN+END while a VM has focus resets the virtual machine. Also, RESET and DEBUG key presses will not be forwarded to the VM anymore. It is possible to dump a VM's state by pressing LWIN+INS keys. The text console is able to detect idle mode, unmaps the buffer from the guest and stops interpreting. Upon the next pagefault in this area, it resumes operation again. The code uses a simple checksum mechanism instead of a large buffer and memcmp to detect an idle text console. False positives don't matter very much.
Symbolic link
1 line
40 B
Plaintext
Symbolic link
1 line
40 B
Plaintext
../../../demo/src/server/nitlog/mono.tff |