Hi Dan, On Fri, 27 Apr 2007 19:07:43 +0100 "Daniel P. Berrange" wrote:
With that the 'virsh dominfo demo' does show correct memory usage. If I do a 'virsh vcpuinfo demo' though the whole box hangs & I get a kernel trace ! At this think I think this is most likely to be something wrong with the Fedora kernel rather than libvirt, since we know there's anumber of other wierd bugs with this 2.6.20 kernel. x86_64 worked fine AFAICT
Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
I'm sorry for my delay in replying. I made a mistake when I confirmed this problem before.
# ./virsh dominfo HVM_RH5_sda6 | grep mem Max memory: 460800 kB Used memory: 299008 kB
I said I could get the value after I changed the definition of XEN_V2_OP_GETDOMAININFOLIST. But actually the virsh command showed the value using "xend_internal.c", not using "xen_internal.c". Here is a result of a comparing between "xend_internal.c" and "xen_internal.c". # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 729 2 r----- 483.5 HVM_RH5_sda6 5 195 2 ------ 10294.2 # virsh setmaxmem HVM_RH5_sda6 500000 # xm list -l HVM_RH5_sda6 | grep mem (maxmem 400) (memory 195) (shadow_memory 6) # ./virsh dominfo HVM_RH5_sda6 [DEBUG] using: xenDaemonDomainGetInfo State: no state CPU(s): 5 CPU time: 10202.0s Max memory: 409600 kB <--- Used memory: 199680 kB <--- # ./virsh dominfo HVM_RH5_sda6 [DEBUG] using: xenHypervisorGetDomainInfo State: no state CPU(s): 5 CPU time: 10214.1s Max memory: 500000 kB <--- Used memory: 207744 kB <--- I think the value is correct when using "xenDaemonDomainGetInfo". So I want to use only "xenDaemonDomainGetInfo" for Xen when executing "virsh dominfo" command. How does that sound ? Thanks, Saori Fukuta