Tomasz Chmielewski wrote: >> >> Look up the qemu -monitor option. This allows you to redirect the >> qemu console anywhere you like, including stdio, pipes, tcp sockets, >> etc. It's wonderfully flexible. > > All right - so I see it belongs more to qemu documentation than KVM's > (+/- KVM extensions like migration etc.). > > > Not as easy to use and intuitive as "xm" - some instruction here, as > Qemu's "-monitor dev" documentation seems a bit incomplete as it > mentions only "vc" and "stdio":
The various device options are documented under '-serial'. > > > 1. Make a /tmp/guest socket; then start a guest > > qemu (...) -monitor unix:/tmp/quest,server,nowait > > > 2. Show qemu-monitor's help: > > echo 'help' | socat - unix-connect:/tmp/quest > > > The things get more complicated if you run multiple quests - you have > to keep track of the pipes etc. > > > Certainly, it is possible to write a powerful backend to that - as you > say, if it supports tcp sockets, it would be even possible to support > multiple KVM/qemu servers with one program or a script - something > that Xen's "xm" can't easily do. > > > Are there any ready solutions for that? Or the wheel still waits to be > invented? > > http://libvirt.org/ -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
