On Wed, Dec 02, 2020 at 10:33:01PM +0530, priyankar jain wrote:
> On 02/12/20 9:46 pm, Daniel P. Berrangé wrote:
> > On Wed, Dec 02, 2020 at 09:25:27PM +0530, priyankar jain wrote:
> > > On 20/11/20 12:17 am, Daniel P. Berrangé wrote:
> > > > On Thu, Nov 19, 2020 at 06:28:55PM +, Priyankar Jain
On 02/12/20 9:46 pm, Daniel P. Berrangé wrote:
On Wed, Dec 02, 2020 at 09:25:27PM +0530, priyankar jain wrote:
On 20/11/20 12:17 am, Daniel P. Berrangé wrote:
On Thu, Nov 19, 2020 at 06:28:55PM +, Priyankar Jain wrote:
Today, dbus-vmstate maintains a constant connection to the dbus. This i
On Wed, Dec 02, 2020 at 09:25:27PM +0530, priyankar jain wrote:
> On 20/11/20 12:17 am, Daniel P. Berrangé wrote:
> > On Thu, Nov 19, 2020 at 06:28:55PM +, Priyankar Jain wrote:
> > > Today, dbus-vmstate maintains a constant connection to the dbus. This is
> > > problematic for a number of reas
On 20/11/20 12:17 am, Daniel P. Berrangé wrote:
On Thu, Nov 19, 2020 at 06:28:55PM +, Priyankar Jain wrote:
Today, dbus-vmstate maintains a constant connection to the dbus. This is
problematic for a number of reasons:
1. If dbus-vmstate is attached during power-on, then the device holds
On Thu, Nov 19, 2020 at 06:28:55PM +, Priyankar Jain wrote:
> Today, dbus-vmstate maintains a constant connection to the dbus. This is
> problematic for a number of reasons:
> 1. If dbus-vmstate is attached during power-on, then the device holds
>the unused connection for a long period of t
Today, dbus-vmstate maintains a constant connection to the dbus. This is
problematic for a number of reasons:
1. If dbus-vmstate is attached during power-on, then the device holds
the unused connection for a long period of time until migration
is triggered, thus unnecessarily occupying dbus.
