From nobody Sat Apr 20 12:11:38 2024 X-Original-To: freebsd-questions@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 4VM9PG3Nsbz5HgHG; Sat, 20 Apr 2024 12:12:18 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VM9PF1FPcz4CMT; Sat, 20 Apr 2024 12:12:17 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=DGSHM6R4; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::1030 as permitted sender) smtp.mailfrom=marietto2008@gmail.com Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-2a559928f46so1954429a91.0; Sat, 20 Apr 2024 05:12:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713615135; x=1714219935; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=G3XSPvuso1yxRpxP0fxpRYkkuDl1di2B3JRSykDUA44=; b=DGSHM6R4S8dVgV8U/g63uSC5S8f9Zbov1CFdyUmJy4YeNXV8jI119yg/PF63OJWep9 7mKHnVc0uF7I1aEGTeB5WZhe5tGEDlGlgwkPg/U5y8Yy21xwoxmE5Xs48SVl+2wTOFry /5TQjPl0umpIwASRhkbm6Rsp0CNCkNifmWH1oMVl+PCjARcD9DYpS2udVU6pqOI0M2XL x/Ds1TyPpwvSgfV5BHjYP1eDjkZ/2OgYr8gqxTpuXnAAHqTzLgbXFAqR7u5+B7asSNEb HJrQojnotfGvJ0Nx9GZCIPNeD7ULaU1SD737uJT8og8i/Kn1JJL3QqlFXNq/gQh0erWz Pl9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713615135; x=1714219935; h=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=G3XSPvuso1yxRpxP0fxpRYkkuDl1di2B3JRSykDUA44=; b=OavmmiQgfOvYN51xujqeEbNveEnEiLG6AVjFtvn9Y+t2K90+txaviGc9cgaC+nGmPM nm3xhOLzy11VBvnCsbDXEU+4R5ZP1vRmpr4f4kyEB+b0N9K8fQ2tJMan0ac+FV84fdIm Tko7RLUoMHMeR9OuAQ56kTZbySsP9sUWLuEqcE+Xlo2cAWK77Cn10c51vJxF+3mY2cdF eGrfza8Ra8LnWwpnovstQLeG2askLLWiWUNAys+zHSf+/viNiMt8uT8fj+w4AW7POf2Y mVkfZTzHjp9KTV2i8rHv0zB9cee9LpWi7N8jgop/PEkNzLvvs18YUFpL7jjK4yS0Y7ia M/hA== X-Forwarded-Encrypted: i=1; AJvYcCUdXIgmCGhNPOMY30tmuron9dBHfsC5quSVbp9nTz+4HNPqgWaVu0MtXqUmvManeP0HLXlTVfzx4OD0yk1vuIdq+DXxd2AEeUGGoNeSgBDtOiRmZL0xpyI+dGjYU18d6auJswqXn9pjinRS X-Gm-Message-State: AOJu0YwXgjKv3IPfzrTfZUvaaU1dqLS+EtK0U+8N+JyuIHwwws3rMLyG ix1L6plL+/qoWvN5nGzKd6SehSrpbRIJg3POgLHMf0CumYcmFDE0HMLEfzgFo9oPeRmD0Ad1PEC ik6fszuL+zqRfO2VT+LBkTgkP5BMEv/HYhYQ= X-Google-Smtp-Source: AGHT+IGzDHRnyPo9Bkgiv6fTvOGPpbhaNHeWYE3nh3tmxr/AeUMuHHvf1rNdu01WWGJmV3jWJNgsvwtvDpPT9KdE7NA= X-Received: by 2002:a17:90a:a085:b0:2a0:4495:1f3d with SMTP id r5-20020a17090aa08500b002a044951f3dmr5641483pjp.0.1713615135010; Sat, 20 Apr 2024 05:12:15 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Sat, 20 Apr 2024 14:11:38 +0200 Message-ID: Subject: Re: Trying to virtualize ReactOS with bhyve : I don't see a viable way to do it... To: FreeBSD virtualization , freebsd-hackers , FreeBSD Mailing List Content-Type: multipart/alternative; boundary="000000000000677a0e0616861d3b" X-Spamd-Bar: - X-Spamd-Result: default: False [-1.62 / 15.00]; URI_COUNT_ODD(1.00)[21]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_SPAM_SHORT(0.38)[0.379]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1030:from]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org,freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4VM9PF1FPcz4CMT --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 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
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 no= t=20 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=20 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,becaus= e 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 wo= rks ? 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 :=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;

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...
=

C= ould it work=C2=A0 as long as reactOS has a network connection ?=C2=A0

<= p>Let me know.

3D""

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 and seabios as boo= tloader.=C2=A0

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=20 /home/marietto/Desktop/Downloads/OS/ReactOS/reactos-livecd-0.4.15-dev-7921-= g6d853be-x86-msvc-win-dbg.iso -boot order=3Dd

Unfortunately,I get the error below= :


but my real goal is to boot ReactOS by u= sing seabios. Even here I'm unlucky. Infact on this web page :


<= /div>
we can read :

Bhyve is somewhat simil= ar to QEMU-KVM without the emulation required to boot SeaBIOS.

Is really true that I can't use s= eabios to boot ReactOS with bhyve ?
Anyway,ok. I've cont= inued my searching and I found this thread :

<= 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/

where we can read :

<= div>bhyveload has nothing to do with BIOS. As detailed in the man page y= ou linked to, it is for loading a FreeBSD guest.

So,it seems that I can't even use bhyveload. So,what can I use ? Wha= t can I do ?

I've gone on the ReactOS for= um and I've created a thread where=C2=A0
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 :

https://ibb.co/N9QHdnp=

Unfortunately it is frozen when it tries to load the mountmgr.sys driver. A= ctually unfixed and no one knows how to fix it.

Now= I'm here,asking for some further ideas and suggestions.
=
--
Mario.


--
Mario.
--000000000000677a0e0616861d3b--