Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenIndiana stuck in reboot loop #2394

Closed
mohd-akram opened this issue Mar 20, 2021 · 6 comments
Closed

OpenIndiana stuck in reboot loop #2394

mohd-akram opened this issue Mar 20, 2021 · 6 comments
Milestone

Comments

@mohd-akram
Copy link

Describe the issue
I can't seem to boot into OpenIndiana. I'm using the 2020.10 Live DVD. It reaches up to Booting..., stays there a bit and then restarts.

Configuration

  • UTM Version: 2.0.22
  • OS Version: 11.2.3
  • Intel or Apple Silicon? Intel

Debug log

Running:  -L /Applications/UTM.app/Contents/Resources/qemu -S -qmp tcp:127.0.0.1:4000,server,nowait -vga none -spice port=4001,addr=127.0.0.1,disable-ticketing,image-compression=off,playback-compression=off,streaming-video=off -device qxl-vga -cpu host -smp cpus=4,sockets=1,cores=2,threads=2 -machine q35, -accel hvf -accel tcg,tb-size=256 -global PIIX4_PM.disable_s3=1 -global ICH9-LPC.disable_s3=1 -boot order=d -m 1024 -device AC97 -name OpenIndiana -device usb-ehci -device usb-tablet -device usb-mouse -device usb-kbd -drive if=ide,media=disk,id=drive0,file=/Users/mohamed/Library/Containers/com.utmapp.UTM/Data/Documents/OpenIndiana.utm/Images/disk-0.qcow2,cache=writethrough -drive if=ide,media=cdrom,id=drive1 -device rtl8139,netdev=net0 -netdev user,id=net0 -device virtio-serial -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,id=vdagent,debug=0,name=vdagent -uuid 22747DC7-CA6C-48B7-B6DF-AA52D3F6E49A -rtc base=localtime
libqemu-x86_64-softmmu.utm.dylib: warning: global PIIX4_PM.disable_s3=1 not used

Upload VM

config.plist

@osy
Copy link
Contributor

osy commented Mar 22, 2021

I can't get it to boot from QEMU either. It may be a QEMU issue. If you can get it to work in QEMU, please reopen this, otherwise you may have to communicate with the QEMU devs.

@osy osy closed this as completed Mar 22, 2021
@mohd-akram
Copy link
Author

Thanks for verifying, I'm very much a QEMU noob. I'll check with the QEMU folks. Thanks for this awesome app!

@mohd-akram
Copy link
Author

This works in virt-manager, so it seems to be a UTM issue. This is the command line it uses:

/opt/local/bin/qemu-system-x86_64 -name guest=openindiana,debug-threads=on -S -object {"qom-type":"secret","id":"masterKey0","format":"raw","file":"/Users/mohamed/.config/libvirt/qemu/lib/domain-7-openindiana/master-key.aes"} -machine pc-i440fx-8.0,usb=off,vmport=off,dump-guest-core=off,memory-backend=pc.ram,hpet=off,acpi=on -accel hvf -cpu qemu64 -m size=1048576k -object {"qom-type":"memory-backend-ram","id":"pc.ram","size":1073741824} -overcommit mem-lock=off -smp 1,sockets=1,cores=1,threads=1 -uuid ffdcc014-d85a-4b41-b651-7b45d6a864b1 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=23,server=on,wait=off -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device {"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pci.0","addr":"0x5"} -device {"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.0","addr":"0x6"} -blockdev {"driver":"file","filename":"/Users/mohamed/.local/share/libvirt/images/openindiana.qcow2","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-2-format","read-only":false,"discard":"unmap","driver":"qcow2","file":"libvirt-2-storage","backing":null} -device {"driver":"virtio-blk-pci","bus":"pci.0","addr":"0x7","drive":"libvirt-2-format","id":"virtio-disk0","bootindex":2} -blockdev {"driver":"file","filename":"/Volumes/MyPassport/Images/OI-hipster-gui-20230502.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"} -device {"driver":"ide-cd","bus":"ide.0","unit":0,"drive":"libvirt-1-format","id":"ide0-0-0","bootindex":1} -netdev {"type":"user","id":"hostnet0"} -device {"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:da:2a:0f","bus":"pci.0","addr":"0x3"} -chardev pty,id=charserial0 -device {"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0} -chardev spicevmc,id=charchannel0,name=vdagent -device {"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"com.redhat.spice.0"} -device {"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"} -audiodev {"id":"audio1","driver":"spice"} -spice port=5900,addr=127.0.0.1,disable-ticketing=on,image-compression=off,seamless-migration=on -device {"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pci.0","addr":"0x2"} -device {"driver":"intel-hda","id":"sound0","bus":"pci.0","addr":"0x4"} -device {"driver":"hda-duplex","id":"sound0-codec0","bus":"sound0.0","cad":0,"audiodev":"audio1"} -chardev spicevmc,id=charredir0,name=usbredir -device {"driver":"usb-redir","chardev":"charredir0","id":"redir0","bus":"usb.0","port":"2"} -chardev spicevmc,id=charredir1,name=usbredir -device {"driver":"usb-redir","chardev":"charredir1","id":"redir1","bus":"usb.0","port":"3"} -device {"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.0","addr":"0x8"} -msg timestamp=on

@osy
Copy link
Contributor

osy commented Jul 17, 2023

libvirt adds a lot of commands. I was wondering if you can get it running on just QEMU (and I presume you are running this on macOS).

@mohd-akram
Copy link
Author

So the magical incantation that fixes the crash is -machine hpet=off:

qemu-system-x86_64 \
 -machine hpet=off \
 -accel hvf \
 -m size=1048576k \
 -cdrom OI-hipster-gui-20230502.iso

It seems virt-manager defaults to hpet being off. Maybe UTM should do the same.

@osy osy reopened this Jul 17, 2023
@osy osy added this to the v4.3 milestone Jul 17, 2023
@osy
Copy link
Contributor

osy commented Jul 17, 2023

Thanks for finding this. I’ll add this to the next update.

@osy osy closed this as completed in 3544572 Jul 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants