Since my upgrade to 13.37 + VirtualBox 4.0.4 (from SBo) I'm having trouble with one of my VMs containing a PostgreSQL installation (also from SBo) which has been running fine before on 13.1 + VBox 3.2.10.
This is what happens: I'm starting an I/O heavy job on the DB that should take about an hour but never finishes because the virtual disk stops working after 10 to 40 minutes.
ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/00:00:e8:11:44/01:00:02:00:00/40 tag 0 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
...lots of these
ata1.00: device reported invalid CHS sector 0
...and lots of these
The messages vary slightly from time to time, so do the symtpoms. Sometimes just the DB crashes, sometimes I get a forced filesystem shutdown. It happens on the original 13.1-VM and also on a freshly installed 13.37-VM.
There's one message...
hrtimer: interrupt took 6544232 ns
...in the VMs syslog as soon as I/O starts which suggests timing problems and which I don't think I've seen before. It's the only hint. The host machine is working fine and the VM's VBox.log doesn't log anything when the crash happens.
Here's what I've tried so far to solve this problem:
- upgraded to VirtualBox 4.0.8 and back to 4.0.4 again
- switched virtual disk between IDE and SATA - with and without host cache
- tested countless kernel boot options in the VM
- downgraded the host-kernel to 18.104.22.168 (config from /testing)
Nothing of this helped. The virtual IDE-disk has different error messages (including a very interesting "lost interrupt" message) but crashes nontheless.
The Postgres-DB is for development only, so I'm not losing any data here, but I haven't been getting any work done since, either :-(
Has anyone else encountered this problem or can at least point me into the right direction?
PS: VirtualBox was built in a multilib VM, but host and guest are pure 64-bit. I've been using this setup since 13.0.