Issue #710: [mutter] anaconda failed to start a live session on a VM with QXL video driver (Virtio works OK) | rhbz#2071226 - blocker-review

fedora-qa / blocker-review

#710 [mutter] anaconda failed to start a live session on a VM with QXL video driver (Virtio works OK) | rhbz#2071226

Closed 2 years ago by blockerbot. Opened 2 years ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2071226
Information from BlockerBugs App:

Current vote summary

FinalBlocker (+0, 0, -1)
- -1 by kparal
Accepted FinalFreezeException (+1, 0, -0)
- +1 by kparal

Commented but haven't voted yet: nielsenb, lruzicka, frantisekz

The votes have been last counted at 2022-04-11 21:20 UTC and the last processed comment was #comment-791838

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)

nielsenb commented 2 years ago

I couldn't reproduce.

FinalBlocker -1

lruzicka commented 2 years ago

I can reproduce. Sometimes (5 in 10 cases) It is not possible to install Fedora on a VM with QXL video driver. The system shows the GDM instead of Anaconda and when trying to log into the live session, it hangs.

FinalBlocker +1

Edited 2 years ago by lruzicka

kparal commented 2 years ago

I suppose this problem is just an autologin issue + bug 2063156 (already a blocker). See my comment.

The autologin itself is probably not really a blocker:

"Release-blocking live images must boot to the expected boot menu, and then to a desktop or to a login prompt where it is clear how to log in to a desktop."
https://fedoraproject.org/wiki/Basic_Release_Criteria#Expected_image_boot_behavior

It's unusual and unpolished, yes, but it's ok by our current definition. The "system stuck" issue is of course not ok, and I believe a clear blocker, due to multiple people confirming it.

So we can either consider the "system stuck" to be the same as bug 2063156, and vote just on the autologin issue, in which case I'm probably FinalBlocker -1, but can be convinced to FinalBlocker 0 and of course we can introduce some new criterion as well, if people desperately want it :)

Or we can say that we're not sure whether the "system stuck" is the same problem as bug 2063156 and vote on both autologin+stuck issues together, in which case I'm FinalBlocker +1, but we should probably specify that the autologin issue is not mandatory to get resolved in order to fix the blocker.