Search results

Jump to: navigation, search

Page title matches

  • Channel I/O is a high-performance input/output (I/O) architecture that is implemented (especially) on s390 (see [https://en.w ...s390 only sees paravirtualized virtio devices via the "Virtio Over Channel I/O (virtio-ccw)" transport. This makes virtio devices discoverable via
    10 KB (1,421 words) - 14:19, 12 December 2017

Page text matches

  • I'm not sure this is the right place to put this. If not, please mark it as i ...nd guest based on virtio-serial. One goal of this channel is to implement features like transparent copy/paste support between the host and guest. This proje
    14 KB (2,116 words) - 15:02, 16 February 2016
  • * Channel I/O is now available when running with TCG. Thus, the default machine for qe * I/O throttling now supports groups, so I/O limits can be shared among multiple drives (use -drive throttling.group=<
    13 KB (2,067 words) - 17:11, 2 December 2015
  • === Hardware features === | RAM || 1 GB LPDDR3 POP memory (2 channel 32 bits @ 800 MT/sec)
    2 KB (241 words) - 11:20, 27 May 2015
  • ...QAPI/GuestAgent Guest Agent]. Please check the guest [http://wiki.qemu.org/Features/QAPI/GuestAgent Guest Agent] page for design and implementation details. The two main guest agent features of interest to live snapshots are:
    21 KB (3,274 words) - 14:58, 11 October 2016
  • * [[Features/QED]] On mid-2010 I implemented a webcam emulation (passthrough) using USB Video Class on the g
    15 KB (2,288 words) - 15:07, 16 February 2016
  • * {{git|f63d074}} usb-storage: cancel I/O on reset ...s without a native code generator can use the TCG interpreter (TCI). See [[Features/TCI]] for more information.
    6 KB (908 words) - 20:51, 17 February 2012

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)