From: "Daniel P. Berrange" <berrange@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
Markus Armbruster <armbru@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Date: Tue, 27 Jul 2010 17:24:49 +0100 [thread overview]
Message-ID: <20100727162449.GR12387@redhat.com> (raw)
In-Reply-To: <4C4F0682.3020400@redhat.com>
On Tue, Jul 27, 2010 at 07:17:06PM +0300, Avi Kivity wrote:
> On 07/27/2010 06:28 PM, Anthony Liguori wrote:
> >
> >If we add docs/deprecated-features.txt, schedule removal for at least
> >1 year in the future, and put a warning in the code that prints
> >whenever raw is probed, I think I could warm up to this.
> >
> >Since libvirt should be insulating users from this today, I think the
> >fall out might not be terrible.
>
> On a related note, we should ask libvirt to make qemu stderr output
> available to its users, or perhaps an ABRT plugin to report such
> messages from libvirt's logs.
QEMU stderr+out is already recorded in /var/lib/libvirt/qemu/$GUESTNAME.log
along with the env variables and argv used to spawn it. Or did you mean
provide an API + virsh command /virt-manager UI for accessing the logs ?
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Date: Tue, 27 Jul 2010 17:24:49 +0100 [thread overview]
Message-ID: <20100727162449.GR12387@redhat.com> (raw)
In-Reply-To: <4C4F0682.3020400@redhat.com>
On Tue, Jul 27, 2010 at 07:17:06PM +0300, Avi Kivity wrote:
> On 07/27/2010 06:28 PM, Anthony Liguori wrote:
> >
> >If we add docs/deprecated-features.txt, schedule removal for at least
> >1 year in the future, and put a warning in the code that prints
> >whenever raw is probed, I think I could warm up to this.
> >
> >Since libvirt should be insulating users from this today, I think the
> >fall out might not be terrible.
>
> On a related note, we should ask libvirt to make qemu stderr output
> available to its users, or perhaps an ABRT plugin to report such
> messages from libvirt's logs.
QEMU stderr+out is already recorded in /var/lib/libvirt/qemu/$GUESTNAME.log
along with the env variables and argv used to spawn it. Or did you mean
provide an API + virsh command /virt-manager UI for accessing the logs ?
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2010-07-27 16:24 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 21:28 KVM call agenda for July 27 Chris Wright
2010-07-26 21:28 ` [Qemu-devel] " Chris Wright
2010-07-26 22:28 ` Anthony Liguori
2010-07-26 22:28 ` [Qemu-devel] " Anthony Liguori
2010-07-26 23:28 ` Anthony Liguori
2010-07-26 23:28 ` [Qemu-devel] " Anthony Liguori
2010-07-27 0:13 ` Alex Williamson
2010-07-27 0:13 ` [Qemu-devel] " Alex Williamson
2010-07-27 13:22 ` Jes Sorensen
2010-07-27 13:22 ` [Qemu-devel] " Jes Sorensen
2010-07-27 7:19 ` Markus Armbruster
2010-07-27 7:19 ` [Qemu-devel] " Markus Armbruster
2010-07-27 13:00 ` Anthony Liguori
2010-07-27 13:00 ` [Qemu-devel] " Anthony Liguori
2010-07-27 13:28 ` Kevin Wolf
2010-07-27 13:28 ` Kevin Wolf
2010-07-27 15:22 ` Markus Armbruster
2010-07-27 15:22 ` Markus Armbruster
2010-07-27 15:28 ` Anthony Liguori
2010-07-27 15:28 ` Anthony Liguori
2010-07-27 15:37 ` Daniel P. Berrange
2010-07-27 15:37 ` Daniel P. Berrange
2010-07-27 16:17 ` Avi Kivity
2010-07-27 16:17 ` Avi Kivity
2010-07-27 16:24 ` Daniel P. Berrange [this message]
2010-07-27 16:24 ` Daniel P. Berrange
2010-07-27 16:29 ` Chris Wright
2010-07-27 16:29 ` Chris Wright
2010-07-27 16:32 ` Avi Kivity
2010-07-27 16:32 ` Avi Kivity
2010-07-27 16:36 ` Chris Wright
2010-07-27 16:36 ` Chris Wright
2010-07-27 16:42 ` Avi Kivity
2010-07-27 16:42 ` Avi Kivity
2010-07-27 17:01 ` Daniel P. Berrange
2010-07-27 17:01 ` Daniel P. Berrange
2010-07-27 17:37 ` Avi Kivity
2010-07-27 17:37 ` Avi Kivity
2010-07-27 16:42 ` Daniel P. Berrange
2010-07-27 16:42 ` Daniel P. Berrange
2010-07-27 16:47 ` Avi Kivity
2010-07-27 16:47 ` Avi Kivity
2010-07-27 16:48 ` Avi Kivity
2010-07-27 16:48 ` Avi Kivity
2010-07-28 11:22 ` Markus Armbruster
2010-07-28 11:25 ` Kevin Wolf
2010-07-28 11:25 ` Kevin Wolf
2010-07-28 13:08 ` Markus Armbruster
2010-07-27 11:51 ` Daniel P. Berrange
2010-07-27 11:51 ` [Qemu-devel] " Daniel P. Berrange
2010-07-27 13:30 ` Anthony Liguori
2010-07-27 13:30 ` [Qemu-devel] " Anthony Liguori
2010-07-27 13:43 ` Cole Robinson
2010-07-27 13:43 ` [Qemu-devel] " Cole Robinson
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=20100727162449.GR12387@redhat.com \
--to=berrange@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--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.