Opened 16 months ago
Closed 11 months ago
#18562 closed bug (fixed)
On kvm-qemu Haiku latest boots into pausing VM
Reported by: | tps800 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | - General | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #18593 | |
Platform: | All |
Description
Booting Haiku hrev57226 on Qemu-KVM boots into paused virtual machine. On real hardware Haiku hrev57226 goes into a boot loop.
VM running on Ubuntu/Debian:
ii grub-firmware-qemu 2.06-2ubuntu16 amd64 GRUB firmware image for QEMU ii ipxe-qemu 1.21.1+git-20220113.fbbdc3926-0ubuntu1 all PXE boot firmware - ROM images for qemu ii ipxe-qemu-256k-compat-efi-roms 1.0.0+git-20150424.a25a16d-0ubuntu4 all PXE boot firmware - Compat EFI ROM images for qemu ii libvirglrenderer1:amd64 0.10.4-1ubuntu1 amd64 virtual GPU for KVM virtualization ii libvirt-daemon-driver-qemu 9.0.0-2ubuntu1.2 amd64 Virtualization daemon QEMU connection driver ii qemu-block-extra 1:7.2+dfsg-5ubuntu2.2 amd64 extra block backend modules for qemu-system and qemu-utils ii qemu-efi 2022.11-6 all transitional dummy package ii qemu-efi-aarch64 2022.11-6 all UEFI firmware for 64-bit ARM virtual machines ii qemu-efi-arm 2022.11-6 all UEFI firmware for 32-bit ARM virtual machines ii qemu-system 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU full system emulation binaries ii qemu-system-arm 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU full system emulation binaries (arm) ii qemu-system-common 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU full system emulation binaries (common files) ii qemu-system-data 1:7.2+dfsg-5ubuntu2.2 all QEMU full system emulation (data files) ii qemu-system-gui 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU full system emulation binaries (user interface and audio support) ii qemu-system-mips 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU full system emulation binaries (mips) ii qemu-system-misc 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU full system emulation binaries (miscellaneous) ii qemu-system-ppc 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU full system emulation binaries (ppc) ii qemu-system-s390x 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU full system emulation binaries (s390x) ii qemu-system-sparc 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU full system emulation binaries (sparc) ii qemu-system-x86 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU full system emulation binaries (x86) ii qemu-user 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU user mode emulation binaries ii qemu-user-static 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU user mode emulation binaries (static version) ii qemu-utils 1:7.2+dfsg-5ubuntu2.2 amd64 QEMU utilities ii qemubuilder 0.89 amd64 pbuilder using QEMU as backend ii u-boot-qemu 2022.10+dfsg-1ubuntu1.23.04.1 all A boot loader for qemu
Change History (8)
comment:1 by , 16 months ago
comment:2 by , 16 months ago
That's probably two different things. The pause problem is probably a duplicate of the known ipro1000 problem #18541. It is indeed leaving the machine suspended without ability to resume. That's why it is difficult for a lambda user to give you things to analyse.
The loop seems a new problem.
comment:3 by , 16 months ago
On qemu-kvm:
The system is paused. There is no way to get it out of the paused state. The only way is to reset or hard shut down the VM. This is right after the "Rocket"-Icon is highlighted.
On real hardware:
The system boots up until the "Rocket" Icon (the last one) is highlighted, then it does nothing for approximately three minutes, then the screen goes black, blinking cursor in upper left corner. Another about three minutes nothing, then it reboots. Any keypress, even num-lock, shift-lock or Ctrl-Alt-Del is ignored. Only turning off works.
comment:4 by , 16 months ago
On qemu-kvm try with rtl8139 instead of e1000. If it boots, it may freeze the desktop while you're downloading things but you will get control back when it has finished and otherwise it should work.
On real hardware, you may try to access Haiku boot menu and play with safe mode options to see if something helps. You should also enable on screen debug output in debug options to see where it hangs.
comment:5 by , 16 months ago
Real hardware may be helped by using the "fail-safe video mode" option.
comment:6 by , 15 months ago
Blocking: | 18593 added |
---|
comment:8 by , 11 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Presuming fixed along with other problems.
More details needed, please. What do you mean by "paused"; and what are the symptoms of the bootloop?