run OpenBSD in Parallels Desktop on Apple M1

I just installed the OpenBSD6.9 in my parallels desktop on Mac mini M1.

• I download and install FreeBSD 14.0 current.

I named it as FBSD
https://download.freebsd.org/ftp/sn...ch64-20210610-597cc550e7b-247271-disc1.iso.xz

• clone the VM FBSD in Parallels Desktop Controll Center.

I named it as OBSD

• configure the VM FBSD

1. In tab Hardware, click the "Add {+}" button to add the new Hard Disk.
2. type: exsiting image file, location: from OBSD directory and setlect the FBSD-0.hdd

• start the FBSD

https://cdn.openbsd.org/pub/OpenBSD/6.9/arm64/miniroot69.img
1. copy the miniroot69.img or install69.img, (i use scp, it up to you)
2. `umount /boot/efi`
3. `dd if=miniroot69.img of=/dev/ada1 bs=1m`
4. shutdown and stop this VM

• start the OBSD

`set tty fb0`

 

@CCTW how did you install? I am unable to install any of the BSDs (including FreeBSD) on apple M1 Parallels. I have posted a separate question for install steps, and a poll regarding the same.

 

Hi

There is a bit unclear behaviour of Parallels Destkop. To install BSD download for example https://download.freebsd.org/ftp/sn...aarch64-20211008-67bceb38f46-249945-disc1.iso
Start the new VM wizard and point it to downloaded ISO. Wizard will not recognize OS. Need to choose "Operating System = Linux" (doesn't matter, Ubuntu/Fedora/Debian/Other) while creating VM. Then all should work.

Note: if you are using some older FreeBSD image, need to change OSType to "Other" in VM configuration after VM is created

 

Nope, that doesn't work.
For reference, I am attempting to boot FreeBSD-13.0-RELEASE-amd64-bootonly.iso and no magic I have attempted gets me anywhere but the boot manager.

 

I did find this note:
https://bugs.freebsd.org/bugzilla//show_bug.cgi?id=257618
However, as instructed, adding "vm.bios.efi=1" to the advanced settings in boot options just gives me a dialog box that says PRL_ERR_VM_VALLOC_MON_BODY.
Norman coordinate.

 

Hi
You need aarch64 build of BSD, not the amd64 one

 

This instruction is for amd64. Please remove it if you are on M1.

 

OMG, I feel stupid now. I guess my brain saw a...64 and was like, "that one!"
Naturally the correct image works much better.

 

The idea of running another OS "natively" on an Mac doesn't sound very appealing to me. It's almost certain that you'll never get it (...) everything working perfectly

This is a bit naive. It is still in my memory when this same argument was used regarding the necessity to install Linux on computers integrated with Windows. I can say that it didn't make any difference to me in the past few decades back when I first was installing Mandrake Linux on a Windows laptop. It made no difference for me that I couldn't achieve hardware acceleration or get the webcam to function, while wifi only worked with ndiswrapper. I was able to run the software I wanted to use on the hardware I purchased which is what's important. Chatroom.
M1 Mac minis are available on market for around 800$ this is a decent price . Their design and style makes them an attractive choice to use as a home server, or workstation. It's beyond comprehension if we couldn't benefit from the hardware and run our selection of software.

 

I'm trying so with FreeBSD 13 ARM in M1 pro, but I'm having a loop at the beginning.
What other things should I do try?
Thank you.

 

I create the virtual machine as mentioned above, proceed with the installation from the ISO image and the VM goes in loop. Opening the VM package I read the following in the log, something about Battery (?).

Code:

02-03 18:12:42.849 F /TransMem:85281:143bd4/ CGuestMemoryAnonymous::close_file(del=1)
02-03 18:12:42.849 F /vm:85281:143bd4/ VM state(VmStateStopped): completed pending 'VmLocalCmdKill'(20008) command with result 0x0
02-03 18:12:42.849 F /vm:85281:143bd4/ VM state(VmStateStopped): completed current 'DspVmStateInfo'(3028) command with result 0x80000009
02-03 18:12:42.849 F /vm:85281:143bd4/ VM state(VmStateStopped): completed current 'DspVmStateInfo'(3028) command with result 0x80000009
02-03 18:12:42.850 F /vm:85281:143bd4/ VM state(VmStateStopped): completed current 'DspCmdVmInitiateDevStateNotifications'(1024) command with result 0x80000009
02-03 18:12:42.850 F /vm:85281:143bd4/ VM state(VmStateStopped): completed current 'DspEvtNotifyVm'(3014) command with result 0x80000009
02-03 18:12:42.850 F /vm:85281:143bd4/ VM state(VmStateStopped): completed current 'DspEvtNotifyVm'(3014) command with result 0x80000009
02-03 18:12:42.850 F /vm:85281:143bd4/ Terminating VM Process ...
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Some battery parameters can't be retrieved
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: SerialNumber
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: BatterySerialNumber
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: DesignVoltage
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: Manufacturer
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: ManufactureDate
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Some battery parameters can't be retrieved
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: SerialNumber
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: BatterySerialNumber
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: DesignVoltage
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: Manufacturer
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: ManufactureDate
02-03 18:12:42.850 F /vm:85281:143bbe/ Wait for PC thread completion.
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Some battery parameters can't be retrieved
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: SerialNumber
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: BatterySerialNumber
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: DesignVoltage
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: Manufacturer
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: ManufactureDate
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Some battery parameters can't be retrieved
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: SerialNumber
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: BatterySerialNumber
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: DesignVoltage
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: Manufacturer
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: ManufactureDate
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Some battery parameters can't be retrieved
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: SerialNumber
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: BatterySerialNumber
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: DesignVoltage
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: Manufacturer
02-03 18:12:42.850 F /BattWatcher:85281:143bd4/ Errorneous: ManufactureDate
02-03 18:12:42.850 F /vm:85281:143bbe/ OK! Now going to destruct VM Controller.
02-03 18:12:42.851 F /vm:85281:143bbe/ SARE state(SareStateStart): enqueued 'SareCmdTerminate'(8) command
02-03 18:12:42.851 F /vm:85281:143bbe/ SARE state(SareStateStart): completed current 'SareCmdTerminate'(8) command with result 0x80000009
02-03 18:12:42.851 F /vm:85281:143bbe/ SARE state(SareStateStart): completed current 'SareCmdTerminate'(8) command with result 0x80000009
02-03 18:12:42.851 F /vm:85281:143bbe/ ***** VM process exiting with code 0
02-03 18:12:42.852 F /BattWatcher:85281:143bbe/ Some battery parameters can't be retrieved
02-03 18:12:42.852 F /BattWatcher:85281:143bbe/ Errorneous: BatterySerialNumber

 

No. Battery is OK. Could you generate technical data, send it to parallels and write its ID here? Thanx!

 

please, help ho to it thanks

I succede install FBSD 13 using "Other" but not Linux, but in this case there is no network...

 

ok, found and sent data. The ID is 389890105. Hope this helps.

 

As I can see, there is a kernel panic during XHCI initialization.
Note: some problems with FreeBSD was fixed previously with a help of Elric.
I do not know if those patches included into FreeBSD 13. I guess you should try FreeBSD 14.
The latest stable snapshot seems doesn't have problem you reported.

 

thank you a lot!
I've installed just now FreeBSD 14 from here https://download.freebsd.org/snapsh...aarch64-20220203-e2fe58d61b7-252875-disc1.iso
Network ok.
Now, I'm proceeding to install GUI.

 

there is no more Gnome3 for 14?
I installed

Code:

pkg install gnome-desktop gdm xorg

(without gnome3, then however I get "something has gone wrong"...
Please, help

 

here the bad message

 

GUI working with Mate and Slim, but mouse is stuck, not working... Any help?

 

Another interesting difference with the Intel installation (also Parallels 17, but freeBSD 13) is that using "Boot option" (gop list) at the boot on freeBSD 14 ARM I get only one resolution (1024x768) while in that Intel installation there were as many as 9 possible resolutions.

Did I have anything wrong with the installation?