Opened 12 years ago
Closed 10 years ago
#11398 closed defect (obsolete)
Guest restarts unexpectedly with a "Reset initiated by keyboard controller" message in the log file.
Reported by: | Jean-Christophe Guillain | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.2.6 |
Keywords: | reset keyboard controller | Cc: | |
Guest type: | BSD | Host type: | Linux |
Description
Sometimes, when its load and I/O are high, the FreeBSD guest reboots. The only message associated wit this restart is in the VBox.log file :
39:16:41.172608 Reset initiated by keyboard controller 39:16:41.244607 Changing the VM state from 'RUNNING' to 'RESETTING'.
Host :
- OS : Debian "Squeeze" 6.0.6 amd64
- VB : virtualbox-4.2 - 4.2.6-82870~Debian~squeeze
Guest :
- FreeBSD 8.3-RELEASE-p3 amd64
Attached :
- VBox.log
- vurdbckp1.vbox (the guest conf file)
Attachments (3)
Change History (13)
by , 12 years ago
by , 12 years ago
Attachment: | vurdbckp1.vbox added |
---|
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Actually, the FreeBSD guest uses a 24.5TB ZFS file system that requires at least 24 GB of RAM to run smoothly... (We use it as a backup server.)
comment:3 by , 12 years ago
I am getting the same error, "Reset initiated by keyboard controller". Host is Ubuntu 11.04 64 bit, guest Windows XP Professional 32 bit. Guest is running with two cores enabled. Virtualbox is 4.2.8, though 4.2.6 had the same problem.
Guest is crashing quite regularly, seemingly on a high network I/O between host and guest and disk I/O on host.
It seems guest is running stable when only one CPU is enabled.
comment:4 by , 12 years ago
But "reset initiated by keyboard controller" normally means that the guest OS triggered the reboot. mvorlov, I would like to see a VBox.log file for such a VM session.
by , 12 years ago
Attachment: | VBox.log.1 added |
---|
comment:5 by , 12 years ago
Here it is. Crashes were rather frequent when running guest with SATA controller (would crash within an hour or two). Turning on/off host I/O cache seem to make no difference. I tried switching back to IDE. It looks like guest is running longer (about 12 hours) before it crashes.
comment:6 by , 12 years ago
Could the guest reboot just a BSOD which triggered an auto-reboot? Did you disable automatic reboot? See here.
comment:7 by , 12 years ago
Frank, With auto reboot disabled VM froze completely (twice) and host is reporting a 100% CPU usage by VM. Does it help?
comment:9 by , 12 years ago
No BSOD.I tried changing the networking interface from Bridged to NAT with port forwarding - same result. Switching to a different network adapters and disabling Windows Firewall / ICS didn't work either. Each time I got a frozen VM windows with CPU running at 100%.
comment:10 by , 10 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Does this also happen if you decrease the guest RAM to 8GB (if that's possible with your setup)?