Date: Fri, 2 May 2025 17:21:29 -0400 From: Joe Nosay <superbisquit@gmail.com> To: qemu-ppc@nongnu.org, "freebsd-virtualization@freebsd.org" <virtualization@freebsd.org>, qemu-devel <qemu-devel@nongnu.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: BHyve on POWEr 64bit machines with virtualization support Message-ID: <CA%2BWntOs8z3Fp3G4q=bUHKcMrC=j%2BYZcz-AcsZY-o4M1Gf1ZWKQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] In the source code of BHyve, there is a reference to qemu. The partial solution is to ask the qemu poc and development what the CPU machine parameters would equal the physical CPU. If that is not available, then the virtualization would need to be the most recent CPU software translation. I thought about this; and, you would also need to study what the Xen project did. If you could find a work around for the hypervisor problem on the Cell CPU, then you could test on any PlayStation 3 that still has the other os function. I am aware that the FreeBSD hackers list usually are i386/ and64 hackers; yet, some may have experience withRISC architectures. [-- Attachment #2 --] In the source code of BHyve, there is a reference to qemu. The partial solution is to ask the qemu poc and development what the CPU machine parameters would equal the physical CPU. If that is not available, then the virtualization would need to be the most recent CPU software translation. <div>I thought about this; and, you would also need to study what the Xen project did. </div><div>If you could find a work around for the hypervisor problem on the Cell CPU, then you could test on any PlayStation 3 that still has the other os function. </div><div>I am aware that the FreeBSD hackers list usually are i386/ and64 hackers; yet, some may have experience withRISC architectures.</div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BWntOs8z3Fp3G4q=bUHKcMrC=j%2BYZcz-AcsZY-o4M1Gf1ZWKQ>