pull cirrus.ko into main kernel package
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
xserver-xorg-video-vesa (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
In disco, xorg stopped shipping a cirrus module/driver, instead relying on the kernel one. But the kernel one is in the linux-modules-
That breaks some assumptions: uvtool, for example, doesn't specify a video device when creating a vm, and the default in libvirt in such cases is to use cirrus. As a conseguence, disco VMs created by tools that do not specify a default video device won't have the cirrus.ko module, and X won't start there.
It's a bit more complicated, however, because X just tries other fallbacks, but they also don't work. In particular, vesa doesn't work:
[ 25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted value
(full log at http://
We can change uvtool and specify a video device instead of leaving it blank (see bug #1818877), but there might be other tools out there spawning guests without telling them which video device to use, and they would also fail.
Changed in xserver-xorg-video-vesa (Ubuntu): | |
status: | New → Confirmed |
Changed in xserver-xorg-video-vesa (Ubuntu): | |
importance: | Undecided → High |
status: | Confirmed → Fix Committed |
Another alternative would be to have vesa specify a working bpp value, if that is the only problem there.