Custom Query (16363 matches)
Results (2242 - 2244 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1381 | worksforme | Corrupted config file | ||
| Description |
I opened VirtualBox after two days without using it, and I got this error: Could not load the settings file '/home/raziel/.VirtualBox/VirtualBox.xml' (VERR_OPEN_FAILED).
FATAL ERROR: Invalid document structure
Location: '/home/raziel/.VirtualBox/VirtualBox.xml', line 1, column 2.
Result Code:
0x80004005
Component:
VirtualBox
Interface:
IVirtualBox {76b25f3c-15d4-4785-a9d3-adc6a462beec}
and the program isn't able to start. The config file starts with uuid="{6ab09deb-429e-4ad4-b59d-e56dd24b2985}"/> and from there on it seems to be complete. I tried to rebuild the config file googling a complete file, and it seems to work ok (I only had to register again and re-configure some things) I suspect the cause of this issue is I run out of space while running a Windows virtual machine, the machine entered a "pause" state, I freed a GB and continued running the VM without problems. |
|||
| #3805 | fixed | Corrupted data on shared folders => Fixed in SVN | ||
| Description |
On a Windows XP host, I use a linux guest as local web server, where the All has been working fine, until I stumbled upon a bug in version 2.1.4 and 2.2.0 - data on the shared directory is corrupted, while read or written. I can reproduce this consistently, and I have found a minimal* text file that can trigger the bug. ( * if I split the file in two, both the parts will be read correctly ) fran@inside:/var/www/test$ rm -f .hg
fran@inside:/var/www/test$ hg init
fran@inside:/var/www/test$ hg add minfail
fran@inside:/var/www/test$ hg commit -m "Boom"
fran@inside:/var/www/test$ hg verify
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
minfail@0: broken revlog! (index data/minfail.i unknown format 25920)
warning: orphan revlog 'data/minfail.i'
1 files, 1 changesets, 0 total revisions
1 warnings encountered!
1 integrity errors encountered!
(first damaged changeset appears to be 0)
fran@inside:/var/www/test$
The problem is not present if I run mercurial on the host machine, or I copy the files on the virtual machine hard drive. This made me think that Mercurial works fine, but VirtualBox has trouble writing on the shared folder.
The |
|||
| #19695 | fixed | Corrupted downloads over network with hyperv backend | ||
| Description |
I've been trying to use VBox with the hyperv backend to run ansible molecule tests. Since I'm running this inside WSL, I can't use the virtualbox backend. I'm getting weird corruptions when downloading stuff from the internet. Running from my host system: ➜ for i in {0..10}; do curl -sL https://github.com/docker/compose/releases/download/1.26.1/docker-compose-Linux-x86_64 | sha256sum -; done
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
b1c7e9b835dd6a4e6436772fe984bf52c93c13149a6b6d06616c7eda1f66123b -
Running inside the guest VM: [vagrant@instance01 ~]$ for i in {0..10}; do curl -sL https://github.com/docker/compose/releases/download/1.26.1/docker-compose-Linux-x86_64 | sha256sum -; done
07db5c367b7e1395a0ed725f184ef093669c2680ab1a88e3b60909d7e0543a72 -
aeaf6054b4cd865031ccb4a505cee358bffe1c8e9cceca24ec2696308a4815cd -
36ba4ce9fd41db373febe4fda7678b3d1769090e7a6f68ba67c04badc2b02369 -
90c6e105ecc3d5b77aea257b3e287b0cae2f74e2974c01657a64cc1b4d7df36a -
57d1fd185bc5bfa100338f1c200b91cd8cf8649775250fa32876056d882cf64f -
cab806c4f8ae9bc5d59127c417bc1532faed58026103d005b56080c830345b3b -
f46d2f63a84497678f5dae7f158c296d2e73eed5ebe0a1795da0a96d90664b57 -
51a2a7ce5f67607162cca7e05739d7b57460712ee1593d9e2b17b30fea23711c -
044cd79f32c3b51546265ab6e70991533e70ad2071814169832ce20a3dd99811 -
7c9aca42a718c275650c28681a2fd80de01f50f5632da0a08a60facba5b5d1c8 -
307248c92a464c35d45686f3ca438683b5f8de41eb6f01f5bf27a778f6d5579d -
I can reproduce that in centos 7, 8 and debian buster. It renders any network interaction dangerous as anything could be corrupted (god bless package managers checking for file integrity). More context: I'm running molecule using a vagrant driver that invokes vagrant inside WSL. Vagrant knows it runs in WSL and escapes it to run VBoxManager.exe from the host system, basically meaning that me running inside WSL should not change anything. |
|||

