From owner-freebsd-xen@FreeBSD.ORG Sat Apr 26 08:40:01 2014 Return-Path: Delivered-To: freebsd-xen@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 76BD5B2F for ; Sat, 26 Apr 2014 08:40:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 634F31345 for ; Sat, 26 Apr 2014 08:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3Q8e1Wf077424 for ; Sat, 26 Apr 2014 08:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3Q8e170077423; Sat, 26 Apr 2014 08:40:01 GMT (envelope-from gnats) Date: Sat, 26 Apr 2014 08:40:01 GMT Message-Id: <201404260840.s3Q8e170077423@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org Cc: From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Subject: Re: bin/188990: [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= 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: Sat, 26 Apr 2014 08:40:01 -0000 The following reply was made to PR bin/188990; it has been noted by GNATS. From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= To: , Cc: Subject: Re: bin/188990: [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest Date: Sat, 26 Apr 2014 10:35:12 +0200 Could you try to move the DNS server to another host? There have been reports of failures on if_xn when sending/receiving data to/from other guests on the same host. I know this is not a valid log-term solution, but it could help in identifying the problem, which is probably related to PR 188261. Roger.