)]}'
{
  "commit": "e93abc147fa628650bdbe7fd57f27462ca40a3c2",
  "tree": "2028a6a8813c5f5cd03eeb7922a057aee3acc6cc",
  "parents": [
    "b9fc20bccfcbac082e82896c54862c939d9cb4d2"
  ],
  "author": {
    "name": "Eduardo Habkost",
    "email": "ehabkost@redhat.com",
    "time": "Fri Oct 03 16:39:50 2014 -0300"
  },
  "committer": {
    "name": "Andreas Färber",
    "email": "afaerber@suse.de",
    "time": "Tue Nov 04 15:48:47 2014 +0100"
  },
  "message": "target-i386: Don\u0027t enable nested VMX by default\n\nTCG doesn\u0027t support VMX, and nested VMX is not enabled by default in the\nKVM kernel module.\n\nSo, there\u0027s no reason to have VMX enabled by default on the core2duo and\ncoreduo CPU models, today. Even the newer Intel CPU model definitions\ndon\u0027t have it enabled.\n\nIn this case, we need machine-type compat code, as people may be running\nthe older machine-types on hosts that had VMX nesting enabled.\n\nSigned-off-by: Eduardo Habkost \u003cehabkost@redhat.com\u003e\nSigned-off-by: Andreas Färber \u003cafaerber@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8d63553bc1f5d917005088cf6a0c792f619deadb",
      "old_mode": 33188,
      "old_path": "hw/i386/pc_piix.c",
      "new_id": "751f3e0265c026ab5f6c04a0a2a5d2bf101e41d5",
      "new_mode": 33188,
      "new_path": "hw/i386/pc_piix.c"
    },
    {
      "type": "modify",
      "old_id": "d2484746c37bf546c4aa1d466e0fcade4b47d830",
      "old_mode": 33188,
      "old_path": "hw/i386/pc_q35.c",
      "new_id": "c5ee250954659178122f3e588006787224436ff5",
      "new_mode": 33188,
      "new_path": "hw/i386/pc_q35.c"
    },
    {
      "type": "modify",
      "old_id": "0c41b929e6eec4df12df7d89b500a589172fc31b",
      "old_mode": 33188,
      "old_path": "target-i386/cpu.c",
      "new_id": "b73183207787df9afdff025cec48033b9bf641a3",
      "new_mode": 33188,
      "new_path": "target-i386/cpu.c"
    }
  ]
}