ZimaOS partners, your voice counts! Our voting campaign for ZVM feature improvements is still ongoing. Currently, features A (support for more formats of mirrors), D (easier access to mirrors), H (allow importing of instances exported from other VMs), and J (support for lxc) have gained more attention.
We encourage you to keep voting and especially welcome more feedback and new requirements. Your input will directly influence the direction of our development and help us build a more user-friendly ZVM.If there are other features or improvements you’d like to see, please don’t hesitate to leave a comment below or show your support by voting!
Click here to vote and leave a comment, and together we will shape the future of ZimaOS! Discord
Thank you for your active participation and valuable feedback, let’s push ZimaOS to a higher level together! 
It would be fantastic for PCI passthrough to allow the VM to directly access GPU and hardware resources.
please bring support for more installation image formats like raw vm images.vdi, .qcow2, .ova withought having to convert to .iso. thank you team.
1 Like
I second this. At least qcow2 would be great to be supported.
Just got my ZimaCube so I’ve not used it a lot yet, but it looks like the creation process expects an ISO installation file. I think there are a fair amount of VM “appliances” out there that don’t have an installation process, but rather a qcow2 file (or the package VMware uses) that lets you drop it in, boot up, and the appliance is active. I have one in particular that uses qcow2 format that I would like to run. (I’ve been able to run it on QNAP and UnRaid.)
It would be nice to be able to install Home Assistant OS in zvm.
Currently I can’t, because they don’t provide an iso to install, only an image with the OS pre-installed…
1 Like
I second that. At this point ZVM only let you use iso images. Not even img, which HAOS has.
