Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 29 7月, 2011 1 次提交
    • 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
  3. 24 7月, 2011 3 次提交
  5. 23 7月, 2011 1 次提交
  7. 05 7月, 2011 1 次提交
  9. 16 6月, 2011 3 次提交
  11. 14 6月, 2011 1 次提交
  13. 08 6月, 2011 1 次提交
  15. 06 6月, 2011 2 次提交
  17. 19 5月, 2011 1 次提交
  19. 08 5月, 2011 4 次提交
  21. 27 4月, 2011 1 次提交
  23. 26 4月, 2011 1 次提交
  25. 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
  27. 04 4月, 2011 3 次提交
  29. 29 3月, 2011 1 次提交
  31. 26 3月, 2011 1 次提交
  33. 25 3月, 2011 1 次提交
  35. 22 3月, 2011 6 次提交
  37. 21 3月, 2011 1 次提交
    • P
      change all rt_clock references to use millisecond resolution accessors · 7bd427d8
      由 Paolo Bonzini 提交于 
      This was done with:

    sed -i '/get_clock\>.*rt_clock/s/get_clock\>/get_clock_ms/' \
        $(git grep -l 'get_clock\>.*rt_clock' )
    sed -i '/new_timer\>.*rt_clock/s/new_timer\>/new_timer_ms/' \
        $(git grep -l 'new_timer\>.*rt_clock' )

after checking that get_clock and new_timer never occur twice
on the same line.  There were no missed occurrences; however, even
if there had been, they would have been caught by the compiler.
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      7bd427d8
  39. 16 3月, 2011 1 次提交
  41. 15 3月, 2011 1 次提交
  43. 07 3月, 2011 1 次提交
    • S
      simpletrace: Thread-safe tracing · 0b5538c3
      由 Stefan Hajnoczi 提交于 
      Trace events outside the global mutex cannot be used with the simple
trace backend since it is not thread-safe.  There is no check to prevent
them being enabled so people sometimes learn this the hard way.

This patch restructures the simple trace backend with a ring buffer
suitable for multiple concurrent writers.  A writeout thread empties the
trace buffer when threshold fill levels are reached.  Should the
writeout thread be unable to keep up with trace generation, records will
simply be dropped.

Each time events are dropped a special record is written to the trace
file indicating how many events were dropped.  The event ID is
0xfffffffffffffffe and its signature is dropped(uint32_t count).
Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      0b5538c3
  45. 14 2月, 2011 3 次提交