[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Re: KVM call agenda for July 27
From: |
Daniel P. Berrange |
Subject: |
Re: [Qemu-devel] Re: KVM call agenda for July 27 |
Date: |
Tue, 27 Jul 2010 17:42:58 +0100 |
User-agent: |
Mutt/1.4.1i |
On Tue, Jul 27, 2010 at 09:29:13AM -0700, Chris Wright wrote:
> * Daniel P. Berrange (address@hidden) wrote:
> > 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 ?
>
> I read that to mean...propagate stderr from qemu to be right in front of
> the user. So that's output from virsh or in virt-manager. Trouble is,
> that's only useful (at best) when starting a guest. Perhaps some
> virt-manager thing (an exclamation point to show there's errors in the
> log and a way to read them), and a virsh utility to match (although
> that'd require the user to actually poll the interface, at which point
> they can just as easily just look at the log).
We already propagate the stderr back to the client when guest startup
fails.
Regards,
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 :|
- Re: [Qemu-devel] Re: KVM call agenda for July 27, (continued)
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Anthony Liguori, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Daniel P. Berrange, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Avi Kivity, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Daniel P. Berrange, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Chris Wright, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Avi Kivity, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Chris Wright, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Avi Kivity, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Daniel P. Berrange, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Avi Kivity, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27,
Daniel P. Berrange <=
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Avi Kivity, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Avi Kivity, 2010/07/27
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Markus Armbruster, 2010/07/28
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Kevin Wolf, 2010/07/28
- Re: [Qemu-devel] Re: KVM call agenda for July 27, Markus Armbruster, 2010/07/28
[Qemu-devel] Re: KVM call agenda for July 27, Daniel P. Berrange, 2010/07/27