Date: Sat, 20 Apr 2024 14:11:38 +0200 From: Mario Marietto <marietto2008@gmail.com> To: FreeBSD virtualization <freebsd-virtualization@freebsd.org>, freebsd-hackers <freebsd-hackers@freebsd.org>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Trying to virtualize ReactOS with bhyve : I don't see a viable way to do it... Message-ID: <CA%2B1FSijJMLGyLj-n9DGdOdwJuP9e_W=DcyPZBG=EAk96jKyy4w@mail.gmail.com> In-Reply-To: <CA%2B1FSihkrqEWgqxHDqNt%2BQkeBBdygUVj2c5kapSmLC332o9b1A@mail.gmail.com> References: <CA%2B1FSihkrqEWgqxHDqNt%2BQkeBBdygUVj2c5kapSmLC332o9b1A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000677a0e0616861d3b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable UPDATE : I've been able to unfreeze ReactOS on the boot stage. I've just removed the bhyve "-A" offending parameter that can't be used because ReactOS probably does not support ACPI. Now I'm at this stage : https://ibb.co/Dtw8Hj1 Now the problem is that I can't move the mouse inside the vm and the keyboard does not work...so I need to find some workaround to supply the absence of the arbiter... I've thought about using virtio-input and I've added this parameter to bhyve : -s 12,virtio-input,/dev/input/event7 \ I've chosen event7,because I've got it here : [root@marietto /bhyve]=3D=3D> ls /dev/input/ event0 event1 event2 event3 event4 event5 event6 event7 Anyway I also tried event6,event5...it didn't work. Can someone quickly explain how it works ? Is it supposed to work even if ReactOS does not have the arbiter ? More precisely the ReactOS developer said : "Hardware initialization doesn=E2=80=99t occur on UEFI due to missing arbiter support : It means tha= t the hardware (even essential such as input devices) will not work and you may not be able to interact with the system in any way" My idea is to use Barrier to be able to use the mouse and keyboard inside the vm...I will install the server on freebsd and the client inside the reactos vm... Could it work as long as reactOS has a network connection ? Let me know. On Fri, Apr 19, 2024 at 3:52=E2=80=AFPM Mario Marietto <marietto2008@gmail.= com> wrote: > Hello. > > I'm trying to boot the 32 bit ISO image of ReactOS using bhyve or qemu an= d > seabios as bootloader. > > As first experiment I tried to boot the x86 version of ReactOS with qemu > (8.2.2) and seabios (version 1.16.1_1),like this : > > qemu-system-x86_64 -machine q35 -m 1G -cdrom > /home/marietto/Desktop/Downloads/OS/ReactOS/reactos-livecd-0.4.15-dev-792= 1-g6d853be-x86-msvc-win-dbg.iso > -boot order=3Dd > > Unfortunately,I get the error below : > > https://ibb.co/tZmFh2x > > but my real goal is to boot ReactOS by using seabios. Even here I'm > unlucky. Infact on this web page : > > https://eradman.com/posts/bhyve-ipxe.html > > we can read : > > *Bhyve is somewhat similar to QEMU-KVM without the emulation required to > boot SeaBIOS.* > > Is really true that I can't use seabios to boot ReactOS with bhyve ? > Anyway,ok. I've continued my searching and I found this thread : > > https://forums.freebsd.org/threads/bhyve-with-bios-boot.79794/ > > where we can read : > > *bhyveload has nothing to do with BIOS. As detailed in the man page you > linked to, it is for loading a FreeBSD guest.* > > So,it seems that I can't even use bhyveload. So,what can I use ? What can > I do ? > > I've gone on the ReactOS forum and I've created a thread where > I 've asked how to boot the 64 bit + UEFI version of ReactOS using bhyve. > The developers helped me,but in the end we have done nothing. Because aft= er > some progress,I found this error : > > https://ibb.co/N9QHdnp > > Unfortunately it is frozen when it tries to load the mountmgr.sys driver. > Actually unfixed and no one knows how to fix it. > > Now I'm here,asking for some further ideas and suggestions. > > -- > Mario. > --=20 Mario. --000000000000677a0e0616861d3b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div role=3D"listitem" aria-expanded=3D"true"><div><div><d= iv><div id=3D"m_-554808317421460299gmail-:1jc"><div><div><div><div><div id= =3D"m_-554808317421460299gmail-:pf"><div id=3D"m_-554808317421460299gmail-:= 1f0"><div dir=3D"ltr"><div><div><div><div id=3D"m_-554808317421460299m_6729= 678916918054419gmail-post_content148907"><div>UPDATE :</div><div><br></div>= <div>I've been able to unfreeze ReactOS on the boot stage. I've just removed the= bhyve "-A" offending parameter that can't be used because ReactOS probably does no= t=20 support ACPI. Now I'm at this stage :<br> <br> <a href=3D"https://ibb.co/Dtw8Hj1" target=3D"_blank">https://ibb.co/Dtw8Hj1= </a><br> <br> Now the problem is that I can't move the mouse inside the vm and the=20 keyboard does not work...so I need to find some workaround to supply the absence of the arbiter...<br> <br></div><div>I've thought about using virtio-input and I've added= this parameter to bhyve : <br></div><div><br></div><div>-s 12,virtio-input= ,/dev/input/event7 \</div><div><br></div><div>I've chosen event7,becaus= e I've got it here :</div><div><br></div><div>[root@marietto /bhyve]=3D= =3D> ls /dev/input/<br>event0 event1 event2 event3 event4 event5 event6 = event7</div><div><br></div><div>Anyway I also tried event6,event5...it didn= 't work.</div><div><br></div><div>Can someone quickly explain how it wo= rks ? Is it supposed to work even if ReactOS does not have the arbiter ?<br= ></div><table cellpadding=3D"0"><tbody><tr><td></td></tr></tbody></table></= div></div></div></div></div></div></div></div></div></div></div></div></div= ></div></div></div><div role=3D"listitem" aria-expanded=3D"true"><div><div>= <div><div id=3D"m_-554808317421460299gmail-:1je"><div><div><div><table cell= padding=3D"0"><tbody><tr><td></td></tr></tbody></table></div></div></div></= div></div></div></div></div><table cellpadding=3D"0"><tbody><tr><td></td><t= d rowspan=3D"2"><div dir=3D"ltr"><div>More precisely the ReactOS developer = said : "Hardware initialization doesn=E2=80=99t occur on UEFI due to = missing arbiter support :=20 It means that the hardware (even essential such as input devices) will=20 not work and you may not be able to interact with the system in any way&quo= t;</div><div><br></div><div><div role=3D"listitem" style=3D""><div class=3D= "gmail-"><div aria-label=3D"At 11:40 AM Saturday, April 20, mariozio wrote,= I wanna try to use barrier to be able to use mouse and keyboard inside the= vm...I will install the server on freebsd and the client inside the reacto= s vm..." id=3D"gmail-post_fq3daagnztdymxpxg7hiu596hy" tabindex=3D"0" class= =3D"gmail-a11y__section gmail-post gmail-same--root gmail-current--user gma= il-same--user"><div role=3D"application" class=3D"gmail-post__content"><div= class=3D"gmail-post__img">My idea is to use Barrier to be able to use the = mouse and keyboard inside the vm...I will install the server on freebsd and= the client inside the reactos vm...</div></div></div></div><div style=3D"d= isplay:inline;width:0px;height:0px;overflow:hidden;margin:0px;padding:0px">= </div></div><div role=3D"listitem" style=3D""><div class=3D"gmail-"><div ar= ia-label=3D"At 11:41 AM Saturday, April 20, mariozio wrote, it should work = or not ? as long as react os has a network connection" id=3D"gmail-post_xz5= ap1txzbdzpcqjzi5gxf3soc" tabindex=3D"0" class=3D"gmail-a11y__section gmail-= post gmail-same--root gmail-current--user gmail-same--user"><div role=3D"ap= plication" class=3D"gmail-post__content"><div class=3D"gmail-post__img"></d= iv><div><div class=3D"gmail-post__header"><div class=3D"gmail-col gmail-d-f= lex gmail-align-items-center"></div><div class=3D"gmail-col gmail-post-menu= "></div></div><div class=3D"gmail-post__body" id=3D"gmail-xz5ap1txzbdzpcqjz= i5gxf3soc_message"><div class=3D"gmail-AutoHeight" style=3D"width:100%;heig= ht:auto;overflow:visible"><div><div class=3D"gmail-post-message gmail-post-= message--collapsed"><div style=3D"max-height:600px" class=3D"gmail-post-mes= sage__text-container"><div tabindex=3D"0" id=3D"gmail-postMessageText_xz5ap= 1txzbdzpcqjzi5gxf3soc" class=3D"gmail-post-message__text" dir=3D"auto"><p>C= ould it work=C2=A0 as long as reactOS has a network connection ?=C2=A0</p><= p>Let me know.</p></div></div></div></div></div></div></div></div></div></d= iv></div></div></div></td></tr></tbody></table><table cellpadding=3D"0"><tb= ody><tr><td colspan=3D"3"><table cellpadding=3D"0"><tbody><tr><td><div id= =3D"m_-554808317421460299gmail-:1lr" aria-haspopup=3D"true" role=3D"button"= aria-label=3D"Show details"><img src=3D"https://mail.google.com/mail/u/0/i= mages/cleardot.gif" alt=3D""></div></td></tr></tbody></table></td></tr></tb= ody></table></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"= gmail_attr">On Fri, Apr 19, 2024 at 3:52=E2=80=AFPM Mario Marietto <<a h= ref=3D"mailto:marietto2008@gmail.com" target=3D"_blank">marietto2008@gmail.= com</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg= in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e= x"><div dir=3D"ltr"><div>Hello.</div><div><br></div><div>I'm trying to = boot the 32 bit ISO image of ReactOS using bhyve or qemu and seabios as boo= tloader.=C2=A0</div><div><br></div><div>As first experiment I tried to boot= the x86 version of ReactOS with qemu (8.2.2) and seabios (version 1.16.1_1= ),like this :<br></div> <br> qemu-system-x86_64 -machine q35 -m 1G -cdrom=20 /home/marietto/Desktop/Downloads/OS/ReactOS/reactos-livecd-0.4.15-dev-7921-= g6d853be-x86-msvc-win-dbg.iso -boot order=3Dd<br><div><br></div><div>Unfortunately,I get the error below= :</div> <br> <div><a href=3D"https://ibb.co/tZmFh2x" target=3D"_blank">https://ibb.co/tZ= mFh2x</a></div><div><br></div><div>but my real goal is to boot ReactOS by u= sing seabios. Even here I'm unlucky. Infact on this web page :</div><di= v><br></div><div><a href=3D"https://eradman.com/posts/bhyve-ipxe.html" targ= et=3D"_blank">https://eradman.com/posts/bhyve-ipxe.html</a></div><div><br><= /div><div>we can read :</div><div><br></div><div><b>Bhyve is somewhat simil= ar to QEMU-KVM without the emulation required to boot SeaBIOS.</b></div><div><br></div><div>Is really true that I can't use s= eabios to boot ReactOS with bhyve ? <br></div><div>Anyway,ok. I've cont= inued my searching and I found this thread :<br></div><div><br></div><div><= a href=3D"https://forums.freebsd.org/threads/bhyve-with-bios-boot.79794/" t= arget=3D"_blank">https://forums.freebsd.org/threads/bhyve-with-bios-boot.79= 794/</a></div><div><br></div><div>where we can read :</div><div><br></div><= div><b>bhyveload has nothing to do with BIOS. As detailed in the man page y= ou linked to, it is for loading a FreeBSD guest.</b></div><div><br></div><d= iv>So,it seems that I can't even use bhyveload. So,what can I use ? Wha= t can I do ? <br></div><div><br></div><div>I've gone on the ReactOS for= um and I've created a thread where=C2=A0</div><div>I 've asked how = to boot the 64 bit + UEFI version of ReactOS using bhyve. The developers he= lped me,but in the end we have done nothing. Because after some progress,I = found this error :<br></div> <br> <a href=3D"https://ibb.co/N9QHdnp" target=3D"_blank">https://ibb.co/N9QHdnp= </a><br> <br> Unfortunately it is frozen when it tries to load the mountmgr.sys driver. A= ctually unfixed and no one knows how to fix it. <br><div><br></div><div>Now= I'm here,asking for some further ideas and suggestions.<br></div><div>= <br></div><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"= ltr" class=3D"gmail_signature">Mario.<br></div></div> </blockquote></div><br clear=3D"all"><br><span class=3D"gmail_signature_pre= fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">Mario.<br></d= iv> --000000000000677a0e0616861d3b--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B1FSijJMLGyLj-n9DGdOdwJuP9e_W=DcyPZBG=EAk96jKyy4w>