FreeBSD 8.2 64 constant rebooting?!

Discussion in 'Other Virtual machines' started by juztin, Apr 11, 2011.

  1. juztin

    juztin Bit poster

    Messages:
    2
    Anyone ever run across an issue where FreeBSD constantly gets rebooted by Parallels?
    I've done fresh installs of FreeBSD 8.2 64 with 2G Ram 2 CPU on three different machines (MacPro 8core 3ghz, MacPro 4core 2.66 and a MBP 13" 2.66)

    With each of these I get the same issue on fresh installs of FreeBSD. After a couple of minutes Parallels restarts FreeBSD randomly, doesn't matter if I'm using it or not (Just letting it sit on it's own will cause it to do this as well).

    The only thing, glaring, I see in the Parallels log file for the VM is this:
    #############################################################
    04-11 17:11:19.998 F /vm:2110:a73f/ Terminating VCPU event loop (1)
    04-11 17:11:19.996 F /vm:2110:915f/ Terminating VCPU event loop (0)
    04-11 17:11:20.125 F /vm:2110:3a17/ Event loop terminated - deinited
    04-11 17:11:20.125 F /vm:2110:3a17/ Setting ASYNC_REQ_SHUTDOWN for Vm
    04-11 17:11:20.125 F /vm:2110:3a17/ Terminating CPU #1 ...
    04-11 17:11:20.125 F /vm:2110:3a17/ Terminating CPU #0 ...
    SystemReset by keyboard controller

    04-11 17:11:20.127 F /vm:2110:3a17/ [Devices] Terminating...
    04-11 17:11:20.127 F /vm:2110:3a17/ [Profile] Storage filter TG req handler termination time is 0 msecs
    04-11 17:11:20.127 F /vm:2110:3a17/ [Profile] PS/2 keyboard termination time is 0 msecs
    04-11 17:11:20.127 F /vm:2110:3a17/ [Profile] USB keyboard termination time is 0 msecs
    04-11 17:11:20.127 F /vm:2110:3a17/ [Profile] PS/2 mouse termination time is 0 msecs
    04-11 17:11:20.127 F /vm:2110:3a17/ [Profile] USB mouse termination time is 0 msecs
    04-11 17:11:20.127 F /vm:2110:3a17/ [Profile] Networking termination time is 0 msecs
    04-11 17:11:23.840 F /vm:2110:3a17/ [Profile] SCSI adapter termination time is 0 msecs
    04-11 17:11:23.840 F /LocalDevices:2110:3a17/ [Floppy0] Terminating
    04-11 17:11:23.840 F /LocalDevices:2110:3a17/ [Floppy0] Disconnecting
    04-11 17:11:23.841 F /vm:2110:3a17/ [Profile] FDD 0 termination time is 1 msecs
    04-11 17:11:23.841 F /vm:2110:3a17/ [Profile] FDD 1 termination time is 0 msecs
    04-11 17:11:23.841 F /LocalDevices:2110:3a17/ [Parallel0] Terminating
    04-11 17:11:23.841 F /LocalDevices:2110:3a17/ [Parallel0] Disconnecting
    04-11 17:11:23.841 F /vm:2110:3a17/ [Profile] Parallels port 0 termination time is 0 msecs
    04-11 17:11:23.841 F /vm:2110:3a17/ [Profile] Sound output termination time is 0 msecs
    04-11 17:11:23.841 F /vm:2110:3a17/ [Profile] Sound input termination time is 0 msecs
    04-11 17:11:23.842 F /vm:2110:3a17/ [Profile] USB controller termination time is 1 msecs
    04-11 17:11:23.842 F /vm:2110:3a17/ [Profile] Power source termination time is 0 msecs
    04-11 17:11:23.843 F /vm:2110:3a17/ [Profile] Tools dispatcher termination time is 1 msecs
    04-11 17:11:23.843 F /vm:2110:3a17/ [Profile] Balooning termination time is 0 msecs
    04-11 17:11:23.843 F /vm:2110:3a17/ [Profile] PCI toolgate termination time is 0 msecs
    04-11 17:11:23.846 F /vm:2110:3a17/ [Profile] PCI video termination time is 3 msecs
    04-11 17:11:23.846 F /vm:2110:3a17/ [Profile] OTG dispatcher 3 termination time is 0 msecs
    04-11 17:11:23.846 F /vm:2110:3a17/ [Profile] OTG request tracker termination time is 0 msecs
    04-11 17:11:24.005 F /vm:2110:3a17/ [Profile] Device used thread termination time is 159 msecs
    04-11 17:11:24.005 F /vm:2110:3a17/ [Devices] Terminating finished
    04-11 17:11:24.005 F /vm:2110:3a17/ [Profile] Terminating time is 3878 msecs
    #############################################################

    It looks as though it's being caused by my keyboard?? ('SystemReset by keyboard controller')
    I've also used three different keyboards??
     
  2. mmika

    mmika Pro

    Messages:
    488
    "SystemReset by keyboard controller" means that reboot was initiated by guest FreeBSD.
    What FreeBSD wrote in kernel logs? What a reason of reboot?
    Please provide a problem report id number here.
     

Share This Page