KVM call agenda for Tuesday 13

KVM call agenda for Tuesday 13

[Juan Quintela]

Hi

Please send in any agenda items you are interested in covering.

Cheers,

Juan.

Re: KVM call agenda for Tuesday 13

[Andreas Färber]

Am 12.03.2012 13:40, schrieb Juan Quintela:
> Please send in any agenda items you are interested in covering.

* QEMU 1.1 roadmap

If we're still aiming for a release in early May that would mean a
feature freeze in about four weeks.

http://wiki.qemu.org/Planning/1.1

My stake is that I'd like to see CPUs and machines QOM'ified for 1.1,
and I'm aware that also CPU hot-plug and CPU versioning features depend
on it. Not sure what timeline the respective authors have in mind, but
IMO we should start counting backwards when series need to be finalized
on the list and by whom they should get merged. Easter is on April 8th
this year!

Other features that I have in mind are qtest, qemu-test, gtk-doc and 4th
QOM series. Not sure which of those were meant for 1.1.

With the Wiki closed, having contributors add Feature pages for their
1.1 wishlist, as done for 1.0, is probably not going to work well, but
collecting a rough list or dependency tree would be nice for planning.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

Re: [Qemu-devel] KVM call agenda for Tuesday 13

[Anthony Liguori]

On 03/12/2012 07:22 PM, Andreas Färber wrote:
> Am 12.03.2012 13:40, schrieb Juan Quintela:
>> Please send in any agenda items you are interested in covering.
>
> * QEMU 1.1 roadmap
>
> If we're still aiming for a release in early May that would mean a
> feature freeze in about four weeks.

Soft freeze.  Hard freeze is about six weeks away.

>
> http://wiki.qemu.org/Planning/1.1

Yup.

>
> My stake is that I'd like to see CPUs and machines QOM'ified for 1.1,
> and I'm aware that also CPU hot-plug and CPU versioning features depend
> on it. Not sure what timeline the respective authors have in mind, but
> IMO we should start counting backwards when series need to be finalized
> on the list and by whom they should get merged. Easter is on April 8th
> this year!
>
> Other features that I have in mind are qtest, qemu-test, gtk-doc and 4th
> QOM series. Not sure which of those were meant for 1.1.

My personal development priorities are qtest, and qbus (4th QOM series). 
qemu-test and gtk-doc are both nice to haves but I have a sneaking suspicion 
that they're going to require a non-trivial amount of work.

>
> With the Wiki closed, having contributors add Feature pages for their
> 1.1 wishlist, as done for 1.0, is probably not going to work well, but
> collecting a rough list or dependency tree would be nice for planning.

The wiki isn't closed...  I would hope most contributors would have an account 
and/or would not have a problem asking for an account.

Regards,

Anthony Liguori

>
> Andreas
>

Re: [Qemu-devel] KVM call agenda for Tuesday 13

[Andreas Färber]

Am 13.03.2012 03:04, schrieb Anthony Liguori:
> On 03/12/2012 07:22 PM, Andreas Färber wrote:
>> Am 12.03.2012 13:40, schrieb Juan Quintela:
>>> Please send in any agenda items you are interested in covering.
>>
>> * QEMU 1.1 roadmap
>>
>> If we're still aiming for a release in early May that would mean a
>> feature freeze in about four weeks.
> 
> Soft freeze.  Hard freeze is about six weeks away.

Correct, and soft freeze defines itself as "Major features should have
initial code committed by this date."

I did consider all mentioned ones "major" features as opposed to random
bug fixes.

My goal would be to assemble a task list with dates and responsibilities
such as in my case, "have qom-cpu series merged <next Friday> by
<Anthony>", "Merge qom-cpu-arm through Peter's target-arm tree by <date>
pulled by <Blue>", ... that we can track and tick off. Who
reviews+merges x86, who mips+sh4/m68k/unicore32, do I merge ppc through
ppc-next (respectively s390x) in Alex' absence next week? When does x86
need to be merged to have enough time for hotplug?
Do we just aim for qtest inclusion or also for some more qtest-based
test coverage (needs time)? If we manage qemu-test, what additional
targets are missing and who covers them? etc.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

Re: [Qemu-devel] KVM call agenda for Tuesday 13

[Eduardo Habkost]

On Tue, Mar 13, 2012 at 01:22:42AM +0100, Andreas Färber wrote:
> Am 12.03.2012 13:40, schrieb Juan Quintela:
> > Please send in any agenda items you are interested in covering.
> 
> * QEMU 1.1 roadmap
> 
> If we're still aiming for a release in early May that would mean a
> feature freeze in about four weeks.
> 
> http://wiki.qemu.org/Planning/1.1
> 
> My stake is that I'd like to see CPUs and machines QOM'ified for 1.1,
> and I'm aware that also CPU hot-plug and CPU versioning features depend
> on it. Not sure what timeline the respective authors have in mind, but
> IMO we should start counting backwards when series need to be finalized
> on the list and by whom they should get merged. Easter is on April 8th
> this year!
> 
> Other features that I have in mind are qtest, qemu-test, gtk-doc and 4th
> QOM series. Not sure which of those were meant for 1.1.

I would like to have the discussion of -nodefconfig semantics regarding
cpudefs & machine-types concluded (on the call, I hope), so we can have
the right semantics implemented on 1.1.

So, the items for the agenda are:

* Possible use of /usr/share for machine-type data (including, but not
  limited to, CPU models)
* Semantics of -nodefconfig regarding machine-types and CPU models

-- 
Eduardo

Re: KVM call agenda for Tuesday 13

[Michael S. Tsirkin]

On Tue, Mar 13, 2012 at 01:22:42AM +0100, Andreas Färber wrote:
> Am 12.03.2012 13:40, schrieb Juan Quintela:
> > Please send in any agenda items you are interested in covering.
> 
> * QEMU 1.1 roadmap
> 
> If we're still aiming for a release in early May that would mean a
> feature freeze in about four weeks.
> 
> http://wiki.qemu.org/Planning/1.1
> 
> My stake is that I'd like to see CPUs and machines QOM'ified for 1.1,
> and I'm aware that also CPU hot-plug and CPU versioning features depend
> on it. Not sure what timeline the respective authors have in mind, but
> IMO we should start counting backwards when series need to be finalized
> on the list and by whom they should get merged. Easter is on April 8th
> this year!
> 
> Other features that I have in mind are qtest, qemu-test, gtk-doc and 4th
> QOM series. Not sure which of those were meant for 1.1.
> 
> With the Wiki closed, having contributors add Feature pages for their
> 1.1 wishlist, as done for 1.0, is probably not going to work well, but
> collecting a rough list or dependency tree would be nice for planning.
> 
> Andreas

My priority is PCI bridge with hotplug support. Should be ready on time.

> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

KVM call agenda for Tuesday 13

[Juan Quintela]

Hi

Please send in any agenda items you are interested in covering.

Thanks, Juan.