From nobody Mon Dec 2 23:33:22 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 4Y2KqY4wTsz5gdX3 for ; Mon, 02 Dec 2024 23:34:01 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 4Y2KqY2dkPz4HDM; Mon, 2 Dec 2024 23:34:01 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x52d.google.com with SMTP id 41be03b00d2f7-7fcc00285a9so1851113a12.2; Mon, 02 Dec 2024 15:34:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733182439; x=1733787239; 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=vvTChmNJjnq8iRP9g/dOhC/YPwTzPRJavNNZ0Y+LZoA=; b=OHwvmrytjmcFy7FP3e80VxKQUHsYyOi1bXpjdtr/yuGuuDj6QWBqj2a8eNW2djfKgO IceHQlle8E/gnsgvllom/LLrLNCLM2oa0A2DIGAEzKmNF1rfqhzoY/nd1/Fzr+IrXWyb i59GRq1rwP3ikgDLYsbl02SP1NmGlFeVqg4pUP798Jw7LrEW7Y8f7Xkm9wR66K22s1mE xdJsmVB5eELVMIeMYnLhJ0ZKUILotcx6gTc1KA2NgMuUZbws8KZHIRxMP6kfTDrmksHj 4iXlyHAey9ZVvIasSc2PN7u52IGr708iAPKpYRlQHcYneyDp75VOkcuco71xZVCDtRvG OIWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733182439; x=1733787239; 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=vvTChmNJjnq8iRP9g/dOhC/YPwTzPRJavNNZ0Y+LZoA=; b=vcurhT9bbwl0jwmwk5w2g0//ZX42DVu/sF6zjW0HZnvHyuA2nkBRMZeURaVp/GfNoF fOiZ1jk/sjOUuUi2Swqnk9iYr7hwYz7fQNqclPYFIMkmFetvET6kGMuYJ7wo9OkKmYo+ 0gBbkqJosD9ZvIbyqrlGoQmRyt/T+t4yyyhyTD1ou335XUkGZtLtf1uKT7FJozMDn1Mc Lwy2xb98cscKPxXuTwXsaVN0nZsaaeB84sAESzmr+lqzcbCvU3TQniUi5GKVILT1xZBc yn5v0x39Y3vLVBzp/X4m7g2DanRrcfrRnFyLp0XkY+np1ACNoXlRvCSjEnengfXSGFNX D1XQ== X-Forwarded-Encrypted: i=1; AJvYcCVDQEvwFF3WjaTdmPqm9defiYHjt9GDC2HRWzlRQnPGj/UoWUEYM8UDZ1SXJadnFnmjNb+t+YfZseJ/mHWunvcwDm9cEHMy@freebsd.org X-Gm-Message-State: AOJu0YywpotwtcIguikcftDVZovBviPQdZFOf667TUvfO32rRlrNfYd3 0RsH2IK98+5Tz507KE4+v8NS0cUmDiax26SIouoaU6YWGEvO74xignegi7xXhx3UER2VrwsLjLE YaowGezc+wWCpvAQKzXF8zqBYAlh+0Ew5vnE= X-Gm-Gg: ASbGnctDY9XgNQjUrTkRwGvGLa8TQNDnuKB7i+j9j5FPwjrK/MaeeUvPkj3JgEGxJFA ixODsfmlr7TYzfBb2oIJEweerpRkAY5ZaZU3qI2mdHg7SmDUX7w== X-Google-Smtp-Source: AGHT+IHPhSgZ8jgGJfqpxAK3P+7bDAFu3RoTeAlJzS2WaqjBkT66KYl9rHugemKiMzl4Xk/DLL5Q8cuUO2N1gcsn4H8= X-Received: by 2002:a05:6a20:6a1b:b0:1db:f00e:2dfe with SMTP id adf61e73a8af0-1e165412f88mr731429637.39.1733182439122; Mon, 02 Dec 2024 15:33:59 -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: Tue, 3 Dec 2024 00:33:22 +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="0000000000009d70dd062851fb8e" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Y2KqY2dkPz4HDM X-Spamd-Bar: ---- --0000000000009d70dd062851fb8e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable --> Did you reboot or reload the module ? I have rebooted the machine. --> Did you use the new bhyve binary you built from the patch ? I didn't recompile bhyve,since I don't need it. --> Note: copying binaries around from other systems or your custom versions will not be something I can help debug. The system that I have on the UFS disk is not another system. It's the same system that I have on the ZFS disk,without the last round of (latest) packages. I'm sure that the system on the ZFS system started to present the problem when I did : # pkg update # pkg upgrade I don't have the problem on the UFS disk because I didn't do that. I haven't done # freebsd-update on the ZFS and UFS systems for some months,so both are stuck to 14.1-RELEASE-p5 GENERIC. On Tue, Dec 3, 2024 at 12:09=E2=80=AFAM Mark Peek wrote: > On Mon, Dec 2, 2024 at 2:39=E2=80=AFPM Mario Marietto > wrote: > >> ok I've used this : >> >> .op_flags =3D VIE_OP_F_IMM8 >> >> After the compilation is finished,I copied the compiled vmm.ko module >> from /usr/obj/usr/src/amd64.amd64/sys/modules/vmm/vmm.ko to /boot/kernel >> and to /boot/modules. >> >> Regarding the bhyve executable,I'm using two custom versions of it,calle= d >> bhyve-lin and bhyve-win. When I upgrade the system,they cannot change. W= hat >> can change is bhyve,but I don't use it. In addition,to be sure,I copied >> bhyve-lin and bhyve-win from the system where I don't have the error. Wi= th >> this being said,the recompilation of vmm.ko didn't solve my issue. >> > > Did you reboot or reload the module? Did you use the new bhyve binary > you built from the patch? Note: copying binaries around from other system= s > or your custom versions will not be something I can help debug. Only code > built from a newly checked out /usr/src and applying the patch will provi= de > the correct information on whether it works or not. > > But if it didn't solve your issue you should document how it can be > reproduced and either 1) add it to the bug I mentioned or 2) open a new > bug. Make sure to include information on the host system as well > (intel/amd, etc.) and how the various guest bits (.img, .fd, etc) were > download/created. > > Mark > --=20 Mario. --0000000000009d70dd062851fb8e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
--> Did you reboot or reload the module ?

I have rebooted the machine.

=
--> Did you use the new bhyve binary you=C2=A0built from the patch = ?

I didn't recompile bhyve,since I don't n= eed it.

--> Note: copying binaries around from = other systems or your custom versions will not be something I can help debu= g.

The system that I have on the UFS disk is not a= nother system. It's the same system that I have on the ZFS disk,without= the last round of (latest) packages. I'm sure that the system on the Z= FS system started to present the problem when I did :

<= div># pkg update
# pkg upgrade

I don'= ;t have the problem on the UFS disk because I didn't do that.

I haven't done # freebsd-update on the ZFS and UFS= systems for some months,so both are stuck to 14.1-RELEASE-p5 GENERIC.
<= /div>



On Tue, Dec = 3, 2024 at 12:09=E2=80=AFAM Mark Peek <mp@freebsd.org> wrote:
On Mon, Dec 2, 2024 at 2:3= 9=E2=80=AFPM Mario Marietto <marietto2008@gmail.com> wrote:
ok I've used this :

.op_flags =3D VIE= _OP_F_IMM8

After the compilation is finished,I cop= ied the compiled vmm.ko module from /usr/o= bj/usr/src/amd64.amd64/sys/modules/vmm/vmm.ko to /boot/kernel and to /boot/= modules.

Regarding the bhyve executable,I= 9;m using two custom versions of it,called bhyve-lin and bhyve-win. When I = upgrade the system,they cannot change. What can change is bhyve,but I don&#= 39;t use it. In addition,to be sure,I copied bhyve-lin and bhyve-win from t= he system where I don't have the error. With this being said,the recomp= ilation of vmm.ko didn't solve my issue.
<= div>
Did you reboot or reload the module? Did you use the new= bhyve binary you=C2=A0built from the patch? Note: copying binaries around = from other systems or your custom versions will not be something I can help= debug. Only code built from a newly checked out /usr/src and applying the = patch will provide the correct information on whether it works or not.

But if it didn't solve your issue you should docum= ent how it can be reproduced and either 1) add it to the bug I mentioned or= 2) open a new bug. Make sure to include information on the host system as = well (intel/amd, etc.) and how the various guest bits (.img, .fd, etc) were= download/created.

Mark=C2=A0


--
Ma= rio.
--0000000000009d70dd062851fb8e--