From owner-freebsd-xen@freebsd.org Thu Feb 7 11:48:24 2019 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADD5E14D6AAA for ; Thu, 7 Feb 2019 11:48:24 +0000 (UTC) (envelope-from prvs=934266883=roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.ctxuk.citrix.com [185.25.65.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.citrix.com", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B7E2585EC4; Thu, 7 Feb 2019 11:48:23 +0000 (UTC) (envelope-from prvs=934266883=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.58,343,1544486400"; d="scan'208";a="85634103" Date: Thu, 7 Feb 2019 12:48:19 +0100 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: "Rodney W. Grimes" CC: Benedict Reuschling , Subject: Re: Extend documentation (was: Re: Issue getting my first Xen domU up) Message-ID: <20190207114819.uvidsagdiqpwfna2@mac> References: <20190206171713.asav4wlhkce2m5wq@mac> <201902061739.x16Hdls7046743@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <201902061739.x16Hdls7046743@pdx.rh.CN85.dnsmgr.net> User-Agent: NeoMutt/20180716 X-ClientProxiedBy: AMSPEX02CAS02.citrite.net (10.69.22.113) To AMSPEX02CL02.citrite.net (10.69.22.126) X-Rspamd-Queue-Id: B7E2585EC4 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of prvs=934266883=roger.pau@citrix.com designates 185.25.65.24 as permitted sender) smtp.mailfrom=prvs=934266883=roger.pau@citrix.com X-Spamd-Result: default: False [-2.41 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.978,0]; NEURAL_HAM_LONG(-0.97)[-0.968,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; ENVFROM_PRVS(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[citrix.com]; TO_DN_SOME(0.00)[]; FORGED_SENDER_VERP_SRS(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[24.65.25.185.list.dnswl.org : 127.0.9.2]; MX_GOOD(-0.01)[cached: smtp.citrix.com.au]; NEURAL_HAM_SHORT(-0.43)[-0.434,0]; IP_SCORE(-0.02)[country: GB(-0.09)]; FORGED_SENDER(0.00)[roger.pau@citrix.com,prvs=934266883=roger.pau@citrix.com]; RCVD_COUNT_ZERO(0.00)[0]; R_DKIM_NA(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:60825, ipnet:185.25.64.0/23, country:GB]; FROM_NEQ_ENVFROM(0.00)[roger.pau@citrix.com,prvs=934266883=roger.pau@citrix.com]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.29 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 Feb 2019 11:48:24 -0000 On Wed, Feb 06, 2019 at 09:39:47AM -0800, Rodney W. Grimes wrote: > > Adding Benedict who wrote the Xen handbook documentation, and > > hopefully would be able to fix it :). > > > > On Tue, Feb 05, 2019 at 08:18:05PM +0000, Marcin Cieslak wrote: > > > On Tue, 5 Feb 2019, Eric Bautsch wrote: > > > > > > > And yes, the qemu-dm-titania.log would have been the place to look. I feel > > > > pretty stupid. It says: > > > > > > Don't feel stupid. I am using Xen with Dom0 on FreeBSD for months now > > > and I didn't know where the qemu logs go - I was able to figure out > > > the problem by staring at the configuration file for a long time. > > > > > > Therefore your question was very helpful also for me - thanks! > > > > It seems there's one piece missing in the handbook which I didn't > > realize, the if_tap module needs to be loaded for QEMU to work. > > > > I suggest the following is added to the handbook: > > > > ``` > > sysrc -f /boot/loader.conf if_tap_load="YES" > > ``` > > > > And then I've also realized the following line: > > > > ``` > > sysrc -f /boot/loader.conf hw.pci.mcfg=0 > > ``` > > > > Is only needed for Xen 4.7, but not for Xen 4.11. > > > > Finally it might be interesting to add a reference to the location of > > the Xen logs. This should likely be added at the end of the document, > > I think something along the lines of: > > > > ``` > > Xen toolstack related logs can be found at /var/log/xen/ be sure to > > check the contents of that directory if experiencing issues. > > ``` > > Is there a troubleshooting section in the handbook? > If not there should be, and this would defanitly be mentioned > in that section. There doesn't seem to be a virtualization troubleshooting section I'm afraid. I've added something similar to my suggestion above as a tip, which will make it more visible. Thanks, Roger.