From nobody Mon Dec 2 21:07:45 2024 X-Original-To: freebsd-virtualization@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 4Y2GbY585qz5gRYK for ; Mon, 02 Dec 2024 21:08:25 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0: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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Y2GbX2BYkz41q0; Mon, 2 Dec 2024 21:08:24 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=DXpAf8P8; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::530 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pg1-x530.google.com with SMTP id 41be03b00d2f7-7fbc65f6c72so4507427a12.1; Mon, 02 Dec 2024 13:08:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733173702; x=1733778502; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3hTNSLC4XjFtZtoKGjbOR5kSOZJFGB8tCp6PPKPaKW8=; b=DXpAf8P8V9xpF2arIQKh9hGlx82MaMmRSz1KFWIVJnkZdWB7Q1VH4M0GYRVP1KsxYt U00XR6FFdDP91DlZFStV6PlzYULjGKdw/qJcII3VMT+T39roPGQ8AHQq/GXJW61k7mPZ 1n3gtWNW9T9Z1HrQ5Q3R5J2Ea8+EJGpzKJwXmVyxRt3HxaaoWYgZgWgoRsAF3Yss7a4Q BEQKzurq60i91DqXXdd6h+wBlG9fREZ6cB4hDe6FzQdKSqE7ie1EXTGyWPNv5v4Crz20 g9+3t0cfGt+mIuZUjVb6yAs+boR3aAdoL7ZXZQC2Rlo238G+i5TzPJtllMS+w2C6Di9o GrxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733173702; x=1733778502; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3hTNSLC4XjFtZtoKGjbOR5kSOZJFGB8tCp6PPKPaKW8=; b=JPe4aj0DopcPbeIsPYwCqHceqg8wFdF7qDAQP4y9B9Sac9znk354CJOWFugxxObRTY Dg/aKaJFubWsGgr4Kuw2vCJ4RUaD7DPe8U8GeIbuB1HcVkX7SCRdYooKVf9cGknycmN0 mYwAKG/542nImBr6C8StxB2aHmXOg2YZDGaseoqN0AvunefYw3rSId7+ZXl1KzzVRZFI i7I3nyuU4bhG/I0bemmMW7qIrNpvbQjjf3z9d2WrybE35j//m45Dc0jRwrriQxJ//GHR 3zJ0WpwXFeLQsCZwSUzvhDyc3KpTl5JIvUCJBv187s9mBUfv8DGeDYlH1IrlqGkZlJuc zB+w== X-Forwarded-Encrypted: i=1; AJvYcCX4TksYn90ObDQjeqd0RxPtbx7mjKVxdwH8hFqTrSUiNcVcQRPUlB6/avyM3DuseGqMlOOViL6+YEHwyKbgj7VjMfN+pH1h@freebsd.org X-Gm-Message-State: AOJu0YxKvBL/8sh9KGL+fEKTTiGjtazgwaAu1zES2LPVMr/IGMNfmpsD IYXc2VcbH7mzf/VZDE9KOYANkRMudbb/+vEjRgKZ7FZSt6F9NB//V0w9X3B2uWqkSj7LXafmWZk 9NM9OlPBNcSGaSmtqGqc6hpIDMT1AORMmsv8= X-Gm-Gg: ASbGncs9TvyLZ6neLP/MkDVk9X4J4Adk64oZAKNfmtUibi0qR3/9nzKoH+st9MEj8aW gcVIf+0BldiKsq+W5Kim5hke3ipOi4K48 X-Google-Smtp-Source: AGHT+IGQ3wgMXJdLXANbFGa2bn1UwaCEobFb+pfiN7/IF5LXoSo760nVq9lngN73bgfJgDYDJEA5D8svkXbd8j0rKrU= X-Received: by 2002:a17:90b:5405:b0:2ee:fb6b:7d7e with SMTP id 98e67ed59e1d1-2eefb6b7e27mr1077883a91.30.1733173701999; Mon, 02 Dec 2024 13:08:21 -0800 (PST) List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Mon, 2 Dec 2024 22:07:45 +0100 Message-ID: Subject: Re: Failed to emulate instruction sequence [ 41f646040874064c017d88eb144c89 ] at 0xbea5fcf9 To: Mark Peek Cc: =?UTF-8?Q?Corvin_K=C3=B6hne?= , FreeBSD virtualization Content-Type: multipart/alternative; boundary="000000000000d785b406284ff21d" X-Spamd-Result: default: False [-1.55 / 15.00]; HTTP_TO_IP(1.00)[]; URI_COUNT_ODD(1.00)[5]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.55)[-0.546]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_ALL(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::530:from]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4Y2GbX2BYkz41q0 X-Spamd-Bar: - --000000000000d785b406284ff21d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I forgot to say that I have also exchanged the whole boot folder. And nope,even this didn't work. On Mon, Dec 2, 2024 at 10:04=E2=80=AFPM Mario Marietto wrote: > Hello Mark, > > I see that your patch is about to modify the code of the vmm.ko module. > I've just exchanged the vmm.ko module that I'm using on the ZFS system wi= th > the module that I use on the UFS system (where I don't see the error) but > this operation didn't solve the problem. I suspect that the wrong code is > not inside the vmm.ko module. Can you offer a quick technical explanation > of the reason why the exchange of the modules does not work for me ? > > On Mon, Dec 2, 2024 at 9:14=E2=80=AFPM Mark Peek wrote: > >> On Mon, Dec 2, 2024 at 11:54=E2=80=AFAM Mario Marietto >> wrote: >> >>> Hello to everyone. >>> >>> Recently I've upgraded one of my FreeBSD systems and I see a strange >>> error when I try to boot Android 7.1.1. I have never seen this error be= fore >>> and I also have another system where I haven't applied the latest pkg >>> upgrades where Android is still able to boot. >>> The bhyve parameters that I use in both systems are the following : >>> >>> /usr/sbin/./bhyve -S -c sockets=3D2,cores=3D2,threads=3D2 -m 8G -w -H -= A \ >>> -s 0,hostbridge \ >>> -s >>> 1,ahci-hd,/mnt/zroot-133/bhyve/img/Android/DarkMatter-qemu.img,bootinde= x=3D1 \ >>> -s 8:0,passthru,4/0/0 \ >>> -s 11,hda,play=3D/dev/dsp,rec=3D/dev/dsp \ >>> -s 13,virtio-net,tap13 \ >>> -s 29,fbuf,tcp=3D0.0.0.0:5913,w=3D1440,h=3D900,wait \ >>> -s 30,xhci,tablet \ >>> -s 31,lpc \ >>> -l >>> bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CODE.fd,/usr/local/sh= are/uefi-firmware/BHYVE_UEFI_VARS.fd >>> \ >>> vm0:13 < /dev/null & sleep 5 && vncviewer 0:13 && echo vncviewer 0:13 & >>> >>> The error I get on this ZFS system : >>> >>> FreeBSD marietto 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 GENERIC amd64 >>> >>> is : >>> >>> *Failed to emulate instruction sequence [ 41f646040874064c017d88eb144c8= 9 >>> ] at 0xbea5fcf9* >>> >>> But I don't get this error on the system installed on the UFS disk (it >>> is also 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 GENERIC amd64). Any >>> suggestions about how I can fix it ? >>> >> >> >> This looks like a duplication of this bug: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282852 >> >> I need to tweak the patch (attached to the bug) before submitting for >> review. Note that both the kernel and bhyve need to be recompiled after >> applying the patch. >> >> Mark >> >> > > > -- > Mario. > --=20 Mario. --000000000000d785b406284ff21d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I forgot to say that I have also exchanged the whole boot = folder. And nope,even this didn't work.

On Mon= , Dec 2, 2024 at 10:04=E2=80=AFPM Mario Marietto <marietto2008@gmail.com> wrote:
Hello Mark,=

I see that your patch is about to modify the code= of the vmm.ko module. I've just exchanged the vmm.ko module that I'= ;m using on the ZFS system with the module that I use on the UFS system (wh= ere I don't see the error) but this operation didn't solve the prob= lem. I suspect that the wrong code is not inside the vmm.ko module. Can you= offer a quick technical explanation of the reason why the exchange of the = modules does not work for me ?

On Mon, Dec 2, 2024 at 9:14=E2=80= =AFPM Mark Peek <mp@= freebsd.org> wrote:
On Mon, Dec 2, 2024 at 11:54= =E2=80=AFAM Mario Marietto <marietto2008@gmail.com> wrote:
Hello to everyone.

Recently I've upgra= ded one of my FreeBSD systems and I see a strange error when I try to boot = Android 7.1.1. I have never seen this error before and I also have another = system where I haven't applied the latest pkg upgrades where Android is= still able to boot.
The bhyve parameters that I use in both= systems are the following :

/usr/sbin/./bhyve -S = -c sockets=3D2,cores=3D2,threads=3D2 -m 8G -w -H -A \
-s 0,hostbridge \<= br>-s 1,ahci-hd,/mnt/zroot-133/bhyve/img/Android/DarkMatter-qemu.img,bootin= dex=3D1 \
-s 8:0,passthru,4/0/0 \
-s 11,hda,play=3D/dev/dsp,rec=3D/de= v/dsp \
-s 13,virtio-net,tap13 \
-s 29,fbuf,tcp=3D0.0.0.0:5913,w=3D1440,h=3D900,wait \
= -s 30,xhci,tablet \
-s 31,lpc \
-l bootrom,/usr/local/share/uefi-firm= ware/BHYVE_UEFI_CODE.fd,/usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd \=
vm0:13 < /dev/null & sleep 5 && vncviewer 0:13 &&= ; echo vncviewer 0:13 &

The error I get on thi= s ZFS system :

FreeBSD marietto 14.1-RELEASE-p5 Fr= eeBSD 14.1-RELEASE-p5 GENERIC amd64

is :

Failed to emulate instruction sequence [ 41f646040874064= c017d88eb144c89 ] at 0xbea5fcf9

But I don&= #39;t get this error on the system installed on the UFS disk (it is also 14= .1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 GENERIC amd64). Any suggestions about= how I can fix it ?


<= div>This looks like a duplication of this bug:
https://bug= s.freebsd.org/bugzilla/show_bug.cgi?id=3D282852

I need to tweak the patch (attached to the bug) before submitting for rev= iew. Note that both the kernel and bhyve need to be recompiled after applyi= ng the patch.

Mark
=C2=A0


--
Ma= rio.


--
Ma= rio.
--000000000000d785b406284ff21d--