Hi Christophe,
Am 30.03.2016 um 13:45 hat Christophe TREFOIS geschrieben:
> Another host went down, so I have to prepare info for this one.
>
> I could not SSH to it anymore.
> Console would show login screen, but no keystrokes were registered.
>
> I could “suspend” the VM and “run” it, but
Hi Kevin,
Ok thanks for the feedback.
Do you have experience with kernel panics and more specifically how to get any
meaningful message if this is happening?
According to syslog on the guest, at least after reboot, there's no information
that something went wrong.
Since this seems to leave
Hi Kevin,
Another host went down, so I have to prepare info for this one.
I could not SSH to it anymore.
Console would show login screen, but no keystrokes were registered.
I could “suspend” the VM and “run” it, but still can’t SSH to it.
Before suspension, all QEMU threads were around 0%,
Am 27.03.2016 um 22:38 hat Christophe TREFOIS geschrieben:
> Hi,
>
> MS does not like my previous email, so here it is again with a link to Dropbox
> instead of as attached.
>
> ——
> Hi Nir,
>
> Inside the core dump tarball is also the output of the two gdb commands you
> mentioned.
>
>
FILE QUARANTINED
Microsoft Forefront Protection for Exchange Server removed a file since it was
found to be infected.
File name: "winmail.dat"
Malware name: "ExceedinglyNested"
___
Users mailing list
Users@ovirt.org
Hi Nir,
Here is another one, this time with strace of children and gdb dump.
Interestingly, this time, the qemu seems stuck 0%, vs 100% for other cases.
The files for strace are attached. The gdb + core dump is found here (too big):
https://dl.dropboxusercontent.com/u/63261/gdb-core.tar.gz
mailto:nsof...@redhat.com]
>> Sent: jeudi 24 mars 2016 20:17
>> To: Christophe TREFOIS <christophe.tref...@uni.lu>; Kevin Wolf
>> <kw...@redhat.com>; Francesco Romani <from...@redhat.com>
>> Cc: users <users@ovirt.org>; lcsb-sysadmins <lcsb-sysadm...@
tref...@uni.lu>; Kevin Wolf
> <kw...@redhat.com>; Francesco Romani <from...@redhat.com>
> Cc: users <users@ovirt.org>; lcsb-sysadmins <lcsb-sysadm...@uni.lu>
> Subject: Re: [ovirt-users] VM get stuck randomly
>
> On Thu, Mar 24, 2016 at 7:51 PM, Ch
On Thu, Mar 24, 2016 at 7:51 PM, Christophe TREFOIS
wrote:
> Hi Nir,
>
> And the second one is down now too. see some comments below.
>
>> On 13 Mar 2016, at 12:51, Nir Soffer wrote:
>>
>> On Sun, Mar 13, 2016 at 9:46 AM, Christophe TREFOIS
>>
---Original Message-
>> From: Nir Soffer [mailto:nsof...@redhat.com]
>> Sent: dimanche 13 mars 2016 12:51
>> To: Christophe TREFOIS <christophe.tref...@uni.lu>
>> Cc: users <users@ovirt.org>
>> Subject: Re: [ovirt-users] VM get stuck randomly
>>
> Sent: dimanche 13 mars 2016 12:51
> To: Christophe TREFOIS <christophe.tref...@uni.lu>
> Cc: users <users@ovirt.org>
> Subject: Re: [ovirt-users] VM get stuck randomly
>
> On Sun, Mar 13, 2016 at 9:46 AM, Christophe TREFOIS
> <christophe.tref...@uni.lu> wrote:
Hello,
I saw the same issue at least once. There were the following lines in
/var/log/libvirt/qemu/VMNAME.log at the moment:
main_channel_link: add main channel client
main_channel_handle_parsed: net test: latency 539.767000 ms, bitrate 7289423
bps (6.951735 Mbps) LOW BANDWIDTH
ophe TREFOIS <christophe.tref...@uni.lu>
> *Cc:* users <users@ovirt.org>
> *Subject:* Re: [ovirt-users] VM get stuck randomly
>
>
>
>
>
>
>
> On Sun, Mar 13, 2016 at 9:46 AM, Christophe TREFOIS <
> christophe.tref...@uni.lu> wrote:
>
>
Hi Yaniv,
See my answers / questions below under [CT].
From: Yaniv Kaul [mailto:yk...@redhat.com]
Sent: dimanche 13 mars 2016 12:08
To: Christophe TREFOIS <christophe.tref...@uni.lu>
Cc: users <users@ovirt.org>
Subject: Re: [ovirt-users] VM get stuck randomly
On Sun, Mar 13, 201
On Sun, Mar 13, 2016 at 9:46 AM, Christophe TREFOIS
wrote:
> Dear all,
>
> I have a problem since couple of weeks, where randomly 1 VM (not always the
> same) becomes completely unresponsive.
> We find this out because our Icinga server complains that host is down.
>
>
On Sun, Mar 13, 2016 at 9:46 AM, Christophe TREFOIS <
christophe.tref...@uni.lu> wrote:
> Dear all,
>
> I have a problem since couple of weeks, where randomly 1 VM (not always
> the same) becomes completely unresponsive.
> We find this out because our Icinga server complains that host is down.
>
Dear all,
I have a problem since couple of weeks, where randomly 1 VM (not always the
same) becomes completely unresponsive.
We find this out because our Icinga server complains that host is down.
Upon inspection, we find we can’t open a console to the VM, nor can we login.
In oVirt engine,
17 matches
Mail list logo