From owner-freebsd-xen@freebsd.org  Tue Jul 21 07:35:12 2015
Return-Path: <owner-freebsd-xen@freebsd.org>
Delivered-To: freebsd-xen@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28C279A6C39
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Tue, 21 Jul 2015 07:35:12 +0000 (UTC)
 (envelope-from prvs=637e9ed86=roger.pau@citrix.com)
Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89])
 (using TLSv1 with cipher RC4-SHA (128/128 bits))
 (Client CN "mail.citrix.com",
 Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id D5E2F10BC
 for <freebsd-xen@freebsd.org>; Tue, 21 Jul 2015 07:35:11 +0000 (UTC)
 (envelope-from prvs=637e9ed86=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.15,514,1432598400"; d="scan'208";a="282818759"
Message-ID: <55ADF616.4090200@citrix.com>
Date: Tue, 21 Jul 2015 09:34:46 +0200
From: =?windows-1252?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Jay West <jwest@ezwind.net>, <freebsd-xen@freebsd.org>
Subject: Re: multipath status changed, freebsd fails
References: <007601d0c323$e0299e80$a07cdb80$@ezwind.net>
In-Reply-To: <007601d0c323$e0299e80$a07cdb80$@ezwind.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-DLP: MIA1
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2015 07:35:12 -0000

Hello,

El 20/07/15 a les 21.40, Jay West ha escrit:
> I realize that this may not be a freebsd-xen issue, but not sure where to turn so thought I'd check here first.
> 
> We have a pool of about 10 xenservers (v6.5). All the servers are using multipath to connect to multiple nas, and each has multiple paths on different subnets. All seems to work ok, but....
> 
> About every 3 or 4 weeks, xencenter will throw an alert... "Multipath status has changed". Further looking in xencenter shows multipath status is AOK. However, a few VM's are down. Recovery is just restarting those VM's.
> 
> What is odd - is that every time this occurs, the VM's that failed are always FreeBSD (10.0-Release, most are P9) VM's, none of the windows VMs fail. Are there any known issues with FreeBSD where a blip in multipath status causes the VM to shutdown? I'd think this is a xenserver thing and not a freebsd thing... but thought I'd check. Any advice appreciated!

>From a FreeBSD (or guest in general) point of view, there's no notion of
multipath or the backing storage details in general, so I very much
doubt it has anything to do with FreeBSD. Are you only running Windows
and FreeBSD guests? Do you have the PV drivers installed on Windows guests?

Can you get the output of the VMs that automatically restart? Do they
crash and reboot or are they rebooted by xencenter?

It might be possible that XenServer does an unexpected virtual hard
drive state change when the multipath status changes and that this makes
FreeBSD crash, but without a ddb trace it's impossible to know.

Roger.