<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="Verdana">Thank you for backing out </font><a
class="missing changeset" title="No changeset 77457 in the
repository">r77457</a> (due to VDI file content corruption) This
seems to have fixed the corruption of currently installed guests.<br>
<br>
Would it be possible to get a current Extension Pack? <br>
<br>
Seems current changes require it to be updated.<br>
<br>
<br>
<br>
<br>
On 04/15/2012 07:35 PM, Perry Halbert wrote:
<blockquote cite="mid:4F8B6951.5070303@cox.net" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<font face="Verdana">This is what the error returns about the
corrupt VDI. <br>
<br>
Failed to open a session for the virtual machine Ubuntu-10.04.<br>
<br>
UUID {01e7f120-0000-0000-0200-00008a000000} of the medium
'/drive/tara1/VirtualBox-VMs/Ubuntu-10.04/Ubuntu-10.04.vdi' does
not match the value {83a60317-2b7a-47a1-8eee-0df6a8b64e61}
stored in the media registry
('/home/perry/.VirtualBox/VirtualBox.xml').<br>
<br>
Result Code: NS_ERROR_FAILURE (0x80004005)<br>
Component: Medium<br>
Interface: IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}<br>
</font><br>
<br>
On 04/15/2012 07:30 PM, Perry Halbert wrote:
<blockquote cite="mid:4F8B680B.8010900@cox.net" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<font face="Verdana">Latest from SVN r40927 completely ruins the
Virtual Guest. It comes back with the following.<br>
<br>
<br>
Failed to open a session for the virtual machine Ubuntu-10.04.<br>
<br>
The device instance structure version has changed.<br>
<br>
If you have upgraded VirtualBox recently, please make sure you
have terminated all VMs and upgraded any extension packs. If
this error persists, try re-installing VirtualBox.
(VERR_PDM_DEVINS_VERSION_MISMATCH).<br>
<br>
Result Code: NS_ERROR_FAILURE (0x80004005)<br>
Component: Console<br>
Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}<br>
<br>
At this point you say ok and the VDI file becomes corrupt and
Inaccessible.<br>
There is no recovery from this that I can find as even trying
to reattach it comes back with the Parent file does not exist
in VirtualBox.xml<br>
<br>
Reverting back to r40867 does not fix the corrupt files but
does work on ones you have not tried to start.<br>
</font> <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
vbox-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.virtualbox.org/mailman/listinfo/vbox-dev">https://www.virtualbox.org/mailman/listinfo/vbox-dev</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
vbox-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a>
<a class="moz-txt-link-freetext" href="https://www.virtualbox.org/mailman/listinfo/vbox-dev">https://www.virtualbox.org/mailman/listinfo/vbox-dev</a>
</pre>
</blockquote>
</body>
</html>