From owner-svn-doc-all@freebsd.org Mon Feb 11 18:34:33 2019 Return-Path: Delivered-To: svn-doc-all@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 87A4714E0249; Mon, 11 Feb 2019 18:34:33 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B1F083D17; Mon, 11 Feb 2019 18:34:33 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1F22B3E96; Mon, 11 Feb 2019 18:34:33 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x1BIYXOb036102; Mon, 11 Feb 2019 18:34:33 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x1BIYXFQ036101; Mon, 11 Feb 2019 18:34:33 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201902111834.x1BIYXFQ036101@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Mon, 11 Feb 2019 18:34:32 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52814 - head/en_US.ISO8859-1/books/handbook/virtualization X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/handbook/virtualization X-SVN-Commit-Revision: 52814 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 2B1F083D17 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.94 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; NEURAL_HAM_SHORT(-0.95)[-0.948,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2019 18:34:33 -0000 Author: bcr Date: Mon Feb 11 18:34:32 2019 New Revision: 52814 URL: https://svnweb.freebsd.org/changeset/doc/52814 Log: Add a troubleshooting section to the Xen chapter. In the discussion leading up to r52813, rgrimes@ suggested to add a troubleshooting section to the Xen chapter to help with debugging issues. In particular, users should know where Xen 4.11 and higher logs important information relevant for debugging. There are also a couple of options that increase the verbosity of the dom0 and enable iommu debugging. These were divided up into two subsections: one for the host and the other for the guest. Thanks go out to royger@ for providing the information and putting together a documentation patch before I could. Suggested by: rgrimes Patch by: royger Approved by: bcr Differential Revision: https://reviews.freebsd.org/D19107 Modified: head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml Mon Feb 11 18:15:48 2019 (r52813) +++ head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml Mon Feb 11 18:34:32 2019 (r52814) @@ -1719,5 +1719,107 @@ freebsd 1 1024 the operating system has been installed and can be used as a virtual machine. + + + Troubleshooting + + This section contains basic information in order to help + troubleshoot issues found when using &os; as a &xen; host or + guest. + + + Host Boot Troubleshooting + + Please note that the following troubleshooting tips + are intended for &xen; 4.11 or newer. If you are still + using &xen; 4.7 and having issues consider migrating to + a newer version of &xen;. + + In order to troubleshoot host boot issues you will + likely need a serial cable, or a debug USB cable. Verbose + &xen; boot output can be obtained by adding options to the + xen_cmdline option found in + loader.conf. A couple of relevant + debug options are: + + + + iommu=debug: can be used to print + additional diagnostic information about the + iommu. + + + dom0=verbose: can be used to + print additional diagnostic information about the + dom0 build process. + + + sync_console: flag to force + synchronous console output. Useful for debugging to + avoid losing messages due to rate limiting. + Never use this option in production environments since + it can allow malicious guests to perform DoS attacks + against &xen; using the console. + + + + &os; should also be booted in verbose mode in order + to identify any issues. To activate verbose booting, run + this command: + + &prompt.root; sysrc -f /boot/loader.conf boot_verbose="YES" + + If none of these options help solving the problem, + please send the serial boot log to + freebsd-xen@FreeBSD.org and + xen-devel@lists.xenproject.org + for further analysis. + + + + Guest Creation Troubleshooting + + Issues can also arise when creating guests, the + following attempts to provide some help for those trying + to diagnose guest creation issues. + + The most common cause of guest creation failures is the + xl command spitting some error and + exiting with a return code different than 0. If the error + provided is not enough to help identify the issue, more + verbose output can also be obtained from + xl by using the v + option repeatedly. + + &prompt.root; xl -vvv create freebsd.cfg +Parsing config from freebsd.cfg +libxl: debug: libxl_create.c:1693:do_domain_create: Domain 0:ao 0x800d750a0: create: how=0x0 callback=0x0 poller=0x800d6f0f0 +libxl: debug: libxl_device.c:397:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=unknown +libxl: debug: libxl_device.c:432:libxl__device_disk_set_backend: Disk vdev=xvda, using backend phy +libxl: debug: libxl_create.c:1018:initiate_domain_create: Domain 1:running bootloader +libxl: debug: libxl_bootloader.c:328:libxl__bootloader_run: Domain 1:not a PV/PVH domain, skipping bootloader +libxl: debug: libxl_event.c:689:libxl__ev_xswatch_deregister: watch w=0x800d96b98: deregister unregistered +domainbuilder: detail: xc_dom_allocate: cmdline="", features="" +domainbuilder: detail: xc_dom_kernel_file: filename="/usr/local/lib/xen/boot/hvmloader" +domainbuilder: detail: xc_dom_malloc_filemap : 326 kB +libxl: debug: libxl_dom.c:988:libxl__load_hvm_firmware_module: Loading BIOS: /usr/local/share/seabios/bios.bin +... + + If the verbose output does not help diagnose the issue + there are also QEMU and &xen; toolstack logs in + /var/log/xen. Note that the name of + the domain is appended to the log name, so if the domain + is named freebsd you should find a + /var/log/xen/xl-freebsd.log and likely + a /var/log/xen/qemu-dm-freebsd.log. + Both log files can contain useful information for debugging. + If none of this helps solve the issue, please send the + description of the issue you are facing and as much + information as possible to + freebsd-xen@FreeBSD.org and + xen-devel@lists.xenproject.org in order to + get help. + +