I'm facing a problem while starting a virtual machine which has a disk placed on a NAS.
First, I thought that it is completly impossible, because I couldn't find the drive p:\ (I mapped the network path to p:\) while setting the disk path. But when I tried to give the network path \\192.168.1.101\public\VirtM\VirtHD - it was ok.
Now, starting the virtual machine lasts for about 1-2 minutes and finally ends with an error: "The application encountered an error while attempting to change the state of 'VirtXP_dev'."
Some details presented on the error screen:
"Failed to Power on with Error 'The process cannot access the file because another process has locked a portion of the file.' (0x80070021)"
During the time machine is starting I've noticed that I cannot access the \\192.168.1.101\ at all, like it wouldn't exist.
Is it possible, that Hyper-V mounts somewhere intenally this net path and the same way blocks this path for itself? Any idea what's going on?
My Hyper-V runs on W2012 Datacenter server. The virtual machine WindowsXP runs without problems from the local drive. Even after removing the mapping (drive letter p:\ no more available) the situation is the same.
Many thanks for any clues.
mcgi