[Spice-devel] Status of 0.6 release
dlaor at redhat.com
Mon Jul 5 07:59:51 PDT 2010
On 07/05/2010 04:44 PM, Alexander Larsson wrote:
> On Mon, 2010-07-05 at 14:49 +0200, Gerd Hoffmann wrote:
>> > Hi,
>>> > > * Qemu integration
>>> > >
>>> > > We have a new qemu repository, based on the current upstream version,
>>> > > with clean patch-series using a new, nicer spice API. Patches have been
>>> > > posted upstream at least for the initial integration (no qxl device
>>> > > support yet though). There has been any feedback yet though, so its hard
>>> > > to judge the status here. Will it be possible to get this merged?
>> > The qemu patches posted don't build due to the qxl parser work and the
>> > spice-protocol changes. I don't expect the spice patches are being
>> > merged quickly for a number of reasons:
>> > (1) I'd like to have the qxl parser work finished first. Having
>> > qxl and spice structs clearly separated makes it easier to
>> > maintain a really stable libspice-server interface for qxl/qemu.
>> > (2) I'll be two weeks away end July (summer vacation).
>> > (3) There is KVM forum early in August.
> Ugh. This is really really bad news. We've set the freeze date at july
> 19th so that we had a chance to finish things for the Fedora 14 feature
> freeze a week later (July 27th). But unless we can get spice support
> into the qemu in fedora we will have a hard time getting spice into
> fedora (no users of the library), and if spice support is not in
> upstream qemu its very unlikely that we'll get spice support in the F14
> qemu (standard "focus on upstream" fedora prio).
Prio but not a must. Focus on users is also nice ...
Spice in F14 is doable w/o qemu acceptance too.
> So, this basically means that we're likely to miss spice in F14, having
> to wait for F15, thus missing half a year of testing and use. That sucks
More information about the Spice-devel