1. 23 2月, 2016 4 次提交
  2. 11 2月, 2016 1 次提交
    • P
      w32: include winsock2.h before windows.h · 1834ed3a
      Paolo Bonzini 提交于
      Recent Fedora complains while compiling ui/sdl.c:
      
          /usr/x86_64-w64-mingw32/sys-root/mingw/include/winsock2.h:15:2: warning: #warning Please include winsock2.h before windows.h [-Wcpp]
      
      And with this patch we dutifully obey.
      
      Stefan Weil:
      
      Without that patch, windows.h will include winsock.h
      (which conflicts with winsock2.h) when compiling sdl.c.
      
      Normally we define WIN32_LEAN_AND_MEAN, and
      windows.h won't include winsock.h.
      
      include/ui/sdl2.h and ui/sdl.c undefine that macro,
      so the order of the include files is important.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Reviewed-by: NStefan Weil <sw@weilnetz.de>
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      1834ed3a
  3. 03 2月, 2016 3 次提交
  4. 02 2月, 2016 1 次提交
  5. 27 1月, 2016 1 次提交
  6. 16 1月, 2016 2 次提交
    • D
      qemu-char: add logfile facility to all chardev backends · d0d7708b
      Daniel P. Berrange 提交于
      Typically a UNIX guest OS will log boot messages to a serial
      port in addition to any graphical console. An admin user
      may also wish to use the serial port for an interactive
      console. A virtualization management system may wish to
      collect system boot messages by logging the serial port,
      but also wish to allow admins interactive access.
      
      Currently providing such a feature forces the mgmt app
      to either provide 2 separate serial ports, one for
      logging boot messages and one for interactive console
      login, or to proxy all output via a separate service
      that can multiplex the two needs onto one serial port.
      While both are valid approaches, they each have their
      own downsides. The former causes confusion and extra
      setup work for VM admins creating disk images. The latter
      places an extra burden to re-implement much of the QEMU
      chardev backends logic in libvirt or even higher level
      mgmt apps and adds extra hops in the data transfer path.
      
      A simpler approach that is satisfactory for many use
      cases is to allow the QEMU chardev backends to have a
      "logfile" property associated with them.
      
       $QEMU -chardev socket,host=localhost,port=9000,\
                      server=on,nowait,id-charserial0,\
      		logfile=/var/log/libvirt/qemu/test-serial0.log
             -device isa-serial,chardev=charserial0,id=serial0
      
      This patch introduces a 'ChardevCommon' struct which
      is setup as a base for all the ChardevBackend types.
      Ideally this would be registered directly as a base
      against ChardevBackend, rather than each type, but
      the QAPI generator doesn't allow that since the
      ChardevBackend is a non-discriminated union. The
      ChardevCommon struct provides the optional 'logfile'
      parameter, as well as 'logappend' which controls
      whether QEMU truncates or appends (default truncate).
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
      [Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      d0d7708b
    • P
      nbd-server: do not exit on failed memory allocation · f1c17521
      Paolo Bonzini 提交于
      The amount of memory allocated in nbd_co_receive_request is driven by the
      NBD client (possibly a virtual machine).  Parallel I/O can cause the
      server to allocate a large amount of memory; check for failures and
      return ENOMEM in that case.
      
      Cc: qemu-block@nongnu.org
      Reviewed-by: NMax Reitz <mreitz@redhat.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      f1c17521
  7. 15 1月, 2016 2 次提交
  8. 22 12月, 2015 1 次提交
  9. 18 12月, 2015 2 次提交
  10. 17 12月, 2015 1 次提交
  11. 30 11月, 2015 1 次提交
  12. 18 11月, 2015 1 次提交
  13. 13 11月, 2015 1 次提交
  14. 12 11月, 2015 1 次提交
  15. 11 11月, 2015 4 次提交
  16. 10 11月, 2015 11 次提交
  17. 06 11月, 2015 3 次提交