You build a vmware image which is good for "testing" and nicely isolates zabbix from the host system. However the disk space configured is 60G which is quite large. I'd suggest that you change the configuration and use LVM with a small initial disk size (5G?).

If users later want to extend the storage they can add another virtual disk and with lvm add that to the volume group and if needed extend the partition (LV) size. This makes the configuration more compact and if for example the database is changed to an external database then the footprint of the zabbix image is unlikely to have to grow at all. If you use the latest ext3 tools you can dynamically resize mounted partitions so there should be no issue about having to bring down the zabbix image should disk requirements grow.

I had a look on the openSuSE build page but couldn't figure out how to download the current definition and modify it.