1. 18 12月, 2018 1 次提交
  2. 31 5月, 2018 2 次提交
    • I
      qapi: introduce new cmd option "allow-preconfig" · d6fe3d02
      Igor Mammedov 提交于
      New option will be used to allow commands, which are prepared/need
      to run, during preconfig state. Other commands that should be able
      to run in preconfig state, should be amended to not expect machine
      in initialized state or deal with it.
      
      For compatibility reasons, commands that don't use new flag
      'allow-preconfig' explicitly are not permitted to run in
      preconfig state but allowed in all other states like they used
      to be.
      
      Within this patch allow following commands in preconfig state:
         qmp_capabilities
         query-qmp-schema
         query-commands
         query-command-line-options
         query-status
         exit-preconfig
      to allow qmp connection, basic introspection and moving to the next
      state.
      
      PS:
      set-numa-node and query-hotpluggable-cpus will be enabled later in
      a separate patches.
      Signed-off-by: NIgor Mammedov <imammedo@redhat.com>
      Message-Id: <1526057503-39287-1-git-send-email-imammedo@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      [ehabkost: Changed "since 2.13" to "since 3.0"]
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      d6fe3d02
    • I
      qapi: introduce preconfig runstate · 8a36283e
      Igor Mammedov 提交于
      New preconfig runstate will be used in follow up patches
      related to introducing --preconfig CLI option and is
      intended to replace prelaunch runstate from QEMU start
      up to machine_init callback.
      Signed-off-by: NIgor Mammedov <imammedo@redhat.com>
      Message-Id: <1525423069-61903-4-git-send-email-imammedo@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      [ehabkost: Changed "since 2.13" to "since 3.0"]
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      8a36283e
  3. 03 3月, 2018 1 次提交
  4. 26 2月, 2018 1 次提交
    • C
      s390x/cpu: expose the guest crash information · 4ada99ad
      Christian Borntraeger 提交于
      This patch is the s390 implementation of guest crash information,
      similar to commit d187e08d ("i386/cpu: add crash-information QOM
      property") and the related commits. We will detect several crash
      reasons, with the "disabled wait" being the most important one, since
      this is used by all s390 guests as a "panic like" notification.
      
      Demonstrate these ways with examples as follows.
      
        1. crash-information QOM property;
      
        Run qemu with -qmp unix:qmp-sock,server, then use utility "qmp-shell"
        to execute "qom-get" command, and might get the result like,
      
        (QEMU) (QEMU) qom-get path=/machine/unattached/device[0] \
            property=crash-information
        {"return": {"core": 0, "reason": "disabled-wait", "psw-mask": 562956395872256, \
            "type": "s390", "psw-addr": 1102832}}
      
        2. GUEST_PANICKED event reporting;
      
        Run qemu with a socket option, and telnet or nc to that,
        -chardev socket,id=qmp,port=4444,host=localhost,server \
        -mon chardev=qmp,mode=control,pretty=on \
        Negotiating the mode by { "execute": "qmp_capabilities" }, and the crash
        information will be reported on a guest crash event like,
      
        {
          "timestamp": {
              "seconds": 1518004739,
              "microseconds": 552563
          },
          "event": "GUEST_PANICKED",
          "data": {
              "action": "pause",
              "info": {
                  "core": 0,
                  "psw-addr": 1102832,
                  "reason": "disabled-wait",
                  "psw-mask": 562956395872256,
                  "type": "s390"
              }
          }
        }
      
        3. log;
      
        Run qemu with the parameters: -D <logfile> -d guest_errors, to
        specify the logfile and log item. The results might be,
      
        Guest crashed on cpu 0: disabled-wait
        PSW: 0x0002000180000000 0x000000000010d3f0
      Co-authored-by: NJing Liu <liujbjl@linux.vnet.ibm.com>
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      Message-Id: <20180209122543.25755-1-borntraeger@de.ibm.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      [CH: tweaked qapi comment]
      Signed-off-by: NCornelia Huck <cohuck@redhat.com>
      4ada99ad
  5. 02 10月, 2017 1 次提交
  6. 04 9月, 2017 1 次提交