VirtualBox stuck when multiple VMs run large NFS3 writes (Sun VDI 3.1)

[stegbk]

We are using a Sun VirtualBox VDI version 3.1 solution. For testing, we create VMs using 64-bit Ubuntu 8.04 desktop and have iozone run automatically on start up from the VDI administrator interface. The iozone benchmark writes/reads from an NFS3 mounted directory, which is served from a Sun Store x7310. One VM works fine, but when I get past 3-4 about 60% end up in a "stuck" state (I have generally tested with 10 and consistently end up with 6 stuck VMs).

This ends up being a fairly major problem because a user who is assigned to a stuck VM can do nothing to get a new VM from the pool without intervention by the VDI administrator.

[Klaus Espenlaub]

The Sun VDI 3.1 EA package you're running comes with VirtualBox 3.0.6, which has known bugs on Solaris hosts which have been fixed in the mean time. Since the VirtualBox setup in the VDI context has a special install configuration (it contains the regular VirtualBox package) you cannot just install a different version. The official way is to wait for VDI 3.1 RR, which will come with VirtualBox 3.0.12.

[Ramshankar Venkataraman]

Afaik, Sun VDI 3.1 RR is available. Closing this ticket as fixed, please reopen if relevant.