You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues and this bug has not been reported previously
Describe the bug
All Quickemu VM's freeze/lock up while booting up after Qemu version upgrade from 9.0.2-2.1 to 9.1.0-1.1. The machine boots as normal through UEFI splash but locks up before OS splash(usually on black screen). Sometime will go past grub sccreens before lockup happens. I have confirmend that all vm's still work as normal in previous Qemu versions and the bug persists no matter what Quickemu version is used. This was tested on both Quickemu versions 4.9.6-5.3, and 4.9.2-6.3. The Quickemu version did not matter, and was related to the Qemu version upgrade.
To Reproduce
Run any Quickemu machine as normal, either on command line with --display spice, or through GUI
flexiondotorg
changed the title
Quickemu VM's freeze upon boot after Qemu upgrade(version 9.1.0-1.1)
triage: Quickemu VM's freeze upon boot after Qemu upgrade(version 9.1.0-1.1)
Oct 7, 2024
Describe the bug
All Quickemu VM's freeze/lock up while booting up after Qemu version upgrade from 9.0.2-2.1 to 9.1.0-1.1. The machine boots as normal through UEFI splash but locks up before OS splash(usually on black screen). Sometime will go past grub sccreens before lockup happens. I have confirmend that all vm's still work as normal in previous Qemu versions and the bug persists no matter what Quickemu version is used. This was tested on both Quickemu versions 4.9.6-5.3, and 4.9.2-6.3. The Quickemu version did not matter, and was related to the Qemu version upgrade.
To Reproduce
Run any Quickemu machine as normal, either on command line with --display spice, or through GUI
Expected behavior
Vm's should launch.
System information
*NOTE- This output is from Qemu version 9.0.2-2.1, and not from the offending version(9.1.0-1.1), as I have already rolled back.
The text was updated successfully, but these errors were encountered: