On Tue, Dec 16, 2008 at 05:11:10PM +0300, Anton Protopopov wrote:
> >
> > As a general rule the public virDomainPtr objects should not be passed
> > down into internal methods. Likewise, when creating / defining a VM,
> > the virGetDomain call should be the last one in the normal execution
> > path
>
> As a general rule the public virDomainPtr objects should not be passed
> down into internal methods. Likewise, when creating / defining a VM,
> the virGetDomain call should be the last one in the normal execution
> path of the method.
>
> Thus, just pass the 'virConnectPtr' instance to
> openvz
On Tue, Dec 16, 2008 at 04:34:15PM +0300, Anton Protopopov wrote:
> 2008/12/16 Daniel P. Berrange
>
> > On Tue, Dec 16, 2008 at 03:05:30PM +0300, Anton Protopopov wrote:
> > > 2008/12/13 Ivan Vovk
> > You can't have one public
> > driver API method, calling into another directly. openvzDomainSet
2008/12/16 Daniel P. Berrange
> On Tue, Dec 16, 2008 at 03:05:30PM +0300, Anton Protopopov wrote:
> > 2008/12/13 Ivan Vovk
> >
> > > Hello,
> > >
> > >
> > >
> > > after updating to the last official release 0.5.1 my application
> stopped
> > > working. No errors to the log file though i raised
On Tue, Dec 16, 2008 at 03:05:30PM +0300, Anton Protopopov wrote:
> 2008/12/13 Ivan Vovk
>
> > Hello,
> >
> >
> >
> > after updating to the last official release 0.5.1 my application stopped
> > working. No errors to the log file though i raised exceptions where it was
> > possible.
> >
> > i ch
2008/12/13 Ivan Vovk
> Hello,
>
>
>
> after updating to the last official release 0.5.1 my application stopped
> working. No errors to the log file though i raised exceptions where it was
> possible.
>
> i checked with virsh xml description used for creating OpenVZ container and
> got the follow
