Managed to reproduce the issue, here's how the Mitaka MSI is called (changed the username):
msiexec /i HyperVNovaCompute_Mitaka_13_0_0.msi /l*v ADDLOCAL=HyperVNovaCompute,NeutronHyperVAgent,iSCSISWInitiator,FreeRDP NEUTRONADMINTENANTNAME=services RPCBACKENDPORT=5672 USECOWIMAGES=1 GLANCEPORT=9292 DYNAMICMEMORYRATIO=1 CONFIGDRIVEINJECTPASSWORD=1 GLANCEHOST=10.63.167.3 NEUTRONURL=http://10.63.167.3:9696 ADDVSWITCH=0 NEUTRONADMINPASSWORD=********** INSTANCESPATH=C:\OpenStack\Instances RPCBACKEND=RabbitMQ NOVACOMPUTESERVICEPASSWORD=******** NEUTRONADMINAUTHURL=http://10.63.167.3:35357/v3 RDPCONSOLEURL=http://HV1:8000 ENABLELOGGING=1 NOVACOMPUTESERVICEUSER=HV1\UsernameChanged NEUTRONADMINUSERNAME=neutron VSWITCHNAME=v-magine-data FORCECONFIGDRIVE=1 LOGDIR=C:\OpenStack\Log RPCBACKENDHOST=10.63.167.3 VERBOSELOGGING=1 /qb /l*v c:\log.txt
If the NOVACOMPUTESERVICEPASSWORD has characters like e.g. =,", etc, this might not be recognized properly by the msiexec escaping, resulting in the service not starting due to a wrong password.
The resulting error is a "service user not found" error that unfortunately Windows translates in a very misleading "The system cannot find the drive specified".
We're currently testing a fix for this issue.
In the v-magine directory, there's a nova_install.log file. Can you please share it?
I have uploaded the nova_install.log file to an Amazon S3 Storage bucket and shared the link above. Hope that helps.
Thanks for the log. Here's the relevant error, this happens when restarting the nova-compute service: http://paste.openstack.org/show/579313/. In order to try to reproduce the issue, what Windows version and build are you using?
I am using Microsoft Hyper-V Server 2012 R2 (Version Major: 6 | Minor: 3 | Build: 9600 | Revision: 0)
Thanks for the details. Some more questions that could help: is the instance fully updated (Windows updates)? Do you have an antivirus running?