I go back and forth with virt-manager and Boxes. The top two problems
I'm having in Boxes that don't happen with virt-manager that relate to
QA testing:
GRUB2 doesn't respond to ctrl-x or f10
https://bugzilla.gnome.org/show_bug.cgi?id=764002
So I can't add boot parameters like rd.break or rd.debug or
systemd.log_level=debug and then F10 or CntrlX to boot. I can only
issue cntl-alt-back, cntrl-alt-f1,2,7. And sometimes the GUI isn't on
tty1, it's on 4, 5, 6 (like I think it is with netinstall?) once I
switch to tty2, I'm hosed, I can't go back to the GUI.
screen flicker at GDM, mouse click erratic response, black login screen
https://bugzilla.gnome.org/show_bug.cgi?id=763960
This is Fedora 24 not usable once installed; the live environment is
OK. I think the issue is that there isn't enough information to debug
this but I don't know how to get more information.
On Thu, Apr 14, 2016 at 5:54 AM, Jiri Eischmann <eischmann(a)redhat.com> wrote:
Hi,
Boxes is the pre-installed solution for VMs on Workstation, but it
doesn't get as much attention as it should.
Currently development composes of F24 don't even work in Boxes on F23,
so users who'd like to test F24 in the default VM app are out of luck.
It clearly violates one of the release criteria:https://fedoraproject.o
rg/wiki/Fedora_24_Beta_Release_Criteria#Guest_on_current_stable_release
I'll make a RHBZ of the screen flicker bug and nominate it. But as far
as I know that criterion applies to virt-manager. If it works there
but not Boxes, I doubt the bug would block. Maybe not even final
release (?).
Chris Murphy