From owner-freebsd-xen@freebsd.org Mon Sep 7 13:18:20 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 EADD39CC1FD for ; Mon, 7 Sep 2015 13:18:20 +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 953841E7B for ; Mon, 7 Sep 2015 13:18:19 +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 t87Cw99t093054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 7 Sep 2015 13:58:11 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Mon, 07 Sep 2015 13:58:28 +0100 From: Karl Pielorz To: freebsd-xen@freebsd.org Subject: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... Message-ID: <9CC4073DE17E3C8BD01EF7D3@[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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Sep 2015 13:18:21 -0000 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). Anyone know if that same "there is no re watchdog" issue is a possible cause? - Or any suggestions for fixes? -Karl From owner-freebsd-xen@freebsd.org Mon Sep 7 14:51:42 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 DC51E9CC1C5 for ; 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 ; 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 , References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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. From owner-freebsd-xen@freebsd.org Mon Sep 7 15:00:53 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 C1B739CC664 for ; Mon, 7 Sep 2015 15:00:53 +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 6A5B91FF7 for ; Mon, 7 Sep 2015 15:00:53 +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 t87F0R9s001275 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Sep 2015 16:00:28 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Mon, 07 Sep 2015 16:00:46 +0100 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , freebsd-xen@freebsd.org Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... Message-ID: In-Reply-To: <55EDA470.1000007@citrix.com> References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable 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: Mon, 07 Sep 2015 15:00:53 -0000 --On 07 September 2015 16:51 +0200 Roger Pau Monn=C3=A9 = =20 wrote: > 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=3De1000" to the network = configuration > line. Hi Roger, I'd love to try that - but as we're running full 'XenServer' (i.e.=20 installed from XenServer .ISO) I have no idea where (or even if it's=20 possible) to set that :( Last time I tried looking it up I hit a bit of a dead end, I'll have=20 another look [in fact, I think it may have actually been impossible to set=20 in XenServer as I seem to remember someone saying that XenServer doesn't=20 have that NIC model/emulation available, only Realtek or PV!] But I'll have another look... -Karl From owner-freebsd-xen@freebsd.org Mon Sep 7 17:20:01 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 1BB2E9C55BA for ; Mon, 7 Sep 2015 17:20:01 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (boomhauer.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id ED07F19AD for ; Mon, 7 Sep 2015 17:20:00 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from boomhauer (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id C8EC953BD9 for ; Mon, 7 Sep 2015 13:11:56 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by boomhauer (boomhauer.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sIe4e6nZXXHd for ; Mon, 7 Sep 2015 13:11:56 -0400 (EDT) Received: from EGR authenticated sender mcdouga9 Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... To: freebsd-xen@freebsd.org References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> From: Adam McDougall Message-ID: <55EDC55B.8000004@egr.msu.edu> Date: Mon, 7 Sep 2015 13:11:55 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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, 07 Sep 2015 17:20:01 -0000 On 09/07/2015 11:00, Karl Pielorz wrote: > > --On 07 September 2015 16:51 +0200 Roger Pau Monné > wrote: > >> 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. > > Hi Roger, > > I'd love to try that - but as we're running full 'XenServer' (i.e. > installed from XenServer .ISO) I have no idea where (or even if it's > possible) to set that :( > > Last time I tried looking it up I hit a bit of a dead end, I'll have > another look [in fact, I think it may have actually been impossible to > set in XenServer as I seem to remember someone saying that XenServer > doesn't have that NIC model/emulation available, only Realtek or PV!] > > But I'll have another look... > > -Karl 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] 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 From owner-freebsd-xen@freebsd.org Wed Sep 9 08:30:04 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 39B919CB8BF for ; 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 ; 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 To: Adam McDougall , freebsd-xen@freebsd.org Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... Message-ID: In-Reply-To: <762F895FF087C3BBB6DB94DA@[10.12.30.106]> References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> <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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2015 08:30:04 -0000 --On 08 September 2015 17:06 +0100 Karl Pielorz 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 From owner-freebsd-xen@freebsd.org Wed Sep 9 09:04:33 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 5F4C8A00F93 for ; Wed, 9 Sep 2015 09:04:33 +0000 (UTC) (envelope-from prvs=687bbb327=roger.pau@citrix.com) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (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 0E983116E for ; Wed, 9 Sep 2015 09:04:32 +0000 (UTC) (envelope-from prvs=687bbb327=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.17,496,1437436800"; d="scan'208";a="298774766" Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... To: Karl Pielorz , Adam McDougall , References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> <55EDC55B.8000004@egr.msu.edu> <762F895FF087C3BBB6DB94DA@[10.12.30.106]> From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= Message-ID: <55EFF61A.3020409@citrix.com> Date: Wed, 9 Sep 2015 11:04:26 +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: Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA2 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: Wed, 09 Sep 2015 09:04:33 -0000 Hello, El 09/09/15 a les 10.29, Karl Pielorz ha escrit: > > --On 08 September 2015 17:06 +0100 Karl Pielorz > 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'. I'm working on importing a new netfront from Linux, which hopefully should solve the problems we are having with the PV nic. In the meantime, I have the following crappy patch to FreeBSD if_re driver, which should disable the watchdog (I have not even compile tested this). --- diff --git a/sys/dev/re/if_re.c b/sys/dev/re/if_re.c index 677d397..a098ce7 100644 --- a/sys/dev/re/if_re.c +++ b/sys/dev/re/if_re.c @@ -278,7 +278,9 @@ static int re_ioctl (struct ifnet *, u_long, caddr_t); static void re_init (void *); static void re_init_locked (struct rl_softc *); static void re_stop (struct rl_softc *); +#ifdef RE_WATCHDOG static void re_watchdog (struct rl_softc *); +#endif static int re_suspend (device_t); static int re_resume (device_t); static int re_shutdown (device_t); @@ -2480,7 +2482,9 @@ re_tick(void *xsc) * lost on PCIe based controllers under certain situations. */ re_txeof(sc); +#ifdef RE_WATCHDOG re_watchdog(sc); +#endif callout_reset(&sc->rl_stat_callout, hz, re_tick, sc); } @@ -3521,6 +3525,7 @@ re_ioctl(struct ifnet *ifp, u_long command, caddr_t data) return (error); } +#ifdef RE_WATCHDOG static void re_watchdog(struct rl_softc *sc) { @@ -3550,6 +3555,7 @@ re_watchdog(struct rl_softc *sc) if (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) re_start_locked(ifp); } +#endif /* * Stop the adapter and free any mbufs allocated to the From owner-freebsd-xen@freebsd.org Wed Sep 9 09:34:01 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 79CD5A0034A for ; Wed, 9 Sep 2015 09:34:01 +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 2237712F9 for ; Wed, 9 Sep 2015 09:34:00 +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 t899XHge069694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Sep 2015 10:33:18 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Wed, 09 Sep 2015 10:33:38 +0100 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , Adam McDougall , freebsd-xen@freebsd.org Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... Message-ID: <34C596D4CD79963C95725C41@[10.12.30.106]> In-Reply-To: <55EFF61A.3020409@citrix.com> References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> <55EDC55B.8000004@egr.msu.edu> <762F895FF087C3BBB6DB94DA@[10.12.30.106]> <55EFF61A.3020409@citrix.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable 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: Wed, 09 Sep 2015 09:34:01 -0000 --On 09 September 2015 11:04 +0200 Roger Pau Monn=C3=A9 = =20 wrote: > I'm working on importing a new netfront from Linux, which hopefully > should solve the problems we are having with the PV nic. That'll be great - I did test a CentOS box domU a while ago, and that=20 didn't have the problem with routing traffic, I wasn't able to test things=20 like OpenVPN/DCHP on it - but the current netfront issues are annoying=20 [there's at least 2 FreeBSD PR's I know of this would also address]. > In the meantime, I have the following crappy patch to FreeBSD if_re > driver, which should disable the watchdog (I have not even compile > tested this). Thanks - I'll give that a go... I also discovered that the 'virtio'=20 virtual NIC's - *do* migrate OK, I'm just setting up a test platform using=20 those to see if they have the same netfront issues as PV xn interfaces=20 (i.e. can't route / openvpn fails). I'll post back with the results of that + the patch when I have them, Thanks, -Kp From owner-freebsd-xen@freebsd.org Wed Sep 9 11:47:13 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 BFE239CD540 for ; Wed, 9 Sep 2015 11:47:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 AC53B12B5 for ; Wed, 9 Sep 2015 11:47:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t89BlDUi058435 for ; Wed, 9 Sep 2015 11:47:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 153477] [xen] XEN pmap code abuses vm page queue lock Date: Wed, 09 Sep 2015 11:47:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 09 Sep 2015 11:47:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D153477 Roger Pau Monn=C3=83=C2=A9 changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Closed CC| |royger@freebsd.org Resolution|--- |Rejected --- Comment #2 from Roger Pau Monn=C3=83=C2=A9 --- PV pmap code has been removed together with the classic PV i386 port. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Wed Sep 9 11:49:14 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 38C329CD59D for ; Wed, 9 Sep 2015 11:49:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 2559E1305 for ; Wed, 9 Sep 2015 11:49:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t89BnEOV060532 for ; Wed, 9 Sep 2015 11:49:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 195824] [xen] xen console broke with 10.1 Date: Wed, 09 Sep 2015 11:49:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 09 Sep 2015 11:49:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195824 Roger Pau Monn=C3=83=C2=A9 changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Feedback Timeout --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Wed Sep 9 12:24:01 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 1F93BA00C5A for ; Wed, 9 Sep 2015 12:24:01 +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 BA113188C for ; Wed, 9 Sep 2015 12:24:00 +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 t89CNG4n080885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Sep 2015 13:23:18 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Wed, 09 Sep 2015 13:23:38 +0100 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , Adam McDougall , freebsd-xen@freebsd.org Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... Message-ID: In-Reply-To: <55EFF61A.3020409@citrix.com> References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> <55EDC55B.8000004@egr.msu.edu> <762F895FF087C3BBB6DB94DA@[10.12.30.106]> <55EFF61A.3020409@citrix.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable 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: Wed, 09 Sep 2015 12:24:01 -0000 --On 09 September 2015 11:04 +0200 Roger Pau Monn=C3=A9 = =20 wrote: > In the meantime, I have the following crappy patch to FreeBSD if_re > driver, which should disable the watchdog (I have not even compile > tested this). fyi - The patch stops the 'watchdog timeout' errors - but the NIC just=20 'dies' after the live migrate (i.e. same as before, but no errors logged). VirtIO (vtnet) so far seems to work for migrates, and work for routing=20 traffic to other DomU guests - so I'm continuing to test that now as a=20 workaround (i.e. test with OpenVPN etc.) The only thing I've noticed with it is that established TCP sessions=20 'through the DomU' tend to die during the migrate (i.e. the DomU 'lands' at = the destination node - but any transfers in progress stall - there's a=20 50/50 chance they recover) - but if I migrate the Windows DomU that's=20 actually got the download in progress, the session stays up - hence more=20 testing needed. -Karl From owner-freebsd-xen@freebsd.org Wed Sep 9 12:28:12 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 6ED61A00E64 for ; Wed, 9 Sep 2015 12:28:12 +0000 (UTC) (envelope-from prvs=687bbb327=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 221421952 for ; Wed, 9 Sep 2015 12:28:11 +0000 (UTC) (envelope-from prvs=687bbb327=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.17,496,1437436800"; d="scan'208";a="302346454" Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... To: Karl Pielorz , Adam McDougall , References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> <55EDC55B.8000004@egr.msu.edu> <762F895FF087C3BBB6DB94DA@[10.12.30.106]> <55EFF61A.3020409@citrix.com> <34C596D4CD79963C95725C41@[10.12.30.106]> From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= X-Enigmail-Draft-Status: N1110 Message-ID: <55F025BF.6020405@citrix.com> Date: Wed, 9 Sep 2015 14:27:43 +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: <34C596D4CD79963C95725C41@[10.12.30.106]> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA2 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: Wed, 09 Sep 2015 12:28:12 -0000 Hello, El 09/09/15 a les 11.33, Karl Pielorz ha escrit: > > > --On 09 September 2015 11:04 +0200 Roger Pau Monné > wrote: > >> I'm working on importing a new netfront from Linux, which hopefully >> should solve the problems we are having with the PV nic. > > That'll be great - I did test a CentOS box domU a while ago, and that > didn't have the problem with routing traffic, I wasn't able to test > things like OpenVPN/DCHP on it - but the current netfront issues are > annoying [there's at least 2 FreeBSD PR's I know of this would also > address]. Do you have an easy way to replicate those issues, right now I'm trying with the following: /etc/etc.conf: pf_enable="YES" /etc/pf.conf block in all pass out all keep state But I don't seem to be able to reproduce them. Throughput between DomU<->Dom0 or DomU<->DomU seems to be fine (no degradation when compared to pf off). Roger. From owner-freebsd-xen@freebsd.org Wed Sep 9 14:01:26 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 4A4A2A0161D for ; Wed, 9 Sep 2015 14:01:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 3648815C2 for ; Wed, 9 Sep 2015 14:01:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t89E1Qkg050103 for ; Wed, 9 Sep 2015 14:01:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 195824] [xen] xen console broke with 10.1 Date: Wed, 09 Sep 2015 14:01:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd@dckd.nl X-Bugzilla-Status: Closed X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 09 Sep 2015 14:01:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195824 Jeroen changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|Feedback Timeout |Not A Bug --- Comment #4 from Jeroen --- Apologies, adding the line as suggested by Roger fixed the problem. Since this is not documented properly, I've opened #201787 to fix that. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@freebsd.org Wed Sep 9 14:02:13 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 49713A016E0 for ; Wed, 9 Sep 2015 14:02:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 233D718CF for ; Wed, 9 Sep 2015 14:02:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t89E2CdX063704 for ; Wed, 9 Sep 2015 14:02:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 195824] [xen] xen console broke with 10.1 Date: Wed, 09 Sep 2015 14:02:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd@dckd.nl X-Bugzilla-Status: Closed X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 09 Sep 2015 14:02:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195824 --- Comment #5 from Jeroen --- (In reply to Jeroen from comment #4) That should be bug #201787 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@freebsd.org Wed Sep 9 20:59:03 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 72A04A01EBB for ; Wed, 9 Sep 2015 20:59:03 +0000 (UTC) (envelope-from syd.meyer@gmail.com) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0281B1E79 for ; Wed, 9 Sep 2015 20:59:03 +0000 (UTC) (envelope-from syd.meyer@gmail.com) Received: by wiclk2 with SMTP id lk2so965134wic.1 for ; Wed, 09 Sep 2015 13:59:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=p5HN/WLRpflKP06LZ1nKbN2TX15SGOH1tGCyWn1fAqA=; b=LY+bBV22WIneaQ7bvjMcFrxa848hsfUv3LdnGfTDmemeSzohmicsI4G8sfjpagCIP6 uLT6C2404hGjMJQ7QYuQTrpFt1NJP2/PLUrkE7H7voUVe3p2Lf2gGkPKHvRJl1aCD7Ls Ww/VuWt+HCte86hzKM9nDM2j+FWsBFhDHRhiWEturpgNOsQJJhUY8wpeOozYt7MwS473 cC93spK52zRrgh6q02BWfOV81VB0WRc2sQl/hF9ZAarsE1rOilcJqUO6cEaNOGPTEeU6 4ON/Tfp0Lzn6az0N06E+vs62504CoepN/XG1x33XpAc4mV/rjGn4aEAQzA3zKl66b2vd RQuw== X-Received: by 10.194.122.97 with SMTP id lr1mr61813256wjb.26.1441832341086; Wed, 09 Sep 2015 13:59:01 -0700 (PDT) Received: from ?IPv6:2a02:a03f:a0f:a200:b8c4:8f36:1407:7c58? ([2a02:a03f:a0f:a200:b8c4:8f36:1407:7c58]) by smtp.gmail.com with ESMTPSA id fa8sm5726667wib.14.2015.09.09.13.59.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Sep 2015 13:59:00 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3093\)) Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... From: Sydney Meyer In-Reply-To: <55F025BF.6020405@citrix.com> Date: Wed, 9 Sep 2015 22:58:58 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <28F73DA3-DC56-47F4-922B-31D73D124981@gmail.com> References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> <55EDC55B.8000004@egr.msu.edu> <762F895FF087C3BBB6DB94DA@[10.12.30.106]> <55EFF61A.3020409@citrix.com> <34C596D4CD79963C95725C41@[10.12.30.106]> <55F025BF.6020405@citrix.com> To: freebsd-xen@freebsd.org X-Mailer: Apple Mail (2.3093) 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: Wed, 09 Sep 2015 20:59:03 -0000 Hello, I'm running Xen 4.4.1 on a Debian 8 Dom0 and with 2 fresh FreeBSD 10.2 = DomU's (pf disabled): IPv4: - Host A (FreeBSD 10.2): "dd if=3D/dev/zero bs=3D1M | nc -l 5001" ---> = Host B (FreeBSD 10.2) "nc 10.0.30.95 5001 | dd of=3D/dev/zero bs=3D1M" =3D= ~46 MB/s - Host A (FreeBSD 10.2): "dd if=3D/dev/zero bs=3D1M | nc -l 5001" ---> = Host B (CentOS 7) "nc 10.0.30.95 5001 | dd of=3D/dev/zero bs=3D1M" =3D = ~65 MB/s - Host A (CentOS 7): "dd if=3D/dev/zero bs=3D1M | nc -l 5001" ---> Host = B (FreeBSD 10.2) "nc 10.0.30.111 5001 | dd of=3D/dev/zero bs=3D1M" =3D = ~685 MB/s IPv6: - Host A (FreeBSD 10.2): "dd if=3D/dev/zero bs=3D1M | nc -6 -l 5001" = ---> Host B (FreeBSD 10.2) "nc -6 2a02:a03f:a0f:a200:216:3eff:fee0:44bd = 5001 | dd of=3D/dev/zero bs=3D1M" =3D ~309 MB/s - Host A (FreeBSD 10.2): "dd if=3D/dev/zero bs=3D1M | nc -6 -l 5001" = ---> Host B (Centos 7) "nc -6 2a02:a03f:a0f:a200:216:3eff:fee0:44bd 5001 = | dd of=3D/dev/zero bs=3D1M" =3D ~246 MB/s - Host A (CentOS 7): "dd if=3D/dev/zero bs=3D1M | nc -6 -l 5001" ---> = Host B (FreeBSD 10.2) "nc -6 2a02:a03f:a0f:a200:216:3eff:fe7c:c4bd 5001 = | dd of=3D/dev/zero bs=3D1M" =3D ~352 MB/s Also, i can confirm problems with FreeBSD 10 acting as a router for = other DomU on the same Dom0 (as in = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261). > On 09 Sep 2015, at 14:27, Roger Pau Monn=C3=A9 = wrote: >=20 > Hello, >=20 > El 09/09/15 a les 11.33, Karl Pielorz ha escrit: >>=20 >>=20 >> --On 09 September 2015 11:04 +0200 Roger Pau Monn=C3=A9 >> wrote: >>=20 >>> I'm working on importing a new netfront from Linux, which hopefully >>> should solve the problems we are having with the PV nic. >>=20 >> That'll be great - I did test a CentOS box domU a while ago, and that >> didn't have the problem with routing traffic, I wasn't able to test >> things like OpenVPN/DCHP on it - but the current netfront issues are >> annoying [there's at least 2 FreeBSD PR's I know of this would also >> address]. >=20 > Do you have an easy way to replicate those issues, right now I'm = trying > with the following: >=20 > /etc/etc.conf: > pf_enable=3D"YES" >=20 > /etc/pf.conf > block in all > pass out all keep state >=20 > But I don't seem to be able to reproduce them. Throughput between > DomU<->Dom0 or DomU<->DomU seems to be fine (no degradation when > compared to pf off). >=20 > Roger. > _______________________________________________ > freebsd-xen@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" From owner-freebsd-xen@freebsd.org Fri Sep 11 22:13:24 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 AF4ECA02067 for ; Fri, 11 Sep 2015 22:13:24 +0000 (UTC) (envelope-from syd.meyer@gmail.com) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 44BD113D7 for ; Fri, 11 Sep 2015 22:13:24 +0000 (UTC) (envelope-from syd.meyer@gmail.com) Received: by wicgb1 with SMTP id gb1so78158469wic.1 for ; Fri, 11 Sep 2015 15:13:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=O0yKg2CftPsL4+N6XM3wbWNA0v187GDcpxfTN5sOxkA=; b=PAP43JyBbLGNNBtnxVFKKU7xSisTMgN7DqRKY5cV5ytR0fC5S8E1ymD+mMcme+OmL0 dm1koNBfOGFHiGGoKnogHw9mHqE0N2A3nE/SoV9y83Nh5CWUn06CQllxBaR2/HoJ2X0R Tq+PVhAsOsasRRUb2I8Ztu/xNVygyQCh7l7ekdCd3hitvGy+WqOktpTiU2IG86g2kw5g VsoHuPTlEMpqYIUUhgVgR0TJcypKCgr4YyeY2pNudDQp/62/p7+Qz1xkKqvY1GP+A7xz lvYqE/8CjEDCfgO5Vsl+QKrlkC17MPiGUJGki1oo/HN5v/ATBOiMB1S6vT4oJDeUejsO Sesg== X-Received: by 10.180.105.138 with SMTP id gm10mr720376wib.37.1442009602000; Fri, 11 Sep 2015 15:13:22 -0700 (PDT) Received: from ?IPv6:2a02:a03f:a0f:a200:918a:f5db:ce7c:1ebe? ([2a02:a03f:a0f:a200:918a:f5db:ce7c:1ebe]) by smtp.gmail.com with ESMTPSA id jc9sm1179592wic.6.2015.09.11.15.13.20 for (version=TLS1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Sep 2015 15:13:21 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\)) Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... From: Sydney Meyer In-Reply-To: <28F73DA3-DC56-47F4-922B-31D73D124981@gmail.com> Date: Sat, 12 Sep 2015 00:13:19 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> <55EDC55B.8000004@egr.msu.edu> <762F895FF087C3BBB6DB94DA@[10.12.30.106]> <55EFF61A.3020409@citrix.com> <34C596D4CD79963C95725C41@[10.12.30.106]> <55F025BF.6020405@citrix.com> <28F73DA3-DC56-47F4-922B-31D73D124981@gmail.com> To: freebsd-xen@freebsd.org X-Mailer: Apple Mail (2.3094) 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: Fri, 11 Sep 2015 22:13:24 -0000 I just noticed that these performance problems do not occur under 10.0 = and 10.1. Starting with 10.2 IPv4 TCP performance drops from ~12 Gb/s under 10.1 = to ~350 Mb/s under 10.2. Should i write a new bugreport for this? > On 09 Sep 2015, at 22:58, Sydney Meyer wrote: >=20 > Hello, >=20 > I'm running Xen 4.4.1 on a Debian 8 Dom0 and with 2 fresh FreeBSD 10.2 = DomU's (pf disabled): >=20 > IPv4: > - Host A (FreeBSD 10.2): "dd if=3D/dev/zero bs=3D1M | nc -l 5001" ---> = Host B (FreeBSD 10.2) "nc 10.0.30.95 5001 | dd of=3D/dev/zero bs=3D1M" =3D= ~46 MB/s > - Host A (FreeBSD 10.2): "dd if=3D/dev/zero bs=3D1M | nc -l 5001" ---> = Host B (CentOS 7) "nc 10.0.30.95 5001 | dd of=3D/dev/zero bs=3D1M" =3D = ~65 MB/s > - Host A (CentOS 7): "dd if=3D/dev/zero bs=3D1M | nc -l 5001" ---> = Host B (FreeBSD 10.2) "nc 10.0.30.111 5001 | dd of=3D/dev/zero bs=3D1M" = =3D ~685 MB/s >=20 > IPv6: > - Host A (FreeBSD 10.2): "dd if=3D/dev/zero bs=3D1M | nc -6 -l 5001" = ---> Host B (FreeBSD 10.2) "nc -6 2a02:a03f:a0f:a200:216:3eff:fee0:44bd = 5001 | dd of=3D/dev/zero bs=3D1M" =3D ~309 MB/s > - Host A (FreeBSD 10.2): "dd if=3D/dev/zero bs=3D1M | nc -6 -l 5001" = ---> Host B (Centos 7) "nc -6 2a02:a03f:a0f:a200:216:3eff:fee0:44bd 5001 = | dd of=3D/dev/zero bs=3D1M" =3D ~246 MB/s > - Host A (CentOS 7): "dd if=3D/dev/zero bs=3D1M | nc -6 -l 5001" ---> = Host B (FreeBSD 10.2) "nc -6 2a02:a03f:a0f:a200:216:3eff:fe7c:c4bd 5001 = | dd of=3D/dev/zero bs=3D1M" =3D ~352 MB/s >=20 > Also, i can confirm problems with FreeBSD 10 acting as a router for = other DomU on the same Dom0 (as in = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261). >=20 >> On 09 Sep 2015, at 14:27, Roger Pau Monn=C3=A9 = wrote: >>=20 >> Hello, >>=20 >> El 09/09/15 a les 11.33, Karl Pielorz ha escrit: >>>=20 >>>=20 >>> --On 09 September 2015 11:04 +0200 Roger Pau Monn=C3=A9 >>> wrote: >>>=20 >>>> I'm working on importing a new netfront from Linux, which hopefully >>>> should solve the problems we are having with the PV nic. >>>=20 >>> That'll be great - I did test a CentOS box domU a while ago, and = that >>> didn't have the problem with routing traffic, I wasn't able to test >>> things like OpenVPN/DCHP on it - but the current netfront issues are >>> annoying [there's at least 2 FreeBSD PR's I know of this would also >>> address]. >>=20 >> Do you have an easy way to replicate those issues, right now I'm = trying >> with the following: >>=20 >> /etc/etc.conf: >> pf_enable=3D"YES" >>=20 >> /etc/pf.conf >> block in all >> pass out all keep state >>=20 >> But I don't seem to be able to reproduce them. Throughput between >> DomU<->Dom0 or DomU<->DomU seems to be fine (no degradation when >> compared to pf off). >>=20 >> Roger. >> _______________________________________________ >> freebsd-xen@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to = "freebsd-xen-unsubscribe@freebsd.org" >=20