> From: Tian, Kevin
> Sent: Thursday, February 04, 2016 11:02 AM
>
> >
> > Thanks for your summary, Kevin. It does seem like there are only a few
> > outstanding issues which should be manageable and hopefully the overall
> > approach is cleaner for QEMU, management tools, and provides a more
>
> From: Zhiyuan Lv
> Sent: Tuesday, February 02, 2016 3:35 PM
>
> Hi Gerd/Alex,
>
> On Mon, Feb 01, 2016 at 02:44:55PM -0700, Alex Williamson wrote:
> > On Mon, 2016-02-01 at 14:10 +0100, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > > Unfortunately it's not the only one. Another example is,
On Wed, Feb 03, 2016 at 08:04:16AM +, Tian, Kevin wrote:
> > From: Zhiyuan Lv
> > Sent: Tuesday, February 02, 2016 3:35 PM
> >
> > Hi Gerd/Alex,
> >
> > On Mon, Feb 01, 2016 at 02:44:55PM -0700, Alex Williamson wrote:
> > > On Mon, 2016-02-01 at 14:10 +0100, Gerd Hoffmann wrote:
> > > >
On Wed, 2016-02-03 at 08:04 +, Tian, Kevin wrote:
> > From: Zhiyuan Lv
> > Sent: Tuesday, February 02, 2016 3:35 PM
> >
> > Hi Gerd/Alex,
> >
> > On Mon, Feb 01, 2016 at 02:44:55PM -0700, Alex Williamson wrote:
> > > On Mon, 2016-02-01 at 14:10 +0100, Gerd Hoffmann wrote:
> > > > Hi,
> > >
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Thursday, February 04, 2016 4:45 AM
> >
> > First, Jike told me before his vacation, that we cannot do any change to
> > KVM module according to community comments. Now I think it's not true.
> > We can do necessary changes, as
