libvirt users - Oct 2015 - openvz driver

Hi,

I've a question regarding the openvz driver. I noticed that the virsh
dumpxml output does not contain the memory settings. E.g.:

<domain type='openvz'>
  <name>104</name>
  <uuid>ad2e9d0b-d242-482a-8640-5102e49d0f9b</uuid>
  <memory unit='KiB'>0</memory>
  <currentMemory unit='KiB'>0</currentMemory>
  <vcpu placement='static'>2</vcpu>
  <os>
    <type>exe</type>
    <init>/sbin/init</init>
  </os>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>destroy</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
  </devices>
</domain>

Can someone explain why this data is missing? As far as I know the driver reads
the container configuration files, which contains the missing information.


Regards
    Volker



Viele Grüße
    Volker

On 21.10.2015 23:19, Volker Janzen wrote:
> Hi,
> 
> I've a question regarding the openvz driver. I noticed that the virsh
dumpxml output does not contain the memory settings. E.g.:
> 
> <domain type='openvz'>
>   <name>104</name>
>   <uuid>ad2e9d0b-d242-482a-8640-5102e49d0f9b</uuid>
>   <memory unit='KiB'>0</memory>
>   <currentMemory unit='KiB'>0</currentMemory>
>   <vcpu placement='static'>2</vcpu>
>   <os>
>     <type>exe</type>
>     <init>/sbin/init</init>
>   </os>
>   <clock offset='utc'/>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>destroy</on_reboot>
>   <on_crash>destroy</on_crash>
>   <devices>
>   </devices>
> </domain>
> 
> Can someone explain why this data is missing? As far as I know the driver
reads the container configuration files, which contains the missing information.

Yes, this is a bug. Mind posting a patch? You'll need to call
virDomainDefSetMemoryInitial() or virDomainDefSetMemoryTotal() from the
correct place.

Michal