From owner-freebsd-xen@freebsd.org Mon Jul 20 19:40:34 2015 Return-Path: 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 766839A403F for ; Mon, 20 Jul 2015 19:40:34 +0000 (UTC) (envelope-from prvs=164384a8b9=jwest@ezwind.net) Received: from ezwind.net (booby.ezwind.net [199.188.211.150]) by mx1.freebsd.org (Postfix) with ESMTP id 4E39B119F for ; Mon, 20 Jul 2015 19:40:33 +0000 (UTC) (envelope-from prvs=164384a8b9=jwest@ezwind.net) X-MDAV-Result: clean X-MDAV-Processed: ezwind.net, Mon, 20 Jul 2015 14:40:04 -0500 X-Spam-Processed: ezwind.net, Mon, 20 Jul 2015 14:40:04 -0500 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on Booby X-Spam-Level: X-Spam-Status: No, score=-4.7 required=6.0 tests=BAYES_00,NO_RELAYS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from jayPC by ezwind.net (MDaemon PRO v15.0.3) with ESMTPA id 28-md50000002595.msg for ; Mon, 20 Jul 2015 14:40:03 -0500 X-MDRemoteIP: 97.91.122.42 X-MDHelo: jayPC X-MDArrival-Date: Mon, 20 Jul 2015 14:40:03 -0500 X-Authenticated-Sender: jwest@ezwind.net X-Return-Path: prvs=164384a8b9=jwest@ezwind.net X-Envelope-From: jwest@ezwind.net X-MDaemon-Deliver-To: freebsd-xen@freebsd.org From: "Jay West" To: Subject: multipath status changed, freebsd fails Date: Mon, 20 Jul 2015 14:40:03 -0500 Message-ID: <007601d0c323$e0299e80$a07cdb80$@ezwind.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdDDItzkBfQOwTFlTLaDgCTbRtZxJA== Content-Language: en-us 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 19:40:34 -0000 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! J