From owner-freebsd-xen@freebsd.org Tue Sep 8 16:07:00 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 184ADA00C71 for ; Tue, 8 Sep 2015 16:07:00 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.krpservers.com", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4E461C17 for ; Tue, 8 Sep 2015 16:06:59 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213] (may be forged)) (authenticated bits=0) by smtp.krpservers.com (8.14.9/8.14.9) with ESMTP id t88G6AMZ000624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Sep 2015 17:06:12 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Tue, 08 Sep 2015 17:06:29 +0100 From: Karl Pielorz To: Adam McDougall , freebsd-xen@freebsd.org Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... Message-ID: <762F895FF087C3BBB6DB94DA@[10.12.30.106]> In-Reply-To: <55EDC55B.8000004@egr.msu.edu> References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> <55EDC55B.8000004@egr.msu.edu> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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: Tue, 08 Sep 2015 16:07:00 -0000 --On 07 September 2015 13:11 -0400 Adam McDougall wrote: > Try this: > http://discussions.citrix.com/topic/329848-openbsd-with-message-watchdog- > timeout/ > > I've used it before for an OpenBSD guest VM. If that patch is in place > on any XenServer you migrate to, it should set e1000 for the NIC type if > you set NicEmulation in the Custom Fields as described in step 2. > > A cleaner patch would just let you specify any driver you want, but this > one is semi-hardcoded for e1000. You could also try 'virtio' with: > argv = [arg.replace('rtl8139','virtio') for arg in argv] Hi, Thanks for the link. I patched both our in-house XenServers [6.5SP1+Hotfixes] with this - it appeared to work OK (i.e. the DomU's came up with em0 NIC's - rather than Realtek). They seem to work OK for pushing traffic - but if I try and migrate a guest VM using Intel NIC's with XenServer - it fails miserably and kills it :( XenServer logs: "Migrating VM 'FreeBSD (SWR)' from 'Xen1' to 'Xen2' Internal error: Xenops_interface.Internal_error("Unix.Unix_error(2\"open\",\"/var/lib/xen/qemu-save.36\")")" Other VM's not using the Intel NIC's seem OK. I made sure both the 'source' and 'destination' XenServers are patch (there's only two in the pool). -Karl