"Qemu-system-ppc 64 (:)
--machine help" mac99
--cpu help" choose CPU of the host machine .
The above needs to be added to the lines in BHyve which start the qemu instance.
Nathan Whitehorn has formerly stated that there is a problem with the software of IBM's PowerVM hypervisor. Is it possible to fix if IBM open sources PowerVM? If not, could the BHyve hypervisor be reprogrammed to follow the same functions.
There is no current graphical interface for any non i386/ and64 qemu or other emulated system. Functions such as USB access are not possible. Hypothetical situations such as access to USB graphics and audio cards could are not able to be tested. The virtual machine monitor needs to have these options. Facilitation of the execution of command line start of the virtual machine monitor requires the writing of an executable shell script:
#/bin/sh qemu-system-ppc64 --machine $MACHINE --cpu $CPU --memory $RAM_AMOUNT --diac $DISC --$USB_OPTIONS --$OTHER_OPTIONS
I have not been able to have more focus on the parts of BHyve because I need to focus on redirecting software to search for the flattened device tree.
On none ppc64 RISC machines, having programs search for hardware means writing the path to the architecture equivalent of the flattened device tree
I have done the testing using termyx on aarch64 and by looking for the device tree in FreeBSD source for ppc64 while working on brltty port to ppc64.
When I have my current dual core ppc64 970 iMac G5 machine set up, I will retest on native bare metal.
The first option of generic input would need to be loaded when Open Firmware loads the kernel and base modules into the RAM. Other boot loaders should function in a similar way.
The secondary driver would need to be chain loaded after firmware load to provide full functionality.
Unless the qemu options provide direct access to USB devices - and this would require the xorg xproto protocol which is not properly functioning on FreeBSD - testing software such as brltty will not work. I have already tested this option. Bluetooth access is limited even in VirtualBox and VMWare. Even this is a hypothetical work around.