1. 24 9月, 2015 1 次提交
  2. 19 9月, 2015 2 次提交
  3. 09 9月, 2015 2 次提交
  4. 07 9月, 2015 3 次提交
  5. 13 8月, 2015 4 次提交
  6. 26 6月, 2015 1 次提交
    • P
      hw/arm/virt: Make block devices default to virtio · 4e2c0b2a
      Peter Maydell 提交于
      Now we have virtio-pci, we can make the virt board's default block
      device type be IF_VIRTIO. This allows users to use simplified
      command lines that don't have to explicitly create virtio-pci-blk
      devices; the -hda &c very short options now also work.
      
      This means we also need to set no_cdrom to avoid getting a
      default cdrom device -- this is needed because the virtio-blk
      device will fail if it is connected to a block backend with
      no media, which is what the default cdrom device typically is.
      Providing a cdrom with media via -cdrom will succeed, but silently
      create a device with non-removable medium. this is probably
      not really what the user wants, but is the best we can do now.
      
      Note that this change means that some command lines which used
      to work (by accident) will stop working. Where a drive was connected
      manually to a device but without 'if=none' being specified, we
      used to treat this as an IDE drive, which we would then not autoplug
      because the board doesn't support IDE. Now we will treat it as a
      virtio disk and autoplug it, which means the attempt to use the
      drive manually will fail:
        qemu-system-arm: -drive file=img.qcow2,id=foo: Drive 'foo' is already
        in use because it has been automatically connected to another device
        (did you need 'if=none' in the drive options?)
      The command line will have to be changed to include 'if=none', as the
      error message suggests.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: NStefan Hajnoczi <stefanha@redhat.com>
      Message-id: 1435068107-12594-4-git-send-email-peter.maydell@linaro.org
      4e2c0b2a
  7. 19 6月, 2015 1 次提交
  8. 16 6月, 2015 2 次提交
  9. 05 6月, 2015 1 次提交
  10. 02 6月, 2015 5 次提交
  11. 29 5月, 2015 4 次提交
  12. 12 5月, 2015 1 次提交
  13. 09 4月, 2015 1 次提交
  14. 02 4月, 2015 2 次提交
  15. 19 3月, 2015 2 次提交
  16. 11 3月, 2015 1 次提交
    • A
      hw/arm/virt: fix cmdline parsing bug with CPU options and smp > 1 · 886bc7a0
      Ard Biesheuvel 提交于
      The recently introduced feature that allows 32 bit guests to be
      executed under KVM on a 64-bit host incorrectly handles the case
      where more than 1 cpu is specified using '-smp N'
      
      For instance, this invocation of qemu
      
        qemu-system-aarch64 -M virt -cpu cortex-a57,aarch64=off -smp 2
      
      produces the following error
      
        qemu-system-aarch64: Expected key=value format, found aarch64
      
      which is caused by the destructive parsing performed by
      cpu_common_parse_features(), resulting in subsequent attempts
      to parse the CPU option string (for each additional CPU) to fail.
      
      So duplicate the string before parsing it, and free it directly
      afterwards.
      Signed-off-by: NArd Biesheuvel <ard.biesheuvel@linaro.org>
      Reviewed-by: NGreg Bellows <greg.bellows@linaro.org>
      Message-id: 1425402380-10488-1-git-send-email-ard.biesheuvel@linaro.org
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      886bc7a0
  17. 10 3月, 2015 1 次提交
    • M
      hw: Propagate errors through qdev_prop_set_drive() · 9b3d111a
      Markus Armbruster 提交于
      Three kinds of callers:
      
      1. On failure, report the error and abort
      
         Passing &error_abort does the job.  No functional change.
      
      2. On failure, report the error and exit()
      
         This is qdev_prop_set_drive_nofail().  Error reporting moves from
         qdev_prop_set_drive() to its caller.  Because hiding away the error
         in the monitor right before exit() isn't helpful, replace
         qerror_report_err() by error_report_err().  Shouldn't make a
         difference, because qdev_prop_set_drive_nofail() should never be
         used in QMP context.
      
      3. On failure, report the error and recover
      
         This is usb_msd_init() and scsi_bus_legacy_add_drive().  Error
         reporting and freeing the error object moves from
         qdev_prop_set_drive() to its callers.
      
         Because usb_msd_init() can't run in QMP context, replace
         qerror_report_err() by error_report_err() there.
      
         No functional change.
      
         scsi_bus_legacy_add_drive() calling qerror_report_err() is of
         course inappropriate, but this commit merely makes it more obvious.
         The next one will clean it up.
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: NPeter Crosthwaite <peter.crosthwaite@xilinx.com>
      Message-Id: <1425925048-15482-3-git-send-email-armbru@redhat.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      9b3d111a
  18. 13 2月, 2015 2 次提交
  19. 05 2月, 2015 1 次提交
  20. 23 12月, 2014 3 次提交