Click on virtual machine having no snapshots.I don't know in witch version this bug appears, I was migrating vbox from v4.0.12 to v4.1.2 today (I'd never used v4.1.0!)ĭetailed step-by-step instruction for VirtualBox v4.1.2: So it looks like snapshots are seriously broken in v4.1.2. Revert to snapshot 1 - and you will get the broken "Inaccessible" state of virtual machine.Click on Current State and create another snapshot start virtual machine and shut-down.Then just shut-down machine, you don't need to change anything. On virtual machine having no snapshots (just like mine following step 12 above) create snapshot, just select default snapshot names.Now I can reproduce the same problem when ever I like following the following actions: So I am back with virtual machine without snapshots. I know I have lost snapshots but I don't care about them, this is just testing computer. Click on Settings button on my virtual machine and on Storage added vdi from step 9.Virtual GUI Virtual Media Manager - removed the non-existing vdi (because of step 8).Moved back the vdi file from step 1 to location step 8 using Linux mv command.Using operating system tools I have deleted vdi file (created by create new virtual machine action).Start VirtualBox GUI, create new virtual machine, selecting default settings.I have run a command to avoiding getting "bad exit status 101" error at system startup: sudo /etc/init.d/vboxdrv setup -force.I have reinstalled the product: sudo dpkg -i virtualbox-4.1.Note: Maybe there is some simpler work-around, just I don't know about it. so I have uninstalled VirtualBox using command: sudo dpkg -P virtualbox-4.1 I have tried to delete virtual machine but got error.I have copied the main vdi file to safe location using operating system tool (Linux: mv command).This is my test environment and having only single virtual machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |