WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Should Qemu monitor be enabled by default

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] Should Qemu monitor be enabled by default
From: "Christian Limpach" <christian.limpach@xxxxxxxxx>
Date: Thu, 12 Apr 2007 22:00:45 +0100
Cc: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "You, Yongkang" <yongkang.you@xxxxxxxxx>, ?????? <kouya@xxxxxxxxxxxxxx>
Delivery-date: Thu, 12 Apr 2007 13:59:34 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oioYeppz5BoqyDD99n9HR4bSv34LlkgabbBolzJNWP1bkjbfoukGd5RRm5ICMGlC3wCoD9HpmL4AbDFwYSXrD0ksxs+++xblRrHZTQ7P6p3S0WCMryWDdtqoR1QMn1xtm8+CChVJ6NrtncEOCij5iBnXfgel0aqr2NqbeFpwmCY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lcQgyYWq62SFgKVvFLzxmc+Sd4OSZ6CqEiFnCwcCL8qb2BEqbIsg8elEbsRUeZSSZj8wiSwWGdDstLJJLiUNVBOavRAxOCB1l4FjH+bL5xmAUYonW1hkXHYMH5cSD5NwlKjeytRfJhPL5y7nH7VkBlgpJ2ExMSFFWBteS+xu5Mc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070412205127.GC19956@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <3d8eece20704110510i31c4f66br56ea3acc5d7b2f68@xxxxxxxxxxxxxx> <094BCE01AFBE9646AF220B0B3F367AABCD9F85@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20070412153831.GM4393@xxxxxxxxxx> <3d8eece20704121340n7ba9b2a9nb67f55eb598019@xxxxxxxxxxxxxx> <20070412205127.GC19956@xxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 4/12/07, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote:
> No, the monitor in qemu is off by default, the patch is correct as is.

Is that a recent Xen-specific change to QEMU ? The regular QEMU has always
had the monitor on by default - and its on by default in Xen 3.0.3/4 :

Yes it is.  The default is not suitable.

> Why shouldn't both co-exist?  You can have either monitor=pty or
> monitor=vc.  This is how serial ports work already.

What I mean is that if we wanted to implement a 'xm monitor' command,
then XenD would need to launch QEMU with '-monitor pty' (or equivalent)
at which point you'd be unable to also have '-monitor vc' on the same
command line.

Which is why the monitor option should take a string, it can then
default to whatever is useable for "xm monitor".  "xm monitor" should
imho be xm console with an option to make it connect to the monitor
pty.

I've not had any trouble with it myself, but I've not tested it much.
I was refering to the earlier mail in this thread

http://lists.xensource.com/archives/html/xen-devel/2007-04/msg00222.html

where Nishi indicated his motivation for wanting access to the monitor
via a VC was that block-configure wasn't reliable.

You should have read the replies as well, before making claims that
something doesn't work.

   christian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel