XS62ESP1014 - Bash Update

Hotfix XS62ESP1014 - For XenServer 6.2.0 Service Pack 1

https://support.citrix.com/article/CTX141486

bash-3.2-33.el5_11.4.i386.rpm

BashのUpdateのみ。

Restartは不要。

XenServer Shellshock と XSA-108

Citrix Security Advisory for GNU Bash Shellshock Vulnerabilities
http://support.citrix.com/article/CTX200217

XenServerは影響を継続調査中とのこと。


XSA-108
http://xenbits.xen.org/xsa/advisory-108.html
http://xenbits.xen.org/xsa/

公表をもったいつけてた？XSA-108の件、
XSA-100の延長って印象。HVMで運用してなきゃ、まぁ影響はなさそう。

Hotfix XS62ESP1011 - For XenServer 6.2.0 Service Pack 1

Hotfix XS62ESP1011 - For XenServer 6.2.0 Service Pack 1

http://support.citrix.com/article/CTX141472

私的にはこの辺かな。

The option Restore Virtual Machine Metadata in xsconsole fails to restore VDIs on the storage repositories (SRs). VDIs are restored if the SRs contain the backup of the pool metadata.

When Linux bridge is used as the network stack, generic receive offload (GRO) does not always work on VLANs.

なお、XS62ESP1002 / XS62ESP1004 / XS62ESP1008 が含まれる。

最近Blogの更新ができません。

だれかうちでXenServerの技術者しませんか？

XenServer6.2 パッチ当て XS62ESP1008まで

Recommended Updates for XenServer 6.x Hotfixes
http://support.citrix.com/article/CTX138115

XenServer6.2だと、

1. XenCenterを最新（XS62SP1のXenCenterを利用）にして、
2. SP1をあてて、
3. Reboot。
4. 起動後、XS62ESP1003、XS62ESP1008、XS62ESP1005の順であてて、
5. 必要ならば、XS62ESP1005のドライバを入れて、
6. Reboot。

という手順。

なぜ、XS62ESP1008をXS62ESP1005の前かというと、
XS62ESP1008のKernelが腐ってる問題を含んでいるから。

もし、XS62ESP1009をあてるなら、
XS62ESP1005の代わりにあてれば良さそう。
XS62ESP1009について書かれてないのはなぜだろう？
XS62ESP1008と同じように、Kernelに問題があったりして。
うちのは動いてるけど。XS62ESP1009のKernel。

XenServer6.2 SP1 のパッチリスト

http://mada0833.blogspot.jp/2014/04/XenServer62SP1PatchList.html

[Xen-users] Xen Security Advisory 107 - Mishandling of uninitialised FIFO-based event channel control blocks

[Xen-users] Xen Security Advisory 107 - Mishandling of uninitialised FIFO-based event channel control blocks
http://lists.xen.org/archives/html/xen-users/2014-09/msg00082.html

FIFOベースのイベントチャンネルで、ある条件下でチェックされない問題の修正。
Xen4.4以上が対象。

Xen メンテナンスリリース と FreeBSDのpty のMEMO

[Xen-announce] Xen Project Maintenance Releases Available (Versions4.4.1, 4.3.3, 4.2.5)
http://lists.xen.org/archives/html/xen-announce/2014-09/msg00000.html

I am pleased to announce the release of Xen 4.4.1, 4.3.3 and 4.2.5. We recommend that all users of the 4.4, 4.3 and 4.2 stable series update to the latest point release.

[Xen-changelog] [qemu-upstream-unstable] serial: poll the serial console with G_IO_HUP
http://lists.xen.org/archives/html/xen-changelog/2014-09/msg00003.html

On FreeBSD polling a master pty while the other end is not connected with G_IO_OUT only results in an endless wait. 

の修正

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.