On 5/26/19 9:41 AM, Yuval Shaia wrote:
On Fri, May 24, 2019 at 08:24:30AM +0300, Marcel Apfelbaum wrote:
Hi Yuval,
On 5/5/19 1:55 PM, Yuval Shaia wrote:
Any GID change in guest must be propogate to host. This is already done
by firing QMP event to managment system such as libvirt which in t
On Fri, May 24, 2019 at 08:24:30AM +0300, Marcel Apfelbaum wrote:
>
> Hi Yuval,
>
> On 5/5/19 1:55 PM, Yuval Shaia wrote:
> > Any GID change in guest must be propogate to host. This is already done
> > by firing QMP event to managment system such as libvirt which in turn
> > will update the host
Hi Yuval,
On 5/5/19 1:55 PM, Yuval Shaia wrote:
Any GID change in guest must be propogate to host. This is already done
by firing QMP event to managment system such as libvirt which in turn
will update the host with the relevant change.
Agreed, *any* management software can do that.
When
On Mon, May 06, 2019 at 10:09:29AM -0500, Eric Blake wrote:
> On 5/5/19 5:55 AM, Yuval Shaia wrote:
> > Any GID change in guest must be propogate to host. This is already done
>
> s/propogate to/propagated to the/
>
> > by firing QMP event to managment system such as libvirt which in turn
>
> s/
On 5/5/19 5:55 AM, Yuval Shaia wrote:
> Any GID change in guest must be propogate to host. This is already done
s/propogate to/propagated to the/
> by firing QMP event to managment system such as libvirt which in turn
s/managment/management/
> will update the host with the relevant change.
>
>
Any GID change in guest must be propogate to host. This is already done
by firing QMP event to managment system such as libvirt which in turn
will update the host with the relevant change.
When qemu is executed on non-qmp framework (ex from command-line) we
need to update the host instead.
Fix it
