Date: Tue, 3 Dec 2024 00:33:22 +0100 From: Mario Marietto <marietto2008@gmail.com> To: Mark Peek <mp@freebsd.org> Cc: =?UTF-8?Q?Corvin_K=C3=B6hne?= <c.koehne@beckhoff.com>, FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: Failed to emulate instruction sequence [ 41f646040874064c017d88eb144c89 ] at 0xbea5fcf9 Message-ID: <CA%2B1FSiiYoxPCLcAhc=04WXnNwPMiWwxo9KDO_bYTgdQnFRw3Kg@mail.gmail.com> In-Reply-To: <CAGGgMJcdSE=FBq%2BOZCf889uhE8n=av_MGrdn3pQe0qM6GQ9CxQ@mail.gmail.com> References: <CA%2B1FSijzwf6xHOv7-CfmdFPmxD46vFEdaJ4V6xy29G4BYEetWA@mail.gmail.com> <CAGGgMJemKNkEB87sHABECYrQT37tzPcF74o6dejAz4=nMApCBQ@mail.gmail.com> <CA%2B1FSigkus=xw6Y%2BQzD8hK9Dmkt6LR1hsY-U8V=yQ3yReTSL8g@mail.gmail.com> <CAGGgMJcVC33joaZ%2BdHsCBMHZ-hZPDt-9E8mL6Nvb=AdbVDQPqA@mail.gmail.com> <CA%2B1FSigZV6GXurd5KmBwVS6LdbOpP1fLK5wEB7-ROAp%2Bz1axsA@mail.gmail.com> <CAGGgMJd%2Box54CyDNk6SgQ29b=Rte=MzpRFbgzM%2BF=QWOV8nu=Q@mail.gmail.com> <CA%2B1FSijkwMk_STP1wCyiX96VY7pn%2BmY-ad0_m1shFTBjQhd57Q@mail.gmail.com> <CAGGgMJcdSE=FBq%2BOZCf889uhE8n=av_MGrdn3pQe0qM6GQ9CxQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] --> 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 AM Mark Peek <mp@freebsd.org> wrote: > On Mon, Dec 2, 2024 at 2:39 PM Mario Marietto <marietto2008@gmail.com> > wrote: > >> ok I've used this : >> >> .op_flags = 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,called >> bhyve-lin and bhyve-win. When I upgrade the system,they cannot change. What >> 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. With >> 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 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 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 > -- Mario. [-- Attachment #2 --] <div dir="ltr"><div>--> Did you reboot or reload the module ?<br></div><div><br></div><div>I have rebooted the machine.</div><div><br></div><div><div>--> Did you use the new bhyve binary you built from the patch ?</div><div><br></div><div>I didn't recompile bhyve,since I don't need it.</div><div><br></div><div>--> Note: copying binaries around from other systems or your custom versions will not be something I can help debug.</div><div><br></div><div>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 :</div><div><br></div><div># pkg update</div><div># pkg upgrade</div><div><br></div><div>I don't have the problem on the UFS disk because I didn't do that. <br></div><div><br></div><div>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.<br></div><div><br></div><div><br></div></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Dec 3, 2024 at 12:09 AM Mark Peek <<a href="mailto:mp@freebsd.org">mp@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Mon, Dec 2, 2024 at 2:39 PM Mario Marietto <<a href="mailto:marietto2008@gmail.com" target="_blank">marietto2008@gmail.com</a>> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>ok I've used this :</div><div><br></div><div>.op_flags = VIE_OP_F_IMM8</div><div><br></div><div>After the compilation is finished,I copied the compiled vmm.ko module from <tt style="color:rgb(0,122,0)">/usr/obj/usr/src/amd64.amd64/sys/modules/vmm/vmm.ko to /boot/kernel and to /boot/modules. <br></tt></div><div><tt style="color:rgb(0,122,0)"><br></tt></div><div><tt style="color:rgb(0,122,0)">Regarding the bhyve executable,I'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'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. With this being said,the recompilation of vmm.ko didn't solve my issue.</tt></div></div></blockquote><div><br></div><div>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 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.</div><div><br></div><div>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.</div><div><br></div><div>Mark </div></div></div> </blockquote></div><div><br clear="all"></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Mario.<br></div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B1FSiiYoxPCLcAhc=04WXnNwPMiWwxo9KDO_bYTgdQnFRw3Kg>