On 2017-08-21 20:43, Lars Ellenberg wrote:
On Thu, Aug 10, 2017 at 03:59:55PM +1200, Brady, Mike wrote:
[requested info]
As to what the box is doing at the time - running the VM one01 and a
DRBDManage cluster with no resources in it.
one01 is an OpenNeubula frontend and both kvm08 and kvm12
On Thu, Aug 10, 2017 at 03:59:55PM +1200, Brady, Mike wrote:
[requested info]
> As to what the box is doing at the time - running the VM one01 and a
> DRBDManage cluster with no resources in it.
>
> one01 is an OpenNeubula frontend and both kvm08 and kvm12 are OpenNebula
> nodes. OpenNebula
On 2017-08-09 20:38, Lars Ellenberg wrote:
IO stack (e.g. lsblk ; lsblk -t ; lsblk -D) may be interesting,
as well as the drbd configuration (drbdadm dump ),
the kernel logs around the "crash" if possible,
and your "best guess" as to what the box may have been doing
when it became unresponsive.
On Wed, Aug 09, 2017 at 04:45:56PM +1200, Brady, Mike wrote:
> I currently have a three node cluster running 9.0.8 that I have tried
> upgrading to 9.0.9rc1.
>
> A couple of minutes after I start a KVM VM on one of the nodes, the node
> becomes unresponsive and reboots. The VM is the third node
I currently have a three node cluster running 9.0.8 that I have tried
upgrading to 9.0.9rc1.
A couple of minutes after I start a KVM VM on one of the nodes, the node
becomes unresponsive and reboots. The VM is the third node in the
cluster and is configured with no storage and shows as being
