Multiple Serial Ports / Direct Boot/ pvSCSI など

◆Multiple Serial Ports

[Xen-changelog] [xen master] libxl: Allow multiple serial ports on HVM domain creation
http://lists.xen.org/archives/html/xen-changelog/2014-08/msg00102.html

This patch allows an HVM domain to be created with multiple serial ports.

[Xen-changelog] [xen master] xl: Accept a list for serial in config file
http://lists.xen.org/archives/html/xen-changelog/2014-08/msg00103.html

Allow the "serial" key to accept a list of serial ports, and pass them in using the new serial_list domain build element.

[Xen-changelog] [xen master] xl.cfg: add 'cmdline' in config file
http://lists.xen.org/archives/html/xen-changelog/2014-08/msg00105.html

Currently in xl.cfg, use 'root' and 'extra' to generate the command line.

◆Other
[Xen-changelog] [xen master] xen: pass kernel initrd to qemu
http://lists.xen.org/archives/html/xen-changelog/2014-08/msg00104.html

 Direct kernel boot allows booting directly from a kernel and initrd
 stored in the host physical machine OS, allowing command line arguments
 to be passed directly. PV guest direct kernel boot is supported. HVM
 guest direct kernel boot is supported with limitation (it's supported
 when using qemu-xen and default BIOS 'seabios'; not supported in case of
 stubdom-dm and old rombios.)

[Xen-changelog] [xen master] x86/hvm: treat non-instruction fetch nested page faults also as read violations
http://lists.xen.org/archives/html/xen-changelog/2014-08/msg00110.html

    As pointed out by Jan Beulich in
    http://lists.xen.org/archives/html/xen-devel/2014-08/msg01269.html:
    "Read-modify-write instructions absolutely need to be treated as read
    accesses, yet hardware doesn't guarantee to tell us so (they may
    surface as just write accesses)." This patch addresses the issue in
    both the VMX and the SVM side.
   
    VMX: Treat all write data access violations also as read violations (in
         addition to those that were already reported as read violations).
    SVM: Refine the meaning of read data access violations to distinguish
         between read/write and instruction fetch access violations.
   
    With this patch both VMX and SVM specific nested page fault handling code
reports violations the same way, thus abstracting the hardware specific
behaviour from the layers above.

[Xen-changelog] [xen master] update pvSCSI protocol description
http://lists.xen.org/archives/html/xen-changelog/2014-08/msg00113.html

    Update the protocol description of the pvSCSI framework used to pass through
    SCSI devices to a guest (pv or hvm).
   
    The main changes are:
    - added comments
    - add support for larger SG-lists by putting them in an own granted page
    - deprecate VSCSIIF_ACT_SCSI_SG_PRESET action with related structures
    - add ref_rqid for action VSCSIIF_ACT_SCSI_ABORT to be able to specify the
      request to abort
    - deprecate timeout_per_command as this really should be handled by the
      backend in case of default settings or by the guest domain by aborting a
      long running command
   
    This update is related to the rework of the pvSCSI backend and frontend drivers
    in the Linux kernel. This interface version is included in that rework, too.