rrolsbe

## console-ramoops.txt
chronos@localhost ~/Downloads $ sudo cat /dev/pstore/console-ramoops
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.8.11 (chrome-bot@build41-m2) (gcc version 4.9.x-google 20140827 (prerelease) (4.9.1_cos_gg_2f9796c_4.9.1-r82) ) #1 SMP Sat Mar 7 08:36:36 PST 2015
[    0.000000] Command line: cros_secure  console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-1 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="2 vboot none ro 1,0 2545920 bootcache PARTUUID=fd8e87f0-de89-904f-8933-34ff423100f1/PARTNROFF=1 2545920 835feb6f6e55491f1919470cb18d7ef3c2add4b5 512 20000 100000, vroot none ro 1,0 2506752 verity payload=254:0 hashtree=254:0 hashstart=2506752 alg=sha1 root_hexdigest=448c2ae84ac9ce345f4832ce391b92668c3ec9ea salt=539f73e0613e47f581d2c68b6c2beb417f9374af5677ad9947abeaf842b2bfd3" noinitrd vt.global_cursor_default=0 kern_guid=fd8e87f0-de89-904f-8933-34ff423100f1 add_efi_memmap boot=local noresume noswap i915.modeset=1 t

## gist:195a2551ffdef7540776
Dennis

If a another script were created to reverse what enable-vmx.sh changed (maybe called unenable-vmx.sh) would a Chromebook boot into Verified mode again?.  Seems if the saved kernel bits were restored (bit-for-bit) so that the hash/digital sign matched Googles, it might boot verified mode (unless something else permanently flags the kernel modifications)?  From what I have read, booting "Verified Mode" while in Developer mode gives a little more security.  Assuming any of the above would work, we could execute the enable-vmx only when we need run a 64Bit VirtualBox VM then execute unenable-vmx.sh reestablish verified boot.

BTW, Thanks for making your enable-vmx.sh script available!!
Regards, Ron
	chronos@localhost ~/Downloads $ sudo cat /dev/pstore/console-ramoops
	[ 0.000000] Initializing cgroup subsys cpu
	[ 0.000000] Linux version 3.8.11 (chrome-bot@build41-m2) (gcc version 4.9.x-google 20140827 (prerelease) (4.9.1_cos_gg_2f9796c_4.9.1-r82) ) #1 SMP Sat Mar 7 08:36:36 PST 2015
	[ 0.000000] Command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-1 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="2 vboot none ro 1,0 2545920 bootcache PARTUUID=fd8e87f0-de89-904f-8933-34ff423100f1/PARTNROFF=1 2545920 835feb6f6e55491f1919470cb18d7ef3c2add4b5 512 20000 100000, vroot none ro 1,0 2506752 verity payload=254:0 hashtree=254:0 hashstart=2506752 alg=sha1 root_hexdigest=448c2ae84ac9ce345f4832ce391b92668c3ec9ea salt=539f73e0613e47f581d2c68b6c2beb417f9374af5677ad9947abeaf842b2bfd3" noinitrd vt.global_cursor_default=0 kern_guid=fd8e87f0-de89-904f-8933-34ff423100f1 add_efi_memmap boot=local noresume noswap i915.modeset=1 t
	Dennis

	If a another script were created to reverse what enable-vmx.sh changed (maybe called unenable-vmx.sh) would a Chromebook boot into Verified mode again?. Seems if the saved kernel bits were restored (bit-for-bit) so that the hash/digital sign matched Googles, it might boot verified mode (unless something else permanently flags the kernel modifications)? From what I have read, booting "Verified Mode" while in Developer mode gives a little more security. Assuming any of the above would work, we could execute the enable-vmx only when we need run a 64Bit VirtualBox VM then execute unenable-vmx.sh reestablish verified boot.

	BTW, Thanks for making your enable-vmx.sh script available!!
	Regards, Ron