[Qemu-devel] Re: KVM call agenda for July 27

[Cole Robinson]

On 07/27/2010 09:30 AM, Anthony Liguori wrote:
> On 07/27/2010 06:51 AM, Daniel P. Berrange wrote:
>> On Mon, Jul 26, 2010 at 05:28:21PM -0500, Anthony Liguori wrote:
>>    
>>> On 07/26/2010 04:28 PM, Chris Wright wrote:
>>>      
>>>> Please send in any agenda items you are interested in covering.
>>>>
>>>>        
>>> - 0.13 update
>>>    I'll pre-empt the 0.13 question with an answer.  I'm just testing the
>>> VNC changes and if all goes well, I'll tag tonight.
>>>
>>>    Initial thinking is to keep 0.14 short and target Dec 1st.
>>>
>>> - if danpb can make it, would like to discuss -help output parsing
>>>    summary: help parsing is terrible, but given the fact that
>>> capabilities is going to take a while to get totally right, would like
>>> to discuss an interim solution that gives us more flexibility to do
>>> reasonable things with the help output.
>>>      
>> I'm not able to make this call today&  next week i'm on PTO
> 
> No problem.  Enjoy your holiday.
> 
>> . I would
>> like to think that we could get a suitable capabilities sytem in place
>> for 0.14 release. Since 0.13 is nearly ready&  libvirt works with it
>> aside from the cache issue which is now addressed in libvirt, I don't
>> think its useful to change libvirt further.
> 
> So 0.8.2 is broken or did 0.8.2 get fixed?
> 

Just to clarify the issues:

1) qemu -help/-version output was changed: libvirt chokes when trying to
parse it: no VMs can use qemu.git/qemu-0.13

2) libvirt improperly parses cache= value from -help output, does not
think emulator supports cache= value. user specified cache values are
not passed on the qemu CLI

Libvirt 0.8.2 fixed the first issue. Libvirt.git will soon fix the
second issue, 0.8.3 is out at the end of the week.

> What changes would need to be made for 0.13 to work with existing 
> versions of libvirt?
> 

- Revert the version string change in
f75ca1ae205f24dae296c82d534c37746f87232f

- Apply Bruces cache -help output patch

Thanks,
Cole

> If we can agree that 0.13 is the last time we make these changes, I'd be 
> willing to do it one more time.  I'd strongly suggest switching 
> eliminating the help parsing entirely instead of just waiting for 
> capabilities.
> 
>>   We need to just focus on
>> getting capabilities (and QMP in general for that matter) ready for
>> 0.14 and not let it slip still further into 0.15.
>>    
> 
> No objections on my side.
> 
> Regards,
> 
> Anthony Liguori
> 
>> Regards,
>> Daniel
>>    
>