[vbox-dev] Major problem with latest from SVN

Perry Halbert phalbert at cox.net
Mon Apr 16 09:07:18 PDT 2012


Oh I have no problems with backups.  Do it daily and all control file 
before any update.  I just though you should know what happens outside 
your environment.



On 04/16/2012 11:00 AM, Frank Mehnert wrote:
> Hi Perry,
>
> in the meantime the changeset was fixed and re-applied. The symptom
> of the bug was that the UUID of VDI files was changed and therefore
> it was probably not correct identified by VirtualBox anymore. But I
> cannot completely rule out that there are other smaller problems in
> the medium registry in comparison to 4.1.12 because there were some
> fixes (which might cause regressions) since then.
>
> There was another bug in the VMM/Devices code which is now also fixed
> so the latest SVN tree as of r40944 should be much stabler now. As
> this problem affected R0 code it might be necessary to reboot your
> host if you run the buggy code on that host before.
>
> But these issues remind us to always backup data, especially when
> using with the VirtualBox SVN repository :)
>
> Kind regards,
>
> Frank
>
> On Monday 16 April 2012 16:39:17 Perry Halbert wrote:
>> Thanks I will give it a shoot.
>>
>> I also noticed a lot of issues when trying to add a *.vdi instead of
>> creating a new HDD at creation.  Error says the *.vdi is not registered
>> in the VirtualBox.xml and refuses to use it.  Since we can't add in the
>> VMM any longer this is a show stopper for using existing guest VDI.
>>
>> Another issue is I have been able to create the guest folder and place
>> the *.VDI file in it and then create the guest and point that to the
>> existing *.VDI file.  No other files in the folder just the VDI.  Now it
>> says that the folder can not be used because it already exists.  It used
>> to be as long as no .vbox file was not there it would allow you to
>> create the guest.
>>
>> On 04/16/2012 09:22 AM, Frank Mehnert wrote:
>>> Perry,
>>>
>>> thanks for the report and sorry for the delayed response. But it seems
>>> that current HEAD has some more problems which we are investigating
>>> (e.g. we see SEGFAULTs in certain circumstances).
>>>
>>> But I've uploaded an extension pack which should work with current
>>> HEAD to
>>>
>>>     http://www.virtualbox.org/download/testcase/Oracle_VM_VirtualBox_Exten
>>>     sion_Pack-4.1.51-77491.vbox-extpack
>>>
>>> Kind regards,
>>>
>>> Frank
>>>
>>> On Monday 16 April 2012 15:55:13 Perry Halbert wrote:
>>>> Thank you for backing out r77457 (due to VDI file content corruption)
>>>> This seems to have fixed the corruption of currently installed guests.
>>>>
>>>> Would it be possible to get a current Extension Pack?
>>>>
>>>> Seems current changes require it to be updated.
>>>>
>>>> On 04/15/2012 07:35 PM, Perry Halbert wrote:
>>>>> This is what the error returns about the corrupt VDI.
>>>>>
>>>>> Failed to open a session for the virtual machine Ubuntu-10.04.
>>>>>
>>>>> 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').
>>>>>
>>>>> Result Code: NS_ERROR_FAILURE (0x80004005)
>>>>> Component: Medium
>>>>> Interface: IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
>>>>>
>>>>> On 04/15/2012 07:30 PM, Perry Halbert wrote:
>>>>>> Latest from SVN r40927 completely ruins the Virtual Guest.  It comes
>>>>>> back with the following.
>>>>>>
>>>>>>
>>>>>> Failed to open a session for the virtual machine Ubuntu-10.04.
>>>>>>
>>>>>> The device instance structure version has changed.
>>>>>>
>>>>>> 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).
>>>>>>
>>>>>> Result Code: NS_ERROR_FAILURE (0x80004005)
>>>>>> Component: Console
>>>>>> Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
>>>>>>
>>>>>> At this point you say ok and the VDI file becomes corrupt and
>>>>>> Inaccessible.
>>>>>> 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
>>>>>>
>>>>>> Reverting back to r40867 does not fix the corrupt files but does work
>>>>>> on ones you have not tried to start.
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> vbox-dev mailing list
>>>>>> vbox-dev at virtualbox.org
>>>>>> https://www.virtualbox.org/mailman/listinfo/vbox-dev
>>>>> _______________________________________________
>>>>> vbox-dev mailing list
>>>>> vbox-dev at virtualbox.org
>>>>> https://www.virtualbox.org/mailman/listinfo/vbox-dev
>>> _______________________________________________
>>> vbox-dev mailing list
>>> vbox-dev at virtualbox.org
>>> https://www.virtualbox.org/mailman/listinfo/vbox-dev
>
>
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> https://www.virtualbox.org/mailman/listinfo/vbox-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.virtualbox.org/pipermail/vbox-dev/attachments/20120416/3dcc7385/attachment-0001.html 


More information about the vbox-dev mailing list