1. 02 9月, 2011 3 次提交
  2. 01 9月, 2011 4 次提交
  3. 23 8月, 2011 2 次提交
  4. 22 8月, 2011 2 次提交
  5. 21 8月, 2011 3 次提交
  6. 05 8月, 2011 1 次提交
  7. 29 7月, 2011 2 次提交
    • J
      Allow to leave type on default in -machine · 2645c6dc
      Jan Kiszka 提交于
      This allows to specify -machine options without setting an explicit
      machine type. We will pick the default machine in this case. Requesting
      the list of available machines is still possible via '-machine ?' e.g.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      2645c6dc
    • W
      showing a splash picture when start · 3d3b8303
      wayne 提交于
          Added options to let qemu transfer two configuration files to bios:
      "bootsplash.bmp" and "etc/boot-menu-wait", which could be specified by command
          -boot splash=P,splash-time=T
      P is jpg/bmp file name or an absolute path, T have a max value of 0xffff, unit
      is ms. With these two options, if user invoke qemu with menu=on option, then
      a splash picture would be showed in a given time. For example:
          qemu -boot menu=on,splash=/root/boot.bmp,splash-time=5000
      would make boot.bmp shown as a brand with 5 seconds in the booting up process.
      This feature need the new seabios's support, which could be got from git.
      Signed-off-by: NWayne Xia <xiawenc@linux.vnet.ibm.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      3d3b8303
  8. 26 7月, 2011 1 次提交
  9. 24 7月, 2011 3 次提交
  10. 23 7月, 2011 1 次提交
  11. 05 7月, 2011 1 次提交
  12. 16 6月, 2011 3 次提交
  13. 14 6月, 2011 1 次提交
  14. 08 6月, 2011 1 次提交
  15. 06 6月, 2011 2 次提交
  16. 19 5月, 2011 1 次提交
  17. 08 5月, 2011 4 次提交
  18. 27 4月, 2011 1 次提交
  19. 26 4月, 2011 1 次提交
  20. 07 4月, 2011 1 次提交
    • M
      exit if -drive specified is invalid instead of ignoring the "wrong" -drive · e2982c3a
      Michael Tokarev 提交于
      This fixes the problem when qemu continues even if -drive specification
      is somehow invalid, resulting in a mess.  Applicable for both current
      master and for stable-0.14 (and the same issue exist 0.13 and 0.12 too).
      
      The prob can actually be seriuos: when you start guest with two drives
      and make an error in the specification of one of them, and the guest
      has something like a raid array on the two drives, guest may start failing
      that array or kick "missing" drives which may result in a mess - this is
      what actually happened to me, I did't want a resync at all, and a resync
      resulted in re-writing (and allocating) a 4TB virtual drive I used for
      testing, which in turn resulted in my filesystem filling up and whole
      thing failing badly.  Yes it was just testing VM, I experimented with
      larger raid arrays, but the end result was quite, well, unexpected.
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      Acked-by: NJes Sorensen <Jes.Sorensen@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      e2982c3a
  21. 04 4月, 2011 2 次提交