From nobody Mon Aug 9 15:23:27 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 592D6124475C for ; Mon, 9 Aug 2021 15:23:32 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 4Gk0GW4vdpz4h6L; Mon, 9 Aug 2021 15:23:31 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: by mail-wr1-x435.google.com with SMTP id z4so21991200wrv.11; Mon, 09 Aug 2021 08:23:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=1l/pvKJ97iEBH0buBktzBHWWiok+aT2QbqlW0vvP1os=; b=g4ZN7Dg8SNYQYSJWegu9KpUrdeSyLz56v1ixWWEmSE2FWXPKMwtiAWG972NkDB/s6Z DJatVSZMHYx39KpKMPyywoNzlm/aHbik6FoREcly3Yq+kMeyc/R5KK5CBgunWpArNeRI jVBRfAgGhWFW4yNy7/0XQRVB7HvYoMHk2R+jK/wptjN8GeedMH7InRfo3REiwIbcRWe0 973cbtNiQoWp/ZmHgl13/MuGDCuuFTv+zxG2iywYi0GKGNEQelsRkv96BEqHVzwreoHO epxbASpG4HfGk2A55pCWr2T0DUBSR2G1yo/U+x/pLgzWl/ZMytoWLjDJ3Wt+bVbGFxi9 2Qlg== 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:mime-version :content-transfer-encoding; bh=1l/pvKJ97iEBH0buBktzBHWWiok+aT2QbqlW0vvP1os=; b=Bxj6laluIfKt6VlQniHR0A3X6QhgvVlYO8KCPBCFIaaJs2eCp6Ocbv9XvMX0siMYx9 K3CSn6ljH7IbBNNxdVKXdcn3lJeMPslkYCpE4gv/RHqpJOAioN55UUarFuNPrRN/T5/b zFo2YqxWiaa0yQX6Ln7dohXhgaSeABHIHPATTFD6VBd4OlkyBIZe5Y27Q7Kj0CPsUQ/i 0uVg5/gzA/yOX/ZkYo8VoyzPj9MEdLSIk4/tsmoGyRRy27klCEgeTGWNGspyW9aLfhOI QRlBioO2Qism+aAYuSslKsx/sEZdgjpqJJlNYdpHaXZ6nPA0oAnvgkFWGoyjuXRFIta+ D4bw== X-Gm-Message-State: AOAM533RuXreKv2mUuCQnrDwPRX0OuWMHl/w0+TrTXXGdypEIXuPibue Ub62g1Zdiukt1tKlkW4oq7BfNW8WN3DVDDD3 X-Google-Smtp-Source: ABdhPJz+fNot6NauzRfDOwaxvf2taMyjo2T/Nc+B/ZrIvd/kWlgqmgYEhdwQKabtNUUWFPiaxQCPag== X-Received: by 2002:a05:6000:120c:: with SMTP id e12mr8477324wrx.130.1628522610238; Mon, 09 Aug 2021 08:23:30 -0700 (PDT) Received: from freebsd_current.localnet (91-115-224-145.adsl.highway.telekom.at. [91.115.224.145]) by smtp.gmail.com with ESMTPSA id n8sm19569529wrx.46.2021.08.09.08.23.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Aug 2021 08:23:29 -0700 (PDT) From: lizbethmutterhunt@gmail.com To: freebsd-xen@freebsd.org Cc: royger@freebsd.org Subject: another xen-kernel UEFI story Date: Mon, 09 Aug 2021 17:23:27 +0200 Message-ID: <3839452.BRNeRiNLvY@freebsd_current> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 4Gk0GW4vdpz4h6L X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=g4ZN7Dg8; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of lizbethmutterhunt@gmail.com designates 2a00:1450:4864:20::435 as permitted sender) smtp.mailfrom=lizbethmutterhunt@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; CTE_CASE(0.50)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; FROM_NO_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::435:from]; RBL_AMI_RCVD_FAIL(0.00)[91.115.224.145:server fail]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N could someone pleas check this link: https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.81556/ does anyone has another idea then duplicating CURRENT and RELEASE via Virtualbox or qemu? XEN simply doesn't boot after setting xen_kernel on in /boot/loader.conf, we tried different ways but none worked. It's loading [text], [data], [syms] and the preconfig but afterwards there's just the reset-button option, because XEN doesn't boot. any help appreciated! lizbeth From nobody Tue Aug 10 00:13:15 2021 X-Original-To: xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 99D1B137A66D for ; Tue, 10 Aug 2021 00:13:15 +0000 (UTC) (envelope-from bugzilla-noreply@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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GkD1l3SlFz4ZjV for ; Tue, 10 Aug 2021 00:13:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 5958611DA4 for ; Tue, 10 Aug 2021 00:13:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 17A0DFHa021292 for ; Tue, 10 Aug 2021 00:13:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 17A0DFOO021291 for xen@FreeBSD.org; Tue, 10 Aug 2021 00:13:15 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: xen@FreeBSD.org Subject: [Bug 257712] xen_kernel doesn't boot at all! Date: Tue, 10 Aug 2021 00:13:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: Unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257712 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |xen@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Tue Aug 10 07:38:58 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A070111FEB26 for ; Tue, 10 Aug 2021 07:39:08 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4GkPwD495Wz3QL1; Tue, 10 Aug 2021 07:39:08 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from localhost (unknown [93.176.187.34]) (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 13097298B2; Tue, 10 Aug 2021 07:39:07 +0000 (UTC) (envelope-from royger@freebsd.org) Date: Tue, 10 Aug 2021 09:38:58 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: lizbethmutterhunt@gmail.com Cc: freebsd-xen@freebsd.org Subject: Re: another xen-kernel UEFI story Message-ID: References: <3839452.BRNeRiNLvY@freebsd_current> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <3839452.BRNeRiNLvY@freebsd_current> X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N On Mon, Aug 09, 2021 at 05:23:27PM +0200, lizbethmutterhunt@gmail.com wrote: > could someone pleas check this link: > https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.81556/ > > does anyone has another idea then duplicating CURRENT and RELEASE via > Virtualbox or qemu? > > XEN simply doesn't boot after setting xen_kernel on in /boot/loader.conf, we > tried different ways but none worked. It's loading [text], [data], [syms] and > the preconfig but afterwards there's just the reset-button option, because XEN > doesn't boot. > > any help appreciated! Hello, There are a couple of things to look at, first of all, do you have a serial console attached to the box? It seems like you do because you have the serial output options enabled in loader.conf, in which case can you paste the output you get from the serial when booting? Also note that the line: xen_cmdline="dom0_mem=4048M dom0_max_vcpus=4 dom0pvh=1 com1=115200,8n1 guest_loglvl=all loglvl=all" Is wrong unless you are using Xen 4.7. The handbook [0] states that for Xen 4.11 and greater dom0=pvh should be used instead of dom0pvh=1. Also note that the line: hw.pci.mcfg=0 Is not needed unless you are using Xen 4.7. If you don't have a serial console, and the above doesn't fix your issue I would recommend that you switch to plain UEFI booting (ie: no BIOS CSM), install FreeBSD 14 (current) and then try to boot Xen with UEFI. FreeBSD 14 should have support for booting Xen from UEFI without the need of the BIOS CSM mode. Thanks, Roger. [0] https://docs.freebsd.org/en/books/handbook/virtualization/#virtualization-host-xen From nobody Tue Aug 10 12:41:34 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 759A9175143A for ; Tue, 10 Aug 2021 12:41:41 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 4GkXdK2dVnz4XKs; Tue, 10 Aug 2021 12:41:41 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: by mail-wm1-x334.google.com with SMTP id i10-20020a05600c354ab029025a0f317abfso1848575wmq.3; Tue, 10 Aug 2021 05:41:41 -0700 (PDT) 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=Mi4n3c67iXlsne2pdShk2fvYxHJ5BZdXZfkJmiwUchE=; b=CM/TvrZAB+lDuIV5THQkAe2aJqPJrXswEWwDC28PKA8X6oC5v1+ynjyhzQbEUMsoLx P8OKJYKMHAIwA6CfNQRfHvH2uf10CHShlOYkkMSCXLLwKL0LuvObkrs5OiMj+dOU+9ft ahLB1bFLf8IZXcZXsy91WD2EishzAMnYVMK28wMynhKpxrxfLi8zzyJpBwXaBLphjd82 vLBlsYLOwlBcB2gso68J5vrxa/f/fXsVUbzfNunkG4JweBFqH8uoeqAVygOqlpXswhnI Dqc3cuDt6Fd45c1cUnkLQz7a0VutzBDjXtkjkHQ8blx9kgqyLq0U/WwWK7Kyfd0KAIBp UzXg== 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=Mi4n3c67iXlsne2pdShk2fvYxHJ5BZdXZfkJmiwUchE=; b=POQcMmk44KPoqSyqTaKDOtvD6XdkNfh5CnVPl3xBT7r+Qj6rCA4HPGqf3xtueRYXxX DY0JNjJ9ykT3PrH4Oy9+68SbpVnCqfDoj+25h6e5gRPioLBfrqUF1UD0DeBBQ93/9XuV JAYQcBP1LlBypHA6jiJueDfhso1SXZF9RnYGgaRRsVFXpCNTRMLlFWf6jkjO2A6Phsme k9G9tlXftTSad4AD1X2e5UFkA4g5ZOk8RUTvJ0LGQgwr90b+H6i044YS6UfWYzF3IE8U Cvp+II9aqbR4VK/hI1EWtgXSd/axZJiuwekoBOSw2j723yMpdANnPvfK0tIZb/De/y5T X1rw== X-Gm-Message-State: AOAM532Lnpxx9/xafl7/rvbSK9B3iVqocS5ihpBLdHPp6EU/dZxotCNt OHOmYi/E8uFOdcWyEeqK2fH6KJDcFgudfw== X-Google-Smtp-Source: ABdhPJyf0dlQWReXoC+YDWbQPHxIdCgPhyosGvdeObQ+q68F6wNdCI6UZt9mMX95k/FBHIuYbVMOmA== X-Received: by 2002:a7b:c8c6:: with SMTP id f6mr4511035wml.44.1628599299931; Tue, 10 Aug 2021 05:41:39 -0700 (PDT) Received: from freebsd_current.localnet (91-115-224-145.adsl.highway.telekom.at. [91.115.224.145]) by smtp.gmail.com with ESMTPSA id k17sm23820080wrw.53.2021.08.10.05.41.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 10 Aug 2021 05:41:39 -0700 (PDT) From: lizbethmutterhunt@gmail.com To: Roger Pau =?ISO-8859-1?Q?Monn=E9?= Cc: freebsd-xen@freebsd.org Subject: Re: another xen-kernel UEFI story Date: Tue, 10 Aug 2021 14:41:34 +0200 Message-ID: <3837161.BRNeRiNLvY@freebsd_current> In-Reply-To: References: <3839452.BRNeRiNLvY@freebsd_current> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 4GkXdK2dVnz4XKs X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Op Tuesday, 10 August 2021 09:38:58 CEST schreef u: > On Mon, Aug 09, 2021 at 05:23:27PM +0200, lizbethmutterhunt@gmail.com wrote: > > could someone pleas check this link: > > https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.81556/ > > > > does anyone has another idea then duplicating CURRENT and RELEASE via > > Virtualbox or qemu? > > > > XEN simply doesn't boot after setting xen_kernel on in /boot/loader.conf, > > we tried different ways but none worked. It's loading [text], [data], > > [syms] and the preconfig but afterwards there's just the reset-button > > option, because XEN doesn't boot. > > > > any help appreciated! > > Hello, hello royger! > There are a couple of things to look at, first of all, do you have a > serial console attached to the box? I guess so, because there are two possibilities to start from via primary and secodary console! > It seems like you do because you have the serial output options > enabled in loader.conf, in which case can you paste the output you get > from the serial when booting? could just make a photo, but it's loading the preemt and than it stops only to recover via the reset key. > Also note that the line: > > xen_cmdline="dom0_mem=4048M dom0_max_vcpus=4 dom0pvh=1 com1=115200,8n1 > guest_loglvl=all loglvl=all" > > Is wrong unless you are using Xen 4.7. The handbook [0] states > that for Xen 4.11 and greater dom0=pvh should be used instead of > dom0pvh=1. tried both versions X-times but didn't react on neither! > Also note that the line: > > hw.pci.mcfg=0 made my # before the line, no change > Is not needed unless you are using Xen 4.7. > > If you don't have a serial console, and the above doesn't fix your > issue I would recommend that you switch to plain UEFI booting (ie: no > BIOS CSM), install FreeBSD 14 (current) and then try to boot Xen with > UEFI. FreeBSD 14 should have support for booting Xen from UEFI without > the need of the BIOS CSM mode. switched in BIOS to plain UEFI mode (auto) but still no difference. making my virtual machine with release (works with 14-CURRENT, too!). But what to do with the hypervisor on an virtual machine; making machines in machines? > Thanks, Roger. thanx a lot for trying to help me! lizbeth > [0] > https://docs.freebsd.org/en/books/handbook/virtualization/#virtualization-h > ost-xen From nobody Tue Aug 10 13:32:45 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id EE0341754BC8 for ; Tue, 10 Aug 2021 13:32:53 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4GkYmP6TFdz4cbc; Tue, 10 Aug 2021 13:32:53 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from localhost (unknown [93.176.187.34]) (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 6E6032C77D; Tue, 10 Aug 2021 13:32:53 +0000 (UTC) (envelope-from royger@freebsd.org) Date: Tue, 10 Aug 2021 15:32:45 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: lizbethmutterhunt@gmail.com Cc: freebsd-xen@freebsd.org Subject: Re: another xen-kernel UEFI story Message-ID: References: <3839452.BRNeRiNLvY@freebsd_current> <3837161.BRNeRiNLvY@freebsd_current> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <3837161.BRNeRiNLvY@freebsd_current> X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N On Tue, Aug 10, 2021 at 02:41:34PM +0200, lizbethmutterhunt@gmail.com wrote: > Op Tuesday, 10 August 2021 09:38:58 CEST schreef u: > > On Mon, Aug 09, 2021 at 05:23:27PM +0200, lizbethmutterhunt@gmail.com wrote: > > > could someone pleas check this link: > > > https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.81556/ > > > > > > does anyone has another idea then duplicating CURRENT and RELEASE via > > > Virtualbox or qemu? > > > > > > XEN simply doesn't boot after setting xen_kernel on in /boot/loader.conf, > > > we tried different ways but none worked. It's loading [text], [data], > > > [syms] and the preconfig but afterwards there's just the reset-button > > > option, because XEN doesn't boot. > > > > > > any help appreciated! > > > > Hello, > hello royger! > > > There are a couple of things to look at, first of all, do you have a > > serial console attached to the box? > I guess so, because there are two possibilities to start from via primary and > secodary console! The serial console is a port (usually a RS-232) on your box that you attach a cable to and connect to another computer, so you can get early text debug output: https://www.computerhope.com/jargon/s/serial-console.htm https://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/intro-why.html There also some boxes that have a virtual serial console like Intel AMT Serial Over LAN: https://en.wikipedia.org/wiki/Intel_Active_Management_Technology If you can setup one of those it would be handy in figuring it what's wrong, since the serial is initialized way before than the VGA adapter and could contain a message detailing what went wrong. > > If you don't have a serial console, and the above doesn't fix your > > issue I would recommend that you switch to plain UEFI booting (ie: no > > BIOS CSM), install FreeBSD 14 (current) and then try to boot Xen with > > UEFI. FreeBSD 14 should have support for booting Xen from UEFI without > > the need of the BIOS CSM mode. > switched in BIOS to plain UEFI mode (auto) but still no difference. > > making my virtual machine with release (works with 14-CURRENT, too!). But what > to do with the hypervisor on an virtual machine; making machines in machines? You can indeed boot Xen inside of QEMU, but in order to boot a FreeBSD dom0 you will need to enable nested virtualization and a virtual IOMMU. Regards, Roger. From nobody Thu Aug 12 07:01:07 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9E812174B357 for ; Thu, 12 Aug 2021 07:01:15 +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 4Glczb2zhgz3qRw; Thu, 12 Aug 2021 07:01:15 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from localhost (unknown [93.176.191.254]) (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 D270F205EB; Thu, 12 Aug 2021 07:01:14 +0000 (UTC) (envelope-from royger@freebsd.org) Date: Thu, 12 Aug 2021 09:01:07 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: "Lizbeth Mutterhunt, Ph.D" Cc: freebsd-xen@freebsd.org Subject: Re: another xen-kernel UEFI story Message-ID: References: <3839452.BRNeRiNLvY@freebsd_current> <3837161.BRNeRiNLvY@freebsd_current> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N Adding the freebsd-xen mailing list again. On Wed, Aug 11, 2021 at 12:48:55AM +0200, Lizbeth Mutterhunt, Ph.D wrote: > Op Tuesday, 10 August 2021 15:32:45 CEST schreef u: > > On Tue, Aug 10, 2021 at 02:41:34PM +0200, lizbethmutterhunt@gmail.com > wrote: > > > Op Tuesday, 10 August 2021 09:38:58 CEST schreef u: > > > > On Mon, Aug 09, 2021 at 05:23:27PM +0200, lizbethmutterhunt@gmail.com > wrote: > > > > > could someone pleas check this link: > > > > > > https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.8155 > > > > > 6/ > > > > > > > > > > does anyone has another idea then duplicating CURRENT and RELEASE > via > > > > > Virtualbox or qemu? > > > > > > > > > > XEN simply doesn't boot after setting xen_kernel on in > > > > > /boot/loader.conf, > > > > > we tried different ways but none worked. It's loading [text], > [data], > > > > > [syms] and the preconfig but afterwards there's just the > reset-button > > > > > option, because XEN doesn't boot. > > > > > > > > > > any help appreciated! > > > > > > > > Hello, > > > > > > hello royger! > hija! > > > > > > > > There are a couple of things to look at, first of all, do you have a > > > > serial console attached to the box? > > > > > > I guess so, because there are two possibilities to start from via > primary > > > and secodary console! > > > > The serial console is a port (usually a RS-232) on your box that you > > attach a cable to and connect to another computer, so you can get > > early text debug output: > > > > https://www.computerhope.com/jargon/s/serial-console.htm > > https://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/intro-why.html > Basically I know the RS-232 "live" in the 80s, and I was soldering a earth- > cable to connect two PCs without any swith via a deviate of Midnight > Commander. So first thought, enable serial port in bios; computer crashing > at > xen and crashes when allocating the re0. so disabled again! I 'm afraid I'm a bit lost here, so your computer does have some kind of serial port? Do you mean that when you enable the serial port in BIOS (I assume a Serial Over LAN) the re0 network interface stops working? > > > There also some boxes that have a virtual serial console like Intel > > AMT Serial Over LAN: > > > > https://en.wikipedia.org/wiki/Intel_Active_Management_Technology > I guess my active management is on or there's no way to enable it in the > BIOS > (ASUS P8H77M-Pro); pitty, there's no search function in the advanced bios. > > I managed to watch BTX with 4 years and with 8 I got my first original IBM > PC > and compatible. the C64 was later in my development and I'm atoning all my > problem adolescence in front of the SNES here with my shell commands. Would > I > just have been become a gamer, I'm considering all the time at that point > of > regression with a problem. But they do have there own, I think! > > > If you can setup one of those it would be handy in figuring it what's > > wrong, since the serial is initialized way before than the VGA adapter > > and could contain a message detailing what went wrong. > yes! yes! yes! do I need a second computer for it? I could modify my Raspi > 4b > for that or an old notebook! but I think it is a simple .log file > somewhere. Sure, you just need something at the other end of the serial (null modem) cable. Whether it's an old laptop or a raspberry pi doesn't make much of a difference. Regards, Roger. From nobody Thu Aug 12 13:52:55 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9DB931379B0A for ; Thu, 12 Aug 2021 13:52:58 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 4Glp6f3gs7z4nr1; Thu, 12 Aug 2021 13:52:58 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: by mail-wr1-x431.google.com with SMTP id x10so2123818wrt.8; Thu, 12 Aug 2021 06:52:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=cYzalEw4Uj/mgsl4ZUj1Ky3lh8WKdyrBR3eedDIrRes=; b=bTtzTy3+cpSBXEF4jfWq8AbInTMowG7614E1fR+/BimyM2njyWBfOoNNvvEpO2CBoX 2qcw7wFOYMSne+cTo/io28/sOvoEIFpXmBy4PA0q7wo1GHX27T/ynCN3QYPh3x8e589U M/+wlNQeaMQSkrKQRt3uITLVS1F6FlXRWdtEv0KgZqiR/QrhStm4dcNKiYZElLecIw++ 64MhDIFlm+pZPw0Hez0FDv8flv6YpZm4p+q2z2u/+Z2PEmUtGNPPtZsG99jLITBLf3al g7TGJDgSXtPH13Ojl5lQdMXpIJAhSk7EeUijWoKOk4S59V+VbCzqWvRfROdfxtwaOjot O4Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=cYzalEw4Uj/mgsl4ZUj1Ky3lh8WKdyrBR3eedDIrRes=; b=n3icP4WzTnqnPRJ/iTNG1J5yVYgdcYhVzY3RFhR9f1V9uNdDBkmpI78YgUxTKn5YgH 2sozPYcDKXe0iN1s6o96v1GVvfr6OgO93jdVRsulget+Rm03DX8SMtx+l48Y20IJ91OA eTVCvMJ/KTL5htKeWdUZoO0IE7X2TdGBECSREDzBQwtQJF7bg889bc+Axi6dvgZf3r+m 8Y3XVDSoqFpyaSOjfgtSkYwIYcAzKs0W5oj/xb8MYQSACwIDZVeE4qb+1GR7cyFRM2v5 h65Ad3iSlC36wThaHL/0Tr2GrqHxpUhAyKvAvHYC2y0qqQJvx29zCkfDwRlaPuXSUL4s oYTQ== X-Gm-Message-State: AOAM533oSj1996cycsOtwzOwVjekrybcQ27mciZNACJhYmKTQuoixzDD Uz6+pzEmVFvpdBVZzotiNFhqh88MD16Hgw== X-Google-Smtp-Source: ABdhPJzdFZIauDoyQww2LePowz413YcxCVKrgbctOTFjkpKQFy1i6L5VLIwHZU3lxqytRHtCtdwJZQ== X-Received: by 2002:a5d:56c7:: with SMTP id m7mr4312635wrw.310.1628776377195; Thu, 12 Aug 2021 06:52:57 -0700 (PDT) Received: from smtpclient.apple (91-115-224-145.adsl.highway.telekom.at. [91.115.224.145]) by smtp.gmail.com with ESMTPSA id s10sm3738302wrv.54.2021.08.12.06.52.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Aug 2021 06:52:56 -0700 (PDT) From: "Lizbeth Mutterhunt, Ph.D" Message-Id: <0FD46B61-6556-4912-814F-4A26988CC23E@gmail.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_FC70A58B-C817-4ACD-8B50-6CCA2DFCCC70" List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3689.0.4\)) Subject: Re: another xen-kernel UEFI story Date: Thu, 12 Aug 2021 15:52:55 +0200 In-Reply-To: Cc: "freebsd-xen@freebsd.org" To: Roger Pau Monn? References: <3839452.BRNeRiNLvY@freebsd_current> <3837161.BRNeRiNLvY@freebsd_current> X-Mailer: Apple Mail (2.3689.0.4) X-Rspamd-Queue-Id: 4Glp6f3gs7z4nr1 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_FC70A58B-C817-4ACD-8B50-6CCA2DFCCC70 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Op 12 aug. 2021, om 09:01 heeft Roger Pau Monn=C3=A9 = het volgende geschreven: >=20 > Adding the freebsd-xen mailing list again. >=20 > On Wed, Aug 11, 2021 at 12:48:55AM +0200, Lizbeth Mutterhunt, Ph.D = wrote: >> Op Tuesday, 10 August 2021 15:32:45 CEST schreef u: >>> On Tue, Aug 10, 2021 at 02:41:34PM +0200, = lizbethmutterhunt@gmail.com >> wrote: >>>> Op Tuesday, 10 August 2021 09:38:58 CEST schreef u: >>>>> On Mon, Aug 09, 2021 at 05:23:27PM +0200, = lizbethmutterhunt@gmail.com >> wrote: >>>>>> could someone pleas check this link: >>>>>>=20 >> = https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.8155 >>>>>> 6/ >>>>>>=20 >>>>>> does anyone has another idea then duplicating CURRENT and RELEASE >> via >>>>>> Virtualbox or qemu? >>>>>>=20 >>>>>> XEN simply doesn't boot after setting xen_kernel on in >>>>>> /boot/loader.conf, >>>>>> we tried different ways but none worked. It's loading [text], >> [data], >>>>>> [syms] and the preconfig but afterwards there's just the >> reset-button >>>>>> option, because XEN doesn't boot. >>>>>>=20 >>>>>> any help appreciated! >>>>>=20 >>>>> Hello, >>>>=20 >>>> hello royger! >> hija! >>=20 Hello Roger! >>>>=20 >>>>> There are a couple of things to look at, first of all, do you have = a >>>>> serial console attached to the box? >>>>=20 >>>> I guess so, because there are two possibilities to start from via >> primary >>>> and secodary console! >>>=20 >>> The serial console is a port (usually a RS-232) on your box that you >>> attach a cable to and connect to another computer, so you can get >>> early text debug output: >>>=20 >>> https://www.computerhope.com/jargon/s/serial-console.htm >>> https://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/intro-why.html >> Basically I know the RS-232 "live" in the 80s, and I was soldering a = earth- >> cable to connect two PCs without any swith via a deviate of Midnight >> Commander. So first thought, enable serial port in bios; computer = crashing >> at >> xen and crashes when allocating the re0. so disabled again! >=20 > I 'm afraid I'm a bit lost here, so your computer does have some kind > of serial port? No, no RS-232 output of course but a parallel and serial console in the = BIOS! I activated the serial port and got in troubles with booting; = beasties logo has been disabled, so no boot menu to unset the xen_xernel = at boot prompt. XEN never booted anyway. > Do you mean that when you enable the serial port in BIOS (I assume a > Serial Over LAN) Yup! > the re0 network interface stops working.=20 Yes, at the dhclient allocations it stops immediately with no output or = debugger info at all. Also the keyboard was disabled and I couldn=E2=80=99= t press CTRL+C for avoiding DHCPREQUEST. =20 >>=20 >>> There also some boxes that have a virtual serial console like Intel >>> AMT Serial Over LAN: >>>=20 >>> https://en.wikipedia.org/wiki/Intel_Active_Management_Technology >> I guess my active management is on or there's no way to enable it in = the >> BIOS >> (ASUS P8H77M-Pro); pitty, there's no search function in the advanced = bios. >>=20 >> I managed to watch BTX with 4 years and with 8 I got my first = original IBM >> PC >> and compatible. the C64 was later in my development and I'm atoning = all my >> problem adolescence in front of the SNES here with my shell commands. = Would >> I >> just have been become a gamer, I'm considering all the time at that = point >> of >> regression with a problem. But they do have there own, I think! >>=20 >>> If you can setup one of those it would be handy in figuring it = what's >>> wrong, since the serial is initialized way before than the VGA = adapter >>> and could contain a message detailing what went wrong. >> yes! yes! yes! do I need a second computer for it? I could modify my = Raspi >> 4b >> for that or an old notebook! but I think it is a simple .log file >> somewhere. >=20 > Sure, you just need something at the other end of the serial (null > modem) cable. Whether it's an old laptop or a raspberry pi doesn't > make much of a difference. >=20 I make myself a bit trusted with the matter RS-232 and not sure how to = connect those two PCs=E2=80=A6 when there=E2=80=99s some outcome for me = today, I do my best tomorrow, ok? > Regards, Roger. Best regards,=20 Lizbeth= --Apple-Mail=_FC70A58B-C817-4ACD-8B50-6CCA2DFCCC70-- From nobody Thu Aug 12 16:45:18 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 47141174BDDF for ; Thu, 12 Aug 2021 16:45:21 +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 4GlsxY1QgHz3HC1; Thu, 12 Aug 2021 16:45:21 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from localhost (unknown [93.176.191.254]) (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 9C2D5252B2; Thu, 12 Aug 2021 16:45:20 +0000 (UTC) (envelope-from royger@freebsd.org) Date: Thu, 12 Aug 2021 18:45:18 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: "Lizbeth Mutterhunt, Ph.D" Cc: "freebsd-xen@freebsd.org" Subject: Re: another xen-kernel UEFI story Message-ID: References: <3839452.BRNeRiNLvY@freebsd_current> <3837161.BRNeRiNLvY@freebsd_current> <0FD46B61-6556-4912-814F-4A26988CC23E@gmail.com> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0FD46B61-6556-4912-814F-4A26988CC23E@gmail.com> X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N On Thu, Aug 12, 2021 at 03:52:55PM +0200, Lizbeth Mutterhunt, Ph.D wrote: > > > > Op 12 aug. 2021, om 09:01 heeft Roger Pau Monné het volgende geschreven: > > > > Adding the freebsd-xen mailing list again. > > > > On Wed, Aug 11, 2021 at 12:48:55AM +0200, Lizbeth Mutterhunt, Ph.D wrote: > >> Op Tuesday, 10 August 2021 15:32:45 CEST schreef u: > >>> On Tue, Aug 10, 2021 at 02:41:34PM +0200, lizbethmutterhunt@gmail.com > >> wrote: > >>>> Op Tuesday, 10 August 2021 09:38:58 CEST schreef u: > >>>>> On Mon, Aug 09, 2021 at 05:23:27PM +0200, lizbethmutterhunt@gmail.com > >> wrote: > >>>>>> could someone pleas check this link: > >>>>>> > >> https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.8155 > >>>>>> 6/ > >>>>>> > >>>>>> does anyone has another idea then duplicating CURRENT and RELEASE > >> via > >>>>>> Virtualbox or qemu? > >>>>>> > >>>>>> XEN simply doesn't boot after setting xen_kernel on in > >>>>>> /boot/loader.conf, > >>>>>> we tried different ways but none worked. It's loading [text], > >> [data], > >>>>>> [syms] and the preconfig but afterwards there's just the > >> reset-button > >>>>>> option, because XEN doesn't boot. > >>>>>> > >>>>>> any help appreciated! > >>>>> > >>>>> Hello, > >>>> > >>>> hello royger! > >> hija! > >> > Hello Roger! > > >>>> > >>>>> There are a couple of things to look at, first of all, do you have a > >>>>> serial console attached to the box? > >>>> > >>>> I guess so, because there are two possibilities to start from via > >> primary > >>>> and secodary console! > >>> > >>> The serial console is a port (usually a RS-232) on your box that you > >>> attach a cable to and connect to another computer, so you can get > >>> early text debug output: > >>> > >>> https://www.computerhope.com/jargon/s/serial-console.htm > >>> https://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/intro-why.html > >> Basically I know the RS-232 "live" in the 80s, and I was soldering a earth- > >> cable to connect two PCs without any swith via a deviate of Midnight > >> Commander. So first thought, enable serial port in bios; computer crashing > >> at > >> xen and crashes when allocating the re0. so disabled again! > > > > I 'm afraid I'm a bit lost here, so your computer does have some kind > > of serial port? > > No, no RS-232 output of course but a parallel and serial console in the BIOS! I activated the serial port and got in troubles with booting; beasties logo has been disabled, so no boot menu to unset the xen_xernel at boot prompt. XEN never booted anyway. > > > Do you mean that when you enable the serial port in BIOS (I assume a > > Serial Over LAN) > Yup! > > the re0 network interface stops working. > Yes, at the dhclient allocations it stops immediately with no output or debugger info at all. Also the keyboard was disabled and I couldn’t press CTRL+C for avoiding DHCPREQUEST. I think it would be better to get Xen out of the picture here, and initially focus on getting a serial console working with plain FreeBSD. Once you have that it should be trivial to attempt to boot Xen and get the output on the serial, but first you need to have it working properly with plain FreeBSD. The handbook contains a good section about how to get it working: https://docs.freebsd.org/en/books/handbook/serialcomms/#serialconsole-setup But it seems like you will need some help from your hardware vendor in order to figure out how to enable Serial Over LAN properly on the firmware. Note that you should be able to get the output of both the FreeBSD loader and kernel on the serial console. Regards, Roger. From nobody Thu Aug 12 16:56:29 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 652CE174C9C7 for ; Thu, 12 Aug 2021 16:56:33 +0000 (UTC) (envelope-from gerd.hafenbrack@gmail.com) Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 4GltBS4YnVz3Hkw for ; Thu, 12 Aug 2021 16:56:32 +0000 (UTC) (envelope-from gerd.hafenbrack@gmail.com) Received: by mail-ed1-x530.google.com with SMTP id dj8so2833208edb.2 for ; Thu, 12 Aug 2021 09:56:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=iqS6YxsteutfPTZIebkKt6iEPtUL49brYwSdW5pOZis=; b=auS+XA9kLW2faL3TRQF/B+scSOl1N4OLtJaKdwyg10+uI0mR2RTXxFSMTn6MSB1ZVk sOXPQ6syWmvtF9W/Kx5wjHskeRqWanUgpKXPY0VECSA/qPeoc9SwVI6KJhnAmCful9Xi SLfFLZDXIxQdklPbmH2hQVTDRuCmmVjZKS3iAYgtMfTzEHfxbWHr81bytRaNyQvAB6Ad 5WP/JLUUIgJGoPa+VVk2u3+kTZM1RZOBn67Shu1TC4QyCYL3PBXZAXkSp+TdBbWqbSkT k7bQZjxAZaLw8Q+XqJk2nlTu+sryuGTwy9UvofNhIMz6VPlEoyqi96n6+zYb8AEzkScv fTfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iqS6YxsteutfPTZIebkKt6iEPtUL49brYwSdW5pOZis=; b=qzRA6CwpDdqtyJCjPZ5sJiTlKOqb5C7Fk20GkyHXypengqiNRtVEzfJ+C4sYia3w2T AoL3y/Su/Nxc9CvXs6Pu7D1OGO3OVMujVZ9WPgv0tssReTYMbIvMGvkVRHW2bN0JFjAU IVfjguQ5vMeX4oi2ArtSAtlSOHZA07sqA6V6XstcB10RwoW7bPxpSYv7hEGi7q0kEr0p /fcg470Lv8sTq8/SW72t3cXn+1lkbPaqUg6F9rlaVn3XbEMM0/EoSz2TvxYrpAlDTyFb IZ7Vi2cLNlvQbHbc4+kJIBZtwU8v+LhqQHindFk+fTv6QdNvRJEQA3nSMJYTS7A8b/Zp kD0w== X-Gm-Message-State: AOAM532FKyDco4urmJxyI6Ay8fwvZ3Ovnp3S+8HnSwuSpQulgx/vsuF0 Zfskzb4FXGGR5w3RktJD4Xw0YTqXEbU= X-Google-Smtp-Source: ABdhPJzk/XwDe6f6am8X5QyaYiat4iOXO1NXc58rf7I5WOECOdfvkbdTTJ85HamKzc0ZyJAZdOAFMg== X-Received: by 2002:aa7:dd0d:: with SMTP id i13mr6639649edv.371.1628787391645; Thu, 12 Aug 2021 09:56:31 -0700 (PDT) Received: from ?IPv6:2a02:8070:e198:fc00:2cb8:161e:3633:370? ([2a02:8070:e198:fc00:2cb8:161e:3633:370]) by smtp.gmail.com with ESMTPSA id kz15sm707010ejc.103.2021.08.12.09.56.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 12 Aug 2021 09:56:31 -0700 (PDT) Subject: Re: another xen-kernel UEFI story To: "Lizbeth Mutterhunt, Ph.D" Cc: "freebsd-xen@freebsd.org" References: <3839452.BRNeRiNLvY@freebsd_current> <3837161.BRNeRiNLvY@freebsd_current> <0FD46B61-6556-4912-814F-4A26988CC23E@gmail.com> From: Gerd Hafenbrack Message-ID: <9cf13949-3436-ce43-9884-d7a028c940fb@gmail.com> Date: Thu, 12 Aug 2021 18:56:29 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4GltBS4YnVz3Hkw X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=auS+XA9k; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gerdhafenbrack@gmail.com designates 2a00:1450:4864:20::530 as permitted sender) smtp.mailfrom=gerdhafenbrack@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-xen@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::530:from]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Hello, The ASUS P8H77M-Pro has an internal serial connector onboard. Lizbeth should get a DB9 male slot bracket with 10 pin internal connector and a null modem cable. Regards, Gerd On 2021-08-12 18:45, Roger Pau Monné wrote: > On Thu, Aug 12, 2021 at 03:52:55PM +0200, Lizbeth Mutterhunt, Ph.D wrote: >> >> >>> Op 12 aug. 2021, om 09:01 heeft Roger Pau Monné het volgende geschreven: >>> >>> Adding the freebsd-xen mailing list again. >>> >>> On Wed, Aug 11, 2021 at 12:48:55AM +0200, Lizbeth Mutterhunt, Ph.D wrote: >>>> Op Tuesday, 10 August 2021 15:32:45 CEST schreef u: >>>>> On Tue, Aug 10, 2021 at 02:41:34PM +0200, lizbethmutterhunt@gmail.com >>>> wrote: >>>>>> Op Tuesday, 10 August 2021 09:38:58 CEST schreef u: >>>>>>> On Mon, Aug 09, 2021 at 05:23:27PM +0200, lizbethmutterhunt@gmail.com >>>> wrote: >>>>>>>> could someone pleas check this link: >>>>>>>> >>>> https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.8155 >>>>>>>> 6/ >>>>>>>> >>>>>>>> does anyone has another idea then duplicating CURRENT and RELEASE >>>> via >>>>>>>> Virtualbox or qemu? >>>>>>>> >>>>>>>> XEN simply doesn't boot after setting xen_kernel on in >>>>>>>> /boot/loader.conf, >>>>>>>> we tried different ways but none worked. It's loading [text], >>>> [data], >>>>>>>> [syms] and the preconfig but afterwards there's just the >>>> reset-button >>>>>>>> option, because XEN doesn't boot. >>>>>>>> >>>>>>>> any help appreciated! >>>>>>> >>>>>>> Hello, >>>>>> >>>>>> hello royger! >>>> hija! >>>> >> Hello Roger! >> >>>>>> >>>>>>> There are a couple of things to look at, first of all, do you have a >>>>>>> serial console attached to the box? >>>>>> >>>>>> I guess so, because there are two possibilities to start from via >>>> primary >>>>>> and secodary console! >>>>> >>>>> The serial console is a port (usually a RS-232) on your box that you >>>>> attach a cable to and connect to another computer, so you can get >>>>> early text debug output: >>>>> >>>>> https://www.computerhope.com/jargon/s/serial-console.htm >>>>> https://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/intro-why.html >>>> Basically I know the RS-232 "live" in the 80s, and I was soldering a earth- >>>> cable to connect two PCs without any swith via a deviate of Midnight >>>> Commander. So first thought, enable serial port in bios; computer crashing >>>> at >>>> xen and crashes when allocating the re0. so disabled again! >>> >>> I 'm afraid I'm a bit lost here, so your computer does have some kind >>> of serial port? >> >> No, no RS-232 output of course but a parallel and serial console in the BIOS! I activated the serial port and got in troubles with booting; beasties logo has been disabled, so no boot menu to unset the xen_xernel at boot prompt. XEN never booted anyway. >> >>> Do you mean that when you enable the serial port in BIOS (I assume a >>> Serial Over LAN) >> Yup! >>> the re0 network interface stops working. >> Yes, at the dhclient allocations it stops immediately with no output or debugger info at all. Also the keyboard was disabled and I couldn’t press CTRL+C for avoiding DHCPREQUEST. > > I think it would be better to get Xen out of the picture here, and > initially focus on getting a serial console working with plain > FreeBSD. > > Once you have that it should be trivial to attempt to boot > Xen and get the output on the serial, but first you need to have it > working properly with plain FreeBSD. > > The handbook contains a good section about how to get it working: > > https://docs.freebsd.org/en/books/handbook/serialcomms/#serialconsole-setup > > But it seems like you will need some help from your hardware vendor in > order to figure out how to enable Serial Over LAN properly on the > firmware. > > Note that you should be able to get the output of both the FreeBSD > loader and kernel on the serial console. > > Regards, Roger. > From nobody Fri Aug 13 08:08:01 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id E21F11763775 for ; Fri, 13 Aug 2021 08:08:03 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 4GmGQC5hPhz3GB6 for ; Fri, 13 Aug 2021 08:08:03 +0000 (UTC) (envelope-from lizbethmutterhunt@gmail.com) Received: by mail-wr1-x431.google.com with SMTP id b13so12112843wrs.3 for ; Fri, 13 Aug 2021 01:08:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KGM/l93s8nvwqrNrZFff+Y6xv87og7o1PDJjxtA+1bE=; b=UL2mvHlExPzJrEc+0K3VHntj7l4FJW8lB8PYKr92RNO076LHxQFBc28YExUX/XnWF5 QGztTOfN659VgUunLjfNOcam5OQ14pWLlEjUfh9NHfoTxc/urR2ygJSkJ0fbI/JlAUBr p+PCR9qFYZBskaAlvCUmB2M75vh4xz/mDNI62XDq0mhQBA2bagdVY+kDk2YIfDZI9VaA MdxNHIO4+EgWXAeYGymvDag8S1QX2BpPFOlnc6rtH55dWF9v0P7CypiyVFdUlP5MRcp9 P+1+qFsw6RnTlARoTsmw8GxSxeYBR81VG3HVDhCkBC7Q8p9qqmy87zm8o21bxcIzhScP NZFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KGM/l93s8nvwqrNrZFff+Y6xv87og7o1PDJjxtA+1bE=; b=r0edMhKiSavgfU9DtnJohkWrosMUDIXDAluYA2Fpuu+xNJDIyy+kzamzWhidLPmpQA PqXLeo4v4pw9QCOKa8c+GSVr9u/mZ4oBkRAJhEy2Se3mdLYgJz4qsgaTyueEIIox3FHD rBm3BtgX/hfqUYJRVTit6CO3o900+PWjmszV/LbsK8JjGbzPY5kdXdwPronxvZDcXpRR WXUL04TBs8ForAK6dxPuZ5IoDb7iXZ3w3JfQkigeS4ispvapCFmCbQ1U0DU1tjH3LIbF 3e+8A7mrfyEPsU+tjUFiQJpP91wpMQwewrxG+erCwMS1tFzt2cgmfgCF/M9e9JbYKBi8 iGRA== X-Gm-Message-State: AOAM532HvA1F4o6V7ZDjb+PxJTK6Qbho3mYqpSXSeohjNEn3BA+VvRt7 G1rNvm9CZ0hRGIRqsreb0Bw= X-Google-Smtp-Source: ABdhPJz1RWXTtq4gurZ49k2unH42Vdv5hTGtwjSqHVt9xR73boHLDcGjzIsVNzSC+KT2SfQ4KsZ6vA== X-Received: by 2002:a05:6000:18a5:: with SMTP id b5mr1567949wri.184.1628842082740; Fri, 13 Aug 2021 01:08:02 -0700 (PDT) Received: from smtpclient.apple (91-115-224-145.adsl.highway.telekom.at. [91.115.224.145]) by smtp.gmail.com with ESMTPSA id u5sm771816wrr.94.2021.08.13.01.08.01 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Aug 2021 01:08:02 -0700 (PDT) Content-Type: text/plain; charset=utf-8 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3691.0.3\)) Subject: Re: another xen-kernel UEFI story From: "Lizbeth Mutterhunt, Ph.D" In-Reply-To: <9cf13949-3436-ce43-9884-d7a028c940fb@gmail.com> Date: Fri, 13 Aug 2021 10:08:01 +0200 Cc: "freebsd-xen@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <14457636-F600-4C4A-A808-09EE87133EA7@gmail.com> References: <3839452.BRNeRiNLvY@freebsd_current> <3837161.BRNeRiNLvY@freebsd_current> <0FD46B61-6556-4912-814F-4A26988CC23E@gmail.com> <9cf13949-3436-ce43-9884-d7a028c940fb@gmail.com> To: Gerd Hafenbrack X-Mailer: Apple Mail (2.3691.0.3) X-Rspamd-Queue-Id: 4GmGQC5hPhz3GB6 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N > Op 12 aug. 2021, om 18:56 heeft Gerd Hafenbrack = het volgende geschreven: >=20 > Hello, >=20 > The ASUS P8H77M-Pro has an internal serial connector onboard. Lizbeth = should get a DB9 male slot bracket with 10 pin internal connector and a = null modem cable. >=20 > Regards, Gerd >=20 > On 2021-08-12 18:45, Roger Pau Monn=C3=A9 wrote: >> On Thu, Aug 12, 2021 at 03:52:55PM +0200, Lizbeth Mutterhunt, Ph.D = wrote: >>>=20 >>>=20 >>>> Op 12 aug. 2021, om 09:01 heeft Roger Pau Monn=C3=A9 = het volgende geschreven: >>>>=20 >>>> Adding the freebsd-xen mailing list again. >>>>=20 >>>> On Wed, Aug 11, 2021 at 12:48:55AM +0200, Lizbeth Mutterhunt, Ph.D = wrote: >>>>> Op Tuesday, 10 August 2021 15:32:45 CEST schreef u: >>>>>> On Tue, Aug 10, 2021 at 02:41:34PM +0200, = lizbethmutterhunt@gmail.com >>>>> wrote: >>>>>>> Op Tuesday, 10 August 2021 09:38:58 CEST schreef u: >>>>>>>> On Mon, Aug 09, 2021 at 05:23:27PM +0200, = lizbethmutterhunt@gmail.com >>>>> wrote: >>>>>>>>> could someone pleas check this link: >>>>>>>>>=20 >>>>> = https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.8155 >>>>>>>>> 6/ >>>>>>>>>=20 >>>>>>>>> does anyone has another idea then duplicating CURRENT and = RELEASE >>>>> via >>>>>>>>> Virtualbox or qemu? >>>>>>>>>=20 >>>>>>>>> XEN simply doesn't boot after setting xen_kernel on in >>>>>>>>> /boot/loader.conf, >>>>>>>>> we tried different ways but none worked. It's loading [text], >>>>> [data], >>>>>>>>> [syms] and the preconfig but afterwards there's just the >>>>> reset-button >>>>>>>>> option, because XEN doesn't boot. >>>>>>>>>=20 >>>>>>>>> any help appreciated! >>>>>>>>=20 >>>>>>>> Hello, >>>>>>>=20 >>>>>>> hello royger! >>>>> hija! >>>>>=20 >>> Hello Roger! >>>=20 >>>>>>>=20 >>>>>>>> There are a couple of things to look at, first of all, do you = have a >>>>>>>> serial console attached to the box? >>>>>>>=20 >>>>>>> I guess so, because there are two possibilities to start from = via >>>>> primary >>>>>>> and secodary console! >>>>>>=20 >>>>>> The serial console is a port (usually a RS-232) on your box that = you >>>>>> attach a cable to and connect to another computer, so you can get >>>>>> early text debug output: >>>>>>=20 >>>>>> https://www.computerhope.com/jargon/s/serial-console.htm >>>>>> https://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/intro-why.html >>>>> Basically I know the RS-232 "live" in the 80s, and I was soldering = a earth- >>>>> cable to connect two PCs without any swith via a deviate of = Midnight >>>>> Commander. So first thought, enable serial port in bios; computer = crashing >>>>> at >>>>> xen and crashes when allocating the re0. so disabled again! >>>>=20 >>>> I 'm afraid I'm a bit lost here, so your computer does have some = kind >>>> of serial port? >>>=20 >>> No, no RS-232 output of course but a parallel and serial console in = the BIOS! I activated the serial port and got in troubles with booting; = beasties logo has been disabled, so no boot menu to unset the xen_xernel = at boot prompt. XEN never booted anyway. >>>=20 >>>> Do you mean that when you enable the serial port in BIOS (I assume = a >>>> Serial Over LAN) >>> Yup! >>>> the re0 network interface stops working. >>> Yes, at the dhclient allocations it stops immediately with no output = or debugger info at all. Also the keyboard was disabled and I couldn=E2=80= =99t press CTRL+C for avoiding DHCPREQUEST. >> I think it would be better to get Xen out of the picture here, and >> initially focus on getting a serial console working with plain >> FreeBSD. >> Once you have that it should be trivial to attempt to boot >> Xen and get the output on the serial, but first you need to have it >> working properly with plain FreeBSD. >> The handbook contains a good section about how to get it working: >> = https://docs.freebsd.org/en/books/handbook/serialcomms/#serialconsole-setu= p >> But it seems like you will need some help from your hardware vendor = in >> order to figure out how to enable Serial Over LAN properly on the >> firmware. >> Note that you should be able to get the output of both the FreeBSD >> loader and kernel on the serial console. >> Regards, Roger. Was big update on Mac beta 5 Monterey, no difference audio out doesn=E2=80= =99t work. Heading over to BSD now and trying the link given with 10 IO = PINS on one protocol bit, like tcp/ip always was.=20 Lizbeth=20