On 3/24/2012 7:08 AM, John Francis Lee wrote:
> On 03/24/2012 08:02 AM, John Francis Lee wrote:
>> On 03/24/2012 07:30 AM, John Francis Lee wrote:
>>> On 03/24/2012 06:27 AM, David wrote:
>>>> On 3/23/2012 6:09 PM, John Francis Lee wrote:
>>>>> On 03/22/2012 09:48 AM, John Francis Lee wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I tried to save state when shutting down a virtual machine but ran out
>>>>>> of space in my home directory in the process. The machine became
>>>>>> unresponsive I HUP'd it... now I get...
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> Cannot attach medium '/usr/share/virtualbox/VBoxGuestAdditions.iso'
>>>>>> {a3e00632-0876-4367-a1f3-b8c66e66a571}: medium is already associated
>>>>>> with the current state of machine uuid
>>>>>> {591e86c6-b770-457b-8838-ccfc62e5d0b2}!.
>>>>>> Result Code:
>>>>>> VBOX_E_OBJECT_IN_USE (0x80BB000C)
>>>>>> Component:
>>>>>> Medium
>>>>>> Interface:
>>>>>> IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>> What should I do?
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>
>>>>> So... I have to delete the old machine and reinstall it?! That doesn't
>>>>> sound like fun...
>>>>>
>>>>
>>>>
>>>> Start the GUI. Highlight the 'broken' VM'. Right click and a menu will
>>>> appear. Select "Discard Saved State". You get to keep the VM but this
>>>> will remove the crashed saved state. When you next start the VM it
>>>> should boot like a cold boot.
>>>>
>>>> You obviously need more space to do this since the "Saved State" file
>>>> can be almost as large, often is, as large as the original VM.
>>>
>>> Thanks, but... when I right click on the broken VM the only choices
>>> available are 'remove' and 'refresh'...  all the rest, including
>>> specifically 'Discard Saved State', are greyed out and unavailable.
>>>
>>> The description next to the icon is 'inaccessible'
>>>
>>
>> Looking in
>>
>>    .VirtualBox/Machines/xp/Snapshots
>>
>> I find nothing.
>>
>> It is not apparent what to change in
>>
>>    .VirtualBox/Machines/xp/xp.xml
>>
>> -----------------------------------------------------------------------
>> jfl@ws3:~$ VBoxManage snapshot xp
>> Oracle VM VirtualBox Command Line Management Interface Version 4.1.10
>> (C) 2005-2012 Oracle Corporation
>> All rights reserved.
>>
>> Usage:
>>
>> VBoxManage snapshot<uuid>|<name>
>>                               take<name>  [--description<desc>] [--pause] |
>>                               delete<uuid>|<name>  |
>>                               restore<uuid>|<name>  |
>>                               restorecurrent |
>>                               edit<uuid>|<name>|--current
>>                                    [--name<name>]
>>                                    [--description<desc>] |
>>                               list [--details|--machinereadable]
>>                               showvminfo<uuid>|<name>
>>
>>
>> Syntax error: Not enough parameters
>> --------------------------------------------------------------------
>>
>> I can't figure out how to run that command... all I get is error after error
>>
> 
> Turns out to have been no problem. I decided to bite the bullet and to 
> reinstall the xp machine from the installation disc image... I clicked 
> 'remove' and then 'new',,, when I got pick a disk to install to, I just 
> looked for the old xp disk and chose it. Voila, I had a new machine. 
> Just like the old machine.
> 
> I'm very glad not to have to reinstall windows! What a headache and 
> waste of time that is with all the updates and reboots! Hooray I skipped it.
> 
> Thanks for the help...
> 


If that was meant for me thank you. But I was not really of much help.
Good to hear that all is well again.

However you said "installation disc image". If that means that you are
using an OEM disk (one that came with this computer) those, normally, do
not work well in a VM. They are made for one computer and running
*inside* a VM is no longer 'that computer'.

Speaking of 'reinstalling' you now have a working VM correct? If you
clone it (takes drive space) you would have a replacement if / when your
VM goes bad again.

GUI > highlight the VM > mouse right-click > select 'clone'

-- 

  David

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community

Reply via email to