On Tuesday 21 July 2009 13:01:06 Daniel P. Berrange wrote:
> On Tue, Jul 21, 2009 at 11:52:11AM +0200, Thomas Treutner wrote:
> > Hi,
> >
> > I'm playing around with libvirt-0.6.5 and libvirt-java-0.2.1 these days.
> > It looks very interesting, but I think I may have found a bug:
> >
> > ....
> > conn = new Connect("xen://node02", false);
> > ....
> > conn.setDom0Memory(512000)
>
> Hmm, dunno what that method is doing - it doesn't correspond to
> one in the libvirt C API.
>
> It would be worth gettinga trace of API calls by setting
> the following environment variables before running your
> app
>
> LIBVIRT_LOG_FILTERS="1:libvirt" LIBVIRT_LOG_OUTPUTS="1:stderr"
Seems like the domain ID is not defined - not surprisingly:
13:24:07.905: debug : virDomainSetMemory:2601 : domain=(nil), memory=512000
13:24:07.905: error : virLibDomainError:433 : invalid domain pointer in
virDomainSetMemory
Since the dom0 is AFAIK very xen-specific, I wonder if such a function may
ever have been part of libvirt?
kr,
thomas
--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list