On Wed, Feb 29, 2012 at 09:08:52AM +0800, Wen Congyang wrote:
At 02/28/2012 06:45 PM, Gleb Natapov Wrote:
On Tue, Feb 28, 2012 at 11:19:47AM +0100, Jan Kiszka wrote:
On 2012-02-28 10:42, Wen Congyang wrote:
At 02/28/2012 05:34 PM, Jan Kiszka Wrote:
On 2012-02-28 09:23, Wen Congyang wrote:
On 02/29/2012 03:29 AM, Wen Congyang wrote:
At 02/28/2012 07:23 PM, Avi Kivity Wrote:
On 02/27/2012 05:01 AM, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on kvm. This patch implemnts
this feature, and the implementation
On Wed, Feb 29, 2012 at 11:49:58AM +0200, Avi Kivity wrote:
On 02/29/2012 03:29 AM, Wen Congyang wrote:
At 02/28/2012 07:23 PM, Avi Kivity Wrote:
On 02/27/2012 05:01 AM, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on
On Wed, Feb 29, 2012 at 11:49:58AM +0200, Avi Kivity wrote:
On 02/29/2012 03:29 AM, Wen Congyang wrote:
At 02/28/2012 07:23 PM, Avi Kivity Wrote:
On 02/27/2012 05:01 AM, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on
On 02/29/2012 11:55 AM, Gleb Natapov wrote:
How about using a virtio-serial channel for this? You can transfer any
amount of information (including the dump itself).
Isn't it unreliable after the guest panicked?
So is calling hypercalls, or dumping, or writing to the screen. Of
On 02/29/2012 11:58 AM, Daniel P. Berrange wrote:
How about using a virtio-serial channel for this? You can transfer any
amount of information (including the dump itself).
When the guest OS has crashed, any dumps will be done from the host
OS using libvirt's core dump mechanism. The
On Wed, Feb 29, 2012 at 12:00:41PM +0200, Avi Kivity wrote:
On 02/29/2012 11:55 AM, Gleb Natapov wrote:
How about using a virtio-serial channel for this? You can transfer any
amount of information (including the dump itself).
Isn't it unreliable after the guest panicked?
On 02/29/2012 12:05 PM, Gleb Natapov wrote:
On Wed, Feb 29, 2012 at 12:00:41PM +0200, Avi Kivity wrote:
On 02/29/2012 11:55 AM, Gleb Natapov wrote:
How about using a virtio-serial channel for this? You can transfer any
amount of information (including the dump itself).
At 02/29/2012 05:36 PM, Gleb Natapov Wrote:
On Wed, Feb 29, 2012 at 09:08:52AM +0800, Wen Congyang wrote:
At 02/28/2012 06:45 PM, Gleb Natapov Wrote:
On Tue, Feb 28, 2012 at 11:19:47AM +0100, Jan Kiszka wrote:
On 2012-02-28 10:42, Wen Congyang wrote:
At 02/28/2012 05:34 PM, Jan Kiszka Wrote:
At 02/29/2012 06:08 PM, Avi Kivity Wrote:
On 02/29/2012 12:05 PM, Gleb Natapov wrote:
On Wed, Feb 29, 2012 at 12:00:41PM +0200, Avi Kivity wrote:
On 02/29/2012 11:55 AM, Gleb Natapov wrote:
How about using a virtio-serial channel for this? You can transfer any
amount of information
On Wed, Feb 29, 2012 at 12:05:32PM +0200, Avi Kivity wrote:
On 02/29/2012 11:58 AM, Daniel P. Berrange wrote:
How about using a virtio-serial channel for this? You can transfer any
amount of information (including the dump itself).
When the guest OS has crashed, any dumps will be
At 02/29/2012 06:05 PM, Avi Kivity Wrote:
On 02/29/2012 11:58 AM, Daniel P. Berrange wrote:
How about using a virtio-serial channel for this? You can transfer any
amount of information (including the dump itself).
When the guest OS has crashed, any dumps will be done from the host
OS using
On 02/29/2012 12:17 PM, Wen Congyang wrote:
Yes, crash can be so severe that it is not even detected by a kernel
itself, so not OOPS message even printed. But in most cases if kernel is
functional enough to print OOPS it is functional enough to call single
hypercall instruction.
Why
On Wed, Feb 29, 2012 at 12:08:19PM +0200, Avi Kivity wrote:
On 02/29/2012 12:05 PM, Gleb Natapov wrote:
On Wed, Feb 29, 2012 at 12:00:41PM +0200, Avi Kivity wrote:
On 02/29/2012 11:55 AM, Gleb Natapov wrote:
How about using a virtio-serial channel for this? You can transfer
On 02/29/2012 12:19 PM, Daniel P. Berrange wrote:
On Wed, Feb 29, 2012 at 12:05:32PM +0200, Avi Kivity wrote:
On 02/29/2012 11:58 AM, Daniel P. Berrange wrote:
How about using a virtio-serial channel for this? You can transfer any
amount of information (including the dump itself).
On 02/29/2012 12:31 PM, Wen Congyang wrote:
At 02/29/2012 06:05 PM, Avi Kivity Wrote:
On 02/29/2012 11:58 AM, Daniel P. Berrange wrote:
How about using a virtio-serial channel for this? You can transfer any
amount of information (including the dump itself).
When the guest OS has
On 02/29/2012 12:44 PM, Gleb Natapov wrote:
Yes, crash can be so severe that it is not even detected by a kernel
itself, so not OOPS message even printed. But in most cases if kernel is
functional enough to print OOPS it is functional enough to call single
hypercall instruction.
On Wed, Feb 29, 2012 at 12:48:57PM +0200, Avi Kivity wrote:
On 02/29/2012 12:44 PM, Gleb Natapov wrote:
Yes, crash can be so severe that it is not even detected by a kernel
itself, so not OOPS message even printed. But in most cases if kernel is
functional enough to print OOPS
At 02/29/2012 06:39 PM, Avi Kivity Wrote:
On 02/29/2012 12:17 PM, Wen Congyang wrote:
Yes, crash can be so severe that it is not even detected by a kernel
itself, so not OOPS message even printed. But in most cases if kernel is
functional enough to print OOPS it is functional enough to call
At 02/29/2012 06:39 PM, Avi Kivity Wrote:
On 02/29/2012 12:17 PM, Wen Congyang wrote:
Yes, crash can be so severe that it is not even detected by a kernel
itself, so not OOPS message even printed. But in most cases if kernel is
functional enough to print OOPS it is functional enough to call
At 02/28/2012 01:26 PM, Wen Congyang Wrote:
At 02/27/2012 11:08 PM, Jan Kiszka Wrote:
On 2012-02-27 04:01, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on kvm. This patch implemnts
this feature, and the implementation is the
At 02/27/2012 11:08 PM, Jan Kiszka Wrote:
On 2012-02-27 04:01, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on kvm. This patch implemnts
this feature, and the implementation is the same as xen:
register panic notifier, and
On 2012-02-28 09:23, Wen Congyang wrote:
At 02/27/2012 11:08 PM, Jan Kiszka Wrote:
On 2012-02-27 04:01, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on kvm. This patch implemnts
this feature, and the implementation is the
At 02/28/2012 05:34 PM, Jan Kiszka Wrote:
On 2012-02-28 09:23, Wen Congyang wrote:
At 02/27/2012 11:08 PM, Jan Kiszka Wrote:
On 2012-02-27 04:01, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on kvm. This patch implemnts
this
On 2012-02-28 10:42, Wen Congyang wrote:
At 02/28/2012 05:34 PM, Jan Kiszka Wrote:
On 2012-02-28 09:23, Wen Congyang wrote:
At 02/27/2012 11:08 PM, Jan Kiszka Wrote:
On 2012-02-27 04:01, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such
On Tue, Feb 28, 2012 at 11:19:47AM +0100, Jan Kiszka wrote:
On 2012-02-28 10:42, Wen Congyang wrote:
At 02/28/2012 05:34 PM, Jan Kiszka Wrote:
On 2012-02-28 09:23, Wen Congyang wrote:
At 02/27/2012 11:08 PM, Jan Kiszka Wrote:
On 2012-02-27 04:01, Wen Congyang wrote:
We can know the
On 02/27/2012 05:01 AM, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on kvm. This patch implemnts
this feature, and the implementation is the same as xen:
register panic notifier, and call hypercall when the guest
is paniced.
At 02/28/2012 06:45 PM, Gleb Natapov Wrote:
On Tue, Feb 28, 2012 at 11:19:47AM +0100, Jan Kiszka wrote:
On 2012-02-28 10:42, Wen Congyang wrote:
At 02/28/2012 05:34 PM, Jan Kiszka Wrote:
On 2012-02-28 09:23, Wen Congyang wrote:
At 02/27/2012 11:08 PM, Jan Kiszka Wrote:
On 2012-02-27 04:01,
At 02/28/2012 07:23 PM, Avi Kivity Wrote:
On 02/27/2012 05:01 AM, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on kvm. This patch implemnts
this feature, and the implementation is the same as xen:
register panic notifier, and
On 2012-02-27 04:01, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on kvm. This patch implemnts
this feature, and the implementation is the same as xen:
register panic notifier, and call hypercall when the guest
is paniced.
At 02/27/2012 11:08 PM, Jan Kiszka Wrote:
On 2012-02-27 04:01, Wen Congyang wrote:
We can know the guest is paniced when the guest runs on xen.
But we do not have such feature on kvm. This patch implemnts
this feature, and the implementation is the same as xen:
register panic notifier, and
31 matches
Mail list logo
