From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: Re: scripted migration (without Alt-Ctrl-2 / qemu-monitor) - possible? Date: Thu, 05 Apr 2007 13:20:39 +0200 Message-ID: <4614DB87.2060705@wpkg.org> References: <4614CA6B.2030303@wpkg.org> <4614CED8.20209@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Avi Kivity Return-path: In-Reply-To: <4614CED8.20209-atKUWr5tajBWk0Htik3J/w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Avi Kivity schrieb: > Tomasz Chmielewski wrote: >> Is it possible to do a migration (or any other maintenance, like >> stopping a guest VM) without qemu-monitor / Alt-Ctrl-2? >> >> >> For those using Xen, it would be similar to a command line "xm" which >> migrates a guest/domain to a different host - just SSH to your server >> (or use it in a script etc.), and do: >> >> xm migrate >> >> >> Similarly, lots of other actions are possible, like pausing, >> rebooting, shutting down, saving, restoring etc. >> >> >> The idea of having to "alt-ctrl-2 on the SDL window" does seem a bit >> incompatible with CLI, doesn't it? >> >> > > 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": 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? -- Tomasz Chmielewski http://wpkg.org ------------------------------------------------------------------------- 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