On Mon, Apr 13, 2020 at 01:39:19PM +0300, Hannu Vuolasaho wrote: > Hi! > > I'm trying to set up testbench for software on different archs and I > ran into few issues when trying to get openbsd to work. > > Has anyone done full install and taken notes how to get OpenBSD to run > on Qemu-system-ppc ? > > My current wishlist is short: > 1) OpenBSD running > 2) network for it > > Point 1) successed from install66.iso but the installed system doesn't boot > Trying hd,\\:tbxi... > No valid state has been set by load or init-program > > I've tried few boot hd,:ofwboot /bsd variations but I'm stuck. > > I try to start Qemu 4.2.0 on AMD64 linux with: > qemu-system-ppc -M mac99 -cpu g4 \ > -usb -device usb-kbd \ > -hda obsd-ppc32.qcow > If I add anything on command line considering network, OpenBSD hangs, > panics or exits to firmware. > > What am I missing?
here is something i posted a while back: https://marc.info/?l=openbsd-ppc&m=158007222311388&w=2 my current commandline is something like: qemu-system-ppc \ -M mac99,via=pmu-adb -cpu g4 \ -nodefaults \ -nographic \ -display none \ -serial mon:stdio \ -cdrom test.iso \ -drive format=raw,file=/path/to/obsd.raw \ -boot d \ $@ 2> stderr as you can see this is console only (a presudo serial console) if you use '-nodefaults' USB devices will not be automatically added, 'pmu-adb' does not need USB, so you get to workaround the USB (ohci) hang. i redirect ... "2> stderr" ... the pesky logs to a file. thus no need to muck around the qemu code. > Point 1) successed from install66.iso but the installed system doesn't boot > Trying hd,\\:tbxi... > No valid state has been set by load or init-program > > I've tried few boot hd,:ofwboot /bsd variations but I'm stuck. please read #3 booting and blessing i tried to do a custom openbios build to debug it but have never got around to trying it out. what i did to overcome this was to create a very rough ISO that contained a test kernel (i was testing clang compiled kernels) ... and mounted the disk (wd0) manually (something like "boot -a")... as i said, very rough. if you used an install disk to boot from ... you get a RAMDISK ... which boots off and mounts your work disk. this was NOT what i wanted to i had to modify the ISO. network has not been good to me either. one time it worked, then it just fails. rgc > > Best regards, > Hannu Vuolasaho >
