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) 
        
gives:

exception caught:org.libvirt.LibvirtException: invalid domain pointer in 
virDomainSetMemory
level:VIR_ERR_ERROR
code:VIR_ERR_INVALID_DOMAIN
domain:VIR_FROM_DOM
hasConn:false
hasDom:false
hasNet:false
message:invalid domain pointer in virDomainSetMemory
str1:invalid domain pointer in %s
str2:virDomainSetMemory
str3:null
int1:0
int2:0


Furthermore, f.e. conn.GetHypervisorVersion(conn.getType())  gives:


exception caught:org.libvirt.LibvirtException: this function is not supported 
by the hypervisor: Xen
level:VIR_ERR_ERROR
code:VIR_ERR_NO_SUPPORT
domain:VIR_FROM_NONE
hasConn:false
hasDom:false
hasNet:false
message:this function is not supported by the hypervisor: Xen
str1:this function is not supported by the hypervisor: %s
str2:Xen
str3:null
int1:0
int2:0

But

        Domain dom0=conn.domainLookupByID(0); //domainLookupByName("Domain-0"); 
too
        DomainInfo dom0info = dom0.getInfo();
        ....
        dom0.setMemory(256000);
        ....


works without glitches and does the job (btw, I can't see any effect of 
setMaxMemory() on Xen?)

Is it possible that there are some inconsistences between libvirt-java and 
libvirt? Since libvirt-java wasn't updated approx. 1y, I assume that. 

Thanks for feedback,

kr,
thomas

--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to