qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: KVM call agenda for July 27


From: Chris Wright
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Date: Tue, 27 Jul 2010 09:36:11 -0700
User-agent: Mutt/1.5.20 (2009-12-10)

* Avi Kivity (address@hidden) wrote:
>  On 07/27/2010 07:29 PM, Chris Wright wrote:
> >
> >>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.
> 
> Yes, that's what I meant.
> 
> >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).
> 
> If things work there's  no reason for the user to go look at the
> logs.  An exclamation point invites clicking.
> 
> Even better would be an ABRT plugin, so if something goes
> (marginally) wrong, the siren pops up and you're invited to report
> the bug.

Despite some of the ABRT growing pains, ABRT plugin seems like a good
idea.  I don't know enough of the plugins to know if that requires
formatted output and just grepping for some known regexps.

thanks,
-chris



reply via email to

[Prev in Thread] Current Thread [Next in Thread]