The cgc-release-documentation from cybergrandchallenge

cgc-release-documentation's People

Stargazers

Watchers

cgc-release-documentation's Issues

Immediate kernel panic on boot under VirtualBox

This occurred on the stock Ubuntu 14.04 x64 release of VirtualBox, when explicitly launching the cgc-linux-dev.box from VirtualBox. No changes were made to the VM, though I tried fiddling whether it thinks it's x86 vs x64, and twiddling virtualization. Host platform is HP z640 / dual E5-2680 / 64GB RAM running Ubuntu 14.04 x64.

$ dpkg -l | grep virtualbox
ii  unity-scope-virtualbox                                      0.1+13.10.20130723-0ubuntu1                         all          VirtualBox scope for Unity
ii  virtualbox                                                  4.3.10-dfsg-1ubuntu5                                amd64        x86 virtualization solution - base binaries
ii  virtualbox-dkms                                             4.3.10-dfsg-1ubuntu5                                all          x86 virtualization solution - kernel module sources for dkms
ii  virtualbox-qt                                               4.3.10-dfsg-1ubuntu5                                amd64        x86 virtualization solution - Qt based user interface
$ md5sum cgc-linux-dev.box
c18a61e772e4be5916d8b96de52fd3f0  cgc-linux-dev.box
$ tar xz < cgc-linux-dev.box
$ VBoxManage import box.ovf
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/user/Downloads/box.ovf...
OK.
Disks:  vmdisk1 10989076480     -1      http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized       cgc-linux-packer-disk1.vmdk    -1      -1
Virtual system 0:
 0: Suggested OS type: "Debian"
    (change with "--vsys 0 --ostype <type>"; use "list ostypes" to list all possible values)
 1: Suggested VM name "cgc-linux-packer_1"
    (change with "--vsys 0 --vmname <name>")
 2: Number of CPUs: 1
    (change with "--vsys 0 --cpus <n>")
 3: Guest memory: 1024 MB
    (change with "--vsys 0 --memory <MB>")
 4: Network adapter: orig NAT, config 3, extra slot=0;type=NAT
 5: IDE controller, type PIIX4
    (disable with "--vsys 0 --unit 5 --ignore")
 6: IDE controller, type PIIX4
    (disable with "--vsys 0 --unit 6 --ignore")
 7: Hard disk image: source image=cgc-linux-packer-disk1.vmdk, target path=/home/user/VirtualBox VMs/cgc-linux-packer_1/cgc-linux-packer-disk1.vmdk, controller=5;channel=0
    (change target path with "--vsys 0 --unit 7 --disk path";
    disable with "--vsys 0 --unit 7 --ignore")
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Successfully imported the appliance.

The "--debug" is wrong.

"Similarly, GDB can attach to processes launched via the cb-server as long as '--debug' is added to the command line as to disable the internal ptracing of CBs. " It should be the "--no_attach" option.