|
|
#1 (permalink) |
|
Guest
Posts: n/a
|
Environment: VS2005 running on Windows Home Server (I know, I know...
).Vista business running as guest. Yes, the disk holding the VHD/VMC files is on a separate disk, not in the WHS pool. I set this up months ago, and everything was fine. About a week ago I noticed the guest wasn't running, so I went into the VS console; sure enough, the guest was off. Tried to start it - VS reports it can't start the guest because the .VHD is read-only! I check the permissions, nothing seems different. So my question: what would cause this, and other than creating a new .VHD is there anything I can do to correct it? Thanks. -- Regards, Dean |
|
|
|
#2 (permalink) |
|
Guest
Posts: n/a
|
No idea what caused it, but you know you're running in a totally unsupported
scenario, so... If the VHD is marked R/O, then check the permissions on the directory where it resides, and the file itself. Make sure both allow read and write. And I'd turn off inherited permissions on them. Finally, make sure that the disk/volume where the VHD resides is NOT part of the WHS pool. -- Charlie. http://msmvps.com/blogs/russel "DPM" <dm@junk.com> wrote in message news:ezZb5UxgKHA.5380@TK2MSFTNGP06.phx.gbl... > Environment: VS2005 running on Windows Home Server (I know, I know... > ). Vista business running as guest. Yes, the disk holding the VHD/VMC> files is on a separate disk, not in the WHS pool. > > I set this up months ago, and everything was fine. About a week ago I > noticed the guest wasn't running, so I went into the VS console; sure > enough, the guest was off. Tried to start it - VS reports it can't start > the guest because the .VHD is read-only! I check the permissions, nothing > seems different. > > So my question: what would cause this, and other than creating a new .VHD > is there anything I can do to correct it? > > Thanks. > -- > Regards, > Dean > > |
|