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.