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

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

 



 On 07/27/2010 07:47 PM, Avi Kivity wrote:
 On 07/27/2010 07:42 PM, Daniel P. Berrange wrote:

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.

I'm talking about when it doesn't fail, just spews out some warnings.


Note, it needn't be during startup. If qemu says something while the guest is running, we need to get it to bugzilla, just like a kernel WARN_ON() or BUG_ON() will make it to kerneloops.org.

--
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux