On Thu, Feb 21, 2019 at 02:55:30PM +0300, Michael Tokarev wrote:
> From my PoV, speaking of hosting (virtual or not), you either have to
> trust your provider or run your own physical machine.
We had the same discussion about unfettered access on the serial console
and people said: we, by
21.02.2019 0:08, Marco d'Itri wrote:
On Feb 20, Michael Tokarev wrote:
...
Looks like I was looking at an old version then: now I have installed
the buster version and it's there.
Blacklist functionality has been in qga for a very long time,
Debian includes it since long time too. But
On Feb 20, Michael Tokarev wrote:
> I'm not sure I understood your question. Ubuntu uses the same package
> as Debian, RHEL comes from the same codebase, and the same manual page
> exists on Debian too, and this manpage hasn't been changed (besides
> minor tweaks) since its addition in 2015.
19.02.2019 4:56, Marco d'Itri wrote:
On Feb 10, Bastian Blank wrote:
On Thu, Feb 07, 2019 at 03:49:55PM +0100, Marco d'Itri wrote:
OTOH by default it allows the host to read/write files in the guest, so
it should be installed with a sensible blacklist in
/etc/default/qemu-guest-agent .
What
On Feb 10, Bastian Blank wrote:
> On Thu, Feb 07, 2019 at 03:49:55PM +0100, Marco d'Itri wrote:
> > OTOH by default it allows the host to read/write files in the guest, so
> > it should be installed with a sensible blacklist in
> > /etc/default/qemu-guest-agent .
> What blacklist? I was
On Thu, Feb 07, 2019 at 03:49:55PM +0100, Marco d'Itri wrote:
> OTOH by default it allows the host to read/write files in the guest, so
> it should be installed with a sensible blacklist in
> /etc/default/qemu-guest-agent .
What blacklist? I was unable to find any evidence of a blacklist on
Le 08/02/2019 à 11:08, Thomas Goirand a écrit :
> On 2/7/19 9:58 PM, Bastian Blank wrote:
>> On Thu, Feb 07, 2019 at 10:17:53AM +0100, Thomas Goirand wrote:
>>> As a follow-up with the discussion about agent inside VMs, I wonder if
>>> we should install qemu-guest-agent inside our images.
On 2/7/19 9:58 PM, Bastian Blank wrote:
> On Thu, Feb 07, 2019 at 10:17:53AM +0100, Thomas Goirand wrote:
>> As a follow-up with the discussion about agent inside VMs, I wonder if
>> we should install qemu-guest-agent inside our images. Normally, it
>> provides what Ted was talking about: hooks
On Thu, 2019-02-07 at 21:58 +0100, Bastian Blank wrote:
> On Thu, Feb 07, 2019 at 10:17:53AM +0100, Thomas Goirand wrote:
> > As a follow-up with the discussion about agent inside VMs, I wonder
> > if
> > we should install qemu-guest-agent inside our images. Normally, it
> > provides what Ted was
On Thu, Feb 07, 2019 at 10:17:53AM +0100, Thomas Goirand wrote:
> As a follow-up with the discussion about agent inside VMs, I wonder if
> we should install qemu-guest-agent inside our images. Normally, it
> provides what Ted was talking about: hooks for freezing filesystem,
> mysql, etc.
In
On Thu, Feb 07, 2019 at 10:17:53AM +0100, Thomas Goirand wrote:
> As a follow-up with the discussion about agent inside VMs, I wonder if
> we should install qemu-guest-agent inside our images. Normally, it
> provides what Ted was talking about: hooks for freezing filesystem,
> mysql, etc.
I don't
On Feb 07, Thomas Goirand wrote:
> As a follow-up with the discussion about agent inside VMs, I wonder if
> we should install qemu-guest-agent inside our images. Normally, it
> provides what Ted was talking about: hooks for freezing filesystem,
> mysql, etc.
>
> Thoughts anyone?
I am in favour:
On Thu, 2019-02-07 at 10:17 +0100, Thomas Goirand wrote:
> Hi,
>
> As a follow-up with the discussion about agent inside VMs, I wonder
> if
> we should install qemu-guest-agent inside our images. Normally, it
> provides what Ted was talking about: hooks for freezing filesystem,
> mysql, etc.
>
>
13 matches
Mail list logo
