Index: head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml =================================================================== --- head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml +++ head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml @@ -1719,5 +1719,107 @@ 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. + +