From owner-freebsd-xen@freebsd.org  Wed Sep  9 08:30:04 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 39B919CB8BF
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Wed,  9 Sep 2015 08:30:04 +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 D80BC1BCA
 for <freebsd-xen@freebsd.org>; Wed,  9 Sep 2015 08:30:02 +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 t898TKBg065481
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Wed, 9 Sep 2015 09:29:21 +0100 (BST)
 (envelope-from kpielorz_lst@tdx.co.uk)
Date: Wed, 09 Sep 2015 09:29:40 +0100
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: Adam McDougall <mcdouga9@egr.msu.edu>, freebsd-xen@freebsd.org
Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors...
Message-ID: <BBDE686A05E03437BB32667C@[10.12.30.106]>
In-Reply-To: <762F895FF087C3BBB6DB94DA@[10.12.30.106]>
References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]>
 <55EDA470.1000007@citrix.com> <C1F8BAECAFA8EB8C9A97D5FA@[10.12.30.106]>
 <55EDC55B.8000004@egr.msu.edu> <762F895FF087C3BBB6DB94DA@[10.12.30.106]>
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
 <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: Wed, 09 Sep 2015 08:30:04 -0000


--On 08 September 2015 17:06 +0100 Karl Pielorz <kpielorz_lst@tdx.co.uk> 
wrote:

> 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\")")"

As a follow-up to this - the patch definitely breaks migrations. Removing 
the 'e1000' from the custom field (so you get Realtek NIC's) - the migrate 
completes fine.

Leave 'e1000' set - you get Intel em devices, but migrates fail - XenCenter 
spits out the error above.

>From /var/log/messages on the destination node - I can also see:

"
Sep  9 09:18:55 Xen2 xapi: [ info|Xen2|33915 INET 
:::80|network.attach_for_vm R:xxxxxxx|xapi] PIF 
yyyyyy-yyyy-yyyy-yyy-yyyyyyyyy is needed by a VM, but not managed by xapi. 
The bridge must be configured through other means.
"

So it looks like XenServer at least cannot support this configuration? - So 
I'm back painted into a corner :( - PV NIC's can't "route" traffic (or do 
DHCP servers, or OpenVPN etc.) - HVM NIC's can do all of that but cannot be 
used agile, and may fail eventually anyway with 'watchdog timeout'.

Gah.

-Karl