Date: Mon, 2 Dec 2024 16:19:04 -0800 From: Mark Peek <mp@freebsd.org> To: Mario Marietto <marietto2008@gmail.com> Cc: Mark Peek <mp@freebsd.org>, =?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: <CAGGgMJchMJv=vFsk_=Wm3xjdGnYsKXLMo2_hoFYawfeUguQ6oA@mail.gmail.com> In-Reply-To: <CA%2B1FSigejmmCyt5QfSxT2SkYEf0iLj6k6boT9inViasiQRnKng@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> <CA%2B1FSiiYoxPCLcAhc=04WXnNwPMiWwxo9KDO_bYTgdQnFRw3Kg@mail.gmail.com> <CAGGgMJc2ceOOQ9Lcj1MbakXav3SLOHNTFo3Na8G5c-5SEpnzvw@mail.gmail.com> <CA%2B1FSigejmmCyt5QfSxT2SkYEf0iLj6k6boT9inViasiQRnKng@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Mon, Dec 2, 2024 at 4:01 PM Mario Marietto <marietto2008@gmail.com> wrote: > --> Please read the bug I mentioned (comments #1 and #2) where the > submitter only compiled a new vmm.ko and it didn't work without the > corresponding bhyve. > > This is the reason why I asked : > > Can you offer a quick technical explanation of the reason why the exchange > of the modules does not work for me ? > > and you didn't give me any answer. There should be no need to recompile > vmm at all,because the first thing I did was to copy vmm.ko,bhyve-win and > bhyve-lin from the UFS system where the problem is not present,to the ZFS > system,where the problem is present. I have recompiled vmm.ko only for the > sake of my curiosity. > If I had steps to recreate and reproduce the issue on my system then I might be able to get to a full root cause on why it would occur differently. Feel free to provide steps to reproduce it that does not include sending me your binaries. I'll go back to your original email that ended with "Any suggestions about how I can fix it ?". I suggested the existing bug is likely the same issue and I've said multiple times it requires both vmm.ko *and* bhyve. At this point there is not much more I can do for you on this issue beyond what I have stated. Mark [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, Dec 2, 2024 at 4:01 PM Mario Marietto <<a href="mailto:marietto2008@gmail.com">marietto2008@gmail.com</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>--> Please read the bug I mentioned (comments #1 and #2) where the submitter only compiled a new vmm.ko and it didn't work without the corresponding bhyve.</div><div><br></div><div>This is the reason why I asked :</div><div><br></div><div> Can you offer a quick technical explanation of the reason why the exchange of the modules does not work for me ?</div><div><br></div><div>and you didn't give me any answer. There should be no need to recompile vmm at all,because the first thing I did was to copy vmm.ko,bhyve-win and bhyve-lin from the UFS system where the problem is not present,to the ZFS system,where the problem is present. I have recompiled vmm.ko only for the sake of my curiosity.</div></div></blockquote><div><br></div><div>If I had steps to recreate and reproduce the issue on my system then I might be able to get to a full root cause on why it would occur differently. Feel free to provide steps to reproduce it that does not include sending me your binaries.</div><div><br></div><div>I'll go back to your original email that ended with "Any suggestions about how I can fix it ?". I suggested the existing bug is likely the same issue and I've said multiple times it requires both vmm.ko *and* bhyve. At this point there is not much more I can do for you on this issue beyond what I have stated.</div><div><br></div><div>Mark</div></div></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGGgMJchMJv=vFsk_=Wm3xjdGnYsKXLMo2_hoFYawfeUguQ6oA>