From nobody Wed Dec 28 17:12:14 2022 X-Original-To: freebsd-current@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 4Nhylw0G8Kz2kcMs for ; Wed, 28 Dec 2022 17:13:32 +0000 (UTC) (envelope-from ronald@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 4Nhylv6rhRz3wJ1 for ; Wed, 28 Dec 2022 17:13:31 +0000 (UTC) (envelope-from ronald@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1672247612; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YTVY+hTNW+tNNrf5gZSF+cMoEhurwfCS6zz54pOcKQw=; b=qs74jhD0H+4HQzLy8vFrCfA5OOsX5e5W0LTdEONvQCR6ZrnOOeTqXMtPwmDx993ZjLKna6 l5cWrrUT0GQsQH9fXuMziFGyYJSag/ABKzl4eESTdCHgoVpeoVhCfLyLfLJITqqOMzEayk HinpyNPPuFOXu6nYL/eQBem+TSbvPm1JoRqZYpsBwpuXO/XdX9GsDFpGiLdc6VGgP8GSM5 2Fj/Ln9qIKFkCQEm5pKs/DYOaTvgzgBy7ess0SLNPj8e1oRrd1OOcLQQrIHz/ErZs37yaq GBdtgr5oPZaoq6dw/7oZPH3t43xGjTJjs9utHM8uDp2g7Ao6+almrUxdd6MXAA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1672247612; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YTVY+hTNW+tNNrf5gZSF+cMoEhurwfCS6zz54pOcKQw=; b=IxkW4Gi16TP0WxPJZvDBBmXircg7zxu9+DR//TN+Q0MJfMkTWxwZWd5Ft/M4VRAlI0glyi 9eYqwbzDZT1seZgH2ckl3SVv+aquU2FvwnZs6iP3rMzj0DJb2xjEoI7OMTI9r5cA/OgGtg PLTYIgy1nvObZP2doXDuL5xQmt6HKrqGzh4tVmt/bCaNHZotXmWSut4YokoPGs3UW7r1AE PXBgw23auwEpjYHtctZIyXLwwRAW2VE6n/E94yOsM/P3agpIOjycH/HsSN/1ZxvQpGysf9 A7lV645lgi/3SmNL2Bvr0iV7DftgRiDXngExJzJ74ImPQOjU3rmKj1IHILlHhw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1672247612; a=rsa-sha256; cv=none; b=DHxqVRphdnAqtPJohS7Umk5mSfE/FfvxJXI6lcyUBeLse+lTFi/Sw9sRSI/AbtcHbj94n2 yT4g0haMDY8T2uERdaibcAzleBDQJE9B5rX2W5TxsqCgrrIQ7Qa7Qkeg0ZSj3TqtebkblY 0WkTmZBEaDioQfZWKS27R+SSIUxQiTrOTkzV6sIdo5fwWwefxrDsOjq3JLONHmEK+n0kPu T883V/x3MkSa7PmKeDLVT/h6p5ToPSlm0ULtxFGxM96wyAzBiJqRvZyJp+bLD0D8LMCEJu WRPp9/4znd03312Q1H9/iURdxiTuNyQMMCLG6Vz9MHOPI0Snl2vk2Hgl+4BH/Q== Received: from [192.168.1.109] (85-147-65-221.cable.dynamic.v4.ziggo.nl [85.147.65.221]) (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 did not present a certificate) (Authenticated sender: ronald/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Nhylv49L1zTym for ; Wed, 28 Dec 2022 17:13:31 +0000 (UTC) (envelope-from ronald@FreeBSD.org) Message-ID: Date: Wed, 28 Dec 2022 18:12:14 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: 14.0-CURRENT panic on boot, i386 VirtualBox client Content-Language: en-US To: freebsd-current@freebsd.org References: From: Ronald Klop In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 12/28/22 17:45, Paul Floyd wrote: > Hi > > For quite a few weeks I've been unable to boot 14.0-CURRENT i386 in a VirtualBox VM. I've tried both booting from iso image and the vmdk image. I get a kernel panic > > The host is running 13.1-RELEASE-p3 amd64 > > No problems with 14.0-CURRENT amd64 guests. > > I haven't been able to see the last message before the panic as it scrolls past too quickly. > > Any suggestions for a working either how to get more info or what vbox settings to use? > > A+ > Paul > I've had success to capture errors by recording the screen with my phone and playing back on slow speed. Another option might be to enable serial port for the console of the guest and capture the output. But I don't know if the default ISO uses that and how hard it is to configure VirtualBox to do that properly. Regards, Ronald.