Re: [Xen-users] Xen 4.2.5 Remus usage triggers random host restarts

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

CC-ing the Remus maintainers listed in the MAINTAINERS file

I know that there has been work going into Xen 4.5 wrt Remus support in
the libxl/xl based stacks. I've no idea what old xend support was like
prior to that.

On Tue, 2014-11-11 at 18:21 +0000, JoÃo LuÃs Pinto wrote:
> Hi,
> 
> I have yet to receive any suggestions regarding this problem.
> 
> Besides what has happened using patched (as mentioned before) Xen
> 4.2.5, I have tried using Remus+DRBD (8.3.11 version patched to
> support protocol D) using out-of-the-box compilations of vanilla Xen
> 4.3.3 and 4.4.1 (optionally building xend). In both these versions
> Remus, after successfully synchronizing the initial vm memory
> snapshot, and when about to start making the incremental state updates
> to the other host, simply fails.
> 
> Is anybody using this feature of Xen? Is this feature working in the
> currently supported Xen minor versions?
> 
> Thank you,
> 
> Joao
> 
> 
> On Thu, Nov 6, 2014 at 3:35 PM, JoÃo LuÃs Pinto <joaoluispinto@xxxxxxxxx> 
> wrote:
> > Hi,
> >
> > I am evaluating Xen Remus usage.
> >
> > The test systems consists of two virtualized hosts running Xen 4.2.5
> > with Debian Wheezy 7.6, with the first compiled with the patches
> > linked in the instructions available at http://remusha.wikidot.com/.
> > Only the patches that can cleanly (or with minor adjustments) migrate
> > to version 4.2.5 are applied, namely patches 02, 03, 05 and 06 and the
> > drbd-hvm-fix.
> >
> > I am using the available patched version of drbd 8.3.11 (and
> > overriding the kernel provided drbd module), and the sch-plug kernel
> > module provided.
> >
> > For tests, I am running a pv domain (with a kernel supporting the
> > event channel). After starting Remus, and after some time of having
> > things running normally (two instances: one a few hours later and
> > another 3.5 days later), the host running Remus unexpectedly reboots,
> > leaving no trace of errors in the several logs
> > (/var/log/{messages,dmesg,syslog},
> > /var/log/xen/{xend.log,xend-debug.log}, the Remus log itself).
> >
> > Does anyone have any idea of what might be happening?
> >
> > Thank you,
> >
> > Joao
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users