It looks like each supported hypervisor uses it's own policy regarding startup script: * Xen => none * VMWare => none * VirtualBox => $DESTDIR/deploy_$hostname.sh * KVM => $DESTDIR/run.sh
While the KVM one will get ownership set to the calling user, the VirtualBox one will not.
It looks like each supported hypervisor uses it's own policy regarding startup script: deploy_ $hostname. sh
* Xen => none
* VMWare => none
* VirtualBox => $DESTDIR/
* KVM => $DESTDIR/run.sh
While the KVM one will get ownership set to the calling user, the VirtualBox one will not.