1. 20 11月, 2013 4 次提交
  2. 19 11月, 2013 6 次提交
  3. 18 11月, 2013 4 次提交
  4. 15 11月, 2013 4 次提交
  5. 14 11月, 2013 5 次提交
  6. 13 11月, 2013 3 次提交
  7. 12 11月, 2013 1 次提交
  8. 13 11月, 2013 3 次提交
  9. 12 11月, 2013 9 次提交
  10. 11 11月, 2013 1 次提交
    • R
      virttest.qemu_vm: Log information about the parent PID and the monitor name. · 03d30d9b
      Ruda Moura 提交于
      When starting the qemu process, there is not much information about
      the running parent PID (the autotest shell script that starts qemu) or
      the monitor name that we are trying to connect (for example, hmp1).
      
      So with this commit we're logging this information when qemu is started,
      in order to provide information for debugging. Example:
      
      When running  ./run -t qemu --tests=uptime --qemu_sandbox=on
      
      From debug.log:
      
      11:43:17 INFO | Created qemu process with parent PID 15592
      11:43:17 INFO | Connecting to monitor 'hmp1'
      11:44:17 WARNI| Could not find (qemu) prompt after connecting to monitor. Output so far: ''
      11:44:18 ERROR| Could not connect to monitor 'hmp1'
      11:44:18 DEBUG| Destroying VM virt-tests-vm1 (PID 15594)
      
      Parent PID is 15592, now we are trying to find what is wrong...
      
      ps -ef | grep 15592
      rmoura   15592 15591  0 11:43 pts/3    00:00:00 /bin/bash -c source /tmp/autotestbMRLRL.sh
      rmoura   15594 15592  0 11:43 pts/3    00:00:00 [qemu-system-x86] <defunct>
      
      In this situation, it's clear that qemu-system-x86_64 goes bad.
      Signed-off-by: NRuda Moura <rmoura@redhat.com>
      03d30d9b