On 10/07/2019 03:27 AM, Philippe Mathieu-Daudé wrote:
> Hi Mario,
>
> On 10/5/19 1:53 AM, Mario Smarduch wrote:
>> In a large VPC environment we want to log memory error occurrences
>> and log them with guest name and type - there are few use cases
>>
>>
>> - if VM crashes on AR mce inform the
Hi Mario,
On 10/5/19 1:53 AM, Mario Smarduch wrote:
In a large VPC environment we want to log memory error occurrences
and log them with guest name and type - there are few use cases
- if VM crashes on AR mce inform the user about the reason and
resolve the case
- if VM hangs notify the
On 10/06/2019 09:11 AM, Paolo Bonzini wrote:
> On 05/10/19 01:53, Mario Smarduch wrote:
>> Guest [Droplet-12345678] 2019-08-02T05:00:11.940270Z qemu-system-x86_64:
>> Guest MCE Memory Error at qemu addr 0x7f3c7622f000 and guest 78e42f000
>> addr of type BUS_MCEERR_AR injected
>>
>> with
On 05/10/19 01:53, Mario Smarduch wrote:
> Guest [Droplet-12345678] 2019-08-02T05:00:11.940270Z qemu-system-x86_64:
> Guest MCE Memory Error at qemu addr 0x7f3c7622f000 and guest 78e42f000
> addr of type BUS_MCEERR_AR injected
>
> with enterprise logging environment we can to take further
In a large VPC environment we want to log memory error occurrences
and log them with guest name and type - there are few use cases
- if VM crashes on AR mce inform the user about the reason and
resolve the case
- if VM hangs notify the user to reboot and resume processing
- if VM continues to
