From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Xen-staging] [xen-unstable] hvm: Remove access to
 QEMU monitor inVNC server
Date: Tue, 27 Mar 2007 16:56:56 -0500
Message-ID: <46099328.9050005@us.ibm.com>
References: <200703271524.l2RFOMNg003926@latara.uk.xensource.com>
	<0326530267625D42A4E36594FDD0D1432EBA8A@exchpamain.ad.xensource.com>
	<46098B8E.8030606@us.ibm.com>
	<0326530267625D42A4E36594FDD0D1432EBAB2@exchpamain.ad.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <0326530267625D42A4E36594FDD0D1432EBAB2@exchpamain.ad.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Christian Limpach <Christian.Limpach@xensource.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Christian Limpach wrote:
>> QEMU 0.9.0 supports redirecting the monitor to a unix socket and 
>> supports reconnecting to the monitor (so that the banner is 
>> shown each 
>> time).
>>
>> When using these options, you can actually execute monitor 
>> commands from 
>> the command line by doing something like:
>>
>> echo help | socat stdin unix:/path/to/socket
>>
>> With these patches (or by moving qemu-dm up to 0.9.0), 
>> someone could add 
>> an xm monitor command that let you execute commands via xm.
>>
>> That, IMHO, would be the best possible solution.
>>     
>
> I've found that redirecting the monitor using "-monitor pty" works quite
> well since you get access to it using xm console.  That might have been
> broken recently though by the changes to how pty information is written
> to xenstore.
>   

Except if you disconnect from the pty, QEMU is prone to ending up in an 
infinite loop of read() == 0.

> I think it would be better to extend xm console to support additional
> pty's instead of adding a single purpose xm monitor command.
>   

xm console could also be extended to work with domain sockets which do 
not suffer from this problem.

Regards,

Anthony Liguori

>     christian
>