Re: [libvirt] [PATCH 0/9] extend virsh domstate to show additional information

2018-07-16 Thread Bjoern Walk
Martin Kletzander [2018-07-13, 10:50AM +0200]: > I'm not very particularly opinionated on this, but I think APIs should be > machine-readable and CLI tools can convert that to human-readable format. > You'll never know when a program will like to access that and having to tell > anyone in the

Re: [libvirt] [PATCH 0/9] extend virsh domstate to show additional information

2018-07-13 Thread Martin Kletzander
On Wed, Jul 11, 2018 at 01:40:31PM +0200, Bjoern Walk wrote: Jiri Denemark [2018-07-11, 01:17PM +0200]: On Wed, Jul 11, 2018 at 12:49:13 +0200, Bjoern Walk wrote: > This patch series introduces the ability to save additional information > for the domain state and exposes this information in

Re: [libvirt] [PATCH 0/9] extend virsh domstate to show additional information

2018-07-11 Thread Bjoern Walk
Jiri Denemark [2018-07-11, 01:17PM +0200]: > On Wed, Jul 11, 2018 at 12:49:13 +0200, Bjoern Walk wrote: > > This patch series introduces the ability to save additional information > > for the domain state and exposes this information in virsh domstate. > > > > For example in the case of QEMU

Re: [libvirt] [PATCH 0/9] extend virsh domstate to show additional information

2018-07-11 Thread Jiri Denemark
On Wed, Jul 11, 2018 at 12:49:13 +0200, Bjoern Walk wrote: > This patch series introduces the ability to save additional information > for the domain state and exposes this information in virsh domstate. > > For example in the case of QEMU guest panic events, we can provide additional >

[libvirt] [PATCH 0/9] extend virsh domstate to show additional information

2018-07-11 Thread Bjoern Walk
This patch series introduces the ability to save additional information for the domain state and exposes this information in virsh domstate. For example in the case of QEMU guest panic events, we can provide additional information like the crash reason or register state of the domain. This