From owner-freebsd-xen@freebsd.org Tue Jan 19 14:06:59 2021 Return-Path: Delivered-To: freebsd-xen@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 050B44F4D79 for ; Tue, 19 Jan 2021 14:06:59 +0000 (UTC) (envelope-from royger@gmail.com) Received: from mail-ot1-f41.google.com (mail-ot1-f41.google.com [209.85.210.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKr7P71ndz3kq9 for ; Tue, 19 Jan 2021 14:06:57 +0000 (UTC) (envelope-from royger@gmail.com) Received: by mail-ot1-f41.google.com with SMTP id v1so1787533ott.10 for ; Tue, 19 Jan 2021 06:06:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=9p7389J7gTKP+8UisVt49lhYfd2IgB+AiShGBXKxbww=; b=Iam9gJEd5iuoqaxtetMRuxj+4xaORViDnfxMODUG1ZzhrN5lkydrVbgXIf+u6lrnsl dudP5jnRKOLotygWxfNdTNifl1aQAfYJXn5nhB1QqxnfCmhFGSBgqAk+Nz5VjoE7fsNi Joxyqa4LtrXAM5q2fnSG5J3LF8/igFVa4RYO0pv2sauF5QKtM6HAhImQ2D+we9OZbhXg JpNV4sXEq+plsO7oTStD/gX/llbfkHZGq4SimB+MkDkZ4q0v04yFo3T+ggO3UNdR7dFv KJW2Xn2lVkrNhhfPqSi2FqRMZP3Bo3gVBfYiwLVhb0Fe+EziJEYCYuO/zIQpYKrL1qPF 3+Jw== X-Gm-Message-State: AOAM531IdRfOF2dN7ynzQ8ViCdQc1cg6TP6xuHf4gJZmJl1bbUqlV1uQ dJ336hBOBTJKLJ2Bgne4duLmtZe+dLqqY9qBWYASKDLzu3w= X-Google-Smtp-Source: ABdhPJwPjCtrH1484amhI5d86wVqKKM8kMboI/sCYkN++qRak/NMRrDH1pz7dug+iGgtBywxoZkUlPkkpxoikqCQLII= X-Received: by 2002:a9d:c66:: with SMTP id 93mr3470210otr.289.1611065216902; Tue, 19 Jan 2021 06:06:56 -0800 (PST) MIME-Version: 1.0 References: <5536984.Zv9zXsTiuT@freebsd-current> In-Reply-To: <5536984.Zv9zXsTiuT@freebsd-current> From: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Date: Tue, 19 Jan 2021 15:06:45 +0100 Message-ID: Subject: Re: Re: either xen or custom To: "Lizbeth Mutterhunt, PhD" Cc: freebsd-xen@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4DKr7P71ndz3kq9 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of royger@gmail.com designates 209.85.210.41 as permitted sender) smtp.mailfrom=royger@gmail.com X-Spamd-Result: default: False [-2.44 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; RWL_MAILSPIKE_GOOD(0.00)[209.85.210.41:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_TO(0.00)[gmail.com]; FORGED_SENDER(0.30)[royger@freebsd.org,royger@gmail.com]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; R_MIXED_CHARSET(0.56)[subject]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[royger@freebsd.org,royger@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.210.41:from]; FREEFALL_USER(0.00)[royger]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-xen@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; SPAMHAUS_ZRD(0.00)[209.85.210.41:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.210.41:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-xen] X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.34 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: Tue, 19 Jan 2021 14:06:59 -0000 On Fri, Jan 15, 2021 at 3:46 PM Lizbeth Mutterhunt, PhD wrote: > > Op Donnerstag, 14. J=C3=A4nner 2021 09:21:09 CET schreef u: > > On Sun, Dec 13, 2020 at 12:11:40AM +0100, lizbethmutterhunt@gmail.com w= rote: > > > to make a long story short: either I get a lock (hard to avoid, not t= o be > > > unlimited with ulimit -l unlimited) or a boot of xen and a blank scre= en > > > with reboot after a 10 seconds with vga=3Dcurrent. > > > > Hello, > Hello Roger, > > > Sorry for the delay on the reply. I'm afraid I will need more info in > > order to help diagnose your issue. > no matter, was occupied other ways; using VirtualBox at the moment, slow = and > the hypervisor tends to make long waiting-times... > > > How do you get the lock that you mention? Is it booting Xen, or just > > plain FreeBSD? > It's booting XEN, but not the CURRENT-kernel afterwards or it boots the > CURRENT but not xen. I have in /boot/loader.conf > > xen_kernel=3D"/boot/xen" > xen_cmdline=3D"dom0_mem=3D4048M dom0_max_vcpus=3D4 dom0=3Dpvh com1=3D1152= 00,8n1 > guest_loglvl=3Dall loglvl=3Dall" > iommu=3D"force,no-intremap" The iommu=3D... option should either be inside the xen_cmdline or removed, it's not an option of loader.conf. > if_tap_load=3D"YES" > console=3Dvga,com1 console=3D should also be inside the xen_cmdline=3D option, not here as a separate line here. Your xen_cmdline should be: xen_cmdline=3D"dom0_mem=3D4048M dom0_max_vcpus=3D4 dom0=3Dpvh com1=3D115200= ,8n1 guest_loglvl=3Dall loglvl=3Dall console=3Dvga,com1 noreboot" Note it's all a single line. > boot_multicons=3D"YES" > boot_serial=3D"YES" > console=3D"comconsole,vidconsole" > vmm_load=3D"YES" > vga=3Dcurrent > > and in /etc/rc.conf: > > xencommons_enable=3D"YES" > cloned_interfaces=3D"bridge0" > ifconfig_bridge0=3D"addm bge0 SYNCDHCP" > ifconfig_bge0=3D"up" > > sudo ulimit -l > unlimited > > sudo uname -a > FreeBSD freeBSD-CURRENT 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r368997: Tue= Jan > 12 13:46:33 CET 2021 lizbeth@freeBSD-CURRENT:/usr/obj/usr/src/amd64.a= md64/ > sys/LIZBETH amd64 > > it's a no-debug kernel! > > /etc/ttys > xc0 "/usr/libexec/getty Pc" xterm on secure > > > when booting without XEN I get the following with 'xl dmesg' > > xencall: error: Could not obtain handle on privileged command interface /= dev/ > xen/privcmd: No such file or directory > libxl: error: libxl.c:102:libxl_ctx_alloc: cannot open libxc handle: No s= uch > file or directory > cannot init xl context Right, without booting as Xen dom0 /dev/xen/privcmd is simply not there. > a normal boot without xen is on pastebin (VERBOSE_SYSINIT=3D2) > > https://pastebin.com/RN1SYXdW > > > > Do you have a serial console attached to the box so that we could > > see the log of Xen and FreeBSD booting? > how to? every time I boot into xen I have to zpool import -f and mount it= from > rescue CD. Is there a log from the last boot somewhere? I duckduckgo'd a = bit > but couldn't find anything else than the dmesg. As it is not a kernel cra= sh > there's nothing in /var/crash and on /var/run I have the running boot ins= ide. You would need to plug a null-modem into the serial port of your box, or alternatively use something like SoL (Serial over LAN) if your box supports it. > Maybe you tell me how to show the log from the serial console; btw, I tri= ed > both ways, only serial, only bios or both --- no matter, xen's booting, > screen's blanking for the "normal" kernel but nothing happens but a sudde= n > reboot. Is it on the /var/* somewhere when booting from resucue? There won't be any logs from Xen in the disk, because Xen has no access to the disk at all. When booting with Xen, do you see any error message on the screen? I've added noreboot to the Xen command line above so that you can maybe take a photo of the crash message if there's any? Roger. From owner-freebsd-xen@freebsd.org Tue Jan 19 17:05:28 2021 Return-Path: Delivered-To: freebsd-xen@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 10CE54D8F88 for ; Tue, 19 Jan 2021 17:05:28 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKw5M703pz3vrf; Tue, 19 Jan 2021 17:05:27 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from localhost (unknown [212.230.157.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: royger) by smtp.freebsd.org (Postfix) with ESMTPSA id 82DAD2CDA3; Tue, 19 Jan 2021 17:05:27 +0000 (UTC) (envelope-from royger@freebsd.org) Date: Tue, 19 Jan 2021 18:05:25 +0100 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: "Lizbeth Mutterhunt, PhD" Cc: freebsd-xen@freebsd.org Subject: Re: either xen or custom Message-ID: <20210119170525.qpf3h4aipefrbdry@Air-de-Roger> References: <5536984.Zv9zXsTiuT@freebsd-current> <2113383.sMrx5ctUpN@freebsd-current> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2113383.sMrx5ctUpN@freebsd-current> X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.34 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: Tue, 19 Jan 2021 17:05:28 -0000 Adding freebsd-xen mailing list for reference. On Tue, Jan 19, 2021 at 05:04:21PM +0100, Lizbeth Mutterhunt, PhD wrote: > Op Dienstag, 19. Jänner 2021 15:06:45 CET schreef u: > > On Fri, Jan 15, 2021 at 3:46 PM Lizbeth Mutterhunt, PhD > > > > wrote: > > > Op Donnerstag, 14. Jänner 2021 09:21:09 CET schreef u: > Hi Roger, > > just to introduce myself a bit: > > !!!thx for your reply and concerns!!! > > I keep in mind that this certain kind of support isn't self-understanding and > will one day be to your advantage, too! For myself: I ask to much and answer > too little in forums, etc., as I know what to do in certain kind of matters > but still too lazy to give a tipp or to post a reply as many others does. > > I'm good in linux, especially Arch Linux, doing projects at the reborn BeOS, > Linux and now as my main system on > > [CODE] > sudo sysctl hw.model hw.machine hw.ncpu > Wachtwoord: > hw.model: Intel(R) Celeron(R) CPU 867 @ 1.30GHz So your CPU doesn't support VT-d (AKA IOMMU), and won't be able to run FreeBSD/Xen sadly. This is a hardware limitation and there's nothing that can be done. The only way to run Xen on that box is to use Linux in PV mode, which FreeBSD doesn't support. You can check the CPU features at: https://ark.intel.com/content/www/us/en/ark/products/63918/intel-celeron-processor-867-2m-cache-1-30-ghz.html Search for VT-d. If you want to run FreeBSD/Xen you will need a newer CPU, sadly there's no way around that. > > > > Do you have a serial console attached to the box so that we could > > > > see the log of Xen and FreeBSD booting? > > > > > > how to? every time I boot into xen I have to zpool import -f and mount it > > > from rescue CD. Is there a log from the last boot somewhere? I > > > duckduckgo'd a bit but couldn't find anything else than the dmesg. As it > > > is not a kernel crash there's nothing in /var/crash and on /var/run I > > > have the running boot inside. > > > You would need to plug a null-modem into the serial port of your box, > > or alternatively use something like SoL (Serial over LAN) if your box > > supports it. > > could you plz. explain this a bit more exactly? I don't have a LAN-switch yet > but it's planned for connecting the Raspi4 and my upcoming RAPTOR9 machine at > easter and to have a "night-light" with blinking RX/TX - LEDS! :-) Getting serial out of a box is the only way to diagnose early boot problems (ie: kernel issues). See: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html That way you can get the output of FreeBSD or Xen booting in text mode, so that you can for example paste it on an email when things go wrong. Roger. From owner-freebsd-xen@freebsd.org Tue Jan 19 17:20:46 2021 Return-Path: Delivered-To: freebsd-xen@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6AA4A4D8FD1 for ; Tue, 19 Jan 2021 17:20:46 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKwR22NwTz3wRW; Tue, 19 Jan 2021 17:20:46 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: by mail-ed1-x533.google.com with SMTP id g24so22411983edw.9; Tue, 19 Jan 2021 09:20:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=EedctC6f6qZTsCrClA24FBzWsewvj6E1AmnYpTvQsa4=; b=oYYMwBrReVBfdNY+2X4D1bXKPeEX53PJntdum7O0n+AfzQz+TXlkF77hoRaLXPLJ8G qVTQ1kmNUnbkObNVzRG5VX/oM1Sx62Va3/VUQJUL5H0WYtb5qpjlJBERrRhsorvYoMvu rXSwEkYXVX78Lxt3WTmw14AxAlwG5MNgRSn24pWDYoIUNAsnOxTFaW+kvVscNQggY0fK w/BItr37KZSFe3tXv5VCo17ONnScZYy/WRGgVmr2XvKL0tOEwFKGzJYwg4hHoQJU1gBW /RHsnu9tS5hjtk0zyQTvDSR8zkM+s0IZ3CdlzLQRwC/uWQXJadn5Cqjs1R0HrbaCK/bU PocA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=EedctC6f6qZTsCrClA24FBzWsewvj6E1AmnYpTvQsa4=; b=nlhRpGC+RwRj88dVHw0G99DtODjROxv/xGbM46yPDa7zLVqn+ppT8Aa4IQwyKxEiq7 BTB2/+HEXb9F6m9ySyrTqrD7SPzgCy9V7xOeqKuXXyEEXUxprsgJt20AgcNpf//ng0CX JFW3txXwQG2dSq5iyiTJNrv6gol82wE3VyLacoIF8GRgvyPljVm+j6p3Y3Oi2HZHjU5N RUD4TQr7CRRGZtE6NddYipp3B92TfjG/T69CuELmZlhJjypYLGe7mliT+FNSwftKtMff PyQQ30X9n/FsYlFL0q0ThOQ+J5EaPK5IThKc9bckwzQZZZOvsD18lHOco+PUbeb761Zx dizg== X-Gm-Message-State: AOAM530BqXX43erOO3U/QFek0aECIDxWR3RWQyTH+bPS6ntELiVZr/ou Y4Np6ZfoW4GK9kyx2xWzyTrUyQakQ9js04Xa X-Google-Smtp-Source: ABdhPJzldzVUui/gpfIncaTf7ptMHQCppWB7yuoln6YUpGlI42rlK5gLBbXNxh3prefxHWmbLFJ5xA== X-Received: by 2002:a05:6402:4c1:: with SMTP id n1mr4255871edw.66.1611076843959; Tue, 19 Jan 2021 09:20:43 -0800 (PST) Received: from freebsd-current.localnet (93-82-110-180.adsl.highway.telekom.at. [93.82.110.180]) by smtp.gmail.com with ESMTPSA id e7sm10203600ejm.115.2021.01.19.09.20.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 19 Jan 2021 09:20:43 -0800 (PST) From: "Lizbeth Mutterhunt, PhD" To: Roger Pau Monn? Cc: freebsd-xen@freebsd.org Subject: Re: either xen or custom Date: Tue, 19 Jan 2021 18:20:41 +0100 Message-ID: <2889120.fEyhCgFcho@freebsd-current> X-Face: jLp,#|qe`P=tm$C@l^; H-:@l=wrh`EUh90+Zq8&japTr{$pA+r^:ne~/Tml>0T8#5?+o&^ zKe%^Q*b52{qhsO_kOj/P.vmm:r`teihTj)qZi]u{qX=h=MhLU%OXcDp])XtYFLu?PS In-Reply-To: <20210119170525.qpf3h4aipefrbdry@Air-de-Roger> References: <5536984.Zv9zXsTiuT@freebsd-current> <2113383.sMrx5ctUpN@freebsd-current> <20210119170525.qpf3h4aipefrbdry@Air-de-Roger> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-Rspamd-Queue-Id: 4DKwR22NwTz3wRW X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.34 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: Tue, 19 Jan 2021 17:20:46 -0000 Op Dienstag, 19. J=E4nner 2021 18:05:25 CET schreef u: > Adding freebsd-xen mailing list for reference. did this, too.=20 =20 > On Tue, Jan 19, 2021 at 05:04:21PM +0100, Lizbeth Mutterhunt, PhD wrote: > > Op Dienstag, 19. J=E4nner 2021 15:06:45 CET schreef u: > > > On Fri, Jan 15, 2021 at 3:46 PM Lizbeth Mutterhunt, PhD > > >=20 > > > wrote: > > > > Op Donnerstag, 14. J=E4nner 2021 09:21:09 CET schreef u: > > Hi Roger, > >=20 > > just to introduce myself a bit: > >=20 > > !!!thx for your reply and concerns!!! > >=20 > > I keep in mind that this certain kind of support isn't self-understandi= ng > > and will one day be to your advantage, too! For myself: I ask to much a= nd > > answer too little in forums, etc., as I know what to do in certain kind > > of matters but still too lazy to give a tipp or to post a reply as many > > others does. > >=20 > > I'm good in linux, especially Arch Linux, doing projects at the reborn > > BeOS, Linux and now as my main system on > >=20 > > [CODE] > > sudo sysctl hw.model hw.machine hw.ncpu > > Wachtwoord: > > hw.model: Intel(R) Celeron(R) CPU 867 @ 1.30GHz >=20 > So your CPU doesn't support VT-d (AKA IOMMU), and won't be able to > run FreeBSD/Xen sadly. This is a hardware limitation and there's > nothing that can be done. The only way to run Xen on that box is to > use Linux in PV mode, which FreeBSD doesn't support. no, XEN stays here at BSD!=20 bhyve is this fast as tmc! =20 > You can check the CPU features at: >=20 > https://ark.intel.com/content/www/us/en/ark/products/63918/intel-celeron-= pro > cessor-867-2m-cache-1-30-ghz.html > Search for VT-d. this is the output for information purpose: "Intel=AE Virtualization Technology for Directed I/O (VT-d) continues from = the=20 existing support for IA-32 (VT-x) and Itanium=AE processor (VT-i) virtualiz= ation=20 adding new support for I/O-device virtualization. Intel VT-d can help end=20 users improve security and reliability of the systems and also improve=20 performance of I/O devices in virtualized environments." =20 > If you want to run FreeBSD/Xen you will need a newer CPU, sadly > there's no way around that. aeh! bulls*! but pitty, pitty, you can't request from an 7 year old machine= =20 everything you want. so heaven stays cloudy but RAPTOR9 willl do? no troubl= es=20 with (U)EFI there? > > > > > Do you have a serial console attached to the box so that we could > > > > > see the log of Xen and FreeBSD booting? > > > >=20 > > > > how to? every time I boot into xen I have to zpool import -f and mo= unt > > > > it > > > > from rescue CD. Is there a log from the last boot somewhere? I > > > > duckduckgo'd a bit but couldn't find anything else than the dmesg. = As > > > > it > > > > is not a kernel crash there's nothing in /var/crash and on /var/run= I > > > > have the running boot inside. > > >=20 > > > You would need to plug a null-modem into the serial port of your box, > > > or alternatively use something like SoL (Serial over LAN) if your box > > > supports it. > >=20 > > could you plz. explain this a bit more exactly? I don't have a LAN-swit= ch > > yet but it's planned for connecting the Raspi4 and my upcoming RAPTOR9 > > machine at easter and to have a "night-light" with blinking RX/TX - LED= S! > > :-) > Getting serial out of a box is the only way to diagnose early boot > problems (ie: kernel issues). See: >=20 > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-= set > up.html ok, this is something like ssh or things concerning booting without monitor= or=20 keybd, understood!=20 > That way you can get the output of FreeBSD or Xen booting in text > mode, so that you can for example paste it on an email when things go > wrong. >=20 so heaven stays a place on earth and clouds change to violet!=20 thx anyway,=20 > Roger. Lizbeth