The normal method for upgrading the PUEL version from the Sun website no longer works. It downloads but when it comes to installing Yast complains about conflicts with the existing version. Is uninstalling the existing Virtualbox and then installing from scratch really the only option??? And if so, is it safe to simply direct the new 3.1.2 to the existing .vdi?
I only ever install PUEL with the .rpm in a terminal
rpm -Uhv <package>
I’ll check it in while and report back
Most likely your present vdi will be automatically picked up by the new VB install and yes it’s safe.
From 3.1 Sun changed the package name to VirtualBox-3.1, so if your old version is pre 3.1 you’ll have to uninstall it and make a new install. From 3.1 to 3.12 is ok to just upgrade the usual way.
Yes it’s 3.0.12. So if I uninstall that and do a fresh install of 3.1.2 it should just pick up the existing vdi?
The main reason I’m asking to make sure is that this is on a “testbed laptop” which I don’t bother to backup (on my main machine I backup everything of course) and Virtualbox runs Windows 7 which I don’t want to have to reinstall if I can avoid it.
Tried that, same result.
rpm -Uhv
went perfectly
http://thumbnails3.imagebam.com/6198/cbb39e61976444.gif](http://www.imagebam.com/image/cbb39e61976444/)
I assume you did the upgrade from a version => 3.1?
Oh I see, Yes.
I just do that with each upgrade.
FYI. In the past when I have done a removal - I just keep the virtual disk, scrap everything else, including .VirtualBox
Then pop the vdi in the Hard Disk folder
Create New Machine, choose use existing HD and point to the vdi
simple
caf4926 wrote:
>
> Oh I see, Yes.
> I just do that with each upgrade.
>
> FYI. In the past when I have done a removal - I just keep the
> virtual disk, scrap everything else, including .VirtualBox
> Then pop the vdi in the Hard Disk folder
> Create New Machine, choose use existing HD and point to the vdi
> simple
>
Just want to verify your steps. You copy the .vdi somewhere. Uninstall
the old 3.0 version, install new 3.1 version then move the old .vdi
back to ~/.virtualbox/harddisks.
Is this correct, will it retain my XP installation or do I need to
reinstall it?
Thanks
–
Russ
[openSUSE 11.2 (2.6.31.5-0.1-desktop, x86_64] KDE 4.3.4 release 2,
Intel Core 2 Dual E7200, 4 GB RAM, GeForce 8400 GS, 320GB Disc (2)
You got it.
You still have to create New Machine, but just choose to use existing HD and point to the vdi you saved.
No re-installing required!
I keep my virtual disks on a separate partition that never gets touched by any operating system installation.
Never have to reinstall Windows no matter what happens.
By default VDIs and machine descriptions iare kept under your home directory so if you retain /home, you should be ok. If you changed it, then it’s your responsibility to back the data up.
It should be ok to use older machine descriptions in XML, VB will convert previous versions as needed.
caf4926 wrote:
>
> You got it.
>
> You still have to create New Machine, but just choose to use
> existing HD and point to the vdi you saved.
> No re-installing required!
>
Thanks. Will try Later today.
–
Russ
[openSUSE 11.2 (2.6.31.5-0.1-desktop, x86_64] KDE 4.3.4 release 2,
Intel Core 2 Dual E7200, 4 GB RAM, GeForce 8400 GS, 320GB Disc (2)
ken yap wrote:
>
> By default VDIs and machine descriptions iare kept under your home
> directory so if you retain /home, you should be ok. If you changed
> it, then it’s your responsibility to back the data up.
>
> It should be ok to use older machine descriptions in XML, VB will
> convert previous versions as needed.
>
Thanks, I keep home and always back it up.
–
Russ
[openSUSE 11.2 (2.6.31.5-0.1-desktop, x86_64] KDE 4.3.4 release 2,
Intel Core 2 Dual E7200, 4 GB RAM, GeForce 8400 GS, 320GB Disc (2)