From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Ways to exit from kvm on behalf of the quest system? Date: Wed, 01 Aug 2007 19:53:36 +0300 Message-ID: <46B0BA90.5020000@qumranet.com> References: <200708010047.36600.amit.shah@qumranet.com> <46B0B779.5050407@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: Dimitry Golubovsky Return-path: In-Reply-To: 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 Dimitry Golubovsky wrote: > Avi, > > OK, I'll try to summarize that. However I'd also like to make a > feature request: a virtual character device (sort of a virtual serial > line) that the guest OS might use to communicate with the QEMU > monitor. That might solve many problems. > That exists now. Look up the -monitor option -- you can redirect the monitor to a unix domain socket, a tcp socket, a pty, or wherever you like. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/