Daniel P. Berrange wrote:
> On Wed, Nov 04, 2015 at 06:08:00PM +0300, Roman Bogorodskiy wrote:
> > Current monitor code overrides domain object's privateData, e.g.
> > in virBhyveProcessStart():
> >
> > vm->privateData = bhyveMonitorOpen(vm, driver);
> >
> > where bhyveMonitorPtr() returns
On Wed, Nov 04, 2015 at 06:08:00PM +0300, Roman Bogorodskiy wrote:
> Current monitor code overrides domain object's privateData, e.g.
> in virBhyveProcessStart():
>
> vm->privateData = bhyveMonitorOpen(vm, driver);
>
> where bhyveMonitorPtr() returns bhyveMonitorPtr.
>
> This is not right
Roman Bogorodskiy wrote:
> Current monitor code overrides domain object's privateData, e.g.
> in virBhyveProcessStart():
>
> vm->privateData = bhyveMonitorOpen(vm, driver);
>
> where bhyveMonitorPtr() returns bhyveMonitorPtr.
>
> This is not right thing to do, so make bhyveMonitorPtr
> a
Roman Bogorodskiy wrote:
> Current monitor code overrides domain object's privateData, e.g.
> in virBhyveProcessStart():
>
> vm->privateData = bhyveMonitorOpen(vm, driver);
>
> where bhyveMonitorPtr() returns bhyveMonitorPtr.
>
> This is not right thing to do, so make bhyveMonitorPtr
> a
Current monitor code overrides domain object's privateData, e.g.
in virBhyveProcessStart():
vm->privateData = bhyveMonitorOpen(vm, driver);
where bhyveMonitorPtr() returns bhyveMonitorPtr.
This is not right thing to do, so make bhyveMonitorPtr
a part of the bhyveDomainObjPrivate struct and
