Hi, > The only thing that's not working is the system console when booting. That is normal. There is no efi gop support on arm, so no efifb boot framebuffer. > After grub loads and starts the kernel, "Guest disabled display." is > shown until X starts. Yep. Once the virtio-gpu kms driver is loaded you'll get an functional display. Maybe delayed until something is actually printed to the console due to CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y. With a "quiet" boot that very well might be no message before gdm starts. > "Guest disabled display." also gets shown when X turns off the > display after inactivity, but it comes when when I wake it up. Yep. That is X / wayland going into DPMS mode and turning off the display. You can disable screen blanking in gnome settings when it bugs you. > And now, I'm upgrading F32 to F33, in the VM completely blind. The only > thing that tells me the VM is not dead is the CPU activity monitoring in > virt manager, and I see the timestamp of the disk image file getting updated > on the host. Hmm. That is not normal. In theory F33 should behave like F32 did ... Can you ssh into the guest, or login on the serial console? Anything suspicious in the kernel messages? take care, Gerd _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
