qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC v4 PATCH 00/49] Initial support of multi-process qemu - status


From: Felipe Franciosi
Subject: Re: [RFC v4 PATCH 00/49] Initial support of multi-process qemu - status update
Date: Mon, 16 Dec 2019 19:57:32 +0000

Heya,

> On 16 Dec 2019, at 20:47, Elena Ufimtseva <address@hidden> wrote:
> 
> On Fri, Dec 13, 2019 at 10:41:16AM +0000, Stefan Hajnoczi wrote:
>>> On Mon, Dec 09, 2019 at 10:47:17PM -0800, Elena Ufimtseva wrote:
>>> At this moment we are working on the first stage of the project with help of
>>> the Nutanix developers.
>>> The questions we have gathered so far will be addressed with muser
>>> and Qemu developers after we finish the first stage and make sure we 
>>> understand
>>> what it will take for us to move onto the next stage.
>>> 
>>> We will also incorporate relevant review from Stefan that he provided
>>> on the series 4 of the patchset. Thank you Stefan.
>>> 
>>> If anyone have any further suggestions or questions about the status,
>>> please reply to this email.
>> 
>> Hi Elena,
>> At KVM Forum we discussed spending 1 or 2 weeks trying out muser.  A few
>> weeks have passed and from your email it sounds like this "next stage"
>> might be a lot of work.
>> 
> 
> Hi Stefan
> 
> Perhaps we were not too clear about our work in the previous email.
> Our assumption was that the question that came from KVM Forum was
> if muser can be used to achieve the same what we have now.
> We should have answered clearly yes to this question.  We have not yet
> discovered major road blocks.
> At the moment, we are mostly engaged in learning the code and discussing
> the design, plus some coding to answer the specific questions.
> We understand that the best way to make a progress is to work with the
> upstream community on early stages and we agree with this and will present
> the proposal shortly for discussion.
> 
>> Is there a work-in-progress muser patch series you can post to start the
>> discussion early?  That way we can avoid reviewers like myself asking
>> you to make changes after you have invested a lot of time.
>> 
> 
> Absolutely, that is our plan. At the moment we do not have the patches
> ready for the review. We have setup internally a milestone and will be
> sending that early version as a tarball after we have it completed.
> Would be also a meeting something that could help us to stay on the same
> page?

Please loop us in if you so set up a meeting.

> 
>> It's good that you are in touch with the muser developers (via private
>> discussion?  I haven't seen much activity on #muser IRC).
>> 
> 
> We use IRC (I know Jag got some answers there) and github for issues
> (one of which was addressed).

I thought there was only the one. Let us know if you run into any other bugs. 
We are looking forward to hearing about people’s experience and addressing 
issues that come with uses we didn’t foresee or test.

Cheers,
Felipe

> We are hoping to get the conversation going over
> the email.
> 
> JJ, Jag and Elena 
>> Stefan
> 
> 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]