CentOS 5.2 + VBox 2.2.2 + Bridge Network = Hang!

[flim]

Hi I am frustrated because each time I start the guest OS, my DELL VOSTRO 1200 will hang! Caplock and scroll lock will flash!

I have 4GB memory, CentOS 5.3 32-bit, VBOX 2.2.2, I check the log and sure VBOX installed successfully, added user in virutalbox group.
I use static IP.

If I choose another network type like NAT, no hang.

Please help.

Thank you.

[Perryg]

Not enough information to be able to help.
Forum Posting Guideline

• Please provide host and guest memory.
• What is the guest OS?
• What are the VBox settings (all of them) for the guest?

Also you may need to re-install VirtualBox due to driver issues, have you tried this yet?

[flim]

Here is my configuration:

Host:
Machine: Dell Vostro 1200
CPU: T7250
Memory: 4GB
OS: CentOS 5.3 32-bit
Network: Static IP

Guest 1:
VBox setting: Default except Memory and Network
OS: SLES 10 SP2
Operating System: Linux
Version: openSUSE
Disk size: 5GB
Memory: 384MB
Video Memory: 12 MB
Network Attach To: Bridged Adapter

I tried to install another Linux, setting same as Guest 1, when I click "Start", the Guest window show up and display the Sun VirtualBox startup screen, it didn't get the opportunity to start the guest but the machine hang, the Caplock and Scroll lock LED is flashing.

I tried remove and install VBox again but same.

I don't have any issue with the Host CentOS, with latest package installed. BIOS settings are default, and I have the latest firmware.

Thank you.

[Perryg]

You need to try to give openSUSE at least 1024 meg of memory to install and then after you get it installed you can bring it back down some. Try that and let me know.
And as a helping thought you might want to give it more (hard drive) dynamic memory. the 5 gig you set will be the maximum it will be able to grow to.

[flim]

The SUSE is build on old version of VBox on Windows Host. It can boot if I choost network attach to other network type. So the hang is just for bridged network.

I tried allocate 1GB memory for a new guest, the VBox just can't start and hang on startup screen.

So I think it is not the size or disk image size issue, should be some problems in bridged network.