Page 3 of 3
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 02:59
by vdotmatrix
Perryg wrote:Is that the error you are seeing? It is not what you posted!
sorry..i don't see what you are referring to . I am going follow your previous instructions in 10mins.
Notifications stopped coming to my inbox for some reason otherwise i would respond to this post immediately.
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 03:08
by Perryg
I was referring to the link you posted. It is a different error than what you posted and dealt with accessing the kernel driver.
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 03:12
by vdotmatrix
Perryg wrote:I was referring to the link you posted. It is a different error than what you posted and dealt with accessing the kernel driver.
no sir...it isn't that at all sorry.
I am going in now Perry. LOL cross n my fingers
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 03:40
by vdotmatrix
Perryg wrote:I don't have any idea what happened to your install. But the issue you have is to get it going again. For what ever reason VirtualBox can not see your guests even though it says it is there.
In the VirtualBox main manager, right click on the guest and left click on remove. When asked if you want to delete say NO. This will remove the guest from VirtualBox but leave everything else in tack. Now close VirtualBox and wait about 30 seconds and start the Main manager again. (your guest should be gone from the tree)
Next click on Machine tab and the add icon. Drill to the folder of the guest and find the *.vbox file and click it to see if VirtualBox will add it back to the tree.
Then see if the guest starts normally. If this works do the same thing to the other guests but if not just stop and tell me what exactly happened and the exact error you see.
You really should do this to one guest only and you should backup the entire guest folder that you are going to do this to before you start.
MacBook Pro, Mac OS X (10.7.4), 16gb ram
This is my hardware. Right now I only have the green NEW button available. when I right clicked and chose remove it only asked once and the choice was cancel or remove: POOF it was gone.
closing and restarting I do not see a machine tab or add button. guest is gone from the tree. the folder with the files I backed up are still around. there is no drilling. LOL
We have been at this all day....
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 03:48
by Perryg
OK. Put the folder back (save the backup) and create a new guest. Try to use the same settings (probably default). When you get to the place where it says create new HDD or use an existing one select to use an existing one and drill to the folder and select the *.vdi file.
Do this on the same guest and not a different one.
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 06:39
by vdotmatrix
Perryg wrote:OK. Put the folder back (save the backup) and create a new guest. Try to use the same settings (probably default). When you get to the place where it says create new HDD or use an existing one select to use an existing one and drill to the folder and select the *.vdi file.
Do this on the same guest and not a different one.
HOLY S**T!!!
Success!
Windows 7 box will not launch though however. windows launch recovery failed to fix the issue and I could not launch windows-7; the xp-pros vb fire right up.
All 3 VB's shared folders are gone; would this be in a -prev file?
thanks for helping me!
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 14:44
by Perryg
You need to assign and remap the shared folders.
I don't know what to do with the Windows 7 can not launch error.
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 15:15
by vdotmatrix
- w7_launch_failure.jpg (43.83 KiB) Viewed 2958 times
I don't need the win-7 box as much but it would be interesting to figure out why during an update all these things failed and at least give someone a fighting chance, THANKS TO YOU, with a similar issue.
I can't thank you enough.....Is this issue related to the original post or should I start another post?
Here are my final Win-7 settings.
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 15:32
by Perryg
I am not sure what happened. Updates rarely cause issues but good backups are always your friend. I remember you saying that you do not use snapshots but you were going to in the future. Just pointing out had you been using snapshots the last attempt that got you going would not have been possible. Snapshots are differencing disks and in no way to be confused with backups. They can be unforgiving and impossible to deal with and IMHO unless you do a daily full backup should not be used.
This topic should be closed as resolved. Please post a new topic on the Windows 7 issues.
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 16:21
by vdotmatrix
Perryg wrote:I am not sure what happened. Updates rarely cause issues but good backups are always your friend. I remember you saying that you do not use snapshots but you were going to in the future. Just pointing out had you been using snapshots the last attempt that got you going would not have been possible. Snapshots are differencing disks and in no way to be confused with backups. They can be unforgiving and impossible to deal with and IMHO unless you do a daily full backup should not be used.
This topic should be closed as resolved. Please post a new topic on the Windows 7 issues.
You know ...I was afraid to comment on the snaps shots because I read a lot of scary issues using snap shots.
UGGGG. should I or can I undo snap shots now?
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 16:33
by Perryg
Can I assume that you have already created a snapshot?
If so I would read the users manual on what to do to merge them back to the base. The wording can be confusing so be sure you know what you are doing. You can also clone the guest to create a new one that has the snapshot/s in one file again. This is also covered in your users manual and no need for me to replicate it.
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 27. Jun 2012, 17:04
by mpack
Perryg wrote:They can be unforgiving and impossible to deal with and IMHO unless you do a daily full backup should not be used.
... and if you
are doing a daily full backup then snapshots simply aren't necessary.
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 21. Nov 2012, 06:12
by mcastarey
Perryg:
Hope that at this time you may be at the forum?!!, cause currently i'm having the same issue.
Suddenly I lost power supply, so I restarted my machine (I'm running the virtual box on windows 7) but when I tried to launch the virtual box I got te same error "Runtime error opening 'C:\Users\Marco\.VirtualBox\Machines\Windows XP\Windows XP.xml' for reading: -102 (File not found.)."
I already read all the suggestions that you were saying to vdotmatrix.
But I still have some doubts of what to do, hope that you are around in the site.
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 21. Nov 2012, 15:28
by vdotmatrix
UGGGGG. so I don't know...still in a lurch.....what I did to bring them back did work, but now they are all dead again...so I have to go and redo the fix...thanks for the reminder.
Re: New Version 4.1.18 now rendered all 3 of my VM inaccessi
Posted: 21. Nov 2012, 16:18
by Perryg
@mcastarey ,
Assuming that you do not have a backup that you can restore from.
Verify that "C:\Users\Marco\.VirtualBox\Machines\Windows XP\Windows XP.xml" exists or not and that it has data in it. Next see if there is a backup file *-prev
If the xml is missing but the *-prev is valid you can (after saving the *-prev to a different location as backup) rename the *-prev to *.xml then see if it opens you guest.