VirtualBOx Upgrade form 2.04 to 2.1

sparticlevbox · Post by **sparticlevbox** » 21. Jan 2009, 18:57

I run a very stable Centos Server currently 5.2 have been using VBox since it came out. Apart form the sometimes flaky HIF networking on reboots. (Have to do service netork restart on the guest to get it working.

VBox is great. However.

Read about the latest and greatest and the promise of much simpler HIF networking.

See link to centos thread. No joy as yet from there.

http://www.centos.org/modules/newbb/vie ... mpost66296

I upgraded after backing up my VM's -FORTUNATELY

I culd run the new 2.1 GUI but trying to start any of my VM's resulted ina complete hang on the host server that only a hard rebooot would solve.

Disabling networkingon the client configs allowed me to boot htem, but whatever networking choice I made resulted in a Host system hang on startup.

I manage dto regress to my stable 2.04 and then I have since upgraded to 2.06 with zero issues. 4 VM's running fine. Can anyone post a step by step to upgrade to 2.1. Or should I wait for 2.1.x

Any help appreciated.

Regards
Spart
Can anyone

Post by **TerryE** » 21. Jan 2009, 20:22

2.1.2 is due out very soon

sparticlevbox · Post by **sparticlevbox** » 21. Jan 2009, 20:46

Cheers, looks like its not only me that is having this issue.

Spart

wpm · Post by **wpm** » 21. Jan 2009, 23:48

I finally got my virtual XP connected via the Host Interface in VirtualBox 2.1 on CentOS 5.2. My initial post is here. Here are the steps I took:

1. Run `VBoxManage clonevdi <virtual xp machine> <outputted xp machine>` to export a clean, unique machine.
2. Remove all installations of VirtualBox from the CentOS machine - mine were installed by yum, I had 2.0.6 and the upgrade to 2.1: I nuked them both. I got rpm to remove them. I verified that all the previous VirtualBox stuff was gone by using `locate` and `whereis`. I doubly ensured that the .Virtualbox directory was gone from my home directory.
3. Install VirtualBox 2.1. I downloaded and installed from the command line: `rpm -Uvh VirtualBox......rpm`
4. Apply [url=ttp://www.virtualbox.org/ticket/2827]this fix[/url] as listed here. This was crucial.
5. Create a virtual machine to initialize the necessary config files and directories.
6. Copy the machine from Step #1 into the .VirtualBox/HardDisk directory in my home directory.
7. Attach that HD to the machine that I created in Step #4.
8. Get the machine up & running with NAT.
9. Manually create a bridge, and attach the XP virtual machine to it, as well as switch the XP machine to Host Interface networking.

I was able to boot the machine without the previous lock-ups, and join the domain where I work. Eureka - several hours invested in finding and applying the solution. It was a lot of work to go at it this way, but it cleared out all the possibilities of problems and ambivalence. I really like VirtualBox: it's fast, light, and has some features that other VMs don't. It was worth it.

Post by **TerryE** » 22. Jan 2009, 18:23

Good! but upgrade to 2.1.2. It's more stable.

sparticlevbox · Post by **sparticlevbox** » 22. Jan 2009, 19:33

Good stuff on the 2.1.2 install etc. BUT I think I am gin gto wait until thi is a biot more stable after taking over 3 hours to undo the damage last time.

Cheers
Spart

wpm · Post by **wpm** » 22. Jan 2009, 21:57

I downloaded the 2.1.2 release this morning, look forward to installing it soon. The above install is still cooking, better than expected.

VirtualBOx Upgrade form 2.04 to 2.1

VirtualBOx Upgrade form 2.04 to 2.1

steps to stabilize CentOS 5.2

Good stuff

still cooking