From: "Daniel P. Berrange" <berrange@redhat.com>
To: Christian.Limpach@cl.cam.ac.uk
Cc: Atsushi SAKAI <sakaia@jp.fujitsu.com>,
xen-devel@lists.xensource.com, "You,
Yongkang" <yongkang.you@intel.com>, ?????? <kouya@jp.fujitsu.com>
Subject: Re: Should Qemu monitor be enabled by default
Date: Thu, 12 Apr 2007 22:04:14 +0100 [thread overview]
Message-ID: <20070412210414.GD19956@redhat.com> (raw)
In-Reply-To: <3d8eece20704121400u59a1026ao1521308e806ef0a@mail.gmail.com>
On Thu, Apr 12, 2007 at 10:00:45PM +0100, Christian Limpach wrote:
> >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.
Yes, that would work pretty well - and shouldn't require much code at
all - 'xm monitor' impl would pretty much be identical to that for the
existing 'xm console' code, merely looking up a different PTY path in
XenStored.
> >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.
Sorry, that's cleared things up.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-04-12 21:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 3:35 Should Qemu monitor be enabled by default You, Yongkang
2007-04-10 5:34 ` You, Yongkang
2007-04-10 9:22 ` Keir Fraser
2007-04-10 9:32 ` Christian Limpach
2007-04-10 9:53 ` You, Yongkang
2007-04-10 10:00 ` Christian Limpach
2007-04-10 12:50 ` Hidetoshi Nishi
2007-04-11 8:02 ` Atsushi SAKAI
2007-04-11 9:24 ` Christian Limpach
2007-04-11 11:06 ` Atsushi SAKAI
2007-04-11 11:32 ` Atsushi SAKAI
2007-04-11 12:10 ` Christian Limpach
2007-04-12 6:40 ` You, Yongkang
2007-04-12 15:38 ` Daniel P. Berrange
2007-04-12 16:09 ` You, Yongkang
2007-04-12 20:40 ` Christian Limpach
2007-04-12 20:51 ` Daniel P. Berrange
2007-04-12 21:00 ` Christian Limpach
2007-04-12 21:04 ` Daniel P. Berrange [this message]
2007-04-12 20:53 ` Christian Limpach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070412210414.GD19956@redhat.com \
--to=berrange@redhat.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=kouya@jp.fujitsu.com \
--cc=sakaia@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
--cc=yongkang.you@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.