All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-commits] [COMMIT ddd9bbd] Support for multiple -monitor devices
Date: Wed, 09 Sep 2009 13:32:46 +0200	[thread overview]
Message-ID: <4AA7925E.9020001@siemens.com> (raw)
In-Reply-To: <4AA791C5.4000802@redhat.com>

Avi Kivity wrote:
> On 09/04/2009 05:43 PM, Anthony Liguori wrote:
>> From: Jan Kiszka<jan.kiszka@siemens.com>
>>
>> Rebased version of Anthony's patch: Allow to specify more than one
>> monitor terminal via the -monitor command line switch. This is
>> particularly useful when libvirt or some other management tool already
>> occupies the primary monitor but you need another one for debugging.
>> The current clumsy workaround is to multiplex such additional terminals
>> over a qemu character device (e.g. -serial mon:<device>).
>>
>>    
> 
> This (as merged into kvm-next) breaks autotest.  Autotest starts 
> qemu-kvm with -monitor unix:/tmp/blah,server,nowait; with this patch it 
> no longer opens the socket (as seen with lsof).  I haven't yet found out 
> why.

Ok, will have a look.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [Qemu-commits] [COMMIT ddd9bbd] Support for multiple -monitor devices
Date: Wed, 09 Sep 2009 13:32:46 +0200	[thread overview]
Message-ID: <4AA7925E.9020001@siemens.com> (raw)
In-Reply-To: <4AA791C5.4000802@redhat.com>

Avi Kivity wrote:
> On 09/04/2009 05:43 PM, Anthony Liguori wrote:
>> From: Jan Kiszka<jan.kiszka@siemens.com>
>>
>> Rebased version of Anthony's patch: Allow to specify more than one
>> monitor terminal via the -monitor command line switch. This is
>> particularly useful when libvirt or some other management tool already
>> occupies the primary monitor but you need another one for debugging.
>> The current clumsy workaround is to multiplex such additional terminals
>> over a qemu character device (e.g. -serial mon:<device>).
>>
>>    
> 
> This (as merged into kvm-next) breaks autotest.  Autotest starts 
> qemu-kvm with -monitor unix:/tmp/blah,server,nowait; with this patch it 
> no longer opens the socket (as seen with lsof).  I haven't yet found out 
> why.

Ok, will have a look.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-09-09 11:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200909041443.n84EhZaA005101@d01av04.pok.ibm.com>
2009-09-09 11:30 ` [Qemu-commits] [COMMIT ddd9bbd] Support for multiple -monitor devices Avi Kivity
2009-09-09 11:30   ` [Qemu-devel] " Avi Kivity
2009-09-09 11:32   ` Jan Kiszka [this message]
2009-09-09 11:32     ` Jan Kiszka
2009-09-09 11:42     ` Avi Kivity
2009-09-09 11:42       ` [Qemu-devel] " Avi Kivity
2009-09-09 11:47       ` Avi Kivity
2009-09-09 11:47         ` [Qemu-devel] " Avi Kivity
2009-09-09 11:50         ` Jan Kiszka
2009-09-09 11:50           ` [Qemu-devel] " Jan Kiszka

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=4AA7925E.9020001@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /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.