Qemu panics after failing to connect to ufs

Expected behavior

Qemu boots into some interactive environment

Actual behavior

Qemu displays 'booting from ROM', then hangs (although the window does close).

Steps to reproduce

Start ufs

export HARVEY=$(pwd)
export PATH=$HARVEY/linux_amd64/bin:$PATH
ufs -root=/$HARVEY -debug=3 &

run util/GO9PCPU
wait

QEMU output

``` qemu-system-x86_64 -s -cpu max,vmware-cpuid-freq=on,+invtsc -smp 4 -m 2048 -enable-kvm -usb -serial stdio --machine q35,accel=kvm -net nic,model=rtl8139 -net user,id=user.0,hostfwd=tcp::5555-:1522,hostfwd=tcp::9999-:9,hostfwd=tcp::17010-:17010,hostfwd=tcp::1666-:1666,hostfwd=tcp::5356-:5356,hostfwd=tcp::17013-:17013 -object filter-dump,id=f1,netdev=user.0,file=/tmp/vm0.pcap -append "service=cpu nobootprompt=tcp maxcores=1024 fs=10.0.2.2 auth=10.0.2.2 nvram=/boot/nvram nvrlen=512 nvroff=0 acpiirq=1 bootargs='tcp -g 192.168.0.2 ether /net/ether0 192.168.0.15 255.255.255.0'" -kernel /home/binarycat/os/harvey/sys/src/9/amd64/harvey.32bit 2021/05/29 14:25:44 Listen failed: listen tcp4 :5640: bind: address already in use (qemu-system-x86_64:5503): dbind-WARNING **: 14:25:44.699: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000007H:EDX.invtsc [bit 8] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000007H:EDX.invtsc [bit 8] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000007H:EDX.invtsc [bit 8] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000007H:EDX.invtsc [bit 8] Harvey Multiboot: magic 0x2badb002 pmbi 0x9500 Multiboot: flags 0x24f Multiboot: cmdline

Harvey-OS / harvey