William Douglas 56028fb214 Try to restore pty configuration on reboot ... When a vm is created with a pty device, on reboot the pty fd (sub only) will only be associated with the vmm through the epoll event loop. The fd being polled will have been closed due to the vm itself dropping the pty files (and potentially reopening the fd index to a different item making things quite confusing) and new pty fds will be opened but not polled on for input. This change creates a structure to encapsulate the information about the pty fd (main File, sub File and the path to the sub File). On reboot, a copy of the console and serial pty structs is then passed down to the new Vm instance which will be used instead of creating a new pty device. This resolves the underlying issue from #2316. Signed-off-by: William Douglas <william.r.douglas@gmail.com>		2021-03-05 18:34:52 +01:00
..
src	Try to restore pty configuration on reboot	2021-03-05 18:34:52 +01:00
Cargo.toml	build(deps): bump libc from 0.2.86 to 0.2.87	2021-03-02 11:14:57 +00:00