You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.
DRBD as Master/Slave Ressource inside Pacemaker works well, see Config attached.
If you get the KVM Network to work, i always ran in this kind of Issue which kills the Kernel completely.
The KVM Guest runs inside a ZVOL replicated with DRBD to the second Node.
What makes me wonder is the fact, the VM is running stable if i don't use network with KVM.
If the Network is up and running, within five to ten minutes the box got killed completely.
I was able to reproduce it several times.
Hopefully it will help you guys.
Hi Guys,
i tried a Setup with Pacemaker, KVM, DRBD
DRBD as Master/Slave Ressource inside Pacemaker works well, see Config attached.
If you get the KVM Network to work, i always ran in this kind of Issue which kills the Kernel completely.
The KVM Guest runs inside a ZVOL replicated with DRBD to the second Node.
Distribution: OpenSuSE 11.4
Kernel: 2.6.37.6-0.7-default
Alternate Kernel 2.6.37.6-0.9-default
But lets have a look
For me this looks like anon maskable Interrupt.
Iron seems to be fine
If i dig deeper
seems that
spl_slab_reclaim
ist triggering something weird.
If i look at the serial console messages i alsways get this back
[ 4919.500236] last sysfs file:
/sys/devices/virtual/net/virbr0/bridge/topology_change_detected
What makes me wonder is the fact, the VM is running stable if i don't use network with KVM.
If the Network is up and running, within five to ten minutes the box got killed completely.
I was able to reproduce it several times.
Hopefully it will help you guys.
The text was updated successfully, but these errors were encountered: