2010/11/30 Dor Laor :
> On 11/29/2010 06:23 PM, Stefan Hajnoczi wrote:
>>
>> On Mon, Nov 29, 2010 at 3:00 PM, Yoshiaki Tamura
>> wrote:
>>>
>>> 2010/11/29 Paul Brook:
>>
>> If devices incorrectly claim support for live migration, then that
>> should
>> also be fixed, either by rem
(2010/11/30 1:41), Dor Laor wrote:
Is this a fair summary: any device that supports live migration workw
under Kemari?
It might be fair summary but practically we barely have live migration working
w/o Kemari. In addition, last I checked Kemari needs additional hooks and it
will be too hard
2010/11/30 Anthony Liguori :
> On 11/29/2010 10:53 AM, Paul Brook wrote:
Is this a fair summary: any device that supports live migration workw
under Kemari?
>>>
>>> It might be fair summary but practically we barely have live migration
>>> working w/o Kemari. In addition, last I
On 11/29/2010 11:18 AM, Paul Brook wrote:
On 11/29/2010 10:53 AM, Paul Brook wrote:
Is this a fair summary: any device that supports live migration workw
under Kemari?
It might be fair summary but practically we barely have live migration
working w/o Kemari. In addition, last
> On 11/29/2010 10:53 AM, Paul Brook wrote:
> >>> Is this a fair summary: any device that supports live migration workw
> >>> under Kemari?
> >>
> >> It might be fair summary but practically we barely have live migration
> >> working w/o Kemari. In addition, last I checked Kemari needs additional
On 11/29/2010 10:53 AM, Paul Brook wrote:
Is this a fair summary: any device that supports live migration workw
under Kemari?
It might be fair summary but practically we barely have live migration
working w/o Kemari. In addition, last I checked Kemari needs additional
hooks and it will b
> > Is this a fair summary: any device that supports live migration workw
> > under Kemari?
>
> It might be fair summary but practically we barely have live migration
> working w/o Kemari. In addition, last I checked Kemari needs additional
> hooks and it will be too hard to keep that out of tree
On 11/29/2010 06:23 PM, Stefan Hajnoczi wrote:
On Mon, Nov 29, 2010 at 3:00 PM, Yoshiaki Tamura
wrote:
2010/11/29 Paul Brook:
If devices incorrectly claim support for live migration, then that should
also be fixed, either by removing the broken code or by making it work.
I totally agree wit
On Mon, Nov 29, 2010 at 3:00 PM, Yoshiaki Tamura
wrote:
> 2010/11/29 Paul Brook :
>>> > If devices incorrectly claim support for live migration, then that should
>>> > also be fixed, either by removing the broken code or by making it work.
>>>
>>> I totally agree with you.
>>>
>>> > AFAICT your cu
> >> Sorry, I didn't get what you're trying to tell me. My plan would
> >> be to initially start from a subset of devices, and gradually
> >> grow the number of devices that Kemari works with. While this
> >> process, it'll include what you said above, file a but and/or fix
> >> the code. Am I m
2010/11/29 Paul Brook :
>> > If devices incorrectly claim support for live migration, then that should
>> > also be fixed, either by removing the broken code or by making it work.
>>
>> I totally agree with you.
>>
>> > AFAICT your current proposal is just feeding back the results of some
>> > fair
> > If devices incorrectly claim support for live migration, then that should
> > also be fixed, either by removing the broken code or by making it work.
>
> I totally agree with you.
>
> > AFAICT your current proposal is just feeding back the results of some
> > fairly specific QA testing. I'd
2010/11/29 Paul Brook :
>> >> To answer Stefan's question, there shouldn't be any requirement
>> >> for a device, but must be tested with Kemari. If it doesn't work
>> >> correctly, the problems must be fixed before adding to the list.
>> >
>> > What exactly are the problems? Is this a device bus
> >> To answer Stefan's question, there shouldn't be any requirement
> >> for a device, but must be tested with Kemari. If it doesn't work
> >> correctly, the problems must be fixed before adding to the list.
> >
> > What exactly are the problems? Is this a device bus of a Kemari bug?
> > If it's
2010/11/29 Paul Brook :
>> 2010/11/29 Paul Brook :
>> >> >> Could you formulate the constraints so developers are aware of them
>> >> >> in the future and can protect the codebase. How about expanding the
>> >> >> Kemari wiki pages?
>> >> >
>> >> > If you like the idea above, I'm happy to make the
> 2010/11/29 Paul Brook :
> >> >> Could you formulate the constraints so developers are aware of them
> >> >> in the future and can protect the codebase. How about expanding the
> >> >> Kemari wiki pages?
> >> >
> >> > If you like the idea above, I'm happy to make the list also on
> >> > the wiki
2010/11/29 Paul Brook :
>> >> Could you formulate the constraints so developers are aware of them in
>> >> the future and can protect the codebase. How about expanding the
>> >> Kemari wiki pages?
>> >
>> > If you like the idea above, I'm happy to make the list also on
>> > the wiki page.
>>
>> He
> >> Could you formulate the constraints so developers are aware of them in
> >> the future and can protect the codebase. How about expanding the
> >> Kemari wiki pages?
> >
> > If you like the idea above, I'm happy to make the list also on
> > the wiki page.
>
> Here's a different question: wha
On Sat, Nov 27, 2010 at 1:11 PM, Yoshiaki Tamura
wrote:
> 2010/11/27 Stefan Hajnoczi :
>> On Sat, Nov 27, 2010 at 8:53 AM, Yoshiaki Tamura
>> wrote:
>>> 2010/11/27 Stefan Hajnoczi :
On Sat, Nov 27, 2010 at 4:29 AM, Yoshiaki Tamura
wrote:
> 2010/11/27 Blue Swirl :
>> On Thu, Nov
2010/11/27 Stefan Hajnoczi :
> On Sat, Nov 27, 2010 at 8:53 AM, Yoshiaki Tamura
> wrote:
>> 2010/11/27 Stefan Hajnoczi :
>>> On Sat, Nov 27, 2010 at 4:29 AM, Yoshiaki Tamura
>>> wrote:
2010/11/27 Blue Swirl :
> On Thu, Nov 25, 2010 at 6:06 AM, Yoshiaki Tamura
> wrote:
> Somehow
2010/11/27 Paul Brook :
>> One question I have about Kemari is whether it adds new constraints to
>> the QEMU codebase? Fault tolerance seems like a cross-cutting concern
>> - everyone writing device emulation or core QEMU code may need to be
>> aware of new constraints. For example, "you are not
2010/11/27 Blue Swirl :
> On Sat, Nov 27, 2010 at 8:53 AM, Yoshiaki Tamura
> wrote:
>> 2010/11/27 Stefan Hajnoczi :
>>> On Sat, Nov 27, 2010 at 4:29 AM, Yoshiaki Tamura
>>> wrote:
2010/11/27 Blue Swirl :
> On Thu, Nov 25, 2010 at 6:06 AM, Yoshiaki Tamura
> wrote:
>> Hi,
>>
>
On Sat, Nov 27, 2010 at 8:53 AM, Yoshiaki Tamura
wrote:
> 2010/11/27 Stefan Hajnoczi :
>> On Sat, Nov 27, 2010 at 4:29 AM, Yoshiaki Tamura
>> wrote:
>>> 2010/11/27 Blue Swirl :
On Thu, Nov 25, 2010 at 6:06 AM, Yoshiaki Tamura
wrote:
Somehow I find some similarities to instrumentat
> One question I have about Kemari is whether it adds new constraints to
> the QEMU codebase? Fault tolerance seems like a cross-cutting concern
> - everyone writing device emulation or core QEMU code may need to be
> aware of new constraints. For example, "you are not allowed to
> release I/O op
On Sat, Nov 27, 2010 at 8:53 AM, Yoshiaki Tamura
wrote:
> 2010/11/27 Stefan Hajnoczi :
>> On Sat, Nov 27, 2010 at 4:29 AM, Yoshiaki Tamura
>> wrote:
>>> 2010/11/27 Blue Swirl :
On Thu, Nov 25, 2010 at 6:06 AM, Yoshiaki Tamura
wrote:
> Hi,
>
> This patch series is a revised
2010/11/27 Stefan Hajnoczi :
> On Sat, Nov 27, 2010 at 4:29 AM, Yoshiaki Tamura
> wrote:
>> 2010/11/27 Blue Swirl :
>>> On Thu, Nov 25, 2010 at 6:06 AM, Yoshiaki Tamura
>>> wrote:
Hi,
This patch series is a revised version of Kemari for KVM, which
applied comments for the prev
On Sat, Nov 27, 2010 at 4:29 AM, Yoshiaki Tamura
wrote:
> 2010/11/27 Blue Swirl :
>> On Thu, Nov 25, 2010 at 6:06 AM, Yoshiaki Tamura
>> wrote:
>>> Hi,
>>>
>>> This patch series is a revised version of Kemari for KVM, which
>>> applied comments for the previous post and KVM Forum 2010. The
>>> c
2010/11/27 Blue Swirl :
> On Thu, Nov 25, 2010 at 6:06 AM, Yoshiaki Tamura
> wrote:
>> Hi,
>>
>> This patch series is a revised version of Kemari for KVM, which
>> applied comments for the previous post and KVM Forum 2010. The
>> current code is based on qemu.git
>> f711df67d611e4762966a249742a5f
On Thu, Nov 25, 2010 at 6:06 AM, Yoshiaki Tamura
wrote:
> Hi,
>
> This patch series is a revised version of Kemari for KVM, which
> applied comments for the previous post and KVM Forum 2010. The
> current code is based on qemu.git
> f711df67d611e4762966a249742a5f7499e19f99.
>
> For general inform
Hi,
This patch series is a revised version of Kemari for KVM, which
applied comments for the previous post and KVM Forum 2010. The
current code is based on qemu.git
f711df67d611e4762966a249742a5f7499e19f99.
For general information about Kemari, I've made a wiki page at
qemu.org.
http://wiki.qem
30 matches
Mail list logo
