VM is inaccessible

[Alex Banha]

The VM is alive (I can ping it) but cannot access any service: HTTP, SSH, SMTP, anything

It happens with version 4.0.8. It also happened with previous versions: 4.0.2 and 4.0.4, but with 4.0.8 it is worse. I can´t remember if it happened with 3.2.8.

HOST: Linux Slackware current 2.6.38.7 (64 bits) Guest: Linux Slackware current 2.6.38.7 (64 bits)

I can't find any trace of a problem in any log file, neither in the host nor the guest. The guest stops registering MARKs in the /var/log/messages. The host stops writing events in the VM log file until I destroy the VM.

I have 5 VMs in a Intel i7 processor with 12GB of RAM, and they hang randomly. The VDI files are stored in a Linux RAID1.

Originally the VMs were created in version 3.2.8 and upgraded until 4.0.8. Because of the random hangs, I decided to build the 5 VMs from scratch in the 4.0.8 version. The problem remains, they still hang randomly.

[Alex Banha]

Log file of one VM that stopped responding. Stopped with: VBoxManage controlvm VMNAME poweroff

[Alex Banha]

Every machine, host and VMs, has a EXT3 filesystem. I always run the VMs as Headless.

[Frank Mehnert]

I think the problem is that you are still using the Linux TAP interface to attach your VMs to. This is still possible, but keep in mind that you have to setup a DHCP server for each TAP interface yourself. I suggest you to switch to bridged networking and attach every VM directly to eth0. Or use host networking and attach your VMs to a vboxnetX interface. So I don't think this is a bug at all, just looks like a mis-usage to me.