So, I upgraded to VirtualBox 4.3.22 earlier this week, and have been using it normally, but today, as I try to boot up my WinXP guest, it throws an error that the image has been set to read-only. So, I went to the VM directory, and, sure enough, everything under the directory had the read-only attribute set. No big thing, I figured, so I removed teh read-only attribute from the VM dir, and applied it to all files & subfolders. Yet, when I restarted VirtualBox, and tried to launch the VM, it gave the same error, and had re-set the read-only flag on the image files.
Has anyone else experienced this behavior? I'm not sure what I need to do. I really don't relish the thought of nuking the image and re-creating it again. Just thought I'd see what my options might be. Oh, some info about my host system would probably be helpful:
HP Pavilion dv7
8Gb RAM
2x750Gb hdd
core i7 CPU
Virtualization codes enabled in the BIOS
I'm just trying to figure out what can be done at this point, so any advice will be appreciated.
Many thanks.
working VM image suddenly goes read-only
-
mhanor
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: various
Re: working VM image suddenly goes read-only
Use Process Monitor to determine which process is setting the file attribute. Run it as administrator and set a filter for "Operation is SetBasicInformationFile then Include"