From owner-freebsd-xen@FreeBSD.ORG Mon Mar 4 11:06:54 2013 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F26FEF7D for ; Mon, 4 Mar 2013 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id C9F18E74 for ; Mon, 4 Mar 2013 11:06:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r24B6rWe038995 for ; Mon, 4 Mar 2013 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r24B6rgd038993 for freebsd-xen@FreeBSD.org; Mon, 4 Mar 2013 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Mar 2013 11:06:53 GMT Message-Id: <201303041106.r24B6rgd038993@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Mar 2013 11:06:54 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/176471 xen [xen] xn driver crash on detach o kern/176053 xen [xen] [patch] i386: Correct wrong usage of vsnprintf() o kern/175954 xen [xen] XENHVM xn network driver extreme packet loss dur o kern/175822 xen [xen] FreeBSD 9.1 does not work with Xen 4.0 o kern/175757 xen [xen] [patch] xen pvhvm looses keyboard input from VNC o kern/171873 xen [xen] xn network device floods warning in dmesg o kern/171118 xen [xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENHVM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exception o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 35 problems total. From owner-freebsd-xen@FreeBSD.ORG Mon Mar 4 11:17:26 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EFA6AD48 for ; Mon, 4 Mar 2013 11:17:26 +0000 (UTC) (envelope-from paul.wollner@macrolan.com) Received: from mail31.mimecast.co.za (mail31.mimecast.co.za [41.74.193.31]) by mx1.freebsd.org (Postfix) with ESMTP id E6411109A for ; Mon, 4 Mar 2013 11:17:25 +0000 (UTC) Received: from exchange01.macrolan.com (41.222.225.231 [41.222.225.231]) (Using TLS) by mail30.mimecast.co.za; Mon, 04 Mar 2013 13:10:52 +0200 Received: from EXCHANGE01.macrolan.com ([fe80::5d7d:103c:90b:ebb2]) by exchange01.macrolan.com ([fe80::5d7d:103c:90b:ebb2%10]) with mapi id 14.01.0438.000; Mon, 4 Mar 2013 13:10:50 +0200 From: Paul Wollner To: FreeBSD bugmaster , "freebsd-xen@FreeBSD.org" Subject: RE: Current problem reports assigned to freebsd-xen@FreeBSD.org Thread-Topic: Current problem reports assigned to freebsd-xen@FreeBSD.org Thread-Index: AQHOGMiklBlLuia44UyPgp34BBM+r5iVYATQ Date: Mon, 4 Mar 2013 11:10:49 +0000 Message-ID: References: <201303041106.r24B6rgd038993@freefall.freebsd.org> In-Reply-To: <201303041106.r24B6rgd038993@freefall.freebsd.org> Accept-Language: en-ZA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.50] MIME-Version: 1.0 X-MC-Unique: 113030413105203701 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Mar 2013 11:17:27 -0000 Hi Angie, How would billing for the service be then? Wil it be for oneDotComs account= our MacroLan's account? I would prefer for it to be billed to MacroLan. Regards Paul -----Original Message----- From: owner-freebsd-xen@freebsd.org [mailto:owner-freebsd-xen@freebsd.org] = On Behalf Of FreeBSD bugmaster Sent: 04 March 2013 01:07 PM To: freebsd-xen@FreeBSD.org Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description ---------------------------------------------------------------------------= ----- o kern/176471 xen [xen] xn driver crash on detach o kern/176053 xen [xen] [patch] i386: Correct wrong usage of vsnpri= ntf() o kern/175954 xen [xen] XENHVM xn network driver extreme packet los= s dur o kern/175822 xen [xen] FreeBSD 9.1 does not work with Xen 4.0 o kern/175757 xen [xen] [patch] xen pvhvm looses keyboard input fro= m VNC o kern/171873 xen [xen] xn network device floods warning in dmesg o kern/171118 xen [xen] FreeBSD XENHVM guest doesn't shutdown clean= ly o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENH= VM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks:= stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from= CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable= Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exce= ption o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not = worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boo= t_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN ker= nel.=20 o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel.= Not=20 o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel r= eboot o kern/154428 xen [xen] xn0 network interface and PF - Massive perf= orman o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentage= s o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork lo= ad o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (F= reeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on int= erfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwai= t=3D1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn'= t wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn'= t wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn'= t wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified = after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netf= ronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when = TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at= all=20 f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when c= onfig o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail= to b 35 problems total. _______________________________________________ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" Paul Wollner Technical Manager T:+27214426548 C:+27827869776 http://www.macrolan.co.za Service Desk: 0861 855 855 Services Email: support@macrolan.co.za Unit 1, The Waverley Business Park, Wycroft Road, Mowbray, Cape Town The information contained in this communication from the sender is confiden= tial. It is intended solely for use by the recipient and others=20 authorized to receive it. If you are not the recipient, you are hereby noti= fied that any disclosure, copying, distribution or taking action in=20 relation of the contents of this information is strictly prohibited and may= be unlawful. This email has been scanned for viruses and malware, and automatically arch= ived by Mimecast SA (Pty) Ltd, an innovator in Software as a Service (SaaS)= for business.=20 Mimecast Unified Email Management????????? UEM offers email continuity, sec= urity, archiving and compliance with all current legislation. To find out = more, http://www.mimecast.co.za/uem mnd From owner-freebsd-xen@FreeBSD.ORG Wed Mar 6 20:17:29 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D460AB1A for ; Wed, 6 Mar 2013 20:17:29 +0000 (UTC) (envelope-from jwest@ezwind.net) Received: from ezwind.net (bobby.ezwind.net [199.188.211.146]) by mx1.freebsd.org (Postfix) with ESMTP id 9E0D33C8 for ; Wed, 6 Mar 2013 20:17:29 +0000 (UTC) Received: from LENOVOD6B52A6B by ezwind.net (MDaemon.PRO.v8.1.3.R) with ESMTP id 64-md50000142847.msg for ; Wed, 06 Mar 2013 14:17:02 -0600 From: "Jay West" To: Subject: misc. questions Date: Wed, 6 Mar 2013 14:17:02 -0600 Message-ID: <000901ce1aa7$90704320$b150c960$@ezwind.net> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac4ap4CYdCzfHX2ERPyysPaBFTCs5Q== Content-Language: en-us X-Authenticated-Sender: jwest@ezwind.net X-Spam-Processed: gateway.ezwind.net, Wed, 06 Mar 2013 14:17:02 -0600 (not processed: message from valid local sender) X-MDRemoteIP: 64.199.139.122 X-Return-Path: jwest@ezwind.net X-MDaemon-Deliver-To: freebsd-xen@freebsd.org X-MDAV-Processed: gateway.ezwind.net, Wed, 06 Mar 2013 14:17:03 -0600 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 06 Mar 2013 20:17:29 -0000 1) One or two of our freebsd 9.1 HVM (with PVM drivers) under Xenserver 6.1 advanced are fairly frequently generating this message on the console: xn_txeof: WARNING: response is -1! Any ideas what this may be and what should be done? It does seem to only occur on the machines that have higher network load than the others. 2) We did a pilot project of about 8 VM's (the above mentioned environment) and all went well. Now that we've moved it into production with many more VM's, I'm wondering about recommended tuning. I seem to recall from watching this list that there are a few sysctl's and the like that are highly recommended, I think they had to do with network settings and turning off "offloading" or somesuch. Does anyone have a quick & dirty list of "here's the first things you should always change" with regards to FreeBSD HVM (pvm drivers) under XenServer? 3) When migrating bare-metal non-VM FreeBSD machines (primarily webservers and mailservers) to the above Xenserver environment, we have always just created VM's from an ISO, installed apache, sendmail, etc. and then migrated the websites, mailboxes, etc. manually "across the wire" from the non-VM machines to the replacement VM's. Xenconvert does not seem to support FreeBSD/gpart/ufs. Does anyone know of a way (software or procedure) to take a bare-metal FreeBSD 9.1 install and turn it into a VDI or OVF/OVA that can be imported to Xenserver? Thanks in advance for any tips, pointers, or insight! Jay West EZwind.net PO Box 460474 Saint Louis, MO 63146 Voice: (314) 262-4143 ext 1000 Toll Free: (866) 343-2589 Fax: (314) 558-9284 jwest@ezwind.net -------------------------------------------- This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. From owner-freebsd-xen@FreeBSD.ORG Wed Mar 6 20:36:27 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 83644FB7 for ; Wed, 6 Mar 2013 20:36:27 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 459206A4 for ; Wed, 6 Mar 2013 20:36:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:To:Content-Type; bh=Ke+yD/LdCCqlTKBmnODO79OOe+9anQsKXEW13Q8ys4c=; b=Yqvbu+iYuY0OdzA8xRm2g5dNsXD7m5ktR7V6cJdYWKQfQs+g18fggLpz8/Ta9i02cys7ktbVxOevTKLve4bnaYNRR8mCO76d0IjlIo6+kPmpCKAgoIky5pbj58PIat3J; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UDL4Y-0008Bp-88; Wed, 06 Mar 2013 14:36:23 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1362602176-61118-61116/5/2; Wed, 6 Mar 2013 20:36:16 +0000 Content-Type: text/plain; format=flowed; delsp=yes To: freebsd-xen@freebsd.org, Jay West Subject: Re: misc. questions References: <000901ce1aa7$90704320$b150c960$@ezwind.net> Date: Wed, 6 Mar 2013 14:36:16 -0600 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: <000901ce1aa7$90704320$b150c960$@ezwind.net> User-Agent: Opera Mail/12.14 (FreeBSD) X-SA-Report: ALL_TRUSTED=-1, KHOP_THREADED=-0.5 X-SA-Score: -1.5 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 06 Mar 2013 20:36:27 -0000 On Wed, 06 Mar 2013 14:17:02 -0600, Jay West wrote: > 1) One or two of our freebsd 9.1 HVM (with PVM drivers) under > Xenserver 6.1 advanced are fairly frequently generating this message on > the > console: xn_txeof: WARNING: response is -1! Any ideas what this may be > and > what should be done? It does seem to only occur on the machines that have > higher network load than the others. You're having success with Xenserver 6.1? That's good news. I wonder why XCP 1.6 is unable to boot FreeBSD if there's an emulated DVDROM? :( > 2) We did a pilot project of about 8 VM's (the above mentioned > environment) and all went well. Now that we've moved it into production > with > many more VM's, I'm wondering about recommended tuning. I seem to recall > from watching this list that there are a few sysctl's and the like that > are > highly recommended, I think they had to do with network settings and > turning > off "offloading" or somesuch. Does anyone have a quick & dirty list of > "here's the first things you should always change" with regards to > FreeBSD > HVM (pvm drivers) under XenServer? If you're using pf, you will certainly need to set net.inet.tcp.tso=0 As far as the other offloading -- I put this on my NICs: ifconfig_xn0="(your stuff here) -txcsum -rxcsum -lro -tso" > 3) When migrating bare-metal non-VM FreeBSD machines > (primarily > webservers and mailservers) to the above Xenserver environment, we have > always just created VM's from an ISO, installed apache, sendmail, etc. > and > then migrated the websites, mailboxes, etc. manually "across the wire" > from > the non-VM machines to the replacement VM's. Xenconvert does not seem to > support FreeBSD/gpart/ufs. Does anyone know of a way (software or > procedure) > to take a bare-metal FreeBSD 9.1 install and turn it into a VDI or > OVF/OVA > that can be imported to Xenserver? We usually install the same version on the VM and rsync the entire OS over. Then replace the kernel with the XENHVM one, do a bit of tweaking (rc.conf, pf.conf, fstab), and move on. FYI, when we build kernels we do: make buildkernel KERNCONF=XENHVM make installkernel KERNCONF=XENHVM DESTDIR=/boot/ KODIR=9.1-XENHVM This puts the kernel and modules in /boot/9.1-XENHVM and leaves the GENERIC kernel alone (as an emergency fallback) /boot/loader.conf then contains kernel="9.1-XENHVM" Note: for 9.0 it doesn't install the modules when you do it this way. We just set module_path="/boot/kernel;/boot/modules" and piggyback on the GENERIC kernel's modules. From owner-freebsd-xen@FreeBSD.ORG Wed Mar 6 22:41:30 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 28BF7BDF for ; Wed, 6 Mar 2013 22:41:30 +0000 (UTC) (envelope-from bounces+73574-0602-freebsd-xen=freebsd.org@sendgrid.me) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) by mx1.freebsd.org (Postfix) with SMTP id BBF85D8B for ; Wed, 6 Mar 2013 22:41:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpapi; bh=CsSxO3Y2wFaJaQXiwvZO5s P9i48=; b=wMBsNvMMGlkaYlNs8MMso6KsrCfkQmBF25igmReA4R+nfKGCHMHPV3 fnlKzdSo63cINZ+9h4d5VriRPVhVWj4N2h590Y+PnWj3pMNtUPIqsSEDacYjmukc 1++70fN+GeAVWZH+OHVHKcHa6N9hP8gB44EinEd+vviB6QpTCgPEw= Received: by 10.12.16.42 with SMTP id mf77.29463.5137C6178 Wed, 06 Mar 2013 16:41:27 -0600 (CST) Received: from mail.tarsnap.com (unknown [10.60.208.15]) by mi17 (SG) with ESMTP id 5137c617.6107.bef534 for ; Wed, 06 Mar 2013 16:41:27 -0600 (CST) Received: (qmail 16299 invoked from network); 6 Mar 2013 22:41:26 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 6 Mar 2013 22:41:26 -0000 Received: (qmail 3117 invoked from network); 6 Mar 2013 22:40:38 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 6 Mar 2013 22:40:38 -0000 Message-ID: <5137C5E6.2070802@freebsd.org> Date: Wed, 06 Mar 2013 14:40:38 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130131 Thunderbird/17.0.2 MIME-Version: 1.0 To: Jay West Subject: Re: misc. questions References: <000901ce1aa7$90704320$b150c960$@ezwind.net> In-Reply-To: <000901ce1aa7$90704320$b150c960$@ezwind.net> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Sendgrid-EID: RUbAm5H8PjswBj/QH+sYVehaJogg3iBnZcyVi1bw/Iyk0zImLtGyWkcNl/843m4YZPUzPxE6l/eh5fnFchOObhHMigd+QUc69nGFlDFN+EBqpwEzGrHPyGnGSRgQ4xHu Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 06 Mar 2013 22:41:30 -0000 On 03/06/13 12:17, Jay West wrote: > 1) One or two of our freebsd 9.1 HVM (with PVM drivers) under > Xenserver 6.1 advanced are fairly frequently generating this message on the > console: xn_txeof: WARNING: response is -1! Any ideas what this may be and > what should be done? It does seem to only occur on the machines that have > higher network load than the others. I see this on EC2 (running under HVM) as well. It doesn't seem to interfere with anything and only occurs occasionally (maybe five times per GB of network traffic?) so I haven't worried too much about it -- but if anyone has a clue about this I'd love to fix it from the "tidy up loose ends" perspective. > 2) We did a pilot project of about 8 VM's (the above mentioned > environment) and all went well. Now that we've moved it into production with > many more VM's, I'm wondering about recommended tuning. I seem to recall > from watching this list that there are a few sysctl's and the like that are > highly recommended, I think they had to do with network settings and turning > off "offloading" or somesuch. Does anyone have a quick & dirty list of > "here's the first things you should always change" with regards to FreeBSD > HVM (pvm drivers) under XenServer? You'll want to turn off tso, since it produces long mbuf chains which most xn netbacks choke on. (I have a very ugly workaround patch for this which I use on EC2, but simply turning off tso is enough unless you need Gbps+ speeds). There's a separate issue affecting pf+tso+xn (possibly pf+tso generally) which I haven't gotten around to tracking down. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-xen@FreeBSD.ORG Thu Mar 7 04:38:21 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0ADC1123 for ; Thu, 7 Mar 2013 04:38:21 +0000 (UTC) (envelope-from jwest@ezwind.net) Received: from ezwind.net (bobby.ezwind.net [199.188.211.146]) by mx1.freebsd.org (Postfix) with ESMTP id C8736E3D for ; Thu, 7 Mar 2013 04:38:20 +0000 (UTC) Received: from LENOVOD6B52A6B by ezwind.net (MDaemon.PRO.v8.1.3.R) with ESMTP id 04-md50000143020.msg for ; Wed, 06 Mar 2013 22:38:18 -0600 From: "Jay West" To: "'Mark Felder'" , References: <000901ce1aa7$90704320$b150c960$@ezwind.net> In-Reply-To: Subject: RE: misc. questions Date: Wed, 6 Mar 2013 22:38:19 -0600 Message-ID: <000601ce1aed$97e06540$c7a12fc0$@ezwind.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKL4ehw6L2D+tg443ETJqm5K2YJBgFv1UkzlxKUNjA= Content-Language: en-us X-Authenticated-Sender: jwest@ezwind.net X-Spam-Processed: gateway.ezwind.net, Wed, 06 Mar 2013 22:38:18 -0600 (not processed: message from valid local sender) X-MDRemoteIP: 71.14.76.0 X-Return-Path: jwest@ezwind.net X-MDaemon-Deliver-To: freebsd-xen@freebsd.org X-MDAV-Processed: gateway.ezwind.net, Wed, 06 Mar 2013 22:38:19 -0600 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 07 Mar 2013 04:38:21 -0000 Mark wrote... > You're having success with Xenserver 6.1? That's good news. I wonder why XCP 1.6 is unable to boot FreeBSD if there's an emulated DVDROM? :( Yes. Stock install 64bit 9.1-R as HVM, recompile kernel using supplied XENHVM config file. Then there's a few things to tweak before rebooting, one is fstab because of the different naming convention for disk devices or you choke on reboot after install (you can still do it after by entering correct device in boot string). The other is the cd drive, you have to remove the cd device (see http://support.citrix.com/article/CTX132411). There may be another step I'm forgetting, but that's the basic gist. Oh, and fix rc.conf to use the xen (xn0) network device. We are still having one really nagging issue - timekeeping. The clocks are way off and fluctuate wildly. FreeBSD is selecting the clock source (from several possibilities) that already has the highest stability rating, so I haven't tried setting the sysctl to use a different clock source. I see no way to fix this and it's pretty crippling in my environment anyways. Anyone have a fix for that? >If you're using pf, you will certainly need to set net.inet.tcp.tso=0 By pf I assume you mean the freebsd firewall? We don't use that, all the firewall stuff is via a frontend pfsense install (non-vm), so I assume the above setting isn't required? >As far as the other offloading -- I put this on my NICs: >ifconfig_xn0="(your stuff here) -txcsum -rxcsum -lro -tso" Ah, good to know. Thanks! >We usually install the same version on the VM and rsync the entire OS over. Then replace the kernel with the XENHVM one, do a bit of tweaking (rc.conf, pf.conf, fstab), and move on. The "best" way I found to do this (WRT speed & functionality) was to just use "dump" on the old machine, create the vm, then use "restore". That being said, I can understand the commercial citrix xenserver being slow to implement "XenConvert" on freebsd... but I'm surprised that the open source Xen doesn't have a tool that turns a bare metal freebsd install into an OVF/VDI file. Surely someone is working on this. Fortunately, all our freebsd boxes are now virtualized, but I'm sure others are wanting "XenConvert" to work on FreeBSD. Thanks a ton for the input folks! Jay From owner-freebsd-xen@FreeBSD.ORG Thu Mar 7 05:06:02 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 281E45DA for ; Thu, 7 Mar 2013 05:06:02 +0000 (UTC) (envelope-from koukoukachu@gmail.com) Received: from mail-qe0-f46.google.com (mail-qe0-f46.google.com [209.85.128.46]) by mx1.freebsd.org (Postfix) with ESMTP id AD89AEFE for ; Thu, 7 Mar 2013 05:06:01 +0000 (UTC) Received: by mail-qe0-f46.google.com with SMTP id a11so45437qen.5 for ; Wed, 06 Mar 2013 21:06:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=GQ7KAhbemT+gO/w+WPo7ySZxMxWX0qgLaHTxbtoTVDw=; b=de1S8ZOxYvvhrjhAdWhJy+IzLxCmBC7yQCAz9wWqpEnPvBs81fVGS6LWUvkhjU7Y2g +hzaT5JRtd51uKwzo1e3aBp+LBFYW8DDW1sVDU4w1BsXwFm8rsqh+s++tS8uc4gebPyV H2JtAgBlFG7rtotHEqfJF5c8tTHp5LNoG6g2SI5wFkHWEJgLE7DKHEAW8/JuS8QqAuqh js9p9mU1EnP+B/ebq8YuGKTVrAtuWax86DVY0gbmBeqJhCZbDTyOwI5Jf1jt07QBe10I uCxgyLhBR6Qtv0gVCETop0wWq/N/snhbcqq/akbtsB7JAuOKz6T1FKovf3cfz909yObm Vz0g== X-Received: by 10.229.176.16 with SMTP id bc16mr10930483qcb.43.1362632355872; Wed, 06 Mar 2013 20:59:15 -0800 (PST) Received: from Hephaestus ([74.61.237.229]) by mx.google.com with ESMTPS id o5sm1030724qao.12.2013.03.06.20.59.13 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 06 Mar 2013 20:59:14 -0800 (PST) From: "Chris Bachmann" To: "'Jay West'" , "'Mark Felder'" , References: <000901ce1aa7$90704320$b150c960$@ezwind.net> <000601ce1aed$97e06540$c7a12fc0$@ezwind.net> In-Reply-To: <000601ce1aed$97e06540$c7a12fc0$@ezwind.net> Subject: RE: misc. questions Date: Wed, 6 Mar 2013 23:59:11 -0500 Message-ID: <037601ce1af0$83be19b0$8b3a4d10$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-index: AQKL4ehw6L2D+tg443ETJqm5K2YJBgFv1UkzAhkruCSXAdQ+0A== Content-Language: en-us X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 07 Mar 2013 05:06:02 -0000 I haven't seen any solutions to the time problems. I have a ton of debian vm clients as well and they have the same issue. I've just gotten used to installing ntp to keep the clocks current. -----Original Message----- From: owner-freebsd-xen@freebsd.org [mailto:owner-freebsd-xen@freebsd.org] On Behalf Of Jay West Sent: Wednesday, March 06, 2013 11:38 PM To: 'Mark Felder'; freebsd-xen@freebsd.org Subject: RE: misc. questions Mark wrote... > You're having success with Xenserver 6.1? That's good news. I wonder > why XCP 1.6 is unable to boot FreeBSD if there's an emulated DVDROM? :( Yes. Stock install 64bit 9.1-R as HVM, recompile kernel using supplied XENHVM config file. Then there's a few things to tweak before rebooting, one is fstab because of the different naming convention for disk devices or you choke on reboot after install (you can still do it after by entering correct device in boot string). The other is the cd drive, you have to remove the cd device (see http://support.citrix.com/article/CTX132411). There may be another step I'm forgetting, but that's the basic gist. Oh, and fix rc.conf to use the xen (xn0) network device. We are still having one really nagging issue - timekeeping. The clocks are way off and fluctuate wildly. FreeBSD is selecting the clock source (from several possibilities) that already has the highest stability rating, so I haven't tried setting the sysctl to use a different clock source. I see no way to fix this and it's pretty crippling in my environment anyways. Anyone have a fix for that? >If you're using pf, you will certainly need to set net.inet.tcp.tso=0 By pf I assume you mean the freebsd firewall? We don't use that, all the firewall stuff is via a frontend pfsense install (non-vm), so I assume the above setting isn't required? >As far as the other offloading -- I put this on my NICs: >ifconfig_xn0="(your stuff here) -txcsum -rxcsum -lro -tso" Ah, good to know. Thanks! >We usually install the same version on the VM and rsync the entire OS over. Then replace the kernel with the XENHVM one, do a bit of tweaking (rc.conf, pf.conf, fstab), and move on. The "best" way I found to do this (WRT speed & functionality) was to just use "dump" on the old machine, create the vm, then use "restore". That being said, I can understand the commercial citrix xenserver being slow to implement "XenConvert" on freebsd... but I'm surprised that the open source Xen doesn't have a tool that turns a bare metal freebsd install into an OVF/VDI file. Surely someone is working on this. Fortunately, all our freebsd boxes are now virtualized, but I'm sure others are wanting "XenConvert" to work on FreeBSD. Thanks a ton for the input folks! Jay _______________________________________________ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" From owner-freebsd-xen@FreeBSD.ORG Thu Mar 7 08:38:19 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E7FE046E for ; Thu, 7 Mar 2013 08:38:19 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 8FB15A7D for ; Thu, 7 Mar 2013 08:38:19 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,800,1355097600"; d="scan'208";a="2268449" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Mar 2013 08:38:06 +0000 Received: from [192.168.1.30] (10.30.249.242) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.297.1; Thu, 7 Mar 2013 08:38:05 +0000 Message-ID: <513851F1.8080009@citrix.com> Date: Thu, 7 Mar 2013 09:38:09 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: Jay West Subject: Re: misc. questions References: <000901ce1aa7$90704320$b150c960$@ezwind.net> <000601ce1aed$97e06540$c7a12fc0$@ezwind.net> In-Reply-To: <000601ce1aed$97e06540$c7a12fc0$@ezwind.net> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 07 Mar 2013 08:38:20 -0000 On 07/03/13 05:38, Jay West wrote: > Mark wrote... >> You're having success with Xenserver 6.1? That's good news. I wonder why > XCP 1.6 is unable to boot FreeBSD if there's an emulated DVDROM? :( > > Yes. Stock install 64bit 9.1-R as HVM, recompile kernel using supplied > XENHVM config file. Then there's a few things to tweak before rebooting, one > is fstab because of the different naming convention for disk devices or you > choke on reboot after install (you can still do it after by entering correct > device in boot string). The other is the cd drive, you have to remove the cd > device (see http://support.citrix.com/article/CTX132411). There may be > another step I'm forgetting, but that's the basic gist. Oh, and fix rc.conf > to use the xen (xn0) network device. We are still having one really nagging > issue - timekeeping. The clocks are way off and fluctuate wildly. FreeBSD is > selecting the clock source (from several possibilities) that already has the > highest stability rating, so I haven't tried setting the sysctl to use a > different clock source. I see no way to fix this and it's pretty crippling > in my environment anyways. Anyone have a fix for that? I think there were several fixes for the RTC clock recently, so trying the Xen 4.2 branch might bring some improvements. Also, it is possible to use the PV clock from HVM (PVHVM) domains, which will probably bring better stability. I'm going to look into this when I have some spare cycles. From owner-freebsd-xen@FreeBSD.ORG Thu Mar 7 12:35:24 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B31C9F57; Thu, 7 Mar 2013 12:35:24 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 10302787; Thu, 7 Mar 2013 12:35:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:Cc:To:Content-Type; bh=Fl8Q4h+zxZ1ejCq1nI7Jbp4bUas6JzJ/aUAN3JhIk5Y=; b=ZNq7mdwG1AdlggdS1aSWHwp82q6HiwT7R+rar06diXx2kz1Se63Wu2oxfRWc/6FaBSfXgcil6jrmhyjgtXUeBX2I/YtNWqYvvWOJePzIE8uUWRYf6SCawLbQEF0xHu9B; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UDa2b-0000La-1l; Thu, 07 Mar 2013 06:35:21 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1362659710-61118-61116/5/3; Thu, 7 Mar 2013 12:35:10 +0000 Content-Type: text/plain; format=flowed; delsp=yes To: Jay West , Colin Percival Subject: Re: misc. questions References: <000901ce1aa7$90704320$b150c960$@ezwind.net> <5137C5E6.2070802@freebsd.org> Date: Thu, 7 Mar 2013 06:35:10 -0600 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: <5137C5E6.2070802@freebsd.org> User-Agent: Opera Mail/12.14 (FreeBSD) X-SA-Report: ALL_TRUSTED=-1, KHOP_THREADED=-0.5 X-SA-Score: -1.5 Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 07 Mar 2013 12:35:24 -0000 On Wed, 06 Mar 2013 16:40:38 -0600, Colin Percival wrote: > You'll want to turn off tso, since it produces long mbuf chains which > most > xn netbacks choke on. (I have a very ugly workaround patch for this > which I > use on EC2, but simply turning off tso is enough unless you need Gbps+ > speeds). Can you link me to this patch? I have an environment that might warrant using it for now. Thanks! From owner-freebsd-xen@FreeBSD.ORG Thu Mar 7 12:42:56 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 52C2B125 for ; Thu, 7 Mar 2013 12:42:56 +0000 (UTC) (envelope-from bounces+73574-0602-freebsd-xen=freebsd.org@sendgrid.me) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) by mx1.freebsd.org (Postfix) with SMTP id EC6177CA for ; Thu, 7 Mar 2013 12:42:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from :mime-version:to:cc:subject:references:in-reply-to:content-type; s=smtpapi; bh=yyW+lyLw3rs13AMwk5hoXERmzRM=; b=f8SZma2PEcCHYD0e2 LsnTfQQhLuu4N37WcQxY6Wt62T40CdsG39WjcB8Eyny3yVbY9q2J9Q20BgjP19j4 ptMUY80WUllsd4QyxkSRe05qJCQz6QcBeD9AXmDBqwsQ+dsuASDef5Gis4kt8Sc8 A00U6i7Nom8JSzKtuh2Q/w9boo= Received: by 10.4.35.240 with SMTP id mf66.16374.51388B491 Thu, 07 Mar 2013 06:42:49 -0600 (CST) Received: from mail.tarsnap.com (unknown [10.60.208.13]) by mi15 (SG) with ESMTP id 51388b49.37d6.188dad1 for ; Thu, 07 Mar 2013 06:42:49 -0600 (CST) Received: (qmail 46775 invoked from network); 7 Mar 2013 12:42:48 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 7 Mar 2013 12:42:48 -0000 Received: (qmail 34920 invoked from network); 7 Mar 2013 12:41:57 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 7 Mar 2013 12:41:57 -0000 Message-ID: <51388B15.1060105@freebsd.org> Date: Thu, 07 Mar 2013 04:41:57 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130131 Thunderbird/17.0.2 MIME-Version: 1.0 To: Mark Felder Subject: Re: misc. questions References: <000901ce1aa7$90704320$b150c960$@ezwind.net> <5137C5E6.2070802@freebsd.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: multipart/mixed; boundary="------------020105010609080700090803" X-Sendgrid-EID: RUbAm5H8PjswBj/QH+sYVehaJogg3iBnZcyVi1bw/IzwwHsH9R1DI2ZrN2/OCZrbpeFjGLcQeytHwJz4DoEsfc6qmJdUUxKB52PEn86S3XgK0agFtMa2R21d8azUAPWR Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 07 Mar 2013 12:42:56 -0000 This is a multi-part message in MIME format. --------------020105010609080700090803 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 03/07/13 04:35, Mark Felder wrote: > On Wed, 06 Mar 2013 16:40:38 -0600, Colin Percival wrote: >> You'll want to turn off tso, since it produces long mbuf chains which most >> xn netbacks choke on. (I have a very ugly workaround patch for this which I >> use on EC2, but simply turning off tso is enough unless you need Gbps+ speeds). > > Can you link me to this patch? I have an environment that might warrant using it > for now. Attached. And remember that I said it was a *very ugly* workaround... :-) -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid --------------020105010609080700090803 Content-Type: text/plain; charset=us-ascii; name="tcp_mbuf_chain_limit.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="tcp_mbuf_chain_limit.patch" --- sys/kern/uipc_mbuf.c (revision 223824) +++ sys/kern/uipc_mbuf.c (working copy) @@ -525,12 +525,14 @@ * only their reference counts are incremented. */ struct mbuf * -m_copym(struct mbuf *m, int off0, int len, int wait) +m_copy_nbufs(struct mbuf *m, int off0, int len, int wait, long * outlen, + int nbufmax) { struct mbuf *n, **np; int off = off0; struct mbuf *top; int copyhdr = 0; + int len_orig = len; KASSERT(off >= 0, ("m_copym, negative off %d", off)); KASSERT(len >= 0, ("m_copym, negative len %d", len)); @@ -546,7 +548,7 @@ } np = ⊤ top = 0; - while (len > 0) { + while (len > 0 && nbufmax-- > 0) { if (m == NULL) { KASSERT(len == M_COPYALL, ("m_copym, length > size of mbuf chain")); @@ -584,6 +586,9 @@ if (top == NULL) mbstat.m_mcfail++; /* XXX: No consistency. */ + if (outlen) + *outlen = len_orig - len; + return (top); nospace: m_freem(top); @@ -591,6 +596,13 @@ return (NULL); } +struct mbuf * +m_copym(struct mbuf *m, int off0, int len, int wait) +{ + + return (m_copy_nbufs(m, off0, len, wait, NULL, INT_MAX)); +} + /* * Returns mbuf chain with new head for the prepending case. * Copies from mbuf (chain) n from off for len to mbuf (chain) m --- sys/netinet/tcp_output.c (revision 228872) +++ sys/netinet/tcp_output.c (working copy) @@ -183,6 +183,7 @@ int sack_rxmit, sack_bytes_rxmt; struct sackhole *p; int tso; + int max_mbuf_chain_len = 16; /* XXX Set this based on interface? */ struct tcpopt to; #if 0 int maxburst = TCP_MAXBURST; @@ -806,16 +807,6 @@ struct mbuf *mb; u_int moff; - if ((tp->t_flags & TF_FORCEDATA) && len == 1) - TCPSTAT_INC(tcps_sndprobe); - else if (SEQ_LT(tp->snd_nxt, tp->snd_max) || sack_rxmit) { - tp->t_sndrexmitpack++; - TCPSTAT_INC(tcps_sndrexmitpack); - TCPSTAT_ADD(tcps_sndrexmitbyte, len); - } else { - TCPSTAT_INC(tcps_sndpack); - TCPSTAT_ADD(tcps_sndbyte, len); - } MGETHDR(m, M_DONTWAIT, MT_DATA); if (m == NULL) { SOCKBUF_UNLOCK(&so->so_snd); @@ -847,7 +838,8 @@ mtod(m, caddr_t) + hdrlen); m->m_len += len; } else { - m->m_next = m_copy(mb, moff, (int)len); + m->m_next = m_copy_nbufs(mb, moff, len, M_DONTWAIT, + &len, max_mbuf_chain_len); if (m->m_next == NULL) { SOCKBUF_UNLOCK(&so->so_snd); (void) m_free(m); @@ -856,6 +848,18 @@ } } + /* Update stats here as m_copy_nbufs may have adjusted len. */ + if ((tp->t_flags & TF_FORCEDATA) && len == 1) + TCPSTAT_INC(tcps_sndprobe); + else if (SEQ_LT(tp->snd_nxt, tp->snd_max) || sack_rxmit) { + tp->t_sndrexmitpack++; + TCPSTAT_INC(tcps_sndrexmitpack); + TCPSTAT_ADD(tcps_sndrexmitbyte, len); + } else { + TCPSTAT_INC(tcps_sndpack); + TCPSTAT_ADD(tcps_sndbyte, len); + } + /* * If we're sending everything we've got, set PUSH. * (This will keep happy those implementations which only --- sys/sys/mbuf.h (revision 223824) +++ sys/sys/mbuf.h (working copy) @@ -849,6 +849,7 @@ int, int, int, int); struct mbuf *m_copypacket(struct mbuf *, int); void m_copy_pkthdr(struct mbuf *, struct mbuf *); +struct mbuf *m_copy_nbufs(struct mbuf *, int, int, int, long *, int); struct mbuf *m_copyup(struct mbuf *n, int len, int dstoff); struct mbuf *m_defrag(struct mbuf *, int); void m_demote(struct mbuf *, int); --------------020105010609080700090803-- From owner-freebsd-xen@FreeBSD.ORG Thu Mar 7 14:00:33 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 86E87CD0 for ; Thu, 7 Mar 2013 14:00:33 +0000 (UTC) (envelope-from jwest@ezwind.net) Received: from ezwind.net (bobby.ezwind.net [199.188.211.146]) by mx1.freebsd.org (Postfix) with ESMTP id 56F63BD7 for ; Thu, 7 Mar 2013 14:00:32 +0000 (UTC) Received: from LENOVOD6B52A6B by ezwind.net (MDaemon.PRO.v8.1.3.R) with ESMTP id 14-md50000143000.msg for ; Thu, 07 Mar 2013 08:00:30 -0600 From: "Jay West" To: =?iso-8859-1?Q?'Roger_Pau_Monn=E9'?= References: <000901ce1aa7$90704320$b150c960$@ezwind.net> <000601ce1aed$97e06540$c7a12fc0$@ezwind.net> <513851F1.8080009@citrix.com> In-Reply-To: <513851F1.8080009@citrix.com> Subject: RE: misc. questions Date: Thu, 7 Mar 2013 08:00:32 -0600 Message-ID: <000801ce1b3c$223a5900$66af0b00$@ezwind.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-index: AQKL4ehw6L2D+tg443ETJqm5K2YJBgFv1UkzAhkruCQCFALI1pbxy/Qw Content-Language: en-us X-Authenticated-Sender: jwest@ezwind.net X-Spam-Processed: gateway.ezwind.net, Thu, 07 Mar 2013 08:00:30 -0600 (not processed: message from valid local sender) X-MDRemoteIP: 71.14.76.0 X-Return-Path: jwest@ezwind.net X-MDaemon-Deliver-To: freebsd-xen@freebsd.org X-MDAV-Processed: gateway.ezwind.net, Thu, 07 Mar 2013 08:00:31 -0600 Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 07 Mar 2013 14:00:33 -0000 It was written.... >I think there were several fixes for the RTC clock recently, so trying the Xen 4.2 branch might bring some improvements. I'm using Citrix Xenserver 6.1, so stuff from the Xen 4.2 branch isn't available for me.... >Also, it is possible to use the PV clock from HVM (PVHVM) domains, which will probably bring better stability. I'm going to look into this when I have some spare cycles. That I would very much like to know how to do so that I can give it a shot. J