VB freezing the system

[phild]

I am currently running VB 5.1.4 (which I thought might solve the problem) but did experience it with the previous version too. The host is PCLinuxOS 64 bit. I have three VMs that I frequently use - Win XP, PCLinuxos 32 bit and PCLinuxos 64 bit. It seems when running one (the PCLinuxos 32 bit) by itself, there is no problem with the system freezing. When a second VM is started (either the Win XP or the PCLinuxos 64 bit) the system will freeze - maybe not right away but eventually - either it seems when idle for a bit or from what I have observed accessing drives. I should note the the PCLos 32 bit and the Win XP are VMs that have been running for a couple of years with no problems. The PCLos 64 bit is relatively new. For a test, I did try running the Win XP alone and it did freeze the system when accessing either the CD ROM or a secondary hard drive in the system (separate tests). The last time I tried the PCLos 64 bit, I was updating options in Vuze when it froze the system. Prior to 5.1.4, there was no problem running the PCLos 32 bit and Win XP together but now starting the second VM will freeze the system.

Without going back to an earlier version, is there anything else that I should be looking at?

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[phild]

Logs for the three VMs have been uploaded

[Perryg]

It probably will be better if you can post a log after the next freeze, since these do not show a real issue. You should also check the syslog and dmesg of the host when this happens to see if you can find the cause.

[phild]

Okay - here is the logs for the two VMs that were running for the most recent freeze. The only thing I had running on the system was VB with the two VMs running when it froze.

[Perryg]

When this happens does it freeze the guest/s or host as well?

How do you recover from this?

Have you tried waiting a bit to see if the freeze is really a hang and you get control back?

What did your syslog and dmesg have to say about this after it happened?

[phild]

When the freeze happens, it is the entire system that locks up. The only way to recover is to turn the entire machine off and reboot. In the case for which the last logs were posted, it was a little over half an hour that the system was frozen before I noticed it (was working on another machine).

I looked in the syslog (posted for around the time of the freeze for all three - host, 32 bit VM, 64 bit WM) but don't see anything that would indicate what the problem might be. Looked in dmesg but as it does not appear to be timestamped didn't notice anything that might indicate a problem (but I wasn't really sure what to be looking for.

Code: Select all

Host syslog
Aug 31 14:42:57 localhost smartd[2620]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 113 to 114 
Aug 31 14:43:08 localhost klogd: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
Aug 31 14:43:08 localhost klogd: sd 6:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
Aug 31 14:43:08 localhost klogd: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
Aug 31 14:43:08 localhost klogd: sd 6:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Aug 31 14:43:08 localhost smartd[2620]: Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 99 to 104 
Aug 31 14:44:36 localhost smbd[8800]: [2016/08/31 14:44:36.848387,  0] lib/util_sock.c:474(read_fd_with_timeout) 
Aug 31 14:44:36 localhost smbd[8800]: [2016/08/31 14:44:36.848460,  0] lib/util_sock.c:1441(get_peer_addr_internal) 
Aug 31 14:44:36 localhost smbd[8800]:   getpeername failed. Error was Transport endpoint is not connected 
Aug 31 14:44:36 localhost smbd[8800]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. 
Aug 31 14:49:36 localhost smbd[9289]: [2016/08/31 14:49:36.857960,  0] lib/util_sock.c:474(read_fd_with_timeout) 
Aug 31 14:49:36 localhost smbd[9289]: [2016/08/31 14:49:36.858087,  0] lib/util_sock.c:1441(get_peer_addr_internal) 
Aug 31 14:49:36 localhost smbd[9289]:   getpeername failed. Error was Transport endpoint is not connected 
Aug 31 14:49:36 localhost smbd[9289]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. 
Aug 31 15:36:28 localhost syslogd 1.5.0: restart.

PCLos 32 Log
Aug 31 14:01:01 lpvml CROND[32543]: (root) CMD (nice -n 19 run-parts --report /etc/cron.hourly)
Aug 31 14:01:02 lpvml smbd[32554]: [2016/08/31 14:01:02.243664,  0] lib/util_sock.c:474(read_fd_with_timeout) 
Aug 31 14:01:02 lpvml smbd[32554]: [2016/08/31 14:01:02.267557,  0] lib/util_sock.c:1441(get_peer_addr_internal) 
Aug 31 14:01:02 lpvml smbd[32554]:   getpeername failed. Error was Transport endpoint is not connected 
Aug 31 14:01:02 lpvml smbd[32554]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. 
Aug 31 19:38:36 lpvml syslogd 1.5.0: restart.

PCLOS 64 Log
Aug 31 16:43:02 localhost syslogd 1.5.0: restart.
Aug 31 16:43:12 localhost anacron[3969]: Job `cron.daily' terminated
Aug 31 21:08:49 localhost syslogd 1.5.0: restart.

[Perryg]

Yes the above does show errors with samba and a network reset. I know samba was updated lately and had to actually put a work around in my samba client just to get it to work ( 100% on one core for an extended period of time but did recover ). I would search the PCLinuxos forum and or ask them about it. Depending on how they handle it this could start the issue. Other than that you will need to start a ticket at bugtracker . I don't have a PCLinux host to test this on and not really sure if the DEVs do either but it must be part of the equation as I don't have this issue on any debian based or RPM based host.

[phild]

Thanks Perry. I don't have samba configured in the two VMs - only NFS. Both Samba and NFS are running on the host however. Will check with the PCLinuxOS folks.

[JSA]

Don't discount a failing drive. Run some smartctl tests on your drive:

[sdc] tag#0 Sense Key : Hardware Error [current] [descriptor]

[mpack]

VirtualBox would normally log I/O errors or timeouts for a failing host drive. But, it does no harm to check.

[micksuley]

I also have this problem, after a few seconds the client freezes, then a few seconds later the whole system, host and client, the only thing that works is the mouse pointer, I can move that around the screen but nothing works, not even the clock. I have to power cycle the host to recover.
Host is Linux Mint 18, client is Linux Mint 18 (I have other clients and it happens with them as well)
VB Version 5.1.4 r110228 (Qt5.5.1)
I have uploaded the VB log and syslog, dmesg just says (Nothing has been logged yet.)

Let me know if there is anything else that I can provide to help solve this
Thanks
Mick