On Mon, Oct 30, 2017 at 10:41 PM, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote:
Felipe's email is waiting in the moderation queue, but he basically says he has no preference either way. I'd personally keep the patch in (use virtio-vga), because I see only benefits and no drawbacks. It's the more future-proof solution. I wish we could do the same for virt-manager.Hi folks!
We have a 'situation' for F27 Final that needs resolving.
One blocker bug - https://bugzilla.redhat.com/show_bug.cgi?id=1164492 -
definitely requires a change to gnome-boxes. That change isn't under
dispute, and is present in an update, gnome-boxes-3.26.1-4.fc27 .
So what's the problem? The problem is that update also includes
*another* change, and I'm not at all sure we actually still want that
change.
gnome-boxes-3.26.1-3.fc27 changed the default video adapter for new VMs
to 'virtio', as an attempt to workaround
https://bugzilla.redhat.com/show_bug.cgi?id=1491320 . However, that bug
now appears to be addressed on the kernel side. Changing the default
video adapter for new VMs could only ever be an incomplete workaround
(it wouldn't help VMs created on other OSes, or existing VMs, or
various other situations), and I believe was a downstream-only change.
So do we still actually want to change Boxes' default video adapter for
F27? If not, can someone please build and submit a 3.26.1-5.fc27 update
which includes the dependency change for #1164492, but reverts the
virtio default video adapter change? Thanks!
_______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
