Hi!
I am a bit aghast after finding my windows xp client has vanished after installing vb 2.2.0 ( previous installed version 2.1.4) on my vista platform.
I had like always shut down the virtual machine before installation.
During the last updates I had always been given a choice of saving existing machines. This time nothing like that happened and instead I am presented with an empty vb.
Any idea what happened? What can I do? Please help urgently!
I do not want to take any wrong step at this point.
Thanks,
Xenia
No virtual machine after update to 2.2.0
Re: No virtual machine after update to 2.2.0
Did you check your VDI's are still there?
[This space is intentionally left blank]
If you can read this, you can read the VirtualBox Manual, the Forum FAQ, and the QuickClick FAQ
-=[ Search this forum with Keywords, VirtualBox solutions at you're fingertips]=-
If you can read this, you can read the VirtualBox Manual, the Forum FAQ, and the QuickClick FAQ
-=[ Search this forum with Keywords, VirtualBox solutions at you're fingertips]=-
Re: No virtual machine after update to 2.2.0
Thanks for responding!
Yes, the xp machine is still there.
Meanwhile I thought it would be a great idea to recover an earlier state of vista just before vb 2.2.0 installation.
Now I am back to 2.1.4.
The xp machine is there. But:
1. On starting VB I get a warning to check as one or more media are not available. When I perform that check the vdi appears to be normal, only guestaddition.iso has an exclamation mark attached.
2. When starting the xp machine I get an error message "Failed to start the virtual machine Windows XP Pro" without any further remarks within the white box below.
I really hope that I did not make things worse by going back to 2.1.4. In the past this windows function has proved to be valuable and it always worked fine provided an appropriate snapshot had been available.
I remarked one thing that seems strange. Below the Sun folder there is now another folder Sun(9) that has also a subfolder "xVM virtual box" that has 2 folders (doc + nls) and 6 files in it, VBoxGuestAdditions.iso being one of them.
Yes, the xp machine is still there.
Meanwhile I thought it would be a great idea to recover an earlier state of vista just before vb 2.2.0 installation.
Now I am back to 2.1.4.
The xp machine is there. But:
1. On starting VB I get a warning to check as one or more media are not available. When I perform that check the vdi appears to be normal, only guestaddition.iso has an exclamation mark attached.
2. When starting the xp machine I get an error message "Failed to start the virtual machine Windows XP Pro" without any further remarks within the white box below.
I really hope that I did not make things worse by going back to 2.1.4. In the past this windows function has proved to be valuable and it always worked fine provided an appropriate snapshot had been available.
I remarked one thing that seems strange. Below the Sun folder there is now another folder Sun(9) that has also a subfolder "xVM virtual box" that has 2 folders (doc + nls) and 6 files in it, VBoxGuestAdditions.iso being one of them.
Re: No virtual machine after update to 2.2.0
You can always try to re-install 2.14
[This space is intentionally left blank]
If you can read this, you can read the VirtualBox Manual, the Forum FAQ, and the QuickClick FAQ
-=[ Search this forum with Keywords, VirtualBox solutions at you're fingertips]=-
If you can read this, you can read the VirtualBox Manual, the Forum FAQ, and the QuickClick FAQ
-=[ Search this forum with Keywords, VirtualBox solutions at you're fingertips]=-
Re: No virtual machine after update to 2.2.0
I had just been about to do so, but wanted to check here to see if there was better adviceYou can always try to re-install 2.14
Repair of version 2.1.4 worked well. Afterwards I deleted the remaining stub of 2.2.0 that is the "Sun(9)" folder.
Back to where I was before the update. Should I try again to update to 2.2.0 or are there known problems with this configuration, that is vista as a host and xp as a guest? I use network via WLAN I should maybe add.
Re: No virtual machine after update to 2.2.0
Wait for 2.2.x
[This space is intentionally left blank]
If you can read this, you can read the VirtualBox Manual, the Forum FAQ, and the QuickClick FAQ
-=[ Search this forum with Keywords, VirtualBox solutions at you're fingertips]=-
If you can read this, you can read the VirtualBox Manual, the Forum FAQ, and the QuickClick FAQ
-=[ Search this forum with Keywords, VirtualBox solutions at you're fingertips]=-
Re: No virtual machine after update to 2.2.0
Thanks a lot for your help!