Changes between Version 1 and Version 2 of Ticket #14296, comment 41
- Timestamp:
- Jun 30, 2016 10:16:06 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14296, comment 41
v1 v2 1 The issue seems to be a corruption of the VirtualBox.xml file in the ~/.homestead folder. Go to this folder delete the VirtualBox.xml file, copy and rename the VirtualBox.xml-prev to VirtualBox.xml-prev and save. Try running VB again and this should resolve the issue. At least it has for me on 2 separate occasions. FYI this happened after I deleted a box and restarted my computer. 1 The issue seems to be a corruption of the VirtualBox.xml file in the ~/.homestead folder. Go to this folder delete the VirtualBox.xml file, copy and rename the VirtualBox.xml-prev to VirtualBox.xml-prev and save. Try running VB again and this should resolve the issue. At least it has for me on 2 separate occasions. FYI this happened after I deleted a box and restarted my computer. VirtualBox.xml is just completely blank. .xml file locked while trying to write to it?
