[one-users] Wrong image-size reported by oneimage

In opennebula-3.2.0 every VMware-image that is created with oneimage has the wrong size (as reported by "oneimage list"). The problem is in $ONE_LOCATION/var/remotes/image/fs/fsrc The du command is used on dirs, and reports the size in kilobytes, but the expected size is in bytes (as report

[one-users] Missing monitoring information from VMware (ESXi 4.1)

We just upgraded from openebula-3.0.0 to 3.2.0, but it looks like monitoring in the VMware-driver is still incomplete, or is our opennebula installation not working properly? I'm speaking about the CPU and MEM stats when using "onevm list" [oneadmin ~]$ onevm list ID USER GROUPNAME

Re: [one-users] oneacctd crashes (opennebula 3.2)

I would just like to add that we too had the exact same problem with acctd after upgrading to 3.2. Have been running the patch for a while and it seems to fix the problem. oneacctd has not crashed again. Thanks for the patch! --- Håkan Isaksson On Mon, 23 Jan 2012 17:41:37 +0100, Daniel Mo

Re: [one-users] Clean up OpenNebula

I believe the database table 'pool_control' contains that information, a "update pool_control set last_oid=0 where tablename like 'vm_pool'" would reset the vm-counter. Exactly how you update it, would depend on if you are using mysql or sqllite. -- Håkan Isaksson Init System Management