积极答复者
运行Virtual server 2005 r2时遇到的问题

问题
答案
-
Incorrect user rights on virtual machine folder causes unexpected or disk-related errors during startup
When you try to start a virtual machine with a user account that does not have Write access to the virtual machine configuration folder, you will receive a message such as, "The virtual machine Virtualmachinename could not be started. An unexpected error occurred." Or "Virtualmachinename could not be started because a disk-related error occurred." This occurs because Virtual Server creates an empty saved state (.vsv) file in the virtual machine configuration folder when a virtual machine starts up. You can resolve this problem by granting Write permission on the virtual machine configuration folder to the user account for the virtual machine.
简单的说因为你的磁盘可能是由于进行做保存状态或者是一个空的错误保存状态,你需要重新设定该虚拟机对该磁盘的写入权限。
全部回复
-
Incorrect user rights on virtual machine folder causes unexpected or disk-related errors during startup
When you try to start a virtual machine with a user account that does not have Write access to the virtual machine configuration folder, you will receive a message such as, "The virtual machine Virtualmachinename could not be started. An unexpected error occurred." Or "Virtualmachinename could not be started because a disk-related error occurred." This occurs because Virtual Server creates an empty saved state (.vsv) file in the virtual machine configuration folder when a virtual machine starts up. You can resolve this problem by granting Write permission on the virtual machine configuration folder to the user account for the virtual machine.
简单的说因为你的磁盘可能是由于进行做保存状态或者是一个空的错误保存状态,你需要重新设定该虚拟机对该磁盘的写入权限。 -
你好, momoheiyu
这通常是权限问题,要提供写入权限
The disk errors were being caused by backups on the host server. Virtual Server needs full access to the VM files. Apparently the backup agent was locking the files which was causing the VMs to shut down intermittently.
解决方法:
This occurs because Virtual Server creates an empty saved state (.vsv) file in the virtual machine configuration folder when a virtual machine starts up. You can resolve this problem by granting Write permission on the virtual machine configuration folder to the user account for the virtual machine.