From owner-freebsd-xen@freebsd.org  Mon Sep  7 14:51:42 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 DC51E9CC1C5
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon,  7 Sep 2015 14:51:42 +0000 (UTC)
 (envelope-from prvs=68525f3d1=roger.pau@citrix.com)
Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63])
 (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 9493D1C1F
 for <freebsd-xen@freebsd.org>; Mon,  7 Sep 2015 14:51:42 +0000 (UTC)
 (envelope-from prvs=68525f3d1=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.17,485,1437436800"; d="scan'208";a="301743871"
Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors...
To: Karl Pielorz <kpielorz_lst@tdx.co.uk>, <freebsd-xen@freebsd.org>
References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]>
From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <55EDA470.1000007@citrix.com>
Date: Mon, 7 Sep 2015 16:51:28 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]>
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: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Sep 2015 14:51:43 -0000

El 07/09/15 a les 14.58, Karl Pielorz ha escrit:
> 
> Hi,
> 
> We have a bunch of FreeBSD 10.1 hosts we run the NIC's as HVM (this
> avoids a known networking issue with XenServer and PV networks under
> FreeBSD to do with routing packets for other Xen DomU).
> 
> This seems to work OK - but recently we've had a whole bunch of:
> 
>  Sep  7 12:41:08 host1 kernel: re0: watchdog timeout
> ...
>  Sep  7 12:42:03 host1 kernel: re1: watchdog timeout
> 
> 
> This seems to 'break' networking for the guest. I've tried doing
> 'ifconfig re0 down / ifconfig re0 up' - this doesn't appear to fix
> things - but rebooting the DomU guest does (when it comes back,
> networking is restored).
> 
> Searching around with Google turns up some similar issues with NetBSD
> along with the comment that the QEMU Realtek card doesn't have watchdog
> emulation - so it should be disabled in the driver.
> 
> How applicable to FreeBSD that is, I don't know.
> 
> This seems to happen when the VM's are migrated (e.g. Xen Storage
> Motion) from one SR to another - or migrated, full stop (i.e. from one
> XenServer to another - but using shared storage).

This sounds like a problem in the if_re driver on FreeBSD or a bug in
Qemu emulation. As a workaround, could you try to use the emulated e1000
instead of the realtek? AFAIK it should also provide better performance.

Since you are using XenServer I'm not sure of the exact rune, with OSS
Xen you basically need to add "model=e1000" to the network configuration
line.

Roger.