相比 VI3 的 Hardening Guide 具有如下亮点：

* 结构上更清晰明了 – 使用了标准的文档格式，在文档结构上，模板定义上以及参考文档引用方面都相比 VI3 的对应部分更正式。
* 推荐设置方面选择更多 – 这份文档将所有的操作指引划分为三个安全等级，而不是为所有的场景给出一个笼统的推荐。这样做的好处是管理员可以有更多的选择，更好的根据自身环境的需求做出更好的配置。

需要指出的是，这个 Hardening Guide 有超过 100 个操作指引，主要按照如下几个部分进行划分：

* Introduction
* Virtual Machines
* Host
* vNetwork
* vCenter
* Console OS (for ESX)

如何获得：http://communities.vmware.com/community/vmtn/general/security?view=documents

呃，这些功能还不够你兴奋的吗，看来 Red Hat 真是厚积薄发啊？看好 KVM 的前景，赶紧搭建 CentOS 玩玩吧。

不过，需要指出的是 Red Hat KVM 产品的系统生态目前还不成熟，其可用性仍然需要经过生产的检验。譬如对其兼容的第三方备份软件目前几乎没有，当然，时间会改变一切不成熟，包括我自己。

点击此处了解更多！

RED HAT ENTERPRISE VIRTUALIZATION FOR SERVERS: COMPETITIVE FEATURES

KVM 相关的一些术语：

* Memory page sharing and ballooning: Maximizes the number of virtual desktops that can be hosted on a single hypervisor, lowering infrastructure and management costs
* Multiple virtual CPUs: Virtual desktops can have up to four virtual CPUs, maximizing performance
* Rapid provisioning: Create new desktop environments in minutes, or grant permission to users to self-provision their own desktops
* Linked images: Provision new virtual desktops based on master images, saving up to 90 percent storage capacity
* Desktop pooling: Create groups of virtual desktops that can be accessed on-demand, simplifying the provisioning process and increasing flexibility
* Search-based management: Easily search for virtual desktops with specific applications and specific versions, enabling rapid identification of virtual desktops in need of upgrades or patches
* Auto suspend: Automatically suspend inactive virtual desktops, conserving resources
* Live migration: Move virtual desktops from one host to another without any end user interruption, facilitating maintenance, scheduled power savings, and load balancing
* Load balancing: Automatically load balance virtual desktops across available hosts to ensure optimal performance
* Snapshots: Capture the state of a virtual desktop at any given point in time, enabling rapid restoration of desktop environments in the case of an end point hardware failure
* Flexible storage: Store virtual desktop images and data using either iSCSI, FCP, or NFS
* USB redirection: Users can connect any USB 1.0 or 2.0 device to their virtual desktops
* WAN optimization: Compression algorithms ensure optimal performance, even across wide-area networks

The new Top25 as published by Eric siebert on vSphere-land:

1. Yellow Bricks – Duncan Epping – 158 #1 votes – total score of 4,191
2. Virtual Geek – Chad Sakac – 111 #1 votes – total score of 2,938
3. Scott Lowe’s Blog – Scott Lowe – 56 #1 votes – total score of 2,889
4. NTPro.nl – Eric Sloof - 22 #1 votes – total score of 2062
5. RTFM Education – Mike Laverick – 7 #1 votes – total score of 1,734
6. Virtualization Evangelist – Jason Boche – 13 #1 votes – total score of 1,482
7. VM/ETC – Rich Brambley – 5 #1 votes – total score of 1,138
8. Gabe’s Virtual World – Gabrie van Zanten – 8 #1 votes – total score of 1,096
9. Virtual Storage Guy – Vaughn Stewart – 58 #1 votes – total score of 990
10. Virtu-Al – Alan Renouf – 18 #1 votes – total score of 831
11. Virtualization Pro – Eric Siebert & Others – 3 #1 votes – total score of 774
12. vCritical – Eric Gray – 15 #1 votes – total score of 738
13. VMware Tips - Rick Scherer -  5 #1 votes – total score of 726
14. Frank Denneman – Frank Denneman – 22 #1 votes – total score of 697
15. The VM Guy – Dave Lawrence – 2 #1 votes – total score of 643
16. Planet VM – Tom Howarth – 4 #1 votes – total score of 633
17. The Slog – Simon Long – 8 #1 votes – total score of 614
18. VMGuru.nl – Various – 18 #1 votes – total score of 569
19. Mike D’s Virt. Blog – Mike DiPetrillo – 2 #1 votes – total score of 537
20. Hypervizor – Hany Michael – 8 #1 votes – total score of 453
21. Techhead – Simon Seagrave – 12 #1 votes – total score of 452
22. vReference – Forbes Guthrie – 11 #1 votes – total score of 443
23. Pivot Point – Scott Drummonds – 2 #1 votes – total score of 380
24. Technodrone – Maish Saidel-Keesing – 3 #1 votes – total score of 378
25. Chris Wolf – Chris Wolf – 0 #1 votes – total score of 375

如果解决这个问题呢？

[root@ntbesx49 ~]# vi /etc/inittab       # 编辑 /etc/inittab 这个文件
# Trap CTRL-ALT-DELETE
# ca::ctrlaltdel:/sbin/shutdown -t3 -r now     # 将这一行注释掉
[root@ntbesx49 ~]# init q   # 重新读取 /etc/inittab 文件，作用是不重启而立刻生效

The book list is:

• Mastering VMware vSphere 4 by Scott Lowe
• VMware vSphere 4 Administration Instant Reference by Scott Lowe, Jason W. McCarty, and Matthew K. Johnson
• VMware vSphere and Virtual Infrastructure Security: Securing the Virtual Environment by Edward L. Haletky
• VMware VI and vSphere SDK: Managing the VMware Infrastructure and vSphere by Steve Jin
• VMware vSphere 4: Install, Configure and Manage (Student Manual P1&2)
• vSphere 4.0 Quick Start Guide: Shortcuts down the path of Virtualization by Duncan Epping, Alan Renouf, Bernie Baker, and Thomas Bryant  (哪位好心人买这本书送给我吧！^_^)

BTW, another great book  must be mentioned that published in 2009 and related with VMware is VMware Cookbook.

Enjoy your reading!

Below are excerpts from the whitepaper of A VMware Administrator’s Guide to Hyper-V, written by Chris Chesley at Vkernel. You can download the document here: http://www.dabcc.com/downloadfile.aspx?id=863

#####
# Differences between VMware and Hyper-V
###################################

Over-committed resources

One of the big differences between VMware and Hyper-V is the ability to over commit memory. In VMware you can assign more memory to virtual machines than physically exists on the host or resource pool. The idea is that the virtual machines will not use all their assigned resources at the same time. Assigning more memory than is available can increase your guest density (more guests running on the same hardware. More VMs on the same physical hardware means a better return on what you paid for the hardware and virtualization software.

Hyper-V will not allow the administrator to over allocate memory. While this may limit your ability to achieve higher density, it also means you can always count on the provisioned memory to be available. There is still a lively debate going regarding memory over committing and if this is beneficial or problematic in a virtual environment.

You can over commit CPU in both VMware and in Hyper-V.

Resource counters

VMware has memory and CPU metrics that are not available in Hyper-V. Specifically these are CPU ready, memory ballooning and swapping. CPU ready is a measurement of how much time a virtual processor has to wait for a physical processor to run on. Memory ballooning and swapping are both needed by VMware since they allow memory over committing and need a way of taking memory from one guest and giving it to another. It is also needed to give more memory to guests than is available on the host.

DRS and TPS

Distributed Resource Scheduler (DRS) and TPS (Transparent Page Sharing) are only available in VMware. DRS will either move virtual machines from one host to another or will make recommendations that you move them based on resources that are used and available on the hosts. TPS is a method where VMware will recognize memory pages that are used by multiple systems and not load duplicate pages. Instead it will load the memory pages once and then provide pointers to all the guests using those pages. It can offer up to a 30% savings in memory utilization if an administrator pays attention to what OS and applications are running on particular hosts and groups them together.

HA

High Availability (HA) is a feature of VMware where they will restart guests on a different host if the system they are on goes down or loses contact with VCenter (VMware’s management interface). Microsoft Hyper-V servers can be configured to be part of a Microsoft failover cluster which offers the same functions as HA from VMware.