Re: Bug in the virDomainGetInfo() API of libvirt 0.1.9 with Xen 3.0.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jan 12, 2007 at 11:47:16AM +0100, Philippe Berthault wrote:
> The maxMem field of the virDomainInfo structure is given in bytes 
> instead of Kbytes when the domain is 0 (Domain-0). With others domains, 
> the value of maxMem is correct.
> 
> Exemple with virsh:
>  On a system with 4 GB memory, virsh reports:
>  # virsh dominfo 0
>  ...
>  Max memory: 4294967292 kB
> 
> With the same libvirt version 0.1.9 but with an older Xen (not 3.0.3), 
> the maxMem value of Domain-0 is correct.

This sounds like a bug in Xen, rather than a bug in libvirt - we don't
have any special handling for Domain-0 - we're just passing back through
whatever data we get from Xen.

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  -=| 


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]