Daniel Veillard wrote: > enclosed is a first version of a patch to allow remote access and control > for QEmu instances, I'm not suggesting to apply it as is (though it seems > to work in my limited testing) but would rather like to get comments back > for choices I'm facing.
This sounds pretty nice. A few general comments: A few weeks ago I wrote a qemu daemon manager. It's a pretty simple script that manages multiple qemu processes, launching each one in an instance of screen. screen does most of the dirty work of keeping track of running processes, assigning a name to each process, attaching to a process's console, terminating a process, etc. Of course screen has many more features that we don't really need, but it might be worth looking at screen as a model for implementing the functions you describe. The other problem my script deals with, which screen doesn't solve, is managing resources like ports (for -redir) and network interface MAC addresses (in cases where uniqueness matters), and providing some way for the user to determine which resource has been assigned to a particular qemu process. If qemu provides access to its console via a socket, this is just another resource that a manager can deal with, perhaps passing the desired port number to qemu via the command line. --Ed
_______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
